Problem installing Microsoft Visual C++ 2005

[Guest]

When attempting to instal Microsoft Visual C++ 2005 Redistributable package
'vcredist_x86.exe' on my Windows Vista computer, I got the following error:
"Error 1935 An error occurred during the installation of assembly component
Microsoft Visual C++ 2005 Redistributable. Microsoft
VC80.ATL.type="win32".version="8.0.50.727.762".publicKeyTOken="1fc8b9a1e183b".processor
Architecture="x86". Please refer to Help and Support for more information".

Although the Microsoft web site does not indicate that 'vcredist_x86.exe' is
supported under Vista, the company that wrote the application that requires
'vcredist_x86.exe' to run assures me that it does run under Vista, that it is
part of their normal instal package for their application, and that something
is wrong with my computer.

Can anyone shed any light on this please?

Wfeg

 

[Andrew McLaren]

Hi Wfeg,

Did you see an HRESULT in the error message? (usually comes after the
"Please refer to Help and Support for more information", will be a number
like 0x800736FD)

In broad terms, the VCRedist_x86.exe package is supported on Vista and
should install without error. So, your vendor is basically correct. However,
it is having trouble installing on this particular machine (or machines).
The "1935" is a standard MSI installer error. These error messages are
documented here:
http://msdn2.microsoft.com/en-us/library/aa372835.aspx

Error 1935 is "An error occurred during the installation of assembly '[6]'.
Please refer to Help and Support for more information. HRESULT: [3].
{{assembly interface: [4], function: [5], component: [2]}}"

MSI running on Windows Vista and Windows XP can install "side-by-side"
assemblies. Assemblies can be COM components, or Win32 DLLs. The concept
behind Side-by-side assemblies is that several versions of the same DLL can
exist on the system at the same time, "side by side". In the past , updating
shared DLLs with newer versions caused many application errors and lead to
the so-called "DLL Hell". With Side-by-Side, each app gets the version of
the shared DLL it likes best. These Side-by-Side files are stored under
C:\Windows\winsxs ("SxS" is the common abbreviation for Side-by-Side).

The problem you're seeing is that the VC Redist package is trying to install
the Active Template Library version 8.0 DLL (ATL80.DLL) into the
Side-by-Side Assembly cache (C:\Windows\winsxs). For some reason, it cannot
do so. The exact reason will probably be indicated by the HRESULT. If you
don't see an HRESULT in the visible error message, look in the Windows Event
Log (under Administrative Tools) for events with a source of "SideBySide" -
these might shed more light on the exact nature of the error.

In Vista, there is a diagnostic tool for troubleshooting Side-by-Side
errors, called sxstrace. This might also shed some light on the problem. To
use sxstrace:

- open a command prompt as Administrator and cd to a scratch directory

- start tracing running, with a log file you specify:
C:\TEMP>sxstrace trace -logfile:myvctrace.etl

- run VCRedist_x86.exe and observe the point of failure (error message);

- alt-tab back to Command Prompt and stop tracing:

C:\TEMP>sxstrace stoptrace

The myvctrace.etl file is a binary file, in Event Tracing for Windows (ETW)
format ("etl" extension = event trace log). You need to run it through a
parse command to turn it into readable text:

C:\TEMP>sxstrace parse -logfile:myvctrace.etl -outfile:myvctrace.txt

Now open myvctrace.txt in Notepad or other text editor, and see what it
says. I have to give a caveat here: sxstrace is good for detecting problems
when an application cannot locate a side-by-side assembly, such as if there
is a missing DLL. I don't know how well it works for problems *installing* a
DLL into the cache, rather than accessing the DLLs from an application. But
it's definitely worth a shot.

The other thing you'd want to check is what versions of ATL80.DLL are
already installed, under C:\Windows\winsxs. Many applications will want to
install ATL80.DLL; so it is quite possible the version the Redist is trying
to install is already on the system. The problem could be that it cannot
overwrite the existing files. This would only apply if they have the same
Public Key token - versions of ATL80.DLL with a different token should not
be a problem (I think).

Other folks might have extra ideas for you ... hope this helps a bit. Good
luck!

 

[Guest]

Andrew

Thank you for your very detailed reply. I really appreciate the effort you
went to in explaining the problem to me.

I get a very similar error trying to instal Apple iTunes updates now (they
used to instal OK). In this case, I get the HRESULT 0x8007054F. The event
log for the C++ Redistributable package vcredist_x86.exe says:

