• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 565
  • Last Modified:

Can't print from Excel 2003 SP3 after migrating to Server 2008 Core Print Server

We have some users who can no longer print from Excel after we migrated from a Server 2003 print server to a 2008 Core print server.  These users can all print from all other applications.
The network printers involved with this are a HP LaserJet 4240N, Xerox Phaser 4500N and a Konica Minolta Color Bizhub 450. I have tried every available driver for all of these.

I have tried the spooler cleaning utility.
I have delete all the Office data from the All Users Application Data.
I have even tried to copy and paste the old spread sheets into new sheets.
I have installed all Office Updates.
All of these PC's are XP SP2 and they have the same updates.
This happens on Dell and HP PC's
I have tried reinstalling fonts.
I have changed all of the print quality settings in the drivers and on the printers.

I am simply out of ideas.
0
MMHDU
Asked:
MMHDU
  • 3
  • 3
2 Solutions
 
LongtimeMCSECommented:
So if they open Word and print a document it works - then they open Excel, attempt to print, and what happens?
Error message on the client or server?
Anything in the event log on either machine?
is any data sent to the printer?
0
 
MMHDUAuthor Commented:
The printer(s) will act like they are going to print sometimes and it just doesn't. The PC will show the job go through the queue, but it happens fast then normal.

I have seen no errors and the event logs don't show anything out of the norm.

I will have to use a sniffer to see what data is being sent to the Server. I try to get that info today.
Since the printer acts like it is going to print, I believe data is being sent to the server, but I'm not sure.
0
 
LongtimeMCSECommented:
You can watch the print queue on the server and see if the print job shows...
0
Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
MMHDUAuthor Commented:
Ok,

The clients show nothing in their event logs, but I filtered the logs on the Server 2008 Core Print Server and I found this in the logs:
Log Name:      System
Source:        Microsoft-Windows-PrintSpooler
Date:          2/18/2009 7:46:03 AM
Event ID:      6161
Task Category: None
Level:         Error
Keywords:      Classic
User:          MINSTER\snappr
Computer:      MinsterPS.MINSTER.COM
Description:
The document 600399.XLS, owned by SnappR, failed to print on printer IS01_LJ. Try to print the document again, or restart the print spooler.
Data type: NT EMF 1.008. Size of the spool file in bytes: 1093092. Number of bytes printed: 117391. Total number of pages in the document: 1. Number of pages printed: 0. Client computer: \\172.16.40.87. Win32 error code returned by the print processor: 87. The parameter is incorrect.

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-PrintSpooler" Guid="{e4c60dfa-ecc5-4889-b406-e9ddd38463c8}" EventSourceName="Print" />
    <EventID Qualifiers="49152">6161</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2009-02-18T12:46:03.000Z" />
    <EventRecordID>4542</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>MinsterPS.MINSTER.COM</Computer>
    <Security UserID="S-1-5-21-2110855865-1834110326-1341851483-2739" />
  </System>
  <EventData>
    <Data Name="param1">600399.XLS</Data>
    <Data Name="param2">SnappR</Data>
    <Data Name="param3">IS01_LJ</Data>
    <Data Name="param4">NT EMF 1.008</Data>
    <Data Name="param5">1093092</Data>
    <Data Name="param6">117391</Data>
    <Data Name="param7">1</Data>
    <Data Name="param8">0</Data>
    <Data Name="param9">\\172.16.40.87</Data>
    <Data Name="param10">87</Data>
    <Data Name="param11">The parameter is incorrect.
</Data>
  </EventData>
</Event>
0
 
LongtimeMCSECommented:
Interesting. I *think* you could try sending the jobs in RAW or other than EMF format.
0
 
MMHDUAuthor Commented:
LongtimeMCSE:

You comment lead me to look into advanced printer options. I simply unticked the advanced printing option box and all documents now print fine. Who would have guessed?
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Microsoft Azure 2017

Azure has a changed a lot since it was originally introduce by adding new services and features. Do you know everything you need to about Azure? This course will teach you about the Azure App Service, monitoring and application insights, DevOps, and Team Services.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now