This method makes you able to "start over" on the existing server.
NB: If you are using a multiserver environment with slave servers, you might need additional steps. This covers only the master or a standalone server. Any slaves might become corrupt.
- You need access to SQL Management Studio. If you are running a standalone server with the SQL-Express running on the same server you can install Management Studio on the same server. Are the SQL running on a separate SQL-server the Management Studio is most likely already available on that server.
- Login to the SQL-instance running the SafeCom-databases. If in doubt you can find this in the registry path on the SafeCom-server: HKEY_LOCAL_MACHINE\SOFTWARE\ SafeCom\SafeComG4\Database
- Running SQL management server on the same server as the SQL-Express usually grants you access if you use Windows Authentication and have local admin access to the server, if not you will need a user account. Try the safecominstall-user found in the manual (only available on external SQL-servers), or a Windows user account you expect to have admin rights. If you need the password for the 'safecom'-user you need to contact us and provide the hostname of the server. Only Kofax can provide this password if necessary and is usually not provided by default during installation.
- Stop the SafeCom Service.
- When logged in to the SQL management server, locate the 4 databases: sccore, scevent, sctracking and scpurse.
- Backup these 4 databases to have a disaster recovery available. (could also be done through the scbackup -b command)
- Locate the folder where these 4 databases are stored on the server.
- Delete these 4 databases. Tick the "Close existing connections" to force the deletion.
- Verify the folder where the databases are stored and verify if they are deleted. If not you can delete them manually now. (each database usually consists of a database-file and a transaction-logfile).
- Start the SafeCom Service
- Wait a minute and log in to the SafeCom Administrator. Voila!