[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 569
  • Last Modified:

Service Pack 4 won't install because netstat.exe is running?

I have a W2K DC (GC/FSMO) that has SP2 and I am trying install SP4 but recieve an error that states
Service Pack 4 won't install because netstat.exe is running. I do not see netstat.exe running under processes.

I have a new server that I installed W2K and promoted to a DC (all latest updates installed). I am upgrading this
to W2K3 and need the other server to be on SP4. I plan on running the GC and FSMO on the new server and
then demoting the old server to member server and then taking it offline for upgrades and a clean install.

Basically I want to fix the netstat.exe error and if I can't should I just Transfer the roles yada yada and then
demote the old DC and then upgrade to W2K3. Then when I bring the old server up and run dcpromo - the
expanded schema will be no problem?
0
tmorrison3
Asked:
tmorrison3
  • 9
  • 8
  • 6
  • +1
1 Solution
 
FocusynCommented:
At what point in the install process are you getting the error?
0
 
kain21Commented:
I would recommend rebuilding the server if you are having problems installing SP4... transfer all the FSMO roles to the new server... demote the old server... upgrade the new server to 2003... verify everything is functioning properly... rebuild the old server with 2000 or 2003 and dcpromo... should work fine... then you can redistribute the roles...
0
 
FocusynCommented:
I just read a post in the MSDN forums about this exact error and exactly when going from SP2 to SP4.  Some users report that upgrading to SP3 and then SP4 successfully worked around this issue.  I would try that.
0
Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

 
tmorrison3Author Commented:
I do not have a disk for SP3 only SP4 - where can I get just SP3?
0
 
Debsyl99Commented:
Hi

SP 3 first is a good idea. Also try start the system in safe mode - locate netstat.exe in the system32 folder, Right click on netstat.exe file, click on security tab and make sure the following users have Full Control permission on the file.
System and Administrators
and that none have deny permission on it. Restart and try it again,

You could also try installing sp4 in safe mode. I think a rebuild may be a bit premature as yet,

Deb :))
0
 
tmorrison3Author Commented:
<At what point in the install process are you getting the error?>

The error occurs when the the update is inspecting your current configuration - Details - performing inventory

Error - the file C:\winnt\system32\netstat.exe is open or in use by another application. Close all other applications and the click retry
0
 
kain21Commented:
here's the link for SP3 http://www.microsoft.com/windows2000/downloads/servicepacks/sp3/default.asp  I still would recommend a rebuild if you can do it... a fresh start never hurts...
0
 
FocusynCommented:
In this case, a fresh start CAN hurt very severely in the case that the machine is a domain controller.  Better to have the replacement running for a week or so before getting in to any rebuild endeavour on your PDC/BDC  lest you missed something.  On clients, I always recommend formatting and reinstalling though.  Just a thought.
0
 
Debsyl99Commented:
What's all this about rebuilds?????? - This error should be troubleshootable - This machine is a DC/GC and FSMO holder. Rebuilding this, transferring roles, apps, data, temp server for AD, - well no need at all on the current info and will cause pain, time, and downtime..........
0
 
tmorrison3Author Commented:
<locate netstat.exe in the system32 folder, Right click on netstat.exe file, click on security tab and make sure the following users have Full Control permission on the file.System and Administrators>

Added administrator will full control - system had full control - no explicit Deny's

This seems to be working as the files are downloading now! I will let you know. I think the system has been compromised
though - Admin account was also Explicitly denied local logon rights a while ago - Format C:\ is needed.


0
 
tmorrison3Author Commented:
I stated a rebuild in my question as that is my intention - Transfer all roles etc. to new server - PDC and then rebuild the old server and dcpromo as additional DC and transfer just infrastruce master role
0
 
Debsyl99Commented:
The error you got was due to lack of access of the administrators account running the sp4 install to that file netstat.exe. The system assumes because it's inaccessible that it must be in use rather than inaccessible due to dodgy permissions. If you really beleive that this system has been compromised, change the admin passwords pronto. If you need to rebuild, then plan it - depends on what you're running, how many users etc, but usually rebuild is the absolute last resort,
0
 
