Troubleshooting
The diagnostics program VehistraServerCheck.exe checks connection, database,
folders and permissions and names the cause in plain words. For problems with
the server connection it is the fastest first step.
Connection and database
| Message | Cause | Solution | | ----------------------------- | ------------------------------------------------------- | -------------------------------------------------------------- | | SQL Server could not be found | Service not running, TCP/IP disabled or firewall closed | Enable TCP/IP, start the SQL Server Browser, open the firewall | | Login was refused | The account has no access to the database | Check the database permissions | | The database does not exist | Setup not completed | Repeat the setup wizard from step 4 | | Timeout exceeded | Server off or network disconnected | Check server and network connection |
The single most common mistake: the server name is incomplete. It consists of
computer name and instance name, for example FLEET-SRV01\SQLEXPRESS.
Folders and shares
| Message | Cause | Solution | | -------------------------------------- | ------------------------------------ | ------------------------ | | The documents folder cannot be reached | Share missing or permissions missing | Check share and path | | Cannot write | NTFS permissions missing | Check the “Security” tab |
Permissions are needed twice: in the share and in the NTFS security settings. The more restrictive of the two wins.
Workstation
- The setup reports a missing runtime: install the .NET Desktop Runtime 10 (x64) and start the setup again.
- “Set up server connection” appears after starting: no configuration has been loaded yet – see Workstation setup.
- “No permission”: the action is not part of the role's permissions – see Users and permissions.
Editing at the same time
If the program reports that a record was changed in the meantime, that is not an error: two people edited the same record. Vehistra deliberately overwrites nothing but offers to load the current data or compare the changes.
An update stops
An update stops when the preceding backup fails. That is intended. Check the backup folder and its permissions, then start the update again – see Updates.
Solo mode
In solo mode there is neither a SQL service nor a firewall rule – the messages revolve around the database file.
| Message | Cause | Solution |
| -------------------------------- | ------------------------------------------------------ | ------------------------------------------------------------------- |
| Database file not found or empty | File moved, deleted or not created yet | Restore a backup or run the setup wizard again |
| File is locked | Vehistra is already running, or a backup tool holds it | Close all windows, wait a moment, start again |
| No write permission | The signed-in user cannot write to the data folder | Check permissions on C:\ProgramData\LSP Virtual Services\Vehistra |
| Disk full | No space for the database or the backup | Free up space, put the backup folder on another drive |
| File damaged | Interrupted write, failing disk | Restore the last verified backup |
Vehistra translates these cases into understandable messages; the server check names the operating mode in its first line and skips the checks that do not exist in solo mode.
Support package
If nothing helps, the program produces a support package with logs, version details and system diagnostics. It contains no passwords, no SQL credentials and no vehicle or personal data – you can send it to support without concern.