'Product: Microsoft Visual C++ 2005 Redistributable -- Error 1935.An error
occurred during the installation of assembly
'Microsoft.VC80.ATL,type="win32",version="8.0.50727.762",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86"'.
Please refer to Help and Support for more information. HRESULT: 0x8007054F.
assembly interface: IAssemblyCacheItem, function: Commit, component:
{97F81AF1-0E47-DC99-A01F-C8B3B9A1E18E}'

The HRESULT is exactly the same as in the case of iTunes instal, i.e.
HRESULT: 0x8007054F.

I have tried sxstrace.exe, but I got no alphanumeric output when I saved it
to a text file, so it gave me no help. Maybe I should try it again and wait
a lot longer time for it to complete?

There are 2 versions of ATL80.DLL installed on my Vista computer dated
03-Apr-07 and 12-Jul-07, located in folders
C:\Windows\winsxs\x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.42_none_dc990e4797f81af1,
and
C:\Windows\winsxs\x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.762_none_11ecb0ab9b2caf3c, respectively.

Thanks for your assistance- maybe you could comment on the above information
for me.

Wfeg

Hi Wfeg,

Did you see an HRESULT in the error message? (usually comes after the
"Please refer to Help and Support for more information", will be a number
like 0x800736FD)

In broad terms, the VCRedist_x86.exe package is supported on Vista and
should install without error. So, your vendor is basically correct. However,
it is having trouble installing on this particular machine (or machines).
The "1935" is a standard MSI installer error. These error messages are
documented here:
http://msdn2.microsoft.com/en-us/library/aa372835.aspx

Error 1935 is "An error occurred during the installation of assembly '[6]'.
Please refer to Help and Support for more information. HRESULT: [3].
{{assembly interface: [4], function: [5], component: [2]}}"

MSI running on Windows Vista and Windows XP can install "side-by-side"
assemblies. Assemblies can be COM components, or Win32 DLLs. The concept
behind Side-by-side assemblies is that several versions of the same DLL can
exist on the system at the same time, "side by side". In the past , updating
shared DLLs with newer versions caused many application errors and lead to
the so-called "DLL Hell". With Side-by-Side, each app gets the version of
the shared DLL it likes best. These Side-by-Side files are stored under
C:\Windows\winsxs ("SxS" is the common abbreviation for Side-by-Side).

The problem you're seeing is that the VC Redist package is trying to install
the Active Template Library version 8.0 DLL (ATL80.DLL) into the
Side-by-Side Assembly cache (C:\Windows\winsxs). For some reason, it cannot
do so. The exact reason will probably be indicated by the HRESULT. If you
don't see an HRESULT in the visible error message, look in the Windows Event
Log (under Administrative Tools) for events with a source of "SideBySide" -
these might shed more light on the exact nature of the error.

In Vista, there is a diagnostic tool for troubleshooting Side-by-Side
errors, called sxstrace. This might also shed some light on the problem. To
use sxstrace:

- open a command prompt as Administrator and cd to a scratch directory

- start tracing running, with a log file you specify:
C:\TEMP>sxstrace trace -logfile:myvctrace.etl

- run VCRedist_x86.exe and observe the point of failure (error message);

- alt-tab back to Command Prompt and stop tracing:

C:\TEMP>sxstrace stoptrace

The myvctrace.etl file is a binary file, in Event Tracing for Windows (ETW)
format ("etl" extension = event trace log). You need to run it through a
parse command to turn it into readable text:

C:\TEMP>sxstrace parse -logfile:myvctrace.etl -outfile:myvctrace.txt

Now open myvctrace.txt in Notepad or other text editor, and see what it
says. I have to give a caveat here: sxstrace is good for detecting problems
when an application cannot locate a side-by-side assembly, such as if there
is a missing DLL. I don't know how well it works for problems *installing* a
DLL into the cache, rather than accessing the DLLs from an application. But
it's definitely worth a shot.

The other thing you'd want to check is what versions of ATL80.DLL are
already installed, under C:\Windows\winsxs. Many applications will want to
install ATL80.DLL; so it is quite possible the version the Redist is trying
to install is already on the system. The problem could be that it cannot
overwrite the existing files. This would only apply if they have the same
Public Key token - versions of ATL80.DLL with a different token should not
be a problem (I think).

Other folks might have extra ideas for you ... hope this helps a bit. Good
luck!

 

[Andrew McLaren]

Hi Wfeg,

