.Net problem? Unable to logon to WinXP pro

By awellman ·
We are having a problem in which many of our computers that just have had a new image installed (WinXP Pro SP3) are unable to logon. Can only logon on in safe mode. Several things are showing up. There are literally thousands of empty folders being greated on the C: drive like '0a0a1d5815e652efa2c130'. Also the application event log has many of these errors:
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile: System.Windows.Presentation, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089 . Error code = 0x80070020
Also errors in the system log for the MS Installer & HotFixInstaller regarding the .Net Framework.
MsInstaller 11729:
Product: Microsoft .NET Framework 2.0 Service Pack 2 -- Configuration failed.

STYSTEM Windows Update Agent 20:
Installation Failure: Windows failed to install the following update with error 0x80070643: Microsoft .NET Framework 3.5 SP1 and .NET Framework 2.0 SP2 Update for Windows Server 2003 and Windows XP x86 (KB982524).

Any ideas what is causing the error or where to start looking.

Thanks in advance.

Art W.

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Collapse -

"Can only logon on in safe mode."

by seanferd In reply to .Net problem? Unable to ...

What does this look like? Credentials denied? No logon box? What?

I don't think dotnet would have anything to do with the logon issues, but there is certainly a problem with it.

I would just rebuild the image, and make sure it has all the correct drivers for the system you are applying the image to (these are all exactly the same systems, right?) Maybe fully update the box from which you are taking the image before creating and applying the image to the other systems.

Collapse -


by awellman In reply to "Can only logon on in saf ...

The problem is happening on several different models. There is a separate image for each model. Prior to creating the image, all MS updates were applied. After these errors start, you can no longer connect to the network or logon. Can logon in safe mode only.
Thanks for your time.

Collapse -

Same Domain???

by Mehul Bhai In reply to Image

If all the image computers are to be connected to the same domain network then you will have to rename all image computers' name and register/join them in the domain/active directory. All computers should have different name from other computers. All names are to be unique to itself. It seems system names are clashing, from what you mention as your problem.
From what you mention about the forlders with random names, it seems that updates were not completed properly in your original computers before creating images of the same.

Collapse -

Same Domain

by awellman In reply to Same Domain???

Images are created per domain and are prepared using MS Sysprep. All updates completed normally on the model computers before creating the images. The folders are not on the computers when they are first started after re-imaging and everything looks fine at first. It is after they have been on for a day or two after imaging that the problems start.
Thanks for helping.

Related Discussions

Related Forums