Question about Fargo DTC550 Thermal Card Printer
Unfortunately, the DTC550 is in its end-of-life phase of support by the manufacturer (HID Global/Fargo), as of Dec. 15, 2014. There is not a driver or support available for Windows Server 2012.
You MAY be able to configure as a shared device via a separate workstation print host/server, using a supported OS:
Posted on Apr 17, 2015
A 6ya expert can help you resolve that issue over the phone in a minute or two.
Best thing about this new service is that you are never placed on hold and get to talk to real repairmen in the US.
The service is completely free and covers almost anything you can think of (from cars to computers, handyman, and even drones).
click here to download the app (for users in the US for now) and get all the help you need.
Posted on Jan 02, 2017
Tips for a great answer:
May 28, 2014 | HP Jetdirect 170x Print Server
on Feb 15, 2011 | Computers & Internet
The Web server (running the Web Site) encountered an unexpected condition that prevented it from fulfilling the request by the client (e.g. your Web browser or our CheckUpDown robot) for access to the requested URL.
This is a 'catch-all' error generated by the Web server. Basically something has gone wrong, but the server can not be more specific about the error condition in its response to the client. In addition to the 500 error notified back to the client, the Web server should generate some kind of internal error log which gives more details of what went wrong. It is up to the operators of the Web server site to locate and analyse these logs.
500 errors in the HTTP cycle
Any client (e.g. your Web browser or our CheckUpDown robot) goes through the following cycle when it communicates with the Web server:
This error occurs in the final step above when the client receives an HTTP status code that it recognises as '500'. (Last updated: March 2012).
- Obtain an IP address from the IP name of the site (the site URL without the leading 'http://'). This lookup (conversion of IP name to IP address) is provided by domain name servers (DNSs).
- Open an IP socket connection to that IP address.
- Write an HTTP data stream through that socket.
- Receive an HTTP data stream back from the Web server in response. This data stream contains status codes whose values are determined by the HTTP protocol. Parse this data stream for status codes and other useful information.
Fixing 500 errors - general
This error can only be resolved by fixes to the Web server software. It is not a client-side problem. It is up to the operators of the Web server site to locate and analyse the logs which should give further information about the error.
Fixing 500 errors - CheckUpDown
Please contact us (email preferred) whenever you encounter 500 errors on your CheckUpDown account. We then have to liaise with your ISP and the vendor of the Web server software so they can trace the exact reason for the error. Correcting the error may require recoding program logic for the Web server software, which could take some time.
Jan 28, 2013 | Facebook Social Network
Jun 11, 2011 | Lantronix CoBox-FL-IAP (COBOXFLIAP11)...
Ensure that communication has been established and that a driver test page can be printed from the 64-bit server. Once functionality has been confirmed from the 64-bit server, proceed to the next step.
Currently, 64-bit clients will be able to connect to the shared 64-bit print driver that has been installed on the 64-bit server as the architecture currently matches. However, if 32-bit clients wish to map to the shared 64-bit print driver on the 64-bit server, the 32-bit version of the same driver will need to be installed within the current 64-bit driver.
This process can be done by navigating to the printer properties of the 64-bit driver on the 64-bit server, clicking the Sharing tab and clicking the Additional Drivers button.
Once the administrator clicks the OK button, a print driver window will pop-up asking for the 32-bit driver components. Again, the administrator will need to download, and extract the 32-bit version of the print driver on the 64-bit server. Once the window below comes up, the administrator will need to navigate to the 32-bit driver components and select the appropriate driver .inf file.
For example, the UPD .inf file would be the first file in the list and be named hpcuXXXc.inf.
Once the appropriate .inf file is selected, the 32-bit driver components will be installed within the 64-bit driver on the 64-bit server. This can be verified as both x86 (32-Bit) and x64 (64-Bit) boxes will now be checked and show the status as installed by clicking the Additional Drivers button compared to the screenshot in Step 3 above.
Now that 64-Bit and 32-Bit drivers have been loaded onto the 64-Bit server, 32-Bit and 64-Bit clients can now navigate to the shared print driver on the 64-Bit server, by manually navigating to the shared print driver on the 64-Bit server from the client machine. Typically the path is \\servername\sharedprintername.
Once the client maps to the shared print driver, printing should work successfully.
For problems or errors that continue to occur after completing the aforementioned process, ensure that the latest version of the print drivers are being used www.hp.com . If there are problems with older discrete drivers, it is recommended to use the latest version of the Universal Print Driver which can be found at www.hp.com/go/upd .
Mar 17, 2011 | HP Laserjet P4515x Printer
Jan 27, 2011 | Canon imageRUNNER C3200 Copier
Feb 09, 2010 | HP Hewlett Packard LaserJet 1022 Printer
Sep 28, 2009 | Microsoft Windows XP Professional
Mar 28, 2009 | Intel Motherboard
152 people viewed this question
Usually answered in minutes!