Thanks for sending the extra detail. According to winerror.h (the source
code file which defines all standard Windows errors), an HRESULT of
0x8007054F means ERROR_INTERNAL_ERROR "An internal error occurred"! Oh
dear, not a very helpful error ...

However, it looks like you already have ATL80.DLL v8.0.50727.762 installed
on your system. I strongly suspect the error is occurring because the MSI
Installer is trying to write to a directory called
C:\Windows\winsxs\x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.762_none_11ecb0ab9b2caf3c,
but this directory already exists. Depending on the elevation requested by
the installer, it may not have permission to overwrite the existing
directory (even if you are running as administrator). Hence, it barfs.

I can see 2 ways to tackle the problem:


1) the empirical approach. Take ownership of the
C:\Windows\winsxs\x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.762_none_11ecb0ab9b2caf3c
directory, so that you can then change it. By default, it will be owned by
"SYSTEM", so not even the Administrator can rename it. Then, once you own
it, rename it to something like
C:\Windows\winsxs\x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.762_none_11ecb0ab9b2caf3c.original.
Then run the VCRedist_x86.exe package again. This time, it should be able to
create the new SxS directory for ATL80.DLL, because there will be no name
collision. Once you have verified that the new directory is created and your
system is working normally, you can then delete the superfluous old
C:\Windows\winsxs\x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.762_none_11ecb0ab9b2caf3c.original
directory.

If for some reason VCRedist_x86 still fails and you don't get a new
directory created, just rename the original directory back to the way it
was, to restore normal operation.


2) The forensic approach. It is possible to create a log file of the
installation of the VCREDist_x86 package, showing detailed, step-by-step
records of what operations it performs. It takes a little work to set up.
For some reason, VCRedist_x86 appears to have been packaged, twice - I'm not
sure why. By the way, I am using the VS2005 SP1 Redist package, from here:
http://www.microsoft.com/downloads/...d9-ae1a-4a14-984d-389c36f85647&displaylang=en

To unpack it, do this:

- at a command prompt, go to a scratch directory cd C:\TEMP
- copy VCRedist_x86.exe to this scratch directory
- create 2 subdirectories called extract1 and extract2:

C:\TEMP>mkdir extract1
C:\TEMP>mkdir extract2

- run this command:

C:\TEMP>vcredist_x86 /T:C:\TEMP\extract1 /c

This will unpack the compressed Redist package into the extract1
subdirectory.

- now change directory to extract1. Observe that the unpacked package
consists of another, single EXE file. Run it with this command:

C:\TEMP\extract1\VCREDI~3.EXE /T:C:\TEMP\extract2 /c

This will unpack the really compressed Redist package into
C:\TEMP\extract2. There should be 2 files: vcredist.msi and vcredis1.cab

- now, install the Redist package from the unpacked MSI by using this
command:

C:\TEMP\extract2>msiexec /i vcredist.msi /l*v vcredist.log

This will create a text file C:\TEMP\extract2\vcredist.log, with a
blow-by-blow description of everything the installer does. The "/l"
(lower-case "L") means "enable logging". The "*" means "with all logging
options" and the "v" means "verbose". So this is the most detailed log
available.

If you continue to get an Error 1935 error message appaearing, go and look
in the vcredist.log file, to find out exactly what the MSI Installer was
doing when it created this error. With any luck there will be additional
error codes, such as 0x00000005 "access denied" or similar. These may give
us some extra clues.


By way of general comment - most installers seem to be able to over-write
existing Side-by-Side DLLs without any problem. I'm not sure why this one is
having such a problem. A quick web search shows that there is a small but
noticeable bunch of users who seem to be hitting this 1935 error, so there
must be some small wrinkle out there in some common application.

Let us know how you get on....

 

[Peter Foldes]

Wseg

Last Time we discussed the following

http://www.microsoft.com/communitie...&tid=5fe125d3-0d35-4763-b55f-4d7580fdf3d2&p=1

Do you have NetFramework 1.1 installed ? If you do is Mscoree.dll running 2 instances
--
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.

Andrew

Thank you for your very detailed reply. I really appreciate the effort you
went to in explaining the problem to me.

I get a very similar error trying to instal Apple iTunes updates now (they
used to instal OK). In this case, I get the HRESULT 0x8007054F. The event
log for the C++ Redistributable package vcredist_x86.exe says:

'Product: Microsoft Visual C++ 2005 Redistributable -- Error 1935.An error
occurred during the installation of assembly
'Microsoft.VC80.ATL,type="win32",version="8.0.50727.762",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86"'.
Please refer to Help and Support for more information. HRESULT: 0x8007054F.
assembly interface: IAssemblyCacheItem, function: Commit, component:
{97F81AF1-0E47-DC99-A01F-C8B3B9A1E18E}'

