Printing causes program to stop responding

  • Thread starter Thread starter Peggy
  • Start date Start date
P

Peggy

I just got a brand new PC running Windows XP SP2. I'm running as a client on
a Windows Server 2003 domain with Small Business Server. Everything is great,
except a weird problem that often occurs when I print something. After I send
the print job, the program from which I'm printing stops responding, i.e.,
top menu bar is greyed out and I can't close the program. This can happen
within seconds of sending a one-page print job. I've noticed the behavior
when working in Office XP as well as another program. One of the programs is
installed locally but connects me to a database on a Win 2003 server;
likewise, I've had it when opening Word or Excel attachments to e-mail that I
am accessing on the Small Business Server. Therefore I don't know if this is
a network or local PC problem.

If I bring up the desktop and then go back to the program, it usually seems
to resolve. That makes this more of an annoynance than anything else, but I'd
like to get it fixed. Any help is appreciated.

PC is a Dell Vostro 220, NIC is Realtek RTL8168C[P]/8111C[P].
 
Peggy

If this is a brand new PC why are you running Windows XP SP2?

Have a look in the System and Application logs in Event Viewer for
Errors and Warnings and post copies here. Don't post any more than 48
hours ago.

You can access Event Viewer by selecting Start, Control Panel,
Administrative Tools, and Event Viewer. When researching the meaning
of the error, information regarding Event ID, Source and Description
are important.

A tip for posting copies of Error Reports! Run Event Viewer and double
click on the error you want to copy. In the window, which appears is a
button resembling two pages. Click the button and close Event
Viewer.Now start your message (email) and do a paste into the body of
the message. Make sure this is the first paste after exiting from
Event Viewer.

--


Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
 
Gerry,

PC came with SP2. I get updates via WSUS, and SP3 isn't approved as of now.

There are no application errors in the past 48 hours, but there are numerous
DCOM errors in the system log, all the same ID, all relating to other PCs
with printers in the directory.

Example:
******************************
Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10006
Date: 7/16/2009
Time: 11:02:59 AM
User: OURDOMAIN\user
Computer: PCNAME
Description:
DCOM got error "The RPC server is unavailable. " from the computer 1W when
attempting to activate the server:
{5A5AA0AA-1DEB-4683-96B0-B43301E83971}

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
*******************************

A new wrinkle, maybe related and maybe not: I'm connecting to the internet
through the SBS server. Several times today the network logon dialog popped
up when I tried to load a new web page.

Thanks for your help.

Peggy


Gerry said:
Peggy

If this is a brand new PC why are you running Windows XP SP2?

Have a look in the System and Application logs in Event Viewer for
Errors and Warnings and post copies here. Don't post any more than 48
hours ago.

You can access Event Viewer by selecting Start, Control Panel,
Administrative Tools, and Event Viewer. When researching the meaning
of the error, information regarding Event ID, Source and Description
are important.

A tip for posting copies of Error Reports! Run Event Viewer and double
click on the error you want to copy. In the window, which appears is a
button resembling two pages. Click the button and close Event
Viewer.Now start your message (email) and do a paste into the body of
the message. Make sure this is the first paste after exiting from
Event Viewer.

--


Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

I just got a brand new PC running Windows XP SP2. I'm running as a
client on a Windows Server 2003 domain with Small Business Server.
Everything is great, except a weird problem that often occurs when I
print something. After I send the print job, the program from which
I'm printing stops responding, i.e., top menu bar is greyed out and I
can't close the program. This can happen within seconds of sending a
one-page print job. I've noticed the behavior when working in Office
XP as well as another program. One of the programs is installed
locally but connects me to a database on a Win 2003 server; likewise,
I've had it when opening Word or Excel attachments to e-mail that I
am accessing on the Small Business Server. Therefore I don't know if
this is a network or local PC problem.

If I bring up the desktop and then go back to the program, it usually
seems to resolve. That makes this more of an annoynance than anything
else, but I'd like to get it fixed. Any help is appreciated.

PC is a Dell Vostro 220, NIC is Realtek RTL8168C[P]/8111C[P].
Click to expand...
Click to expand...
 
Hi Peggy,
Make sure the machine is clean from malware and viruses and also the SBS
well batched and getting all the security updates, also all permissions set
correct!

I don't what printer you are using but you need to use the Print server on
the SBS or from the Manufacturer of the printer. Allow the printer access on
the Firewall exceptions .

Some info below:
You receive a "The RPC server is unavailable" error message when you open
Disk Management in Windows XP
http://support.microsoft.com/kb/884564


http://www.eventid.net/display.asp?eventid=10006&eventno=272&source=DCOM&phase=1

Subject: RWW & RPC - two related (?) problems
http://www.smallbizserver.net/Default.aspx?tabid=53&forumid=26&tpage=2&view=Topic&postid=32539

<Q::>
Error message when you use Forefront Security: "ERROR: Unable to connect to
service."
http://support.microsoft.com/kb/929072/en


If with these procedures it is not solved, to create the exception in the
firewall of Windows 2008 for the process, it is a good alternative. For it,
we open a console CMD (executed as Administrator) and we give the following
code:

