Network printer not printing on 32bit Windows

I recently migrated all of our printers to a new file and print server running Windows Sever 2008 R2. All printers are working correctly except for my Dell 2335dn. I downloaded the latest drivers from Dell and they installed correctly. Both the x86 and x64 bit versions are nstalled. The printer will print just fine from x64 but not on 32bit machines. I even tried a later driver and still not working. This is occuring on all of my 2335's. The driver will install on the OS but will not print at all. It errors before I can even send the document. Any help would be greatly appreciated,.

Thanks
NNarelAsked:
Who is Participating?
 
dew_associatesCommented:
According to Microsoft, the best solution is to try removing the printer AND the driver.

I'm not sitting at a console, so bear with me as I believe this should be the procedure.

Go to the Control Panel and click Printers

Right-click on the white space and click "Run as administrator > Server Properties"

Click on the "Drivers" tab, click on the offending printer and click on the "Remove" button

When prompted, click "Remove driver and driver package."
Answer "Yes" when prompted to delete the driver.

You will then see a dialog indicating that driver package information has been collected. Click on the "Delete" button.

Back in the printer list, delete the offending printer by clicking on it and pressing the Delete key on your keyboard.

If the printer refuse to be deleted, note the files the printer driver uses and delete.

"Drivers" tab, click the printer and click properties. Sort the "File" column alphabetically by clicking on the heading. Write down the files involved and also write down the "driver path" above the "File" column. Delete these files in, then repeat the removal procedure above.

Reboot the server and then reinstall the drivers as noted in my earlier post.
0
 
JohnnyCanuckCommented:
Can you roll back the driver, maybe the one on the original CD?
0
 
vaderjCommented:
are you receiving any errors in the event log?
0
How do you know if your security is working?

Protecting your business doesn’t have to mean sifting through endless alerts and notifications. With WatchGuard Total Security Suite, you can feel confident that your business is secure, meaning you can get back to the things that have been sitting on your to-do list.

 
NNarelAuthor Commented:
I have used the original driver from the CD as well as the one newest one from Dell's website
0
 
NNarelAuthor Commented:
I am not receiing any errors. I just get a message saying I cannot print.

"An error occured when trying to print." Please contact your administrator"
0
 
Dr. KlahnPrincipal Software EngineerCommented:
I've requested that this question be deleted for the following reason:

This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
0
 
NNarelAuthor Commented:
Noone has answered my question. Or tried to. Where are my genius' at?
0
 
James HaywoodCommented:
What is the client OS you are trying to print from?
0
 
dew_associatesCommented:
Installing 32 Bit printer drivers on a 64 Bit server:

· Login using a domain administrator account to a 32 bit machine.

· On any one of the clients machine running 32-bit OS

· Access the print server \\PrintserverName\Printers

· Open the printer required to add the 32-bit driver

· Go to properties -> Sharing Tab -> Additional drivers

· Check the box with appropriate architecture type.

In this case it is nothing but using the same steps as in the x64 driver scenario, but in this case the additional driver we will be adding will be a 32bit driver.

Common Issues seen while installing a 32-bit driver on a 64-bit server and vice versa.

1) Option to choose OS architecture i.e. x64 could be grayed out.

2) You may see the error ‘Driver is not installed.’

3) You may see architecture incompatibility errors while trying to install drivers.

The x64 option could be grayed out or not visible if the OS on the print server doesn’t support or is not aware of the x64 architecture. A good example is Windows 2000 print servers where you cannot add an x64 driver.

The option is also grayed out in Windows Server 2003 RTM (without any Service Pack)

The ‘Driver is not installed’ error can occur if the additional driver you installed doesn’t match the existing driver in name and INF parameters.

These names need to be the same if the driver installation is to go through without errors.

An example of this is a recent case I was working where we needed to install a 32-bit driver for an already present (inbox) HP LaserJet 8150 PCL 5 x64 driver.

The obvious thing to do first was to obtain the 32-bit driver from the OEM website for installation. Upon looking for the HP LaserJet 8150 PCL 5 (32 bit) driver, we find that vendor gives us the option to download HP Universal Print Driver for Windows PCL 6. Hence we downloaded and tried installing it, but this failed.

The problem was that when we were using the inbox 64-bit driver to install the HP LaserJet 8150 PCL 6 driver, the actual driver is named “HP LaserJet 8150 Series PCL6”.

However, the HP LaserJet 8150 PCL 6 (32-bit driver) from the HP website is named “HP Universal Printing PCL 6”.

As you see, the names are different and hence the installation errors out. The same installation goes through successfully if we download the HP LaserJet PCL 6 32-bit driver from the website. This is because the driver is named “HP Universal Printing PCL 6”, which is the same name as the 64-bit driver.

0
 
NNarelAuthor Commented:
I have tried installing the printer on both Windows 7 32bit as well as XP and I still get the same error message.

I have downloaded both the correct driver from the Dell website for the printer. The 64bit version automatically installed the 32bit version of the driver as well.
0
 
dew_associatesCommented:
You're performing the procedure I laid out on the server, not your work stations. Read the instructions carefully and follow them to the letter.
0
 
NNarelAuthor Commented:
Yes I did everything exactly like that before you posted your comment. I am still getting the error on 32bit workstations. I have rolled back the driver as well and instlled the correct version of both from the Dell CD that came with the printer.
0
 
dew_associatesCommented:
You had none of the common issues arise?
0
 
NNarelAuthor Commented:
No. The 32bit driver installs with the 64bit one under the additional driver tab. I do not have to install one seperately. It still gives me the error after this is done. I didnt run into any of the common issues.
0
 
dew_associatesCommented:
So you have both drivers, 32-bit and 64-bit installed?
0
 
NNarelAuthor Commented:
That is correct. The driver will work on 64bit OS but not 32bit.
0
 
dew_associatesCommented:
Okay, let me ask the question in a different way.

In order for you to do as you wish, you need both drivers, 32-bit and 64-bit installed on the server and named as noted above.

So you have both drivers installed on the server?
0
 
NNarelAuthor Commented:
Yes both are installed
0
 
NNarelAuthor Commented:
Here is an image of the additional drivers page showing they are both installed
drivers.png
0
 
James HaywoodCommented:
Can you get the printer installed on a workstation manually? Just to check the drivers actually work
0
 
NNarelAuthor Commented:
A week ago I could install the printer without any issue. Now anytime I try to print a test page, change any setting, print from the client side, the print service on the server errors out and shows all the printers offline even though they are not. I cannot work on the printers at all due to the print spooler service erroring out. This is the log file from the server showing the error:

  - Provider

   [ Name]  Application Error
 
  - EventID 1000

   [ Qualifiers]  0
 
   Level 2
 
   Task 100
 
   Keywords 0x80000000000000
 
  - TimeCreated

   [ SystemTime]  2012-02-01T21:45:21.000000000Z
 
   EventRecordID 6677
 
   Channel Application
 
   Computer JOLFP1.CC.CraneEM.int
 
   Security
 

- EventData

   spoolsv.exe
   6.1.7601.17514
   4ce7b4e7
   sdf1m.dll
   0.3.0.0
   4b9726a8
   c0000005
   0000000000054ee3
   df0
   01cce12ac47982f9
   C:\Windows\System32\spoolsv.exe
   C:\Windows\system32\spool\DRIVERS\x64\3\sdf1m.dll
   096c0ea3-4d1e-11e1-b7ae-00155d01141a
0
 
dew_associatesCommented:
Okay, before we go too much further, what have you changed between a week ago and now that may be causing this problem?
0
 
NNarelAuthor Commented:
Absolutely nothing. I tried to print from the server to test it again and now the print spooler just errors out constatntly
0
 
dew_associatesCommented:
Given this change in facts, I suspect that you don't have a driver issue at all, but rather a communication issue or a settings issue on your network.

Anything in any of the event logs, especially with regard to the spooler service?
0
 
NNarelAuthor Commented:
only thing I can find is what I posted previously and this information error as well

- System

  - Provider

   [ Name]  Windows Error Reporting
 
  - EventID 1001

   [ Qualifiers]  0
 
   Level 4
 
   Task 0
 
   Keywords 0x80000000000000
 
  - TimeCreated

   [ SystemTime]  2012-02-01T21:19:22.000000000Z
 
   EventRecordID 6665
 
   Channel Application
 
   Computer JOLFP1.CC.CraneEM.int
 
   Security
 

- EventData

   
   0
   APPCRASH
   Not available
   0
   spoolsv.exe
   6.1.7601.17514
   4ce7b4e7
   sdf1m.dll
   0.3.0.0
   4b9726a8
   c0000005
   0000000000054ee3
   
   
   
   C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_spoolsv.exe_44997aef85423b5e4d62c0ec1d5d89fc991151_a4633daa
   
   0
   68a5b01c-4d1a-11e1-b7ae-00155d01141a
   4
0
 
NNarelAuthor Commented:
I also found error containing this: Document failed to print and was deleted because of corruption in the spooled file. The associated driver is trying to print the document again.

This would occur when just trying to print a test page from the server
0
 
NNarelAuthor Commented:
I am unable to do a server reboot until the weekend. I will uninstall the printers in the meantime and try this. I will get back to you after I have rebooted the server and tried the reinstallation of the printers
0
 
dew_associatesCommented:
We'll be waiting
0
 
NNarelAuthor Commented:
I've requested that this question be deleted for the following reason:

Never got required answer
0
 
dew_associatesCommented:
Questioner never responded to the last request.
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.

All Courses

From novice to tech pro — start learning today.