MSSQL error 'Invalid Object name'

MSSQL error 'Invalid Object name'


When you get a similar error as mentioned below 


java.sql.BatchUpdateException: Invalid object name 'TABLE NAME'




please change the COLLATION in the MSSQL server for the database 'servicedesk' as CASE-INSENSITIVE.

You can get this error at the time of restore or backup or you can also find this in the serverout file if it is a runtime error.


If you are running MSSQL 2000 then run the below query to alter the collation:


​

ALTER DATABASE servicedesk COLLATE SQL_Latin1_General_CP1_CI_AS 




      New to ADSelfService Plus?

      Start your free trial

        Resources

            • Related Articles

            • License is Expired / License is invalid

              The application will not start if the license is expired / Corrupted. If the error is, Registration period is expired Open the command prompt with Admin privileges (Run it as Administrator) and point to the bin directory of ManageEngine ServiceDesk ...

            • How to change the database from MySQL/PostgreSQL to MSSQL

              The steps mentioned below are applicable only if you migrate the DB from PgSQL to MSSQL. This means that the application server is going to remain the same. The data alone is going to be transferred to MSSQL DB from the existing PgSQL DB.    For ...

            • How to change the database from MSSQL to PostgreSQL

              The steps mentioned below are applicable only if you migrate the DB from MSSQL to PgSQL. This means that the application server is going to remain the same. The data alone is going to be transferred to PgSQL DB from the existing MSSL DB.    For ...

            • How to find the MSSQL Lock on the database directly?

              Connect to the MSSQL database and open the query editor for service desk database(any database should work) 1. Execute the query  sp_who2 2. Above command will show the list of database query process which is currently in execution that causes the ...

            • Exception while Processing Inline Image with incorrect file name extension

              Reference : #7938623, #8561970 Cause : Inline Images could not be processed with incorrect file name, for example "4d54308871ec465c8233d0f470db0308.do?sys_id=4fdfcb17475c1d50c594c133846d436a" . While constructing the filename in our end, the values ...