Troubleshooting

Communication Messages

Examples

Communication message--Invalid password
User is entering an incorrect or invalid Access account password.

Communication message--Registry object not found
User is entering an incorrect or invalid Access account password.

Communication message--Communication Problem--Server may be down or busy.
FIT is experiencing communication problems. Please contact the AIS Support Center, (814)-863-2276.

Communication message--OSErrorHolder inaccessible signal
User is not connected to the network or PSU network is down.

Communication message--No bindings available from bind management thread.
The DCE server may not available. Please contact the AIS Support Center, (814)-863-2276.

Communication message--Clock skew too great.
Users PC's clock time is out of sync with mainframe. The time client is not installed or being executed.

Communication message--Request time-out
FIT is experiencing communication problems. Please contact the AIS Support Center, (814)-863-2276.

Communication message--OSErrorHolder peerFaultSignal
FIT is experiencing communication problems. Please contact the AIS Support Center, (814)-863-2276.

Communication message--OSErrorHolder notReadySignal
FIT is experiencing communication problems. Please contact the AIS Support Center, (814)-863-2276.

Communication message--Net.SSLHandshakeFailure
FIT is experiencing communication problems. Please contact the AIS Support Center, (814)-863-2276.

Communication message--Error processing your request. Please contact the GI development team for assistance.
FIT is experiencing communication problems. Please contact the AIS Support Center, (814)-863-2276.

[ Back to Top ]

Unhandled Exceptions

For all messages identified as an "Unhandled exception:," the first line will identify the error and the lines following will always be:

Examples

Unhandled exception--File does not exist
Configuration file not in components directory (fitGI.xml). Please download updates during login.

Unhandled exception--Key not found
FIT is trying to load files which are corrupted. Go to the "ibisfit" directory and open the "data" folder. Delete the follow two files: (cenobj.bos & cindcalc.bos). Do not delete the options.bos file. Re-launch FIT and the two files will be recreated with the correct version attached.

Unhandled exception--The identifier PSU.Codeset.Codeset...
FIT is trying to load files with an incorrect version attached. Go to the "ibisfit" directory and open the "data" folder. Delete the follow two files: (cenobj.bos & cindcalc.bos). Do not delete the options.bos file. Re-launch FIT and the two files will be recreated with the correct version attached.

Unhandled exception--Referent Inaccessible
FIT is experiencing an operating system error with the users ethernet connection. Please contact the AIS Support Center, (814)-863-2276.

[ Back to Top ]

Sharing Reports

Communication message--No bindings available from bind management thread.

Using FIT, Windows users can share reports among other Windows users; Mac users can share reports among other Mac users. However, reports can not be shared between platforms (i.e., Windows users sharing with Mac users or 16-bit platforms with 32-bit platforms).

[ Back to Top ]

Printing

An error has occurred while trying to print a FIT report.

You have just installed FIT for the first time or upgraded FIT and unsuccessfully tried to print. Try the following:

Immediately after receiving this error message, shut down all running applications and do a 'clean' reboot of the PC. This action initializes a component within FIT that should allow you to print. This problem is known to happen with first time printers of FIT on Windows '95 PCs. After the PC reboots, launch FIT and initiate the print job again.

If you still can't print, verify the following:

If the steps listed above do not resolve the issue, please submit a Request for Service (RFS) form. On the request form, select To correct a problem and specify in the freeform text area that you are having a FIT printing problem.

Note: We are aware that a small percentage of Windows 95 configurations will not print from FIT.

Output sent but not received, or output sent in Postscript (Prints off a blank page or Fills the page with cryptic text and starts with a %)

[ Back to Top ]

Miscellaneous

Unacceptable Report Names in Windows

In the Report Name, exclude the use of the following characters to avoid or resolve this error:

[ Back to Top ]