The HRESULT is exactly the same as in the case of iTunes instal, i.e.
HRESULT: 0x8007054F.

I have tried sxstrace.exe, but I got no alphanumeric output when I saved it
to a text file, so it gave me no help. Maybe I should try it again and wait
a lot longer time for it to complete?

There are 2 versions of ATL80.DLL installed on my Vista computer dated
03-Apr-07 and 12-Jul-07, located in folders
C:\Windows\winsxs\x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.42_none_dc990e4797f81af1,
and
C:\Windows\winsxs\x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.762_none_11ecb0ab9b2caf3c, respectively.

Thanks for your assistance- maybe you could comment on the above information
for me.

Wfeg

Hi Wfeg,

Did you see an HRESULT in the error message? (usually comes after the
"Please refer to Help and Support for more information", will be a number
like 0x800736FD)

In broad terms, the VCRedist_x86.exe package is supported on Vista and
should install without error. So, your vendor is basically correct. However,
it is having trouble installing on this particular machine (or machines).
The "1935" is a standard MSI installer error. These error messages are
documented here:
http://msdn2.microsoft.com/en-us/library/aa372835.aspx

Error 1935 is "An error occurred during the installation of assembly '[6]'.
Please refer to Help and Support for more information. HRESULT: [3].
{{assembly interface: [4], function: [5], component: [2]}}"

MSI running on Windows Vista and Windows XP can install "side-by-side"
assemblies. Assemblies can be COM components, or Win32 DLLs. The concept
behind Side-by-side assemblies is that several versions of the same DLL can
exist on the system at the same time, "side by side". In the past , updating
shared DLLs with newer versions caused many application errors and lead to
the so-called "DLL Hell". With Side-by-Side, each app gets the version of
the shared DLL it likes best. These Side-by-Side files are stored under
C:\Windows\winsxs ("SxS" is the common abbreviation for Side-by-Side).

The problem you're seeing is that the VC Redist package is trying to install
the Active Template Library version 8.0 DLL (ATL80.DLL) into the
Side-by-Side Assembly cache (C:\Windows\winsxs). For some reason, it cannot
do so. The exact reason will probably be indicated by the HRESULT. If you
don't see an HRESULT in the visible error message, look in the Windows Event
Log (under Administrative Tools) for events with a source of "SideBySide" -
these might shed more light on the exact nature of the error.

In Vista, there is a diagnostic tool for troubleshooting Side-by-Side
errors, called sxstrace. This might also shed some light on the problem. To
use sxstrace:

- open a command prompt as Administrator and cd to a scratch directory

- start tracing running, with a log file you specify:
C:\TEMP>sxstrace trace -logfile:myvctrace.etl

- run VCRedist_x86.exe and observe the point of failure (error message);

- alt-tab back to Command Prompt and stop tracing:

C:\TEMP>sxstrace stoptrace

The myvctrace.etl file is a binary file, in Event Tracing for Windows (ETW)
format ("etl" extension = event trace log). You need to run it through a
parse command to turn it into readable text:

C:\TEMP>sxstrace parse -logfile:myvctrace.etl -outfile:myvctrace.txt

Now open myvctrace.txt in Notepad or other text editor, and see what it
says. I have to give a caveat here: sxstrace is good for detecting problems
when an application cannot locate a side-by-side assembly, such as if there
is a missing DLL. I don't know how well it works for problems *installing* a
DLL into the cache, rather than accessing the DLLs from an application. But
it's definitely worth a shot.

The other thing you'd want to check is what versions of ATL80.DLL are
already installed, under C:\Windows\winsxs. Many applications will want to
install ATL80.DLL; so it is quite possible the version the Redist is trying
to install is already on the system. The problem could be that it cannot
overwrite the existing files. This would only apply if they have the same
Public Key token - versions of ATL80.DLL with a different token should not
be a problem (I think).

Other folks might have extra ideas for you ... hope this helps a bit. Good
luck!

 

[Guest]

Peter

Thanks for your feedback. I checked in Services and I do have Microsoft
..NET Framework NGEN v2.0.50727_x86 listed as a service, but it says startup
type is manual, so I presume that it is not started? I also looked in the
Windows Rask Manager under Processes and Services for Mscoree.dll, but I
could not see this as a running process or service.