kain21Commented:
He has another domain controller... no downtime would result... demoting a domain controller would not hurt the domain in any way... why troubleshoot when there's a problem if you can rebuild it... takes 2 hours tops... plus you could prevent a problem in the future when the domain controller could crash while having FSMO roles... then you get into having to manually remove a domain controller from active directory (ADSI edit) and so on... being as this server only has SP2 on it I'm assuming it's been running for several years now... a rebuild would not hurt... sure would beat spending 4 to 5 hours trying resolve replication errors in active directory...
0
 
kain21Commented:
one change... when your doing the rebuild... if you are going to put windows 2000 back on the old server... rebuild it prior to upgrading to 2003 and join the domain...  then perform the upgrade to 2003 on the new server...
0
 
Debsyl99Commented:
Ahhhhh - sorry missed your rebuild bit in the initial question - I think I must have been reading another question! Doh !

Wondered why people were on about rebuilds - am normally a little bit more observant so forgive me. Any reason that you didn't just bring the w2k3 server in as is and run adprep /forestprep etc?  So long as you have replication functioning ok across the two DC's - then transfer should be fine, and then when all is replicated acroos you can happily run dcpromo to demote etc. Just make sure if you use dhcp to set that up too.

0
 
kain21Commented:
this will prevent any downtime during the upgrade process
0
 
tmorrison3Author Commented:
My main concern in getting to SP4 is to install 2003 server on the new machine per http://support.microsoft.com/default.aspx?kbid=325379

 
0
 
tmorrison3Author Commented:
From my reading, scanning EE etc. I went with the philosophy that it is better to install W2K on the new server
DCpromo, transfer roles etc. and THEN upgrade to 2003 - since I am in a 2000 native domain. That way I have
a 2003 as my PDC and then adding W2K DC will not be a problem in W2K3 mixed mode.
0
 
kain21Commented:
don't add the w2k dc... promote it back to a dc prior to the upgrade to 2003 on the new server
0
 
Debsyl99Commented:
Yep you need sp4 to upgrade.... hopefully it's going in ok now. I've just spent the last few weeks building a small mirror of our existing network on a test network and running the preps to prepare for introducing w2k3 dc's into our existing production forest so we don't have any downtime either. Great fun with exchange 2000 on the network etc but it's looking good.

I decided to go the forestprep, domainprep route then promo the new 2k3 server. I need to run a fix against the exchange server anyway to prevent the mangled attributes problem, but I tend to go for clean installs rather than upgrades after previously bad experiences with upgrading rather than clean installing on Microsoft kit. No I'm not suggesting for a second you'll have any problems with it, just wondered why in case I'd missed anything....

0
 
tmorrison3Author Commented:
Downloaded SP4 - I will have to wait and reboot - but that seemed to have fixed the problem!

Thanks Debsyl99 and others for your comments/suggestions
0
 
tmorrison3Author Commented:
kain21 - why shouldn't I add a W2K DC to a W2K3 mixed moded Domain?
0
 
kain21Commented:
i can't find any documentation to state whether it will or will not work... once the domain is upgraded to a windows 2003 domain with the new schema you may not be able to join a new 2000 domain controller to the domain... mixed mode is generally an active directory mode designed to allow migration to a 2003 domain... for instance... you upgrade or join a new 2003 domain controller to the domain and leave the other 2000 domain controllers in place until you purchase and have time to upgrade them... this allows for a gradual upgrade process rather than having to do it all at once...
0
 
Debsyl99Commented:
You can add one quite happily - the modifications are mainly with the scema which is propagated to the dc's as and when they are dcpromo'd. Win2k3 supports a number of functional levels - you just can't raise it to win2k3 native mode until all dc's are win2k3 - But that's why you have the mixed mode,
0
 
kain21Commented:
if you decide to go that way tmorrison3 let me know how it went... thanks for the info debsyl99
0
 
tmorrison3Author Commented:
Thats what I thought - as long as the W2K3 is the PDC it will extend schema to W2K DCs - i am going to do it that way
and will verify that it worked fine. THanks
0

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!

  • 9
  • 8
  • 6
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now