Thank you for your post.
Are the workstations that are printing fine using the same layout as the workstations that freeze? That is, if most of the workstations are printing Layout "A", but only those workstations that print Layout "B" freeze, then I can focus on the layout?
Is everyone using the same printing script?
From the workstations that freeze, are you able to manually pull down the File menu and select Print?
From the workstations that freeze, is it only certain layouts that freeze or is it every layout?
If you create a new file, are you able to print?
Any other information you can provide may be helpful.
Hello TSGal, The program is being used by multiple users and they are printing the same or other layouts randomly.I tried installing Adobe Reader 9.5 but that didn't helped too.The catch is that this issue appears only after 3 PM and local printer or cute pdf also freeze up the aapplication.However when they relogin to program it starts working normally. I have been working on this from so many days but unable to figure out the cause. Printer is working very well outside filemaker but not within.Different layouts from different .fp7 files are having the issue while printing. Please suggest. Thanks Alex S
Thank you for the additional information.
When you say the "program is being used by multiple users", is the file being hosted by FileMaker Server? If so, what version?
Has anybody crashed before 3PM? I'm curious to know if there is anything occurring at 3PM that may affect connected users. The fact that this also occurs with other files rules out a file issue.
How long are the other users connected before the freezing occurs? Or, if a user connects at 2:55 PM, will the same user be unable to print after 3PM?
The files are being hosted from FileMaker Server 11. Admin console version 184.108.40.2060.
There are only 2 workstations out of 22 which have the issue while printing after 3PM. The users stays connected and keeps working and suddenly when they print something it hangs the application and ultimately they have to relogin in order to make it work.
So relogin to the application fix the issue temporarily but after sometime the issue re-appears. Whereas at the same time it doesn't affect printing outside of program (locally from Windows).
Still there are some users who can print after 3 PM,
Kindly suggest as it is something which is coming up for most of out clients.
I'd check for any kind of scheduled task type operation set up on those two workstations to see if there is anything that might hog network bandwidth on those two client machines that starts up around 3 pm.
And are those workstations shut down at close of business or left running 24/7? If they are shut down each evening, leave one up over night and see if you can print from it the next morning.
There is not any scheduled task on those 2 workstations , but I will ask them to leave the workstation up and running overnight and will try to print next day.
But do we need to keep the application up and running or shall we close it down as closing the application and keeping the workstation up and running will not help since next morning once we open the program it will not recreate the issue.
The idea behind the "leaving the workstation open" test is that something--could even be malware on those two machines, is interfering with FileMaker's ability to access the networked printer. If you leave the workstation up and running and it then cannot print the next morning until the user restarts their machine, that might be a useful clue as to what might be causing this issue.
In similar vein, once the workstation fails to print to the printer from FileMaker, can the user print to that printer from a different application? Their ability or inability to do so might also prove to be a useful clue.
Regardless of what results that test produces, I'd be contacting a computer tech to put those two machines under a microscope to see if any issues with those machines might be the cause of this issue.
They do not have to close the workstation and restart the machine. They just need to close the application via Task Manager and re-open it in order to make the printing work.
They are able to print from other applications from that workstation using the same printer.
Its just something is wrong with FileMaker and Printer.
After talking this over with another online technician (TSFalcon), there is something on those two workstations that is different from the workstations that are working. We both suggest reinstalling the printer drivers or transfer the printer drivers from the other workstations. If that doesn't exist, then reinstall every relevant component on those two workstations.
Also check to see if any plug-ins are installed on those two workstations that don't exist on the other workstations.
We agree with PhilModJunk that you should contact the person who initially set up the workstations as she/he is most familiar with the set up. She/he may notice any additional third-party software/utilities that weren't initially installed.
This was working previously on those workstations and we tried re-installing the printer's drivers on that workstation . but I will check for the additional components which might not be present on the workstation.
There was Adobe Reader 9.3 which was installed on the working workstation and Adobe Reader XI was present on the workstation with issue which I uninstalled and installed with 9.3 but now the workstation with 9.3 is also having the issues , so now a new workstation has been added into the segment of printing issue.
I am confused and its actually very frustrating for the clients.
Here is what it stuck on. Either we have to cancel it or press ESC to get rid off this dialog box.
Any suggestion on this ?
I am still unable to fix this printing issue. Can anyone suggest anything ?
- Alex S
While that dialog is up, the printer driver and Filemaker are generating a temporary "print job" file that should be visible in the printer's status monitor. If it hangs at this point, it would seem that FileMaker is unable to finish "spooling" the print job to a temporary file on your disk. Look in the status monitor for a preceding print job that is "hung" with some kind of error message and also have a tech check to make sure that the user's hard drive is healthy.
Yes it stays on spooling while it stuck on the dialog box. None of the error message comes up in Event Viewer and none of the exe is actually taking lot of memory from the workstation.
They have sufficient space on C: drive where FileMaker Pro is installed.
The issue comes up only after 2PM every day and none of the schedule from task scheduler runs at that time.