Office 2013
We added out first machine to the domain running Office 2013. The machine is an HP Z4xx class machine, Windows 7 Pro 64 bit, 16 gigs of RAM.
The network printer selected is an HP LaserJet M5035 MFP. There has been no issue using this as a network printer for other Win 7 64 bit clients to date until we got the Office 2013. I have no local printers available to run further tests against the problem.
The problem is that once a print job iscalled on from one of the Office 2013 programs, you may print once successfully and after that, the program you are printing from falls into an unresponsive state. After that happens, the printer remains in a spool state until the unresponsive program halts, the job in the queue removed, and the machine is logged off and logged back on.
There seems to be many complaints about this issue and many a registry edit, a few I've tried without resolution. Some suggest this is an issue using the suite without a Sky Drive account. (Hope not). I am wondering if anyone else has come across this problem. All things being equal with the other Win 7 pro machines, I'm convinced the root cause is Office 2013.
The network printer selected is an HP LaserJet M5035 MFP. There has been no issue using this as a network printer for other Win 7 64 bit clients to date until we got the Office 2013. I have no local printers available to run further tests against the problem.
The problem is that once a print job iscalled on from one of the Office 2013 programs, you may print once successfully and after that, the program you are printing from falls into an unresponsive state. After that happens, the printer remains in a spool state until the unresponsive program halts, the job in the queue removed, and the machine is logged off and logged back on.
There seems to be many complaints about this issue and many a registry edit, a few I've tried without resolution. Some suggest this is an issue using the suite without a Sky Drive account. (Hope not). I am wondering if anyone else has come across this problem. All things being equal with the other Win 7 pro machines, I'm convinced the root cause is Office 2013.
SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
Thank you I will have to try that when the user is not here, most likely Friday.
For my education, would you mind informing as to the difference between LPR and TCP/IP printing? Currently, the printer is not tied to a print server but does have a fixed IP address from the DHCP manager as passed out by the domain controller. I created a local TCP/IP port to print to the device. As stated, no other Win 7 64 bit clients have this issue when running Office 2010.
Thank you.
For my education, would you mind informing as to the difference between LPR and TCP/IP printing? Currently, the printer is not tied to a print server but does have a fixed IP address from the DHCP manager as passed out by the domain controller. I created a local TCP/IP port to print to the device. As stated, no other Win 7 64 bit clients have this issue when running Office 2010.
Thank you.
SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
Good. I will try that. On hold until Friday.
ASKER
Many solutions were offered on this one from both inside and outside the EE community.
Thanks to all.
I built a duplicate environment to replicate the problem. That was not a problem. I decided to apply the most simple suggested fixes first and move to the progressively more complicated solutions.
Yep. The simple one seems to have worked.
Printer Properties/Device Settings/Installable Options/Printer Status Notifications
Change from Enable to Disable.
Log off, log back on.
It appears, so far, that the HP and some Epson hardware hangs the offending dll file when notifications are enabled.
The duplicate environment will become my owner's new machine, and he has a Brother local printer. I'll let you know if that too has an issue with 2013. The other Win 7 64x users have both the HP MFP network and Brother local printers against Office 2010, no problem. I guess 2013 has some issues in that regard.
I climb out on the bleeding edge and get cut? Never happens...
Thanks!
Thanks to all.
I built a duplicate environment to replicate the problem. That was not a problem. I decided to apply the most simple suggested fixes first and move to the progressively more complicated solutions.
Yep. The simple one seems to have worked.
Printer Properties/Device Settings/Installable Options/Printer Status Notifications
Change from Enable to Disable.
Log off, log back on.
It appears, so far, that the HP and some Epson hardware hangs the offending dll file when notifications are enabled.
The duplicate environment will become my owner's new machine, and he has a Brother local printer. I'll let you know if that too has an issue with 2013. The other Win 7 64x users have both the HP MFP network and Brother local printers against Office 2010, no problem. I guess 2013 has some issues in that regard.
I climb out on the bleeding edge and get cut? Never happens...
Thanks!
ASKER
My solution is the one I used, not to discount the ones offered here, but that solution was not offered here. Good information has been offered here for the future.
Thanks.
Thanks.
ASKER
OK, EE kept telling me I MUST assign 20 points to EVERY answer?
This is new to me and I screwed it up...
Much appreciated...
This is new to me and I screwed it up...
Much appreciated...
@afrend - Thank you and thanks for the update. ... Thinkpads_User
ASKER
Thanks.