I have installed printer a hp deskjet 1515 in windows 7 ultimate 32 bits and it is successfully installed, however when I tried to test print out there showed message "test page failed to print. Would you like to view the print troubleshooter for assistance?". I tried to clicked Yes and running the troubleshooter until completed but the result still the same showed the same message above when test print again.
Please need assistance how to solve this problem
Thanks
Sopyan
Maybe this isn't a big deal but I need an explanation for my Supervisor.
The Port is set up for SNMP enabled with the standard community "public". Occasionally the SNMP Device Index changes from 1 to 0 taking the printer off-line.
No rhyme or reason as to printer type or driver model. I should mention that this behavior can happen on printers where the SMNP Status is disabled also. The instances happened on Server 2008 and now on Server 2012 SP2.
Changing the index back to 1 solves the issue. Strange to me as it doesn't seem like a fix rather a work-around.
I know I can avoid the issue by turning of SNMP. Any ideas as to why this is happening?
John
Hi guys,
I'm working on authoring Management Pack (MP) for SCOM 2012 for Print Servers and have several questions concerning clustered Print Servers, specifically clustered Print Server queues. I would appreciate if you could shed a light on this.
Currently Print Server MP requests Print Server queues fromWin32_Printer wmi branch, but this works only with non-clustered queues instances.It looks like for clustered instances I have to request another branch - Win32_ClusterShare. The wmi request is supposed to be called on target computer (cluster node) and used to discover (and as a result to create appropriate objects in SCOM) queues instances.
So I have a bunch of questions regarding:
1. Should "select * fromwin32_clustershare wheretype='1 or 2147483649'" be requestedon each cluster node or is itsomething common for cluster group (several cluster nodes)?
2. Will "select * fromwin32_clustershare wheretype='1 or 2147483649'" contain enough information describing print queues on cluster / cluster node?
3. Win32_ClusterShare has two types which might be potentially used for cluster print queues discovery:
1='Print Queue'
2147483649='Print Queue Admin'
http://www.powertheshell.com/reference/wmireference/root/cimv2/win32_clustershare/
Which one should be used?
4. Is it possible that on one specific cluster node print queues information is returned by both Win32_Printer and Win32_ ClusterShare? I think, not, but would like to clarify.
5. Will requesting "select * fromwin32_clustershare wheretype='1 or 2147483649'" work for both Windows Server 2008 (R2) and Windows Server 2012 (R2)?
I’m wondering this, because I found changes in print role clustering implementation.
Below is the link how to install Print Server on Windows Server 2012:
https://technet.microsoft.com/en-us/library/jj134159.aspx
In Windows Server 2008 R2 there was available Print Server Cluster Role:
https://technet.microsoft.com/en-us/library/cc771509(v=ws.10).aspx
But it looks like Print Server clustering on Windows Server 2012 is performed differently:
https://technet.microsoft.com/en-us/library/jj556311.aspx
Thanks in advance.
Igor Savchenko, VIAcode Consulting LLC (http://www.viacode.com/)
I was wondering if anyone ever had an issue with deploying printers through preferences by having multiple entries when trying to create a single entry. Then when it deploys the printer it creates multiple print queues on the client PCs. It just started doing this for no apparent reason. Does anyone know what may have caused this issue and how it may be resolved? Thanks much.
Hi Everyone,
We recently moved to a Server 2008 R2 print server. Many of our users use Remote Desktop to run applications on servers, one of which is a 32-bit Server 2003 box. We have a LaserJet 4350 with an automatic duplexer. The duplexing works correctly on client machines running 32-bit XP, but as soon as these users try to print a document in an RD session to the same 4350 (redirected though), the auto duplexing will not work.
I loaded the same 32bit driver on the Server 2003 box as is on the Server 2008 R2 print server, and thus the XP client machines. Any ideas why this would not work? It seems like it would be a driver issue, but I'm not sure why the redirected printer would be using a different driver than the one installed on the client machine.
Thanks!
Server 2008R2 Standard Server - Fax Server
Server 2003 Standard - DC
Workstations: Windows 7 x64 - Domain users
Modem US robotics USB modem
Message when trying to add account: you do not have security permissions to complete this operation. Contact your administrator for more information.
I had a working fax server in a production environment that had been working for years. On Tuesday users were unable to send faxes. Faxes still were being received and placed in a folder.
When looking at the Fax Account it showed Disconnected. After removing that and trying to reconnect, I got a message saying that I did not have security permissions.
I tried it from the fax server itself. It works. I tried it from the workstation using a Domain Admin account that we use and it works. I temporarily made the user a domain admin logged out and logged back in. Still cannot connect to
fax server.
Other things that I have done.
uninstalled/reinstalled modem on server
Removed Fax Server Role and re-added
Took ownership of Fax in the Advanced Security section by domain users
Removed fax on server from workstation and re-added successfully
Re-added permissions in the fax manager for domain users, network service, everyone
Disabled Windows Firewall on server
Disabled Antivirus on server
Hi, Friends
I am working on printer server upgrade and printer migration project in my company.
The old server is Windows Server 2003 x64, and the new one is Windows Server 2008 x64.
When I import the file to new server, I get message 'Import complete' (but the progress bar is grey, not blue).
I check the the problem in Event Viewer.
Event ID 29
Printbrm.exe (the Printer Migration Wizard or the command-line tool) could not restore language monitor Esker MF Language Monitor while restoring print queues from a file. Check the print queue backup file and examine the Windows error returned by this event to determine the cause.
And when I check the printers, there is nothing imported, no printer, no dirver, no port.
So, I am confused if the problem in event viewer stops other printers in the import processing?
Or I do somthing wrong before importing the file? Anyone has met this problem before?
Thank you in advance.
Lixingkai
I have a Windows Server 2012 R2 box running as a Fax Server for my organization. Up until last night, everything was working fine. The only thing that's different to me, was the installation of Updates from Microsoft. After the updates, I was prompted for a reboot so I complied and now incoming faxes to one of the 3 lines/devices is being sent to the wrong device and - thus - the wrong department.
Here's more details:
The Fax Service is configured with 3 lines/devices of the same make [Zoom 3095 USB Modem] - all with the Conexant driver version 2.0.23.0 dated 9/7/2012. The first two lines are receiving and sending properly and following the routing settings. The problem is with the 3rd line/device. All incoming faxes are processed by Device #2 and sent to the routing settings for that device.
Now what's got me baffled is that the phone line for Device #3 is active (otherwise the call wouldn't have come in anyway) and attached to Device #3, so how is Device #2 answering that call? The only thing I can think of right now is, perhaps, a software issue that could've been triggered by the Microsoft Update. If so, how best to I verify my suspicion?
Prior to posting this, I have restarted the Fax Service three times - testing in between each restart - but Device #2 is still getting the faxes sent to Device #3. Rebooting the physical server would be disruptive at this time, so I will do that later tonight after close of business. In the meantime, if anyone has come across this situation and can help me figure out what's going on please advice.
PS. I've checked and there are no event logs in the Event Viewer pertaining to the time frame in question (which is within the last hour of creating this post).
G'day,
an annoying effect both on Win 8.1 and Win Server 2012 R2: after installing/connecting a network printer for a user, it takes about 10 minutes (sic!) till printer is shown in devices and printers...
Printer is shown and can be used immediately after connect in word/notepad, but properties of printers can only be managed via devices and printers. Work around for setting standard printer: open notepad, click
print and right-click printer.
But we have to choose a special printer profile, which cannot be done else than devices and printers.
Sometimes even previously installed printers do not show for minutes after logon...
Restarting spooler: no effect
Changing drivers: no effect
Printers are Konica C554 series and 4700P series with Konica PCL drivers.
Print server for network printers in Win Server 2012 R2 (VM on Hyper-V 2012 R2)
No other network issues.
Thanks and regards.
McButtonn
Environment: 2 Virtual servers hosted by Hyper-V using Server 2012 R2. Print Management Server is deploying printers via Group Policy. Second server is a terminal
server.
All of the issues began with a bad Oce' driver. We setup this client brand new and they had issues with this one Oce' printer. It would take several minutes to
print anything. I called them and they gave me newer print drivers but they were still slightly outdated but they worked. After about a week the print spooler started crashing and I narrowed it down to the Oce' Driver causing it. I turned on Driver Isolation
for that one driver and more issues occurred. The printer would flat out not show up on the terminal server.
I completely removed that printer from print management and deleted the driver package. Now some printers are working on the terminal server and some are not.
The GPO is working and shows the printers being deployed properly. There's a bunch of random errors in the event viewer that I believe is coming from when the DC attempts to deploy the printers to the terminal server. If I try to manually add the printers
that will not deploy I get an error message saying "Printer Installation Failed Element not found". I have also attempted to use different drivers. I tried the Universal Printer Driver from HP and it actually installed the printer, but would not
print anything at all.
Before all of this with the Oce' drivers none of this was a problem. I believe something was corrupted preventing the installation of the printers after so many
spooler crashes on the DC. It was crashing several hundred times a day until I found the problem. I need help on where to possibly look to fix this. The event ID below may or may not be related but I believe it is. No event is generated when I attempt to manually
install. I believe there is something stopping the installation of the drivers due to either some temp driver pool being full or possibly registry but I don't know where to look. Any help would be appreciated. Thanks!
Below are two of the constant error messages in the event viewer.
Fault bucket , type 0
Event Name: PnPDriverInstallError
Response: Not available
Cab Id: 0
Problem signature:
P1: x64
P2: 00000490
P3: prnhpcl1.inf
P4: 3202cb0742bf01dc4dc73846866c3e12706090d8
P5: NON_IO_VIPA_PCL3_COPY
P6:
P7:
P8:
P9:
P10:
Attached files:
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_x64_cb3d981ce61d5af5412e10fbe3c75c95468a_00000000_11991d23
Analysis symbol:
Rechecking for solution: 0
Report Id: 1ba23610-7c9b-11e4-80db-00155d328701
Report Status: 4100
Hashed bucket:
Another one:
Fault bucket , type 0
Event Name: PnPDriverNotFound
Response: Not available
Cab Id: 0
Problem signature:
P1: x64
P2: {E94144F8-03A3-406a-BB1F-048C78226855}
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:
Attached files:
C:\Windows\Temp\DMI90A8.tmp.log.xml
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_x64_5bd93b8e4aaf2f4a331d6499e51a4166b43df94b_00000000_cab_1a448e1e
Analysis symbol:
Rechecking for solution: 0
Report Id: 4bc968e2-7bbf-11e4-80db-00155d328701
Report Status: 4
Hashed bucket:
Here's the contents of one of the log files referenced in the above error:
Version=1New Windows Server 2012 R2 Standard in the environment. Added print services to it and added five HP printers to it and shared them. Also deployed the printers via group policy.
Clients are running Windows 7 Pro x64. The group policy fails to install the printers (error 0x00000002). We get the same error when trying to manually add the printer from the client side.
From Event Viewer: Group Policy was unable to add per computer connection <<printer share>>. Error code 0x2. This can occur if the name of the printer connection is incorrect, or if the print spooler cannot contact the print server.
Any ideas on troubleshooting this?
Thanks.
-John
Good Day,
We have migrated from a W2k3 Citrix 4.5 environment to a W2k12R2 RDS/RemoteApps environment. The only issue we are having is with reduction of speed in printing over the WAN. In the old world, the Citrix Universal Print Driver was utilized and it did such a fine job of compressing the print stream. We have some users that do a batch print job (printing 500 invoices at once) and the time to print has quadrupled.
We have taken some steps to improve this by sharing the printers on the same LAN as the RDS environment instead of using the redirected easy print driver printers, but still we are wondering what else we can do besides purchasing Citrix for the new environment? Third party product like TSPrint or ThinPrint?
Thank you,
Steve J.
Hi
I have used printbrm to backup my printers on 1 machine to a file and then restore sucessfully on another
The 2 lines below were used to accomplish this 1st line backs up and 2nd line restored
Printbrm.exe /b /f C:\users\test\backup.printerExport
Printbrm.exe /r /f C:\users\test\backup.printerExport
Im trying this again and its not working it does put the drivers into the new system but the printers do not appear in the Devces and printers section as they did before.
I definately just used 2 simple lines before and the internet searches on the same speak of more complex ways
I have fulladmin rights on both machines
I have tried the various switches from printbrm.exe /?
Still no successWhat am I overlooking?
Thanks for reading
Confuseis
confuseis
Hi All,
"The print queue could not be found on domain AD.CONTOSO.COM It may have been deleted from the Active Directory directory service. Windows will attempt to republish the print queue. Error: 2116"
This event is seen in our print server but it doesn't actually state which queue it is trying to publish. How do I republish? Is it just a matter of unticking List in Directory and reticking it again?
The queue still exists and we haven't actually changed it at all. Why is it suddenly having publishing errors?
I recently installed Windows Server 2012 R2 64-Bit.
We have Printer Epson LX-300+ii and LX-310 (dot-matrix) that we share among users. Each user access the Server using Remote Desktop. From previous experience with Windows Server 2008, I knew that these printers will be problematic, especially regarding the Easy Print driver.
And I was right, using the Easy Print driver, I got the following result:
And so, I did manual mapping & disable the "Use Remote Desktop Easy Print printer driver first". Haha, what a surprise, I got the following result:
And so I uninstalled the printer driver, and install it again, thinking that I might chose a wrong driver, but.... same result. I know for sure that I chose the correct driver.
Next, I tried connecting the printer DIRECTLY to the server. Log-in to the Server directly,not using Remote Desktop. And tried printing again, haha... really... what a surprise... I got the same problem here !!!
So now I know the problem is not the Easy Print driver, not mapping or registry problem either. It's the print driver. This is SUPER FRUSTRATING, I tried the same driver from the same CD in Windows 8.1 64-Bit with no problem. I tried it too in Windows 7 32-Bit with no-problem either. But somehow, this driver is problematic in Windows Server 2012 R2.
Any help? Anybody else bump into this same problem ? I'm close to giving up, been spending too much time figuring out this damn thing.
Andy
Hi All,
Need a help.
Is there any way, we can failover the print queue from one server to another server automatically without cluster. Server 2012 R2 does not have print cluster. Without WIN8 client, BODP will not work. Hence desperately looking for some DR for print server