A Microsoft support technician pointed me to a beta2 release of Microsoft
Visual C++ 2008 at:
http://msdn2.microsoft.com/en-au/express/future/bb421473.aspx
I tired to instal this, but it would not instal the first component
(Microsoft .NET Framework 3.5), and the other 4 component did not instal
after this.

Wfeg

Wseg

Last Time we discussed the following

http://www.microsoft.com/communitie...&tid=5fe125d3-0d35-4763-b55f-4d7580fdf3d2&p=1

Do you have NetFramework 1.1 installed ? If you do is Mscoree.dll running 2 instances
--
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.

Andrew

Thank you for your very detailed reply. I really appreciate the effort you
went to in explaining the problem to me.

I get a very similar error trying to instal Apple iTunes updates now (they
used to instal OK). In this case, I get the HRESULT 0x8007054F. The event
log for the C++ Redistributable package vcredist_x86.exe says:

'Product: Microsoft Visual C++ 2005 Redistributable -- Error 1935.An error
occurred during the installation of assembly
'Microsoft.VC80.ATL,type="win32",version="8.0.50727.762",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86"'.
Please refer to Help and Support for more information. HRESULT: 0x8007054F.
assembly interface: IAssemblyCacheItem, function: Commit, component:
{97F81AF1-0E47-DC99-A01F-C8B3B9A1E18E}'

The HRESULT is exactly the same as in the case of iTunes instal, i.e.
HRESULT: 0x8007054F.

I have tried sxstrace.exe, but I got no alphanumeric output when I saved it
to a text file, so it gave me no help. Maybe I should try it again and wait
a lot longer time for it to complete?

There are 2 versions of ATL80.DLL installed on my Vista computer dated
03-Apr-07 and 12-Jul-07, located in folders
C:\Windows\winsxs\x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.42_none_dc990e4797f81af1,
and
C:\Windows\winsxs\x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.762_none_11ecb0ab9b2caf3c, respectively.

Thanks for your assistance- maybe you could comment on the above information
for me.

Wfeg

Hi Wfeg,

Did you see an HRESULT in the error message? (usually comes after the
"Please refer to Help and Support for more information", will be a number
like 0x800736FD)

In broad terms, the VCRedist_x86.exe package is supported on Vista and
should install without error. So, your vendor is basically correct. However,
it is having trouble installing on this particular machine (or machines).
The "1935" is a standard MSI installer error. These error messages are
documented here:
http://msdn2.microsoft.com/en-us/library/aa372835.aspx

Error 1935 is "An error occurred during the installation of assembly '[6]'.
Please refer to Help and Support for more information. HRESULT: [3].
{{assembly interface: [4], function: [5], component: [2]}}"

MSI running on Windows Vista and Windows XP can install "side-by-side"
assemblies. Assemblies can be COM components, or Win32 DLLs. The concept
behind Side-by-side assemblies is that several versions of the same DLL can
exist on the system at the same time, "side by side". In the past , updating
shared DLLs with newer versions caused many application errors and lead to
the so-called "DLL Hell". With Side-by-Side, each app gets the version of
the shared DLL it likes best. These Side-by-Side files are stored under
C:\Windows\winsxs ("SxS" is the common abbreviation for Side-by-Side).

The problem you're seeing is that the VC Redist package is trying to install
the Active Template Library version 8.0 DLL (ATL80.DLL) into the
Side-by-Side Assembly cache (C:\Windows\winsxs). For some reason, it cannot
do so. The exact reason will probably be indicated by the HRESULT. If you
don't see an HRESULT in the visible error message, look in the Windows Event
Log (under Administrative Tools) for events with a source of "SideBySide" -
these might shed more light on the exact nature of the error.

In Vista, there is a diagnostic tool for troubleshooting Side-by-Side
errors, called sxstrace. This might also shed some light on the problem. To
use sxstrace:

- open a command prompt as Administrator and cd to a scratch directory

- start tracing running, with a log file you specify:
C:\TEMP>sxstrace trace -logfile:myvctrace.etl

- run VCRedist_x86.exe and observe the point of failure (error message);

- alt-tab back to Command Prompt and stop tracing:

C:\TEMP>sxstrace stoptrace

The myvctrace.etl file is a binary file, in Event Tracing for Windows (ETW)
format ("etl" extension = event trace log). You need to run it through a
parse command to turn it into readable text:

C:\TEMP>sxstrace parse -logfile:myvctrace.etl -outfile:myvctrace.txt

