This error may pop up when System Five is first started in a Terminal Services environment, and may be more likely to occur in a Published App, or Remote App environment.

This error is caused by System Five trying to start before the mapped drives have connected and/or the Pervasive engine has a chance to start.

The only solution at this time is to either run System Five from a normal Terminal Services connection, or inform the client's Computer Tech or IT People to built a delay into the shortcut, so there are a few seconds between when the Terminal services connection starts, and when System Five is started.