Xtraction reports fail after copying Xtraction database to a new server
search cancel

Xtraction reports fail after copying Xtraction database to a new server


Article ID: 106226


Updated On:


SUPPORT AUTOMATION- SERVER CA Service Desk Manager - Unified Self Service CA Service Desk Manager CA Service Management - Asset Portfolio Management CA Service Management - Service Desk Manager


After copying Xtraction database to a new test server and installing Xtraction onto the new server, and configuring it to use the new database, install will appear to complete successfully and Xtraction Settings Check will pass but reports will fail to run with UI error code:
"An error has occurred during processing. Please try again. If this continues to occur, please contact the application administrator.

Xtraction logs will show errors similar to the following:
Date : 7/9/2018 10:40:43 AM
Querystring : 
User Id : USPHC\TZ26297
System.Data.SqlClient.SqlException (0x80131904): Invalid object name 'CALL_REQ'.
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData()
   at System.Data.SqlClient.SqlDataReader.get_MetaData()
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString, Boolean isInternal, Boolean forDescribeParameterEncryption)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, Boolean inRetry, SqlDataReader ds, Boolean describeParameterEncryptionRequest)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
   at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
   at 0.E.0(String , String , String , String , Int32 )
   at 0.E.0(String , String , String , String )
   at 0.i.0(GroupComponentStandardSeries , Int32 )
   at 0.i.0(GroupComponentStandardSeries , Int32 , IndexedDataTable )
   at 0.i.0(GroupComponent )
   at 0.i.GetDataXml(GroupComponent component)
   at SqlDataEngine.Services.Components.GroupComponentService.GetDataXml(GroupComponent component)
   at Xtraction.Web.Services.SqlDataEngineWebService.GetGroupComponentData(GroupComponent component)
ClientConnectionId: xxx
Error Number:208,State:1,Class:16


Component: XTR4SM


When installing Xtraction after copying the database from one server to another, the Xtraction installer will not allow you to install a new data model because it will detect that a data model already exists, forcing you to skip this step. Once the installation is complete, the data model specific to the old server will be in use which will cause the reports to fail. 


Rename the existing DataModel.dat file and then rerun the installer. You will now be given the option to select a data model to install. Proceed with the installation and once the install completes, you can proceed to the "Data Model Settings" portion of the install guide and once this is complete. Once this is complete reports should now run.

Note: You may have to reload the data model and license on the Xtraction home screen by clicking on "Administration -> Reload" in the bottom left corner of the Xtraction home screen.