ReferralNet Client Troubleshooting

I am getting a "Cache must be enabled for nativelib or installer-desc support" error when trying to install the client application, how do I resolve this?

  1. Open the Java Control Panel.
  2. Go to the General tab.
  3. Temporary Internet Files > Settings.
  4. Tick temporary files on my computer.
  5. Click OK, then Apply changes.

I am getting a "The server sent HTTP status code 400: Bad Request" message when using the Desktop client, how do I fix this?

The ReferralNet messaging service implements WS-Security UsernameToken for its' authentication scheme and requires a valid time stamp as part of the service request. If the client desktop clock is not synchronised then the service will reject the request (with a HTTP 400 Bad Request) as the time stamp variation is outside the acceptable range. This measure is used to counteract replay attacks and is part of the WS-Security specification.

You need to check that the date and time set on your computer is correct.

Some of my received messages are ending up in the Problems folder rather than the Inbox, what does this mean?

If the client application encounters any issue in regard to receving a message, it moves it to the Problems folder. The primary cause of a message to be moved to this folder and not the Inbox is due to a problem being encountered during the PKI phase, with the primary culprits being;

  1. The message was encrypted with a public cerificate that does not correlate to the certificate of the recipient.
  2. If the current user is utilising an individual certificate that is bound to a token (SmartCard, iKey etc) which was removed from the computer at the same time as the application was attempting to decrypt and verify the message.
  3. There is a transient decryption issue occurring between the application and the hardware that the individual certificate resides on. The smart card for example may not be contacting or seated correctly with the reader or the contact plate may be scratched / damaged etc.

If a message ends up in the Problems folder it does not necessarily mean that the message cannot be remedied and moved to the Inbox. In the case of cause #2 or potentially #3 above, the user would simply need to re-connect their token to the computer and attempt to process the message once more. To instruct the application to do this, simply highlight the desired message and right-click the mouse button to display the context menu and select the Retry option. If the application fails to process the message after a Retry is requested, an error dialog will be displayed with a detailed description of the problem it is encountering, otherwise it will be moved into the Inbox folder.

 
client/troubleshoot.txt · Last modified: 2009/08/26 15:00 by timc