Now open myvctrace.txt in Notepad or other text editor, and see what it
says. I have to give a caveat here: sxstrace is good for detecting problems
when an application cannot locate a side-by-side assembly, such as if there
is a missing DLL. I don't know how well it works for problems *installing* a
DLL into the cache, rather than accessing the DLLs from an application. But
it's definitely worth a shot.

The other thing you'd want to check is what versions of ATL80.DLL are
already installed, under C:\Windows\winsxs. Many applications will want to
install ATL80.DLL; so it is quite possible the version the Redist is trying
to install is already on the system. The problem could be that it cannot
overwrite the existing files. This would only apply if they have the same
Public Key token - versions of ATL80.DLL with a different token should not
be a problem (I think).

Other folks might have extra ideas for you ... hope this helps a bit. Good
luck!

 

[Guest]

Andrew

Thanks for your update. There is a lot of very welcome detail and
explanations here.

I tried the first approach (empirical) last night, but I ran into a problem.
I located the folder
C:\Windows\winsxs\x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.762_none_11ecb0ab9b2caf3c
and clicked on Properties. I notice that many folders that I get Properties
from shows the Read Only attribute not ticked, but blanked out, and when you
try to delete such a folder, or move files from it, it says that you dojn't
have permission (I am Administrator). Anyway, this folder did the same, so I
'unclicked' its Read Only attributes properties, then I went to the Security
tab and changed the ownership to Administrators, and gave permission to allow
'modify' and 'write'. Then I clicked on Advanced, and set Ownership to
Administrators under the Owner tab. But when I cilcked on OK twice, it said
that I needed permission to do this. So I did the same for Wfeg (User), and
got the same message. Then, when I tried to rename the folder to
C:\Windows\winsxs\x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.762_none_11ecb0ab9b2caf3c.original, it again said that I needed permission to do this.

So, I haven't got very far down the track yet. Can you suggest a way around
this?

Wfeg

 

[Peter Foldes]

Wfeg

I strongly suggest that you install the Net Framework 1.1 with the latest Updates.

In your reply you stated that you have Net 2.0 installed. I was asking about Net 1.1. Install Net Framework 1.1 with the latest updates and then see if your issue with VB will correct itself.

--
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.

Peter

Thanks for your feedback. I checked in Services and I do have Microsoft
.NET Framework NGEN v2.0.50727_x86 listed as a service, but it says startup
type is manual, so I presume that it is not started? I also looked in the
Windows Rask Manager under Processes and Services for Mscoree.dll, but I
could not see this as a running process or service.

A Microsoft support technician pointed me to a beta2 release of Microsoft
Visual C++ 2008 at:
http://msdn2.microsoft.com/en-au/express/future/bb421473.aspx
I tired to instal this, but it would not instal the first component
(Microsoft .NET Framework 3.5), and the other 4 component did not instal
after this.

Wfeg

Wseg

Last Time we discussed the following

http://www.microsoft.com/communitie...&tid=5fe125d3-0d35-4763-b55f-4d7580fdf3d2&p=1

Do you have NetFramework 1.1 installed ? If you do is Mscoree.dll running 2 instances
--
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.

Andrew

Thank you for your very detailed reply. I really appreciate the effort you
went to in explaining the problem to me.

I get a very similar error trying to instal Apple iTunes updates now (they
used to instal OK). In this case, I get the HRESULT 0x8007054F. The event
log for the C++ Redistributable package vcredist_x86.exe says:

'Product: Microsoft Visual C++ 2005 Redistributable -- Error 1935.An error
occurred during the installation of assembly
'Microsoft.VC80.ATL,type="win32",version="8.0.50727.762",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86"'.
Please refer to Help and Support for more information. HRESULT: 0x8007054F.
assembly interface: IAssemblyCacheItem, function: Commit, component:
{97F81AF1-0E47-DC99-A01F-C8B3B9A1E18E}'

The HRESULT is exactly the same as in the case of iTunes instal, i.e.
HRESULT: 0x8007054F.

I have tried sxstrace.exe, but I got no alphanumeric output when I saved it
to a text file, so it gave me no help. Maybe I should try it again and wait
a lot longer time for it to complete?

There are 2 versions of ATL80.DLL installed on my Vista computer dated
03-Apr-07 and 12-Jul-07, located in folders
C:\Windows\winsxs\x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.42_none_dc990e4797f81af1,
and
C:\Windows\winsxs\x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.762_none_11ecb0ab9b2caf3c, respectively.

