Basics I would start with here.
Also I would be sure the pc is virus free and also besure that you have all windows updates and filemaker updates.
This is a very basic level system error. Can the user print from other applications? It's possible that the problem has nothing to do with FileMaker.
I have exactly the same problem in two separate installations, both running Windows 7 and FM11. Reconfiguring the printer port never works. Other applications can print to it without any problem. I have never had to do a re-install of FM; simply re-starting the computer corrects the problem, but not so easy if it is also acting as the 'Server'. From memory I cured it last time by simply restarting the Print Spooler Service on the computer (I think).
This sounds like something to report in Report an Issue if other applications print successfully and FileMaker cannot.
I thought it was 'me' when it first happened, but when it happened again (regularly, but not frequently) at a second site I thought I should raise it. It only happens on the FM Client 'server' for 4 clients, so at the time it happens it is a matter of getting it back working again with the least possible disruption, so I haven't yet had time to record a ste-by-step scenario of what happens, what works, what doesn't, etc. But I think the print spooler restart works, so if I can prove that next time I'll have more chance of posting something meaningful. At every incident other applications (Word, Excel, or Outlook would have been candidates I tried) would always print.
My puddled mind remembers reading something that Bonjour may be the problem. If I have the luxury of time the next time it happens I'll investigate the Bonjour line as well.
Hmmm, just to rule out issues with the file, Try recovering it and test the recovered copy to see if that makes any difference. Since the recoverd copy will have rebuilt indexes and some cached printer settings are cleared by the recover, test the recovered copy even if the recover did not report finding any problems.
If the recovered copy works with no trouble, you'll need to decide whether to use the recovered copy or look for a backup copy that doesn't have this issue. You might also play with different advanced recover options such as those that just rebuild the indexes or that rebuild the indexes and also those that "delete cached settings" but which 'copy file blocks as is'.
Things to keep in mind about Recover:
While Recover almost always detects and fully corrects any problems with your file...
- The recovered copy may behave differently even if recover reports "no problems found".
- Recover does not detect all problems
- Recover doesn't always fix all problems correctly
- Best Practice is to never put a recovered copy back into regular use or development. Instead, replace the damaged file with an undamaged back up copy if this is at all possible. You may have to save a clone of the back up copy and import all data from your recovered copy to get a working copy with the most up to date information possible.