connect ETIMEDOUT when printing report

Reference: https://www.sagecity.com/za/sage-x3/f/general-discussion/155387/error-cannot-connect-to-server-xx-server-local-1807-error-connect-etimedout---error-code-500

If Print Server was already set in stone for a long time (ref link assumed connectivity issue which is not a case for me), consider checking and do some manual spring cleaning on the AppData/temp folder for Windows Users.

Got surprised by a client today when the print server failed after working flawlessly for 7 years or so.

Cause :

Print Server main OS drive no space.

Sometimes, Print Server will make use of AppData/temp to store temporary X3 reports before printing out to customers.

Fix.

Two methods, temporary and expect to reoccur:

[1] Ask client to increase space on C:\ drive from host machine.

[2] Client no space to provision from host server.

1. Login to the Print Server with Administrators privileges. Expecting to break into other users folders so check with client IT before doing this. 

2. Analyze the harddisk. Take one from list and go: https://www.lifewire.com/free-disk-space-analyzer-tools-3986870

3. Go to the user's AppData/temp folder and check the date. I normally keep one week old temp files and purge everything else.

4. Check available space.

5. Test print report again.