Thanks for your assistance- maybe you could comment on the above information
for me.

Wfeg

:

Hi Wfeg,

Did you see an HRESULT in the error message? (usually comes after the
"Please refer to Help and Support for more information", will be a number
like 0x800736FD)

In broad terms, the VCRedist_x86.exe package is supported on Vista and
should install without error. So, your vendor is basically correct. However,
it is having trouble installing on this particular machine (or machines).
The "1935" is a standard MSI installer error. These error messages are
documented here:
http://msdn2.microsoft.com/en-us/library/aa372835.aspx

Error 1935 is "An error occurred during the installation of assembly '[6]'.
Please refer to Help and Support for more information. HRESULT: [3].
{{assembly interface: [4], function: [5], component: [2]}}"

MSI running on Windows Vista and Windows XP can install "side-by-side"
assemblies. Assemblies can be COM components, or Win32 DLLs. The concept
behind Side-by-side assemblies is that several versions of the same DLL can
exist on the system at the same time, "side by side". In the past , updating
shared DLLs with newer versions caused many application errors and lead to
the so-called "DLL Hell". With Side-by-Side, each app gets the version of
the shared DLL it likes best. These Side-by-Side files are stored under
C:\Windows\winsxs ("SxS" is the common abbreviation for Side-by-Side).

The problem you're seeing is that the VC Redist package is trying to install
the Active Template Library version 8.0 DLL (ATL80.DLL) into the
Side-by-Side Assembly cache (C:\Windows\winsxs). For some reason, it cannot
do so. The exact reason will probably be indicated by the HRESULT. If you
don't see an HRESULT in the visible error message, look in the Windows Event
Log (under Administrative Tools) for events with a source of "SideBySide" -
these might shed more light on the exact nature of the error.

In Vista, there is a diagnostic tool for troubleshooting Side-by-Side
errors, called sxstrace. This might also shed some light on the problem. To
use sxstrace:

- open a command prompt as Administrator and cd to a scratch directory

- start tracing running, with a log file you specify:
C:\TEMP>sxstrace trace -logfile:myvctrace.etl

- run VCRedist_x86.exe and observe the point of failure (error message);

- alt-tab back to Command Prompt and stop tracing:

C:\TEMP>sxstrace stoptrace

The myvctrace.etl file is a binary file, in Event Tracing for Windows (ETW)
format ("etl" extension = event trace log). You need to run it through a
parse command to turn it into readable text:

C:\TEMP>sxstrace parse -logfile:myvctrace.etl -outfile:myvctrace.txt

Now open myvctrace.txt in Notepad or other text editor, and see what it
says. I have to give a caveat here: sxstrace is good for detecting problems
when an application cannot locate a side-by-side assembly, such as if there
is a missing DLL. I don't know how well it works for problems *installing* a
DLL into the cache, rather than accessing the DLLs from an application. But
it's definitely worth a shot.

The other thing you'd want to check is what versions of ATL80.DLL are
already installed, under C:\Windows\winsxs. Many applications will want to
install ATL80.DLL; so it is quite possible the version the Redist is trying
to install is already on the system. The problem could be that it cannot
overwrite the existing files. This would only apply if they have the same
Public Key token - versions of ATL80.DLL with a different token should not
be a problem (I think).

Other folks might have extra ideas for you ... hope this helps a bit. Good
luck!

 

[Andrew McLaren]

and clicked on Properties. I notice that many folders that I get
Properties
from shows the Read Only attribute not ticked, but blanked out, and when
you
try to delete such a folder, or move files from it, it says that you
dojn't
have permission (I am Administrator).

Actually, the "Read-Only" attribute has NO EFFECT on directories on Windows
NT ("NT" also including here, Windows 2000, XP, Server 2003, and Vista).

The Windows Explorer shell uses the read-only attribute on directories, to
determine whether it should look for icon resources within files under the
directory. That is all. The read-only attribute is ignored by the rest of
Windows, apert from Explorer. The read-only attribute does not make the
directory read-only, undeletable, or anything else. It's just a left-over
appendage from FAT and Windows 95. The only thing which affects whether you
can delete, write to, read, etc a directory are the ACLs.

Anyway, this folder did the same, so I
'unclicked' its Read Only attributes properties, then I went to the
Security
tab and changed the ownership to Administrators, and gave permission to
allow
'modify' and 'write'. Then I clicked on Advanced, and set Ownership to
Administrators under the Owner tab. But when I cilcked on OK twice, it
said
that I needed permission to do this. So I did the same for Wfeg (User),
and
got the same message. Then, when I tried to rename the folder to
C:\Windows\winsxs\x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.762_none_11ecb0ab9b2caf3c.original,
it again said that I needed permission to do this.

