More SP4 problems.

[northstardave]

Just a quick datapoint for those who are interested.

After applying SP4 to a brand new out-of-the-box Dell PowerEdge 2650s (dual cpu, 1g ram, no raid) I'm getting blue screens at boot complaining about missing winsrv.dll.

 

[mapleleaf]

northstardave,

If you can get to the %systemroot%\System32 directory with the RC, check and see if WINSRV.DLL is 247kb and dated 06/19/2003.

Just out of interest, how did you update this machine to SP4.

Windows Update, Express from WebSite or downloaded Network Install File ??

Ian

Everyday the Computer Gods pick one person to be "it". Maybe, today is your day !!

 

[northstardave]

I'll check that out & maybe I can put the right one in by hand. I did notice (yesterday) that there was a file present but I did not record the version/date.

The install was done from the Network install file.

thanks for the pointer!! I'll report back.

 

[northstardave]

Ok. I checked it out & winsrv.dll has the characteristics you described. Any ideas?

 

[vick53]

Hey at least you got Service Pack 4 Install ,,we tried on 2 dif machines 1 brand new Dell and 1 Compaq ,,Scenario
Both are inline upgrades from NT 4 to 2000 server ,,and since we just did this I hadnt created a ERD yet,,well anyway,the message states that the update cant be continued and that I need to do a restore because the OS was partial updated and that it may be corrupted,,And of course didnt do the archive feature to do a roll back,,<<i know I know >>we pulled a bone head move ,,but I loaded Service Pack 4 on a Clean install of 2k server and no problem,,any suggestion,,or has anyone else seen this scenario

 

[mapleleaf]

northstardave,

Since this is &quot;brand new&quot;, was Win2K pre-installed ??. It may be worth booting with the Dell Software CD, to see what it finds.

Then, I think I'd try &quot;last known good&quot; at startup, if you can get that far.



Ian

Everyday the Computer Gods pick one person to be &quot;it&quot;. Maybe, today is your day !!

 

[paulray]

SP4 Rolled back. We installed SP4 on 3 servers and 1 WS. We rolled back the Professional due to ADO problems that surfaced on one of our apps. Don't recommend it for workstations that run ADO based apps!

 

[ajwright]

Just ran into first W2Ksp4 related problem. Windows 2000 Adv Svr with Microsoft ISA proxy services installed. Lost networking after install. Now, trying to open properties on the network connection crashes the Network Connections app. I can't get at networking to do anything about it. I've uninstalled sp4, back to sp3, done a Windows 2000 repair and reinstalled the NIC driver, all to no avail. Both on-board NICs properties behave the same way on this fairly new Dell PowerEdge 1650 server. Anyone know how I can get networking going again without being able to get to network properties? --ajwright

 

[pito78]

Hey Northstardave,

Any luck with your winsrv.dll issue? I'm having the same problem with my W2K Advanced Server and all the Documents about winsrv.dll point to NT.

 

[GlenJohnson]

mapleleaf is correct, last known good is worth a try. Tried installing it on my server and desktop, install wouldn't take. Had to re-boot, then went to un-install, same thing. Luckily, I don't seem to have much of a problem besides that.

Glen A. Johnson
Johnson Computer Consulting
MCP W2K
glen@johnsoncomputers.us

http://www.johnsoncomputers.us

Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884
&quot;Watson, the game is afoot!&quot;

 

[northstardave]

Just an update, cause I forgot...

I tried replacing winsrv.dll using a floppy & it was a big no-go. I ended up doing a re-install, applied sp4, & have had no further problems.

 

[dholbrook]

You need to remember that any system &quot;upgraded&quot; from NT is NOT the same as a system built directly from the WIN2k CD. There are file system differences (especially if the NT box was using mirroring or other Raid configurations, since the upgrade will continue to recognize these drives, but a new full Win2k requires the drive to be converted.), and there are probably many other files that are different between the two.

The Service pack, however, assumes you have a full WIn2k clean build, so you may run into severe problems because the files replaced may no longer work in the &quot;updated system&quot;, which is why I recommend a clean build to WIn2k, not an upgrade.

The only exception to this is when converting the PDC in the NT Domain, and even then I recommend using a clean BDC install, no applications, etc., which is promoted to PDC and then converted to be the new WIN2k DC. Once the conversion has been done, and once a second DC is available with the AD copied, rebuild the first system into a clean Win2k server and promote back. Solves a whole lot of headaches. I have not had any issues yet with SP4 on clean built systems, and I have DELL, HP, IBM and other brands.

Just my thoughts,

David