Re: Spooler SubSystem App continuously crashing
- From: "Jan Kucera" <miloush@xxxxxxxxxxxxxxxx>
- Date: Wed, 28 Mar 2007 11:13:49 +0200
Hello Terence,
Thank you for your response. This is only to notify you that I'll try steps you have provided as soon as there will be no people in the office, likely during the weekend. As for your questions I can only answer that this is happening on the SBS R2 server, there are connected these printers at the moment:
HP DesignJet 500 42 by HP ... over USB
HP DesignJet 350C (E/A0) by HP ... on LPT1
Lanier 5222 PCL 6 as a network printer
magicolor 2300 DL as a network printer
The record in Events is like this:
Source: Application Error, Category: 100, Event ID: 1004
Message about queue error: Failing application: spoolsv.exe, version 5.2.3790.1830, failing module RIC622LM.DLL, version 4.0.1381.1, error address 0x0000457c.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 73 70 6f ure spo
0018: 6f 6c 73 76 2e 65 78 65 olsv.exe
0020: 20 35 2e 32 2e 33 37 39 5.2.379
0028: 30 2e 31 38 33 30 20 69 0.1830 i
0030: 6e 20 52 49 43 36 32 32 n RIC622
0038: 4c 4d 2e 44 4c 4c 20 34 LM.DLL 4
0040: 2e 30 2e 31 33 38 31 2e .0.1381.
0048: 31 20 61 74 20 6f 66 66 1 at off
0050: 73 65 74 20 30 30 30 30 set 0000
0058: 34 35 37 63 457c
for case it helps you. The module seems to me as to belong to the Lanier printer, but failure of the spool server results in loosing work being printed on all printers (unfortunately most notable on the HP plotters drawing large projects). So I'd guess the Lanier's driver has a problem (although signed), which we can't resolve. Unless there is possible to run the spool server as an isolated process for each printer, is it?
Thanks,
Jan
"Terence Liu [MSFT]" <v-terliu@xxxxxxxxxxxxxxxxxxxx> wrote in message news:uZ3%23UODcHHA.1820@xxxxxxxxxxxxxxxxxxxxxxxxx
Hello Jan,
Thank you for kind update. And I'm sorry for the unclear description.
This issue may occur if the correct installation and functionality of a
newly installed printer is affected by an existing third-party printer
driver or service. May be you have installed more than one printer on one
computer, or you had installed printer before and the driver did not
cleanly uninstall. All of these will affect on the problematic HP printer.
Since you did not install Lexmark printer, I modify the steps as following,
please perform the following steps:
WARNING: If you use Registry Editor incorrectly, you may cause serious
problems that may require you to reinstall your operating system. Microsoft
cannot guarantee that you can solve problems that result from using
Registry Editor incorrectly. Use Registry Editor at your own risk.
1. Start the computer in Safe mode.
For additional information about starting your computer in Safe mode, click
Start, click Help and Support, type safe mode in the Search box, press
ENTER, and then click the Start Windows in Safe mode topic.
2. Start Windows Explorer, and then delete all files and folders in the
following two folders:
c:\windows\system32\spool\printers
c:\windows\system32\spool\drivers\w32x86
3. Click Start, click Run, type regedit in the Open box, and then press
ENTER.
4. Navigate to and then click the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environment\Window
s NT x86
View the list of subkeys. There should be only the following subkeys:
Drivers
Print Processors
5. If there are any keys other than those listed in step 4, follow these
steps:
a. On the File menu, click Export.
b. In the File Name box, type a descriptive name for this key -- for
example, type WindowsNTx86regkey -- and then click Save.
You can use this backup of the
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environment\Window
s NT x86 registry key to restore the key if you experience any problems
after you complete this procedure.
c. Delete all keys other than those listed in step 4.
6. Navigate to and then click the
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitors registry
key. View the list of subkeys. There should be only the following subkeys:
BJ Language Monitor
Local Port
PJL Language Monitor
Standard TCP/IP Port
USB Monitor
7. If there are any keys other than those listed in step 6, follow these
steps:
a. On the File menu, click Export.
b. In the File Name box, type a descriptive name for this key -- for
example, type WindowsNTx86regkey -- and then click Save.
You can use this backup of the
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitors registry
key to restore the key if you experience any problems after you complete
this procedure.
c. Delete all keys other than those listed in step 6.
8. Disconnect the printer cable from the computer, and then restart the
computer.
9. Reconnect the printer cable to the computer, install the printer
according to the manufacturer's installation instructions, and then try to
print a test page.
If the issue persists, please kindly help me collect some information for
further investigation:
1. Please capture screenshots on the error messages and send the pictures
to me at v-terliu@xxxxxxxxxxxxx
2. Does this issue happen on SBS or on XP clients?
3. Save the application event log and system event log as evt files on the
problematic machines and send to my mailbox: v-terliu@xxxxxxxxxxxxx
Hope these steps will give you some help.
Thanks and have a nice day!
Best regards,
Terence Liu(MSFT)
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.
Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.
For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.
Any input or comments in this thread are highly appreciated.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| Reply-To: "Jan Kucera" <kucera@xxxxxxxxxxxx>
| From: "Jan Kucera" <miloush@xxxxxxxxxxxxxxxx>
| References: <OhTCo5ebHHA.5052@xxxxxxxxxxxxxxxxxxxx>
<OK1LF8ebHHA.3616@xxxxxxxxxxxxxxxxxxxx>
<LelZxU2bHHA.468@xxxxxxxxxxxxxxxxxxxxxx>
| In-Reply-To: <LelZxU2bHHA.468@xxxxxxxxxxxxxxxxxxxxxx>
| Subject: Re: Spooler SubSystem App continuously crashing
| Date: Mon, 26 Mar 2007 16:55:42 +0200
| Lines: 257
| MIME-Version: 1.0
| Content-Type: text/plain;
| format=flowed;
| charset="iso-8859-2";
| reply-type=original
| Content-Transfer-Encoding: 7bit
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Windows Mail 6.0.6000.16386
| X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6000.16386
| Message-ID: <e$h0Vb7bHHA.2300@xxxxxxxxxxxxxxxxxxxx>
| Newsgroups: microsoft.public.windows.server.sbs
| NNTP-Posting-Host: 176-207-207-85.strcechy.adsl-llu.static.bluetone.cz
85.207.207.176
| Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP06.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:25413
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| Hello Terence,
| thank you very much for your response. In fact I'm not trying to add
any
| printer. Before I set the automatically restart of service, the problem
for
| example happened when the plotter was printing (HP), in process of which
the
| spooler crashed and the drawing had gone. Until I restarted the service,
no
| more documents could have been printed.
|
| You suggest this is caused by the printer driver, or third party
| service?
|
| Thanks
| Jan
|
|
|
| "Terence Liu [MSFT]" <v-terliu@xxxxxxxxxxxxxxxxxxxx> wrote in message
| news:LelZxU2bHHA.468@xxxxxxxxxxxxxxxxxxxxxxxxx
| > Hello Jan,
| >
| > Thank you for posting here.
| >
| > According to your description, I understand that the you got error
message
| > about Spooler SubSystem App when you start the computer. If I have
| > misunderstood the problem, please don't hesitate to let me know.
| >
| > Based on my research, This issue may occur if a third-party printer
driver
| > or a third-party service that is installed prevents you from adding
| > printers, or if the third-party printer driver or the third-party
service
| > affects the functionality of a newly installed printer.
| >
| > For example, this issue may occur if the Lexmark print service (LexBce
| > Server service) is installed and is running on your computer before you
| > try
| > to add another printer.
| >
| > I suggest we try the following steps to see if we can resolve this
issue:
| >
| > Warning: If you use Registry Editor incorrectly, you may cause serious
| > problems that may require you to reinstall your operating system.
| > Microsoft
| > cannot guarantee that you can solve problems that result from using
| > Registry Editor incorrectly. Use Registry Editor at your own risk.
| >
| > 1. If the Lexmark print service is installed on your computer, turn off
| > the LexBce Server service. To do this, follow these steps:
| > a. Click Start, right-click My Computer, and then click Manage.
| > b. Expand Services and Applications, and then click Services.
| > c. In the right pane, right-click LexBce Server, and then click
| > Properties.
| > d. On the General tab, in the Startup type list, click Disabled.
| > e. Under Service status, click Stop, and then click OK.
| > f. Right-click the Print Spooler service, and then click Start (if it
is
| > stopped).
| > g. Quit Computer Management.
| >
| > 2. Test whether the issue is resolved. If the issue is resolved, you do
| > not have to follow the remaining steps. If the issue is not resolved,
go
| > to
| > step 3, and then follow the remaining steps.
| >
| > 3. Start the computer in Safe Mode.
| >
| > For additional information about how to start your computer in Safe
Mode,
| > click Start, click Help and Support, type safe mode in the Search box,
| > press the ENTER key, and then click the Start Windows in Safe Mode
topic.
| >
| > 4. Start Microsoft Windows Explorer, and then delete all the files and
| > the
| > folders in the following two folders:
| > C:\Windows\System32\Spool\Printers
| > C:\Windows\System32\Spool\Drivers\w32x86
| >
| > 5. Start Registry Editor. To do this, click Start, click Run, type
| > regedit
| > in the Open box, and then click OK.
| >
| > 6. Locate and expand the following registry key:
| >
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windo
| > ws NT x86
| > View the list of subkeys. There should only be the following subkeys:
| > Drivers
| > Print Processors
| >
| > 7. If there are any subkeys other than the subkeys that are listed in
| > step
| > 6, follow these steps:
| > a. On the File menu, click Export.
| > b. In the File Name box, type a descriptive name for this key, and then
| > click Save--for example, type WindowsNTx86regkey .
| >
| > You can use this backup of the
| >
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windo
| > ws NT x86 registry key to restore the key if you experience any issues
| > after you complete this procedure.
| >
| > c. Delete all the subkeys other than the subkeys that are listed in
step
| > 6. To do this, right-click each subkey that is not on the list, and then
| > click Delete. Click Yes when you are prompted to confirm the deletion.
| >
| > 8. Locate and then expand the following registry key:
| >
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windo
| > ws NT x86\Drivers
| > The registry entries for the printer drivers that are installed on the
| > computer are stored in the Version- x subkey or subkeys, where x is a
| > number (typically 2 or 3).
| >
| > 9. Expand the Version- x subkey or subkeys, and then delete the printer
| > driver entries. To do this, right-click each printer driver subkey, and
| > then click Delete. Click Yes when you are prompted to confirm the
| > deletion.
| >
| >
| > 10. Locate and then expand the following registry key:
| > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitors
| > View the list of subkeys. There should only be the following subkeys for
| > the default print monitors:
| > BJ Language Monitor
| > Local Port
| > PJL Language Monitor
| > Standard TCP/IP Port
| > USB Monitor
| >
| > 11. If there are any subkeys other than the subkeys that are listed in
| > step 10, follow these steps:
| > a. On the File menu, click Export.
| > b. In the File Name box, type a descriptive name for this key -- for
| > example, type MonitorsRegkey , and then click Save.
| >
| > You can use this backup of the
| > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitors
| > registry
| > key to restore the key if you experience any issues after you complete
| > this
| > procedure.
| >
| > c. Delete all the subkeys other than the subkeys that are listed in
step
| > 10. To do this, right-click each subkey that is not on the list, and
then
| > click Delete. Click Yes when you are prompted to confirm the deletion.
| >
| > 12. If you have a local printer attached, disconnect the printer cable
| > from the computer, and then restart the computer.
| >
| > 13. Verify that the Print Spooler service is running. To do this,
follow
| > these steps:
| > a. Click Start, right-click My Computer, and then click Manage.
| > b. Expand Services and Applications, and then click Services.
| > c. In the right pane, right-click the Print Spooler service, and then
| > click Start (if it is stopped).
| > d. Quit Computer Management.
| >
| > 14. If you have a local printer attached, reconnect the printer cable
to
| > the computer, add the printer that you want, and then try to print a
test
| > page. To add your printer, follow these steps:
| > a. Click Start, and then click Printers and Faxes.
| > b. Click Add a printer.
| >
| > The Add Printer Wizard starts.
| >
| > c. Follow the instructions in the Add Printer Wizard to install the
| > printer that you want.
| >
| > If the issue persists, please kindly help me collect some information
for
| > further investigation:
| >
| > 1. Please capture screenshots on the error messages and send the
pictures
| > to me at v-terliu@xxxxxxxxxxxxx
| >
| > 2. Does this issue happen on SBS or on XP clients?
| >
| > 3. Save the application event log and system event log as evt files on
the
| > problematic machines and send to my mailbox: v-terliu@xxxxxxxxxxxxx
| >
| > Hope these steps will give you some help.
| >
| > Thanks and have a nice day!
| >
| > Best regards,
| >
| > Terence Liu(MSFT)
| >
| > Microsoft CSS Online Newsgroup Support
| >
| > Get Secure! - www.microsoft.com/security
| >
| > =====================================================
| > This newsgroup only focuses on SBS technical issues. If you have issues
| > regarding other Microsoft products, you'd better post in the
corresponding
| > newsgroups so that they can be resolved in an efficient and timely
manner.
| > You can locate the newsgroup here:
| > http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
| >
| > When opening a new thread via the web interface, we recommend you check
| > the
| > "Notify me of replies" box to receive e-mail notifications when there
are
| > any updates in your thread. When responding to posts via your
newsreader,
| > please "Reply to Group" so that others may learn and benefit from your
| > issue.
| >
| > Microsoft engineers can only focus on one issue per thread. Although we
| > provide other information for your reference, we recommend you post
| > different incidents in different threads to keep the thread clean. In
| > doing
| > so, it will ensure your issues are resolved in a timely manner.
| >
| > For urgent issues, you may want to contact Microsoft CSS directly.
Please
| > check http://support.microsoft.com for regional support phone numbers.
| >
| > Any input or comments in this thread are highly appreciated.
| > =====================================================
| >
| > This posting is provided "AS IS" with no warranties, and confers no
| > rights.
| >
| > --------------------
| > | Reply-To: "Jan Kucera" <kucera@xxxxxxxxxxxx>
| > | From: "Jan Kucera" <miloush@xxxxxxxxxxxxxxxx>
| > | References: <OhTCo5ebHHA.5052@xxxxxxxxxxxxxxxxxxxx>
| > | In-Reply-To: <OhTCo5ebHHA.5052@xxxxxxxxxxxxxxxxxxxx>
| > | Subject: Re: Spooler SubSystem App continuously crashing
| > | Date: Sat, 24 Mar 2007 09:32:33 +0100
| > | Lines: 14
| > | MIME-Version: 1.0
| > | Content-Type: text/plain;
| > | format=flowed;
| > | charset="iso-8859-2";
| > | reply-type=response
| > | Content-Transfer-Encoding: 7bit
| > | X-Priority: 3
| > | X-MSMail-Priority: Normal
| > | X-Newsreader: Microsoft Windows Mail 6.0.6000.16386
| > | X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6000.16386
| > | Message-ID: <OK1LF8ebHHA.3616@xxxxxxxxxxxxxxxxxxxx>
| > | Newsgroups: microsoft.public.windows.server.sbs
| > | NNTP-Posting-Host: 176-207-207-85.strcechy.adsl-llu.static.bluetone.cz
| > 85.207.207.176
| > | Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP05.phx.gbl
| > | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:25141
| > | X-Tomcat-NG: microsoft.public.windows.server.sbs
| > |
| > | Well actually on login I only get all the crashed informations.
| > | And I have set to automatically restart service after failure (every
| > | failure).
| > |
| > |
| > | "Jan Kucera" <miloush@xxxxxxxxxxxxxxxx> wrote in message
| > | news:OhTCo5ebHHA.5052@xxxxxxxxxxxxxxxxxxxxxxx
| > | > Hi,
| > | > on every system startup (after login) this service keeps crashing.
| > What
| > | > can I do with it?
| > | >
| > | > Thanks,
| > | > Jan
| > |
| > |
| >
|
|
.
- Follow-Ups:
- Re: Spooler SubSystem App continuously crashing
- From: Terence Liu [MSFT]
- Re: Spooler SubSystem App continuously crashing
- References:
- Spooler SubSystem App continuously crashing
- From: Jan Kucera
- Re: Spooler SubSystem App continuously crashing
- From: Jan Kucera
- Re: Spooler SubSystem App continuously crashing
- From: Terence Liu [MSFT]
- Re: Spooler SubSystem App continuously crashing
- From: Jan Kucera
- Re: Spooler SubSystem App continuously crashing
- From: Terence Liu [MSFT]
- Spooler SubSystem App continuously crashing
- Prev by Date: Re: VPN Error 721 on one machine, others work
- Next by Date: Re: Retain Original Recipient (To-) Address with POP3 Connector
- Previous by thread: Re: Spooler SubSystem App continuously crashing
- Next by thread: Re: Spooler SubSystem App continuously crashing
- Index(es):
Relevant Pages
|
Loading