Yeah, that was actually my mistake. Sorry. Even after you have permissions
to the x86_microsoft.vc80.atl_1fc8.etc subdirectory, you still don't have
write permissions to the winsxs directory. So you can't move the atl
subdirectory to a new location under C:\Windows\winsxs.

Rather than mess with the permissions on winsxs directory (which could
easily screw your entire system), make a backup copy of the subdirectory
elsewhere, with a command like this:

C:\TEMP>xcopy
C:\Windows\winsxs\x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.762_none_11ecb0ab9b2caf3c
.. /e /i /h /k /o /x

That will create a safe backup copy under the C:\TEMP directory. The "/e /i
/h /k /o /x" parameters will also copy the file permissions and auditing
information. Note also teh "." full stop, after the subdirectory and before
the parameters (meaning "current directory", ie, copy it here).

After you have made a backup copy of
x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.762_none_11ecb0ab9b2caf3c,
you can now delete the original under C:\Windows\winsxs. You may need to
grant yourself "Full Control" in order to delete it.

After you have deleted the
x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.762_none_11ecb0ab9b2caf3c
subdirectory, try running VCRedist_x86 again. This time there will be no
name collision, and (hopefully) it will install correctly.

Cheers,

 

[Guest]

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

 

[Guest]

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]

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,

 

[Guest]

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]

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,

 

[Guest]

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

 

[Andrew McLaren]

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?

Run msiexec with an additonal "x" parameter, lik ethis:

C:\TEMP\extract2>msiexec /i vcredist.msi /l*xv vcredist.log

The "x" will put additional debugging information into the log. This might
make it more obvious what is failing.

If you just need to get Visual Studio up and running then reinstalling Vista
could be a crude-but-effective, brute force approach to the problem. If you
go down that path, make sure that Visual Studio is the first application you
re-install; the problem might be caused by a conflict with some other app
you have installed (a SxS conflict or similar).

I'm not necessarily recommending you re-install Vista - as a solution, it
lacks finesse and elegance. But it might get you up and running in a short
time. If you do go down that route you should save your existing,
unsuccessful log file. Create a log file as you make the new installation of
Visual Studio, on the re-installed Vista. Then when you have finished, you
can compare the unsuccessful log file with the successful log file. This may
help you to understand what was failing, in your current installation
attempt. You'll be the local expert in your team, for interpreting MSI log
files!

Good luck.

 

[Guest]

Hi all,

Just to let you know that I am going away for the next couple of days, so I
will not be able to reply during that time. I will however return soon and be
ready to continue.

Thanks

 

[Guest]

Hi all,

The new log seems to suggest that setup is examining my setup, there is info
about my system such as username and screen resolution. The final line is;

Property(C): ACTION = INSTALL

This is after all the system info. Could there be a problem with my system?
I find this unlikely because my system is only about a week old! Just in case
here is my spec;

AMD Athlon 64 4000+ Live!
2 GB RAM
320 GB HDD
ATI Radeon X1300

Is there anything that could be causing a problem?

I have just realised that I am trying to install C++ Redistributable rather
than the development tool, would the error codes mean the same or is this the
wrong thread?

Thanks
Michael

 

[Andrew McLaren]

I have just realised that I am trying to install C++ Redistributable
rather
than the development tool, would the error codes mean the same or is this
the

I regret to say, I have compassion-fatigue. You don't know what product you
are trying to install. I have tried to help; but I suspect you just need to
sit down, think carefully, and work out what the hell you are doing, before
you continue wasting people's time. I regret sounding a bit harsh, but ...
geez!! At this rate, we could spend years on this issue and still get
nowhere.

This is after all the system info. Could there be a problem with my
system?
I find this unlikely because my system is only about a week old! Just in
case

Yes, there is a problem with your system - you cannot install the VC Redist.
I don't think the problem you're seeing is intrinsic to Vista.

Make sure that you are installing the latest redistributable package:
http://www.microsoft.com/downloads/...D9-AE1A-4A14-984D-389C36F85647&displaylang=en
(or x64 version, if appropriate).

If that doesn't work, try asking over on microsoft.public.vstudio.general.
Good luck.

 

[Guest]

I apologise for any of your time that I have wasted, I will continue to try
and find a solution on my own.

Thank you very much for your help.