/*Check your settings against this example, if you don't know what all that
mean please get back and ask!*/

netsh advfirewall firewall add rule yam = " Forefront Server Security for
Microsoft Exchange Controller Service " dir = "in" action = "allow" program =
" % ProgramFiles % (x86) \Microsoft Forefront Security\Exchange
Server\FSCController.exe " description = " FF for Exchange 2007 rules to be
able to execute the console of ForeFront " enable = "yes" profile = "domain"
localip = "any" remoteip = "any" localport = " RPC " remoteport = "any"
protocol = " TCP " interfacetype = "any" edge = " not " security =
"notrequired"

Pablo D. Vernocchi
Microsoft Exchange MVP
MCSE + M / MCSE + Sec
Gerry,

PC came with SP2. I get updates via WSUS, and SP3 isn't approved as of now.

There are no application errors in the past 48 hours, but there are numerous
DCOM errors in the system log, all the same ID, all relating to other PCs
with printers in the directory.

Example:
******************************
Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10006
Date: 7/16/2009
Time: 11:02:59 AM
User: OURDOMAIN\user
Computer: PCNAME
Description:
DCOM got error "The RPC server is unavailable. " from the computer 1W when
attempting to activate the server:
{5A5AA0AA-1DEB-4683-96B0-B43301E83971}

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
*******************************

A new wrinkle, maybe related and maybe not: I'm connecting to the internet
through the SBS server. Several times today the network logon dialog popped
up when I tried to load a new web page.

Thanks for your help.

Peggy


Gerry said:
Peggy

If this is a brand new PC why are you running Windows XP SP2?

Have a look in the System and Application logs in Event Viewer for
Errors and Warnings and post copies here. Don't post any more than 48
hours ago.

You can access Event Viewer by selecting Start, Control Panel,
Administrative Tools, and Event Viewer. When researching the meaning
of the error, information regarding Event ID, Source and Description
are important.

A tip for posting copies of Error Reports! Run Event Viewer and double
click on the error you want to copy. In the window, which appears is a
button resembling two pages. Click the button and close Event
Viewer.Now start your message (email) and do a paste into the body of
the message. Make sure this is the first paste after exiting from
Event Viewer.

--


Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

I just got a brand new PC running Windows XP SP2. I'm running as a
client on a Windows Server 2003 domain with Small Business Server.
Everything is great, except a weird problem that often occurs when I
print something. After I send the print job, the program from which
I'm printing stops responding, i.e., top menu bar is greyed out and I
can't close the program. This can happen within seconds of sending a
one-page print job. I've noticed the behavior when working in Office
XP as well as another program. One of the programs is installed
locally but connects me to a database on a Win 2003 server; likewise,
I've had it when opening Word or Excel attachments to e-mail that I
am accessing on the Small Business Server. Therefore I don't know if
this is a network or local PC problem.

If I bring up the desktop and then go back to the program, it usually
seems to resolve. That makes this more of an annoynance than anything
else, but I'd like to get it fixed. Any help is appreciated.

PC is a Dell Vostro 220, NIC is Realtek RTL8168C[P]/8111C[P].
Click to expand...
Click to expand...
Click to expand...
 
Peggy

When you say "SP3 isn't approved as of now." infers you have do not
have a free hand with regard to your computer. Is my understanding
correct?

The DCOM error is a complicated one as indicated by this link:
http://www.eventid.net/display.asp?eventid=10006&eventno=272&source=DCOM&phase=1--Hope this helps.Gerry ~~~~FCAStourport, EnglandEnquire, plan and execute~~~~~~~~~~~~~~~~~~~Peggy wrote:> Gerry,>> PC came with SP2. I get updates via WSUS, and SP3 isn't approved as> of now.>> There are no application errors in the past 48 hours, but there are> numerous DCOM errors in the system log, all the same ID, all relating> to other PCs with printers in the directory.>> Example:> ******************************> Event Type: Error> Event Source: DCOM> Event Category: None> Event ID: 10006> Date: 7/16/2009> Time: 11:02:59 AM> User: OURDOMAIN\user> Computer: PCNAME> Description:> DCOM got error "The RPC server is unavailable. " from the computer 1W> when attempting to activate the server:> {5A5AA0AA-1DEB-4683-96B0-B43301E83971}>> For more information, see Help and Support Center at> http://go.microsoft.com/fwlink/events.asp.> *******************************>> A new wrinkle, maybe related and maybe not: I'm connecting to the> internet through the SBS server. Several times today the network> logon dialog popped up when I tried to load a new web page.>> Thanks for your help.>> Peggy>>> "Gerry" wrote:>>> Peggy>>>> If this is a brand new PC why are you running Windows XP SP2?>>>> Have a look in the System and Application logs in Event Viewer for>> Errors and Warnings and post copies here. Don't post any more than 48>> hours ago.>>>> You can access Event Viewer by selecting Start, Control Panel,>> Administrative Tools, and Event Viewer. When researching the meaning>> of the error, information regarding Event ID, Source and Description>> are important.>>>> A tip for posting copies of Error Reports! Run Event Viewer and>> double click on the error you want to copy. In the window, which>> appears is a button resembling two pages. Click the button and close>> Event Viewer.Now start your message (email) and do a paste into the>> body of the message. Make sure this is the first paste after exiting>> from Event Viewer.>>>> -->>>>>> Hope this helps.>>>> Gerry>> ~~~~>> FCA>> Stourport, England>> Enquire, plan and execute>> ~~~~~~~~~~~~~~~~~~~>>>>>> Peggy wrote:>>> I just got a brand new PC running Windows XP SP2. I'm running as a>>> client on a Windows Server 2003 domain with Small Business Server.>>> Everything is great, except a weird problem that often occurs when I>>> print something. After I send the print job, the program from which>>> I'm printing stops responding, i.e., top menu bar is greyed out and>>> I can't close the program. This can happen within seconds of>>> sending a one-page print job. I've noticed the behavior when>>> working in Office XP as well as another program. One of the>>> programs is installed locally but connects me to a database on a>>> Win 2003 server; likewise, I've had it when opening Word or Excel>>> attachments to e-mail that I am accessing on the Small Business>>> Server. Therefore I don't know if this is a network or local PC>>> problem.>>>>>> If I bring up the desktop and then go back to the program, it>>> usually seems to resolve. That makes this more of an annoynance>>> than anything else, but I'd like to get it fixed. Any help is>>> appreciated.>>>>>> PC is a Dell Vostro 220, NIC is Realtek RTL8168C[P]/8111C[P].
 
