Troubleshooting

ODDC Server exits immediately with a SQL connection error #

• Confirm SQL Server is running and listening
• Confirm the server and instance name in OddcDbConnection
• If using integrated security, grant access to the Windows service identity
• Confirm encryption and certificate options are correct for the SQL Server
• Run the executable interactively as the service account to reproduce the failure

HTTPS fails to start #

• Verify the certificate thumbprint and remove hidden spaces
• Confirm the certificate is in one of the four searched stores
• Confirm it has a private key and is valid for server authentication
• Grant the service identity access to the private key
• Check whether the configured port is already in use

Windows login succeeds at the browser but the application denies access #

• Add the exact DOMAIN\username or MACHINE\username identity to Users
• Confirm the user is active and has a valid role
• If the server is using Basic mode, use the login page instead of expecting Negotiate sign-in

HTTP Basic login fails for a Windows user #

This is normal operation. Windows users have an empty password hash and are explicitly blocked from HTTP Basic. Create a separate Basic-authentication user for an integration client.

Files remain in the source folder #

• Confirm the project and intended batch are active
• Confirm the batch is current for processing
• Confirm the selected input mode is File System
• Confirm the service account can read, write, move, and delete in all project folders
• Wait beyond Global.LastWriteOlderThanSeconds and ensure the producing application has closed the file
• Review Logs and the Status processing-state breakdown

Documents remain locked #

Check the Status page for the locking job. The maintenance job returns locks older than the configured timeout to import. If locks recur, investigate the named job, storage access, and database errors instead of repeatedly lowering the timeout.

Exports do not appear #

• Confirm at least one export type is selected
• Confirm the selected output mode and destination configuration
• Confirm destination permissions and free space
• Check whether the document is waiting for Manual Review or exception handling
• Check license validity and job trigger status
• Look for an existing filename and determine whether overwrite is disabled; the output may have a numbered suffix

Manual Review has no downloadable exception TIF #

This is normal operation. Manual Review does not generate the special exception TIF object. Choose File System, ODDC API Only, or Microsoft 365 SharePoint exception handling if a generated exception file is required.

Configuration changes appear to be ignored #

• Restart the service after changing the JSON configuration
• Restart after direct AppSettings updates so job schedules are rebuilt and cached settings are cleared
• Confirm that you edited the configuration file next to the running executable, not a source-tree or working-directory copy