technomonkey

I am having the same problem and have done the 'forensic' method;

At the end I still received the error however I do have a large log file
that will hopefully tell us what is going on.

How do you want the log file?

Thanks
Michael

technomonkey

Hi,

I have exactly the same problem - I have .NET Framework SP 1 installed, the
'empirical' method did not work for me and I will try the forensic method and
post the results when I have finished.

Michael

Andrew McLaren

"technomonkey" <technomonkey@discussions.microsoft.com> wrote...
> At the end I still received the error however I do have a large log file
> that will hopefully tell us what is going on.
> How do you want the log file?


Hi Michael,

Well personally, I don't want the log file at all :-) What I was suggesting
for the OP was that he create a log file and then examine it *himself*.

What you'll be looking for are indications of what Visual Studio Installer
was doing at the time it stopped. So you'll see error messages like "access
denied", "file not found", etc. Some of the errors may be in the form of
Winerror codes such as 0x00000005, or HRESULTs such as 0x80070005, for
"Access denied". Your corrective actions will depend on what errors you
find.

If you want to compile programs with Visual Studio, you will need to get
pretty good at understanding inscrutable errors in masses of compile and
link messages. So this is a good head start.

The log file is a plain text file so you can open it using Notepad or your
favourite text editor.

Hope it helps,
--
Andrew McLaren
amclar (at) optusnet dot com dot au

technomonkey

I am having the same problem and have done the 'forensic' method;

At the end I still received the error however I do have a large log file
that will hopefully tell us what is going on.

How do you want the log file?

Thanks
Michael

Andrew McLaren

"technomonkey" <technomonkey@discussions.microsoft.com> wrote...
> At the end I still received the error however I do have a large log file
> that will hopefully tell us what is going on.
> How do you want the log file?


Hi Michael,

Well personally, I don't want the log file at all :-) What I was suggesting
for the OP was that he create a log file and then examine it *himself*.

What you'll be looking for are indications of what Visual Studio Installer
was doing at the time it stopped. So you'll see error messages like "access
denied", "file not found", etc. Some of the errors may be in the form of
Winerror codes such as 0x00000005, or HRESULTs such as 0x80070005, for
"Access denied". Your corrective actions will depend on what errors you
find.

If you want to compile programs with Visual Studio, you will need to get
pretty good at understanding inscrutable errors in masses of compile and
link messages. So this is a good head start.

The log file is a plain text file so you can open it using Notepad or your
favourite text editor.

Hope it helps,
--
Andrew McLaren
amclar (at) optusnet dot com dot au

technomonkey

Sorry about the misunderstanding

There seem to be two errors codes;

MSI (c) (30:EC) [22:46:41:132]: Note: 1: 1708

This note is the line under --logging stopped-- and therefore I thought it
might have something to do with the problem and why setup failes. The last
file it accesed was ;

c:\Users\Michael\AppData\Local\Temp\22e61a.msi

Setup deletes this file when it fails and so I have no access to it.

and

Installation success or error status: 1603


I have Googled both errors and I have tried all of the 'work arounds' I
could find - any ideas??

technomonkey

Sorry about the misunderstanding

There seem to be two errors codes;

MSI (c) (30:EC) [22:46:41:132]: Note: 1: 1708

This note is the line under --logging stopped-- and therefore I thought it
might have something to do with the problem and why setup failes. The last
file it accesed was ;

c:\Users\Michael\AppData\Local\Temp\22e61a.msi

Setup deletes this file when it fails and so I have no access to it.

and

Installation success or error status: 1603


I have Googled both errors and I have tried all of the 'work arounds' I
could find - any ideas??

Andrew McLaren

"technomonkey" <technomonkey@discussions.microsoft.com> wrote

> The last file it accesed was ;
> c:\Users\Michael\AppData\Local\Temp\22e61a.msi
> Setup deletes this file when it fails and so I have no access to it.

That bit is normal. MSIexec will create a temporary msi file under the
%TEMP% location while it runs, then delete it when installation is finished.
All MSI installations work this way, whether it is Visual Studio, Office, or
whatever.


> Installation success or error status: 1603

Unfortunately, 1603 is a rather generic error, meaning ERROR_INSTALL_FAILURE
"A fatal error occurred during installation". There could be many causes.
The MSI error codes are documented here:

http://msdn2.microsoft.com/en-us/library/aa368542.aspx


> MSI (c) (30:EC) [22:46:41:132]: Note: 1: 1708
> This note is the line under --logging stopped-- and therefore I thought it
> might have something to do with the problem and why setup failes.

Note sure what that signifies, if anything. "1708" doesn't look like an
error to me. Well., Winerror.h does define an error code 1708
"RPC_S_NO_ENDPOINT_FOUND", but that hardly applies in this situation, I
think it's just coincidence.

You might need to walk back through the log and study what actions MSI was
trying to perform when it abended. Was it trying to create new directories?
Write files? Create new registry keys? etc.

If you get stuck, you might want to try asking over in
microsoft.public.vstudio.general or microsoft.public.vstudio.general. Even
though you se the problem on the Vista platform, it is VS Setup which is
failing, so the folks in those groups may have more immediate answers for
you.

Good luck,
--
Andrew McLaren
amclar (at) optusnet dot com dot au

Andrew McLaren

"technomonkey" <technomonkey@discussions.microsoft.com> wrote

> The last file it accesed was ;
> c:\Users\Michael\AppData\Local\Temp\22e61a.msi
> Setup deletes this file when it fails and so I have no access to it.

That bit is normal. MSIexec will create a temporary msi file under the
%TEMP% location while it runs, then delete it when installation is finished.
All MSI installations work this way, whether it is Visual Studio, Office, or
whatever.


> Installation success or error status: 1603

Unfortunately, 1603 is a rather generic error, meaning ERROR_INSTALL_FAILURE
"A fatal error occurred during installation". There could be many causes.
The MSI error codes are documented here:

http://msdn2.microsoft.com/en-us/library/aa368542.aspx


> MSI (c) (30:EC) [22:46:41:132]: Note: 1: 1708
> This note is the line under --logging stopped-- and therefore I thought it
> might have something to do with the problem and why setup failes.

Note sure what that signifies, if anything. "1708" doesn't look like an
error to me. Well., Winerror.h does define an error code 1708
"RPC_S_NO_ENDPOINT_FOUND", but that hardly applies in this situation, I
think it's just coincidence.

You might need to walk back through the log and study what actions MSI was
trying to perform when it abended. Was it trying to create new directories?
Write files? Create new registry keys? etc.

If you get stuck, you might want to try asking over in
microsoft.public.vstudio.general or microsoft.public.vstudio.general. Even
though you se the problem on the Vista platform, it is VS Setup which is
failing, so the folks in those groups may have more immediate answers for
you.

Good luck,
--
Andrew McLaren
amclar (at) optusnet dot com dot au

technomonkey

I have found nothing yet...

Thanks for the advice on microsoft.public.vstudio.general - I will check
there soon.

Do you think reinstalling Vista solve the problem?

Thanks