troubleshooting Question

Windows 2003 SBS & MSI K8NGM2-FID (nVidia C51) Motherboard

Avatar of dsa_erie
dsa_erie asked on
SBS
17 Comments1 Solution2588 ViewsLast Modified:
I've been trying for days to get this setup to work.

One of my clients has a small network and they wanted to upgrade to Windows 2003 SBS.  I built them a server based off of an Opteron 148 CPU and a MSI K8NGM2-FID motherboard.  There is a RAID1 using SATA (2-Seagate 160GB).  2GB (1GBx2) Patriot PC3200 DDR.  RAM was tested with memtest86.

I can install the base operating system without issue.  The chipset, raid and video drivers seem to install fine.

Once I start the domain setup this is where things start to fail.  I'm getting errors after I put in the basic address information.

When it start the 'Domain Configuration' a message box pops up with the following message: "The application could not be initialized."

I've reformatted and reinstalled 3 times.

Here are some of the error messages I'm seeing in the event logs.

***
Application log:

Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance.  hr = 0x80040154.
Volume Shadow Copy Service error: Writers will not receive events since the COM+ database is corrupted.  This might happened if an error occurred during Windows setup.  The error returned from CoCreateInstance on class with CLSID {4e14fba2-2e22-11d1-9964-00c04fbbb345} and Name CEventSystem is [0x80040154]
***
Windows couldn't log the RSoP (Resultant Set of Policies) session status. An attempt to connect to WMI failed. No more RSoP logging will be done for this application of policy.
***

***
System log:

The Cryptographic Services service failed to initialize the VSS backup "System Writer" object.

Details:
Could not open the EventSystem service for query.

System Error:
The specified service does not exist as an installed service.
***

Windows Setup encountered non-fatal errors during installation. Please check the setuperr.log found in your Windows directory for more information.

The following is the setuperr.log:

Error:
Setup was unable to open information file rootau.inf.

Contact your system administrator. The specific error code is 0xe0000100 at line 0.

***

Error:
Setup was unable to process some components because of the following error in section DefaultInstall of information file secdrv.inf:
A required privilege is not held by the client.


***

Error:
Setup could not register the OLE Control C:\WINDOWS\system32\gpedit.dll because of the following error:
LoadLibrary returned error 126 (the specified module could not be found).


***

Error:
Setup could not register the OLE Control C:\WINDOWS\system32\appmgr.dll because of the following error:
LoadLibrary returned error 126 (the specified module could not be found).


***

Error:
Setup could not register the OLE Control C:\WINDOWS\system32\wbem\nlbmprov.dll because of the following error:
LoadLibrary returned error 126 (the specified module could not be found).


***

Error:
Setup could not register the OLE Control C:\WINDOWS\system32\dgnet.dll because of the following error:
LoadLibrary returned error 126 (the specified module could not be found).


***


Any help would be greatly appriciated.

Thanks!

Rick Miller
Join the community to see this answer!
Join our exclusive community to see this answer & millions of others.
Unlock 1 Answer and 17 Comments.
Join the Community
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 17 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros