Re: SBS Server 2003 R2 Premium

I was only thinking DHCP if you had two SBS boxes on the same LAN, so that's probably not an issue. The files I mentioned to delete are spooled print jobs. Those directories should be empty unless there are jobs queued. Sometimes when jobs fail to print, they leave the files behind, and that can cause issues for future jobs (you won't always see a job in the queue just because there are files in that spool directory). I'm guessing that since all the client PCs are having this issue, if there are files that need to be deleted, they're on the server. But, it wouldn't hurt to check one of the clients as well.

You can't print a test page from the server? And some of the printers work? In that case, I think I'd delete the problem printer and reinstall it from scratch. If you have the choice between just a plain driver, or a whole software program, I'd just install the driver. And unless you have the need for one of these applications, I'd uninstall the HP printer apps from the server as well. Whatever you reinstall, I'd do it from newly downloaded drivers from hp.com.

Good thing I didn't put any money on this one - I would have bet on the leftover printers from the old server, just as Les suggested. I've seen some real messes from that, including not only print failures, but spooler crashes and blue screens.


"Beach, Walter" <wbeach@xxxxxxxxxxxxxxxxxx> wrote in message news:C0B71683-9230-40A0-9601-528422374408@xxxxxxxxxxxxxxxx
(Are you running two SBS networks on the same physical
>LAN?

No, the old server has actually failed and can not be booted anymore, so unfortunately I can't even make any comparisons any more.

If so, maybe you've got a DHCP problem? If so, please check/fix or
>post back if that's your configuration).

I don't believe this is a DHCP problem. My server is using a static IP addresss and the printer was configured at one point with a Static IP with no result.

It is currently using a DHCP reservation which matches its old configuration.

Please post back the exact symptom you get when print jobs "fail immediately." Do you get an error message, and if so, what's the exact message?

Generic Printer, but here is exactly what it says.

Printer Properties: Test page failed to print. Would you like to view the print troubleshooter for assistance.
Notepad: The handle is invalid.
IE7: www.google.ca - Script error: An error has occured in the script on this page
Wordpad: It appears to print, but it never enters the queue and nothing comes form the printer.

Any relevant errors in the logs of the SBS and the client PCs when these jobs fail?

Nothing relevant found, I see print jobs going to the other printers and that they were successful

I'm assuming no one is trying to print to these printers - if so, please ask them to stop. On the SBS, open Printers and Faxes and switch to Details view. Under Documents, do all the printers show 0 documents queued? If not, please dbl-click the printers and delete the jobs from the queue.

Any attempts to print to the printer comes up with an immediate failure or it will appear to work, but nothing gets printed.

If we are just talking about the printers having issues then the print queues are empty.

Now go to C:\WINDOWS\system32\spool\PRINTERS. Any files there? If so, please delete them to the recycle bin. You may have to stop the Print Spooler service while deleting the files, then restart it. At some point, you're going to want to do this for the same folder on the client PCs.

What are these files used for? They should just be local print spooler files created when people print. I'm guessing you want me to delete them to confirm the spool is empty

Make sure that the latest operating-system appropriate drivers are installed on the SBS and the client PCs.

Using current drivers.

Make sure the client PCs are not showing any printer twice, or as attached to an inappropriate host. For example, you should not see HP Laserjet 1300 on OldSBS and HP Laserjet 1300 on NewSBS. Delete any "extra" printers other than those you expect to see based on the installation on the new server.

I have verified the old printers are gone.

Please resist the temptation to conduct any experiments based on WAGs from HP support. They should be diagnosing this, not just throwing out suggestions hoping to luck into one that works. This is especially true for anything that's a lot of work or doesn't have a clear path back from.

I understand I never do things that don't make any sense or does not have a logical reason for it. Such as registry or system file changes.

If you go through all of the above without results, the last thing to do is to go to Printers and Faxes -> File -> Server Properties -> Advanced tab. After noting the existing settings for undo purposes, turn on all the logging options and see if you get anything useful in the system or application log when a job fails.


I currently already having all logging on and it is not providing any useful information.

"Dave Nickason [SBS MVP]" <gwdibble@xxxxxxxxxxxxxxxxxxxxxx> wrote in message news:OPDO%23I$%23IHA.528@xxxxxxxxxxxxxxxxxxxxxxx
At a quick read, it sounds like you've ruled out problems with the printers themselves, the print server, and the network. So that leaves the client PCs and the new SBS. (Are you running two SBS networks on the same physical LAN? If so, maybe you've got a DHCP problem? If so, please check/fix or post back if that's your configuration).

Please post back the exact symptom you get when print jobs "fail immediately." Do you get an error message, and if so, what's the exact message?

Any relevant errors in the logs of the SBS and the client PCs when these jobs fail?

I'm assuming no one is trying to print to these printers - if so, please ask them to stop. On the SBS, open Printers and Faxes and switch to Details view. Under Documents, do all the printers show 0 documents queued? If not, please dbl-click the printers and delete the jobs from the queue.

Now go to C:\WINDOWS\system32\spool\PRINTERS. Any files there? If so, please delete them to the recycle bin. You may have to stop the Print Spooler service while deleting the files, then restart it. At some point, you're going to want to do this for the same folder on the client PCs.

Make sure that the latest operating-system appropriate drivers are installed on the SBS and the client PCs.

Make sure the client PCs are not showing any printer twice, or as attached to an inappropriate host. For example, you should not see HP Laserjet 1300 on OldSBS and HP Laserjet 1300 on NewSBS. Delete any "extra" printers other than those you expect to see based on the installation on the new server.

Please resist the temptation to conduct any experiments based on WAGs from HP support. They should be diagnosing this, not just throwing out suggestions hoping to luck into one that works. This is especially true for anything that's a lot of work or doesn't have a clear path back from.

If you go through all of the above without results, the last thing to do is to go to Printers and Faxes -> File -> Server Properties -> Advanced tab. After noting the existing settings for undo purposes, turn on all the logging options and see if you get anything useful in the system or application log when a job fails.

"Beach, Walter" <wbeach@xxxxxxxxxxxxxxxxxx> wrote in message news:030D9F03-8391-451A-9124-2429E9948B13@xxxxxxxxxxxxxxxx
Hello,

I know this is going to be a weird question, but I don't know where else to turn.

I currently needed to replace a Windows Server 2003 SBS server. What I did was load up a new SBS server with a new domain name and basically recreated all the roles from scratch. I then migrated all the data to the new server.

Everything was working fine except the HP printer in the environment. They for some reason will not print and will fail immediately.

I can ping them, I can browse the website URL, I can make configuration changes. I have configured a static IP address everything connects fine, but when I go to print it immediately fails.

Any computer on the old domain can print without issues, and if I install the printer on my notebook which is not part of their domain it works fine.

I have run through troubleshooting with HP and they do not have an answer for me.

Any help would be appreciated. I have switched the printers to USB cables and for a short time I thought they were working, but slowly as a few days went by they all stopped working.

Oh yeah on further note because the printer was under warranty HP replaced it with their advanced exchange program, so any network settings embeded in the printer would have been lost.

Thank you,

Walter Beach



.

Relevant Pages

  • Re: 2nd Branch Server and Laptop configuration suggestion
    ... please share all printers and folders the laptop user ... This newsgroup only focuses on SBS technical issues. ... now, that way, each branch is independent of any possible Server down at ...
    (microsoft.public.windows.server.sbs)
  • Re: !!HELP!! Pulling my hair on this one. Printer problems. Really need some help on this.
    ... Yes Larry I have already moved them off of the SBS server and onto a high ... When the printers were connecte they did show as being offline. ... have workstations connected are plugged into the same. ...
    (microsoft.public.windows.server.sbs)
  • Re: Client PCs and NAS not visible on server
    ... Get your SBS Health Check ... Ethernet adapter Server Local Area Connection: ... I normally allow the workstations to print directly to ip printers. ...
    (microsoft.public.windows.server.sbs)
  • Re: Windows 2008 Print Server
    ... appliances you may be able to backup the printers and drivers using Print ... Total Jobs Spooled 44,220 ... we will be decommissioning an old server which is an HP DL360G3 ... We are slowly starting to introduce Server 2008 into our environment. ...
    (microsoft.public.windows.server.general)
  • Re: Client PCs and NAS not visible on server
    ... Find the iptest.txt files on the C drive of the SBS and the workstation, copy the unedited results from each to your next post here, and let us know which is which. ... but you could change the name of the server and of the domain if you feel you must. ... I normally allow the workstations to print directly to ip printers. ...
    (microsoft.public.windows.server.sbs)
Quantcast