G
Guest
The print spooler on my TS keeps crashing. The event log shows the following:
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7023
Date: 3/31/2005
Time: 12:30:33 PM
User: N/A
Computer: SBTS1
Description:
The Print Spooler service terminated with the following error:
The access code is invalid.
Background: A week ago a print server crashed and died. This print server
hosted several network printers for the TS. Because everyone connects to the
same network printers, these printers are listed over and over again as the
TS loads them for each person who logs onto the TS. My brilliant (?) idea
was to have the TS act as the print server for two of these network printers.
My reasoning was that way the TS users would not have to load these printers
on their local machines, and each network printer would only show up once on
the TS for everybody.
Other Possibility:
Some of the TS Profiles, when loaded, are still looking for the network
printers on the old crashed print server. Could the fact that these profiles
are trying to connect to a printer/print server that no longer exists cause
the print spooler to crash?
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7023
Date: 3/31/2005
Time: 12:30:33 PM
User: N/A
Computer: SBTS1
Description:
The Print Spooler service terminated with the following error:
The access code is invalid.
Background: A week ago a print server crashed and died. This print server
hosted several network printers for the TS. Because everyone connects to the
same network printers, these printers are listed over and over again as the
TS loads them for each person who logs onto the TS. My brilliant (?) idea
was to have the TS act as the print server for two of these network printers.
My reasoning was that way the TS users would not have to load these printers
on their local machines, and each network printer would only show up once on
the TS for everybody.
Other Possibility:
Some of the TS Profiles, when loaded, are still looking for the network
printers on the old crashed print server. Could the fact that these profiles
are trying to connect to a printer/print server that no longer exists cause
the print spooler to crash?