Gerry,

I do have administrator rights on my computer, but some functions are
controlled by group policy at the server level. SP3 was initially declined
through Server Management for all client computers as we were not sure
whether it would cause issues with some critical third party software. At
this date it should probably be OK to roll it out.

Peggy

Gerry said:
Peggy

When you say "SP3 isn't approved as of now." infers you have do not
have a free hand with regard to your computer. Is my understanding
correct?

The DCOM error is a complicated one as indicated by this link:
http://www.eventid.net/display.asp?eventid=10006&eventno=272&source=DCOM&phase=1--Hope this helps.Gerry ~~~~FCAStourport, EnglandEnquire, plan and execute~~~~~~~~~~~~~~~~~~~Peggy wrote:> Gerry,>> PC came with SP2. I get updates via WSUS, and SP3 isn't approved as> of now.>> There are no application errors in the past 48 hours, but there are> numerous DCOM errors in the system log, all the same ID, all relating> to other PCs with printers in the directory.>> Example:> ******************************> Event Type: Error> Event Source: DCOM> Event Category: None> Event ID: 10006> Date: 7/16/2009> Time: 11:02:59 AM> User: OURDOMAIN\user> Computer: PCNAME> Description:> DCOM got error "The RPC server is unavailable. " from the computer 1W> when attempting to activate the server:> {5A5AA0AA-1DEB-4683-96B0-B43301E83971}>> For more information, see Help and Support Center at> http://go.microsoft.com/fwlink/events.asp.> *******************************>> A new wrinkle, maybe related and
Click to expand...
maybe not: I'm connecting to the> internet through the SBS server. Several times today the network> logon dialog popped up when I tried to load a new web page.>> Thanks for your help.>> Peggy>>> "Gerry" wrote:>>> Peggy>>>> If this is a brand new PC why are you running Windows XP SP2?>>>> Have a look in the System and Application logs in Event Viewer for>> Errors and Warnings and post copies here. Don't post any more than 48>> hours ago.>>>> You can access Event Viewer by selecting Start, Control Panel,>> Administrative Tools, and Event Viewer. When researching the meaning>> of the error, information regarding Event ID, Source and Description>> are important.>>>> A tip for posting copies of Error Reports! Run Event Viewer and>> double click on the error you want to copy. In the window, which>> appears is a button resembling two pages. Click the button and close>> Event Viewer.Now start your message (email) and do a paste into the>> body of the message. Make sure this is the first
paste after exiting>> from Event Viewer.>>>> -->>>>>> Hope this helps.>>>> Gerry>> ~~~~>> FCA>> Stourport, England>> Enquire, plan and execute>> ~~~~~~~~~~~~~~~~~~~>>>>>> Peggy wrote:>>> I just got a brand new PC running Windows XP SP2. I'm running as a>>> client on a Windows Server 2003 domain with Small Business Server.>>> Everything is great, except a weird problem that often occurs when I>>> print something. After I send the print job, the program from which>>> I'm printing stops responding, i.e., top menu bar is greyed out and>>> I can't close the program. This can happen within seconds of>>> sending a one-page print job. I've noticed the behavior when>>> working in Office XP as well as another program. One of the>>> programs is installed locally but connects me to a database on a>>> Win 2003 server; likewise, I've had it when opening Word or Excel>>> attachments to e-mail that I am accessing on the Small Business>>> Server. Therefore I don't know if this is a network or
local PC>>> problem.>>>>>> If I bring up the desktop and then go back to the program, it>>> usually seems to resolve. That makes this more of an annoynance>>> than anything else, but I'd like to get it fixed. Any help is>>> appreciated.>>>>>> PC is a Dell Vostro 220, NIC is Realtek RTL8168C[P]/8111C[P].
 
Back
Top