Server Problems

shayser

I have a Win2k server on a network as a stand-alone server. It's used for printer and file sharing and one app.

Recently, the shares are getting disconnected and jobs are not printing. The app crashes a few times a week.

If I right-click on any of the printers (7 physical and 14 logical) I get a BSOD. I can cause the BSOD again to get the code, but only if I have to.

I only see one error in the app log and this occurs at reboot time (7am daily) though this scheduled reboot was introduced since the problems started. Don't seem connected to problem, to me.

Error (3 different event IDs but same message):

Event Type: Error
Event Source: Remote Storage
Event Category: (2)
Event ID: 1005 (& 1000 & 905)
Date: 25/09/2007
Time: 07:02:06
User: N/A
Computer: WHITE
Description:
The description for Event ID ( 1005 ) in Source ( Remote Storage ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: Class not registered (0x80040154).
Data:
0000: 72 6d 73 2e 63 70 70 20 rms.cpp
0008: 40 20 20 20 20 35 30 34 @ 504 (& 436 & 884))
0010: 4e 74 20 20 32 31 39 35 Nt 2195
0018: 52 73 20 20 20 34 38 34 Rs 484

There are a couple of warnings in FRS and System logs.

Any ideas at all? Cheers.

homehelptech

Has the app always crashed frequently? If not, is it worth deinstalling/reinstalling.

Have you tried reinstalling the printers or doing a registry cleanup. It's worth a shot.

Capt'n Midnight

What printers do you have ?
Windows 2000 can be unstable with third party printer drivers, best to use the flat microsoft ones instead of installing an exe from the printer maker.

any changes recently, try windows update on the offchance it updates the printer driver

can be a real pain with terminal server when a users printer driver upsets the server

also make sure you have plenty of space on C:


have a look at \winnt\system32\spooler[ - don't delete anything yet - I can't remember the files offhand

Static M.e.

IF you do decide to rebuild MS have a tool called PrintMig (Printer Migration)
which exports all your printers/drivers/setting and then lets you reimport them.

ressem

If you look in the %SystemRoot%\Minidump there might be a dump file created from the last time the server BSODed. Make sure that the creation date is recent.


You can analyse it for the files in which the error occurred using the methods described http://support.microsoft.com/kb/315263
Alternatively, if it's a small dump file you can post it up and someone might point out the files that look wrong.

shayser

Just getting back to this. Some good info here, thanks.