Error after Database Restore

We have performed a database restore to our system and are now encountering the following error message when we attempt to do anything with the iMIS iBOs.

Asi.Business.SchemaLoadException: Unable to load object schema definition for User ---> Asi.Business.Common.DocumentNotFoundException: Document not found or insufficient permissions to read document. $/Business Object Schema/User

   at Asi.Business.Common.DocumentSystem.DocumentByPath(DataServer server, Guid organizationKey, String documentPath, Boolean publishedOnly, Boolean ignoreLicensing)
   at Asi.Business.BusinessData.BufferFromDatabase(DataServer server, Guid organizationKey, String documentPath)
   at Asi.Business.BusinessData.BufferFromDatabaseWithBootStrap(Guid organizationKey, String documentPath)
   at Asi.Business.BusinessData.GetDocumentBlob(Guid organizationKey, String documentPath, Boolean enableCache)
   at Asi.Business.BusinessData.GetDocumentBlob(Guid organizationKey, String documentPath)
   at Asi.Business.BusinessController.LoadSchema(String controllerName)
   --- End of inner exception stack trace ---

We have not encountered this error before and we believe everything is setup correctly.  Any insight is greatly appreciated.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Any time a database is

Any time a database is restored (but especially if it's restored under a new name, to a new server, etc), you need to be sure to run the "DBRepair" utility, and click the "Prepare Database" button.

If that doesn't fix your problem, try this:

Open a command window on the app server, and navigate to the net/bin folder under the ASI iMIS install

Run the BuildPublishBOs.exe tool with the command line (making sure to substitute your correct local server name, user name (typically 'sa'), password (sa password), and database name) from the 'bin' folder:
 

BuildPublishBOs.exe -O User -CS SERVERNAME -CU USERNAME -CP PASSWORD -CD DBNAME

 

 

One of those two should have you fixed up unless there's something else very wrong (perhaps connection strings in .config files not updated with the new database name or location?)

 

 

 

The above steps were

The above steps were performed but from the iMIS Desktop front end and the DB Repair Utility.  The ultimate resolution was to perform another restore and it worked.  I am chalking the failure up to a corrupt backup or a corrupt restore attempt.  Thank you for your responses.