Hi Guys,
I have virtual windows 2012 R2 installed on Hyper V with the roles of file server and print server.
And my problem was when i open devices and printers tab it hangs.
I tried the following fix but no luck;
Well we were hoping to try the server 2012 HA Printing but I don't think I can. Between the shared storage requirement and the fact that all of our available servers are all a little different, I can not set up anything that fits the hardware requirements.
How broad or how much wiggle room is their in this statement?
"Servers: We recommend that you use a set of matching computers that contain either the same or similar features."
My 2 end servers are not the same but close different Intel CPU families, and the amount of RAM is very different, One does not have enough NICS (this could be rectified), and the RAID controllers are very different in performance. Dell R530 and an IBM System X3630 M3.
I have 2 very low end (Dell R210) servers that are exactly the same but too much effort to migrate their configurations elsewhere to set up a cluster that won't give me the performance we would need. And there is no upgrade path for them or money.
We are looking for print server failover or redundancy so we can take a print server offline without interfering with the user base being able to print. We have a need to be able to print on demand during the normal work day for the public but are constrained when it comes to working after hours.
Hi All,
We have a weird situation where a small number of clients find themselves unable to print on a certain queue.
We have 5 print servers with two queues each (one black and white, one colour) using the same driver on all 10 queues. Lately one queue on one server has been giving us issues: jobs sent to the queue just delete themselves, and there are errors logged to the client but no corresponding errors on the server. The print queue window also randomly and frequently closes itself on the client.
Errors on the client:
Event 372, Print Service
The document Print Document, owned by <user> failed to print on printer {id}. Try to print the document again, or restart the print spooler.
Data type: RAW. Size of the spool file in bytes: 132221715. Number of bytes printed: 0. Total number of pages in the document: 72. Number of pages printed: 0. Client computer: \\<PC Name>. Win32 error code returned by the processor: 2. The system cannot find the file specified.
OpCode: Spooler Operation Failed
If it was the driver, I'd expect all the other queues to have an issue, if it was the server i'd expect the other queue to have the issue. All the clients are the same image / managed operating environment (university PC lab).
Deleting and reconnecting the print queue on the client fixes the issue, as does a reboot / logout. When the colour queue is broken the black and white queue still works.
I've tried deleting and recreating the colour queue on the server in question, but that seems to have had no impact.
Any suggestions or hints?I'm printing from a Windows 7 to an OKI Data 5200n that is connected to a server. I have several printers that run just fine but this one keeps freezing up, and from this machine only. Every computer in the office can print to it with no problems. I've tried restarting the computer and restarting the print spooler service on both ends. Troubleshooting does nothing. It never sees a problem. I've looked around in the Event Viewer and found this:
----------------------------------------------------------
Fault bucket , type 0
Event Name: AppHangXProcB1
Response: Not available
Cab Id: 0
Problem signature:
P1: chrome.exe
P2: 45.0.2454.101
P3: 56034380
P4: 3bb1
P5: 128
P6: splwow64.exe
P7: 0.0.0.0
P8:
P9:
P10:
Attached files:
C:\Users\OFFICE1\AppData\Local\Temp\WERA16D.tmp.appcompat.txt
C:\Users\OFFICE1\AppData\Local\Temp\WERA229.tmp.WERInternalMetadata.xml
These files may be available here:
C:\Users\OFFICE1\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppHang_chrome.exe_88fc1dec397d7584e7a73e65784ef8f124f60b6_0940aa72
Analysis symbol:
Rechecking for solution: 0
Report Id: e17f25d9-71d7-11e5-a1db-00215a2d63f6
Report Status: 1
(along with this)
------------------------------------------
| EventData |
| 0 |
| AppHangXProcB1 |
| Not available |
| 0 |
| chrome.exe |
| 45.0.2454.101 |
| 56034380 |
| 3bb1 |
| 128 |
| splwow64.exe |
| 0.0.0.0 |
| C:\Users\OFFICE1\AppData\Local\Temp\WERA16D.tmp.appcompat.txt C:\Users\OFFICE1\AppData\Local\Temp\WERA229.tmp.WERInternalMetadata.xml |
| C:\Users\OFFICE1\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppHang_chrome.exe_88fc1dec397d7584e7a73e65784ef8f124f60b6_0940aa72 |
| 0 |
| e17f25d9-71d7-11e5-a1db-00215a2d63f6 |
| 1 |
Can someone help me figure this out? It's worked fine up until today after our server went down.
Dear Experts,
Will this setup work at all? Extremely hard to find support on this, as printer driver manufacturer won't support Windows sharing, and Microsoft won't support Windows XP. Here is the setup:
We have an application that resides on Windows Server 2008 R2, which has a Print Server role (among others) and sends print jobs to printers that are installed in print queue (printers that you see when you go to "Administrative Tools > Print Management> Print Servers"). Practically all of the printers in there are printers that have ethernet ports and plugged into RJ-45 ethernet cables. Now, recently, they bought new label printers Zebra FX420t, with modification that does not have ethernet port
built in. It only has USB and serial ports. Our thinking naturally was this: why don't we plug the printer via USB to the local workstation (Windows XP) and then share it, and then install the printer on the print server (that is on Windows 2008 R2 server
above) and it will work that way.
Basically GX420t -USB-> Windows XP workstation -LAN-> Windows Server 2008 R2.
While there was no error (except for warning "selected port does not support bidirectional communication needed by the driver. If you install the driver on this port, you will not be able to use its full functionality.") during the install of the
printer, and it showed status of the printer as "ready", when I tried printing a test page from the server, it never went through on the Windows XP workstation, nor attached printer. It does however print well from the Windows XP machine.
I tried searching google but could not find anything on this topic.
Really need some insight on this. Will such setup work at all? Is it supported by the operating system? Much appreciate your help on this.
Dear,
A couple of weeks ago I installed new printers for our organisation. Since we were getting rid of the other ones I figured I could use the same ip ports for the new ones. However, I did something wrong but not sure of what. Today some documents came out on the printer that was sent a week ago. And most people have problems printing on the new machine. I'm guessing it is a network or ip conflict. Can someone help me sort out the problem?
I have Windows server 2008 r2. The workstations have XP, Vista, 7 and 8.1 The old printer is a canon and the new one is sharp. The server says the port for the new printer is something like adsl-172-10-0-8.dsl.sndg02.sbcglobal.net but the old printer was on just 172.10.0.8. I don't know what I did wrong when installing it.
Thanks,
Hi,
I need to push out some new default printer settings (mono and duplex) for 300 printers across about 12 x 2003/2008 print servers. All of these devices are already mapped by around 2500 WinXP/7 users, so reconnecting the devices for everybody is not an option, nor is redeploying via GPO. I've read the following thread, which appears to explain what I need to do:
Firstly, I need the latest version of setprinter.exe, as the one I've got is date stamped April 2003, which I assume is the one that fails to work with devmode 9. Does anybody know where I can get this from?
Secondly, I think it says that the clients will periodically update themselves with the server's default settings. This is perfect, if correct. However, would anybody please be able to explain when these periodic updates take place?
Many thanks in advance !
Andy
Hi, I have a 3-month-old installation of Windows 7. I am attempting to use Windows Fax & Scan. It scans, but when I go to send, I get the error message "RPC Server is unavailable."
I am NOT a techie. Anybody have English-language instructions about what to do?
Thank you! Sonni
Dear All,
I have a Windows SBS 2008 Server with a Windows Server 2008 R2 Terminal Server. I deploy the printers using GPO, and I also do Item-Level Targeting to manage default printers.
When the user has no printers installed in his session, the deployment of the printers is going fine... The printers are installed, and the correct printer is taken as the default one.
When the user logs off, and logs on again, following messages appear in the event viewer :
The user '<user>' preference item in the 'Printer Policy' Group Policy object did not apply because it failed with error code '0x80070709 The printer name is invalid.' This error was suppressed.
--> Item-Level Targetting is no longer applied.
I already tried :
- Adding the Terminal Server Computer account to the printers security
- Played around with Group Policy LoopBack Mode
- Gave the user administrator rights
-...
I really don't know what to do next and the customer is really complaining about this.
Can somebody please help me?
Kind Regards,
Koen Verbeke
Koen Verbeke ICT Consultant @ IF-IT4U bvba
We are looking at putting print servers in a data center location that is a couple hundred kilometers away from most of our users. The print server and our desktops will be on the same domain, and the users will access the printers from their desktops. Pretty standard stuff, just with the print servers being farther away than is normally the case.
My immediate concern was in regards to WAN utilization and bandwidth. I worry about how much WAN bandwidth the print jobs will consume. Are there some "standard rules" that apply to this? Is the bandwidth simply "management bandwidth" or does the full print job go across the WAN? Ex: If I print a 10 MB PDF file, does the 10 MB go across the WAN, or is it just "management/meta data" that goes across the WAN? Apologies for rather simple question, my experience with print servers is quite limited.
Windows Server 2012 R2
Brooktrout Board TRxStream Board
getting error when sending fax from windows fax and scan
error "File error"
The attempt to send the fax failed. The service will attempt to resend the fax.
Reason: File error.
Sender: Administrator.
Billing code: .
Sender company: Company.
Sender dept: .
Device name: Brooktrout Line #1.
Job Id: 0x0201d10c13ba36f1.
User name: domain\Administrator.
Please check the activity log for further details of this event.
Details
| - | System |
|
|
|
|
|
|
|
|
|
|
| - | EventData |
| File error |
| Administrator |
| Company |
| Brooktrout Line #1 |
| 0x0201d10c13ba36f1 |
| domain\Administrator |
XML Details
We are running a 2008 R2 print server with AD with windows 7 clients. I have been having an issue with one building where some of our students don't get all the printers that are assigned via GPO. I would say that about 90% of the students do get all the printers but 10% don't. Of the printers that don't show up 2 of them were printers that were added to the GPO recently. Normally I would say to run a gpudate /force but that sometimes has no effect on the problem. The only thing that seems to work consistently is to delete the local user profile and have them log in again.
Does anyone have any ideas?
Thanks
Hello Experts
We have a windows 2012 R2 RDS / Terminal services with about 165 users.
Printers are pushed Via a windows 2012 R2 print server using GPO.
For some reason some user printers will not stay as Default. There does not see to be a pattern that I have noticed.
If the user logs of the printer will reset to other Printer.
I was able to come up with a work around by clearing out the printer connections under the user key in regedit
HKCU/PRINTERS/CONNECTIONS removing all the connected printers under the list.
Then GP0 rebuilt the list. .
The issue is if I restart the printer Spooler or Restart the server the issue comes right back.
Any ideas?
I would prefer not to use Log on Scripts if possible.
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
I'm cross posting here as it seems this hasn't been discussed on Technet yet.
There seems to be a fundamental issue printing PDFs on 2012 R2 RDS.
Adobe Reader, Sumatra PDF, different printers & drivers all haven't fixed this issue.
At least one person has raised a ticket with Microsoft for this issue and they're apparently aware of it.
https://forums.adobe.com/thread/1344069
Can anyone help?
Environment: Windows Server 2008 R2 Enterprise 64-bit. Virtual server using VMWare.
We're having an issue with some printers showing as offline when they're actually online and we can ping them. If we disable SNMP by configuring the TCP/IP port, the printer comes online. However, we don't want that as a solution. We want to find out why it's showing offline when SNMP is enabled. This is only affecting 4 printers out of 136 printers and the make and model varies: 1x Brother MFC-9450CDN, 2x HP Officejet 6100 and 1x Ricoh Aficio MPC2500. The drivers are up-to-date for all printers. I've tried restarting the print spooler on the server and also creating a new port but this doesn't change anything.
Any help is appreciated.
Thanks
Simon