Servicing Director Application Logon Error: "Invalid object name ..."
Invalid object name '<a database table name>',
Statement(s) could not be prepared.
Root Cause:
If you receive this error when you try to open a Servicing Director application and the expected logon screen does not appear, then usually the root cause is a database server configuration issue. This error message will appear in a series, displaying various table names starting with the Company Table, then the tLicensing, and the tCurrentUsers table.
Workaround:
This information is for your local IT or system administrator:
- This error usually means the Servicing Director application is not finding the expected database content, as if the application is connecting to the wrong database. The error messages related to SQL login configuration issues or permissions issues usually present different message text then this, and invalid object usually means the object is not found.
- The applications are directed to the Servicing Director databases by the desktop ODBC data sources named Servicing and ServEM.
- The Servicing data source is normally set to the database named Service.
- The ServEM data source is normally set to the databases named SvcEventMgr.
- The data sources are set during the application installation, as directed by the person completing the installation, and the settings were tested as correct for the installation to complete successfully.
- Since the ODBC settings can be manually changed, confirm the ODBC data sources are still correctly set for your system. Local changes to the SQL configuration could be one cause for this issue, and you should review any changes made.
ArticleNumber:
000041587