When people have trouble with their cars, they tell the mechanic what needs fixing (headlight out, etc.). When people have trouble with their computers, they frequently freeze like a deer in headlights: “my computer isn’t working”.
The first rule of troubleshooting is: start with the simple things first. Is it plugged in? (I actually had a client a number of years ago that came in one morning to discover their network was down - the cleaning crew had mistakenly unplugged it during the night).
So the first step is to log out of the program(s) giving you problems and/or reboot the computer.
The next step is to ask: are you the only user with the issue or is it firm-wide? If you are the only person with the issue then the problem is likely not to be Worldox or other similar program, but something with your specific computer setup/configuration.
Are there any error messages? These can be critical in deciding what is wrong. For example, a “1460” error in Worldox means that there is a time delay in communicating with the server (especially when saving PDF’s). Is there anything else peculiar happening?
What were you doing when the error occurred? Saving a document? Opening a document? Attaching a document to an email? And does this happen every time or is it sporadic? (Much harder to troubleshoot if the issue is sporadic).
Providing this sort of information to your consultant/technician can dramatically reduce the amount of time it takes to solve any given issue, as well as helping prevent it from happening in the future.
Recent Comments