VS2008 installation woes (and VS2010)

[ASB]

Just a longshot that somebody might have had the same problem.

I have ended up with a system where NGEN will not run ("The application failed to initialize properly (0xc00000005)")> Same is true for ILASM.

Have uninstalled, tried everything suggested on the various MSDN fora, been told by them to do the same thing again etc. etc. The integrity tool says everything is fine.

The problem appears to occur when .NET fw 3.5 SP1 is installed (i.e. if I install VS2008 with no service packs it seems OK).

VS2008 itself seems to run just fine.

Only perhaps slightly unusual thing is that the machine also has VB6 installed, and this was installed after the original installation of VS2008 (though VS2008 has been uninstalled and reinstalled with great regularity since).

Only slight weirdo is that dependency walker show a warning with a function in MPR.DLL (WNetRestoreConnectionA) though this is apparently not an issue from searching.

Just wondered if anybody had any similar issues, or perhaps some suggestions as to how I can find out what it is that is giving the access violation so I can at least try a different avenue to attempt to figure it out.

Cheers.

[eek]

You've probably got a dodgy or non-existent file within the files that need to be compiled. Check the ngen log files and see what they come up with.

ngen.log
ngen_service.log

My guess is ddeleting the queue will fix the issue but as it may screw something else up do it at your own risk.

ngen /delete *

[ASB]

You've probably got a dodgy or non-existent file within the files that need to be compiled. Check the ngen log files and see what they come up with.

ngen.log
ngen_service.log

My guess is ddeleting the queue will fix the issue but as it may screw something else up do it at your own risk.

ngen /delete *

Since ngen won't run at all I couldn't delete the queue even if I wanted to.

But helpful since it got me looking in a different direction.

File: C:\WINNT\assembly\NativeImages_v2.0.50727_32\Syste m.Xml\c98cb65a79cfccb44ea727ebe4593ede\System.Xml. ni.dll
Dependencies:
mscorlib, Version=2.0.0.0, PublicKeyToken=b77a5c561934e089:
Guid:{5B8A4961-93B0-43B1-A337-BDF5962ECE99}
Sign:bd6c58fc8f03105a020331f4a60084e337a27a33
Hardbound Guid:{03F7E632-14C1-A9F3-71CB-E706586E3655}
System.Xml, Version=2.0.0.0, PublicKeyToken=b77a5c561934e089:
Guid:{56B829E1-D568-4AC9-8390-1A595A688DA0}
Sign:546fb0968a3ad8f39d84fd920ec9850c096e8faf
System, Version=2.0.0.0, PublicKeyToken=b77a5c561934e089:
Guid:{FEF73977-5832-438E-8BD7-0FDA47BE005C}
Sign:a87ed832d6e6b76aa0302a427ffe6d77c00a6408
Hardbound Guid:{223A0EBA-1B21-34A7-3E01-16B051F2965A}
System.Data.SqlXml, Version=2.0.0.0, PublicKeyToken=b77a5c561934e089:
Guid:{BFC562F7-035D-41E6-871B-6C03818BDCCE}
Sign:a9f9d97d66169e668a9898983175896798274be7
System.Configuration, Version=2.0.0.0, PublicKeyToken=b03f5f7f11d50a3a:
Guid:{B585B913-AF24-4E74-A787-0EBE1B5D5D06}
Sign:58961b3f64a74093492875c9d8f1e648b2f75545

07/09/2010 15:49:50: Succesfully compiled: System.Xml, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
07/09/2010 15:51:09: Service state is now SERVICE_PAUSE_PENDING
07/09/2010 15:51:09: Service state is now SERVICE_PAUSED
07/09/2010 15:53:02: Service state is now SERVICE_STOP_PENDING

It does seem as though some update at around 15:50 on the 9th July might be the problem. Though this does seem to be the usual trace when updates are installed. [I think this coincides with then 3.5 SP1 was installed - most recently]

There are also loads of

06/10/2010 18:45:42 [1324]: Warning: Failed to load method token 690000bd from profile data. Can't find anything useful about this.

The ngen service (mscorsvw) is not running - it fails to start. Trying to start it manually from the command line gives the same error as trying to run NGEN. Exactly the same issue with ASP.NET state service (aspnet_state).

[eek]

have you upgraded vs2008 to sp1?

It looks like something is wrong in a configuration file or the registry and I'd personally try that upgrade and if that fails blast the machine back to a fresh operating system.

Yes I know its not what you want to hear but it looks like a needle in the haystack type issue.

[ASB]

have you upgraded vs2008 to sp1?

It looks like something is wrong in a configuration file or the registry and I'd personally try that upgrade and if that fails blast the machine back to a fresh operating system.

Yes I know its not what you want to hear but it looks like a needle in the haystack type issue.

Yes, it is upgraded to SP1. I can't get to fresh OS. It's a corporate install for the base system (though I'm not saying that's the problem). And it was this I started from

It is definitely needle in haystack I know. If I could even find out what it was that was actually giving the protection violation it might help.

[eek]

Try reinstalling the 3.5 sp1 framework separate to vs2008. It could be something like the aspnet_regiis issue.

[ASB]

Try reinstalling the 3.5 sp1 framework separate to vs2008. It could be something like the aspnet_regiis issue.

Tried that

[eek]

have you checked services to see if its running or disabled. You can always stop and start it again.

Glancing at my machine I seem to have ngen 4 running and ngen 2 disabled.

[ASB]

have you checked services to see if its running or disabled. You can always stop and start it again.

Glancing at my machine I seem to have ngen 4 running and ngen 2 disabled.

The ngen service (mscorsvw) is not running - it fails to start. Trying to start it manually from the command line gives the same error as trying to run NGEN. Exactly the same issue with ASP.NET state service (aspnet_state).