• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 404
  • Last Modified:

Trying to run DCPROMO and then...TERMINATED UNEXPECTEDLY WITH STATUS CODE 128

I'm running a clean, newly-configured Win2K member server and would like to promote it to DC along side (2) other DC's in the same domain.  This is what's happening...

I run DCPROMO from the Run command and answer the first question ("Additional domain controller...").  The next screen comes up, but immediately gives me this message:

...This shutdown was initiated by NT AUTHORITY\SYSTEM
SHUTDOWN TIME: 00:60
THE SYSTEM PROCESS 'C:\WINNT\SYSTEM32\SERVICES.EXE'
TERMINATED UNEXPECTEDLY WITH STATUS CODE 128.  THE SYSTEM
WILL NOW SHUTDOWN & RESTART.

This occurs every time, no fail.  DNS has been setup properly (as seen in http://www.petri.co.il/create_a_new_dns_server_for_ad.htm).


-Steve
0
Elmo_Oxygen
Asked:
Elmo_Oxygen
1 Solution
 
Fatal_ExceptionCommented:
Try this fix"

6520 » 'The system process C:\WINNT\SYSTEM32\SERVICES.EXE terminated unexpectedly with status code 128'?

When you start Windows 2000, you receive:

The system is shutting down. Please save all work in progress and log off. Any unsaved changes will be lost. This shutdown was initiated by NT AUTHORITY\SYSTEM.The system process C:\WINNT\SYSTEM32\SERVICES.EXE terminated unexpectedly with status code 128. The system will shut down and restart.

This behavior will occur if the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Lanmanserver\Shares registry key contains references to non-shared objects.

To fix this problem:

01. Restart your computer.

02. Press F8 when the Please select the operating system to start message is displayed.

03. Select Safe Mode on the Windows Advanced Options menu.

04. If you have multiple operating systems, select the instance of Windows 2000 that has the damaged registry key.

05. Use Regedit.exe to navigate to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\Shares.

06. Press Export Registry File on the Registry menu.

07. Type Save_Shares into the File name box and press Save so that you have a backup.

08. For every Value Name in the right-hand pane, make sure that the Path= value is a valid, existing, shared object, either printer or folder. If the Path= value is not valid, delete the Value Name for this REG_MULTI_SZ data type.

09. Exit the Registry Editor.

10. Restart your computer normally.

http://www.jsiinc.com/SUBN/tip6500/rh6520.htm

FE
0
 
appopCommented:
Steve -


 I would start checking the Basics like,   The Service packs of the other DC's , and the current SP of your machine, also I would check the Ip addresses in the Domain , and that you are using a Unique Ipaddress.  But nontheless I would re-apply the Service pack 4 onto the Dc , as I've seen Corrupt Dll's and executables on the Install Media from time to time..


 Regards

 Appop
0
 
Elmo_OxygenAuthor Commented:
FE & Appop-

I checked for dead shares according to that article, and I did in fact find one.  I had previously installed Exchange 2000, and then uninstalled it upon which it left behind a "MAILxxx.log" share.  I deleted the reg key hoping this would fix it, re-ran SP4, rebooted, but got the same exact error upon running DCPROMO.

I just spent a few hours totally rebuilding this server from scratch.  Latest drivers, security updates, etc.  The only "foreign" app at this point is McAfee.  DNS is configured and then I try DCPROMO which returns the same exact error!

Feel free to check out the debug log (the first attempt at running DCPROMO since server rebuild):
http://home.comcast.net/~sgatzos/EE/dcpromoui.log

0
Cloud Class® Course: Ruby Fundamentals

This course will introduce you to Ruby, as well as teach you about classes, methods, variables, data structures, loops, enumerable methods, and finishing touches.

 
Fatal_ExceptionCommented:
And I assume you have patched it fully...  I have found references to this happening on machines not patched with SP3 and SP4...  very strange to see this in a newly built server..!!
0
 
Elmo_OxygenAuthor Commented:
I troubleshot w/ Microsoft:

They suggested copying over MSConfig.exe from an XP box, launching it, and using the "disable all" services option.  By doing so, I was able to get much further along the dcpromo process.  Now, we had to narrow down the cultprit.

Long story short, by simply disabling the "DNS Client" service, I was able to successfully promote the server to DC, restart the "DNS Client" service, reboot, and confirm that the new DC replicates properly.  I didn't have time to contiue troublshooting as to why the DNS Client service was to blame, so we left it at that.  That was the only workaround that allowed me to dcpromo successfully.  Interestingly enough, I tried this on a totally different stand alone Win 2K server and had the same exact crash, so it wasn't specific to the first box.

Seems like a DNS issue within my domain, but everything is replicating cleanly and have never had any DNS issues!  Regardless, I can put this behind me now.

This can be CLOSED.
0
 
Fatal_ExceptionCommented:
:)
0
 
Elmo_OxygenAuthor Commented:
Hello.  I answered the question myself with my 1-6-2005 post and already requested that it be closed.

Thx.
0
 
moduloCommented:
PAQed with points refunded (300)

modulo
Community Support Moderator
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now