This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

D1IM History database import error

Hi Team,

We have configured the environment as below:
- D1IM Application, D1IM database and History database are installed on different servers.
- We have carried out the instructions from Configuration.pdf(Prerequisites for Maintaining a History Database), for the above scenario.

We are facing error while executing the script "Import process information directly" from HistoryDB Designer. Please find the attached screenshot and Error log below.

We have also followed the instructions from the discussion "en.community.dell.com/.../19561559", but no luck.

Kindly let us know if anyone has faced the issue or any suggestion as a pointer.

************************************LOG - Start*****************************************************

2015-08-25 02:40:48 -04:00 - Process step parameter d2bfb948-5cd2-4260-911d-51ecb0b8f685:
[Job]
    ComponentAssembly=SQLComponent
    ComponentClass=VI.JobService.JobComponents.SQLComponent
    Task=Execute SQL
    Executiontype=INTERNAL
[Parameters]
    ConnectionProvider=VI.DB.ViSqlFactory,VI.DB
    ProcID=919DC9D5-D513-47D9-A255-D32570D86765
    SQLStmt=exec vi_GetRawFromSource_DropLink N'<DB-Server>', N'<DB-User>', 0
    Value=0
    WithoutTransaction=True
2015-08-25 02:40:48 -04:00 - VI.JobService.JobComponents.SQLComponent - d2bfb948-5cd2-4260-911d-51ecb0b8f685: Successful
    Optimizing by using the existing connection.
2015-08-25 02:40:48 -04:00 - Process step parameter 9887850b-9d97-46f4-aa62-53c223af3f49:
[Job]
    ComponentAssembly=SQLComponent
    ComponentClass=VI.JobService.JobComponents.SQLComponent
    Task=Execute SQL
    Executiontype=INTERNAL
[Parameters]
    ConnectionProvider=VI.DB.ViSqlFactory,VI.DB
    ProcID=919DC9D5-D513-47D9-A255-D32570D86765
    Value=0
    WithoutTransaction=True
2015-08-25 02:40:48 -04:00 - VI.JobService.JobComponents.SQLComponent - 9887850b-9d97-46f4-aa62-53c223af3f49: Errors occured
    Optimizing by using the existing connection.
    [810023] Error during execution of statement: *****
    [810143] Database error 266:
    [System.Data.SqlClient.SqlException] Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements. Previous count = 0, current count = 1.
       at VI.JobService.ProcessorThread._ThreadFunction()
       at VI.JobService.ProcessorThread._ExecuteJob(Job job)
       at VI.JobService.JobComponents.SQLComponent.Activate(String task)
       at VI.JobService.JobComponents.SQLComponent.Task_Execute()
       at VI.DB.SqlExecutor.SqlExecuteNonQuery(String sqlStatement)
       at VI.DB.SqlExecutor.SqlExecuteNonQuery(IQueryProvider provider, IDataParameter[] parms)
       ---- Start of Inner Exception ----
       at VI.DB.SqlExecutor.SqlExecuteNonQuery(IQueryProvider provider, IDataParameter[] parms)
       at VI.DB.SqlExecutor._SqlExecuteNonQuery(DbStatement stmt)
       ---- Start of Inner Exception ----
       at VI.DB.Implementation.SafeDbCommand.ExecuteNonQuery()
       at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
       at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
       at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async)
       at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
       at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
       at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
2015-08-25 02:40:48 -04:00 - Process step parameter 0d8fb5f7-139d-4019-8d99-5212ff5b5516:
[Job]
    ComponentAssembly=SQLComponent
    ComponentClass=VI.JobService.JobComponents.SQLComponent
    Task=Execute SQL
    Executiontype=INTERNAL
[Parameters]
    ConnectionProvider=VI.DB.ViSqlFactory,VI.DB
    ProcID=919DC9D5-D513-47D9-A255-D32570D86765
    SQLStmt=exec vi_GetRawFromSource_DropLink N'<DB-Server>', N'<DB-User>', 0
    Value=0
    WithoutTransaction=True
2015-08-25 02:40:48 -04:00 - VI.JobService.JobComponents.SQLComponent - 0d8fb5f7-139d-4019-8d99-5212ff5b5516: Successful
    Optimizing by using the existing connection.
2015-08-25 03:06:17 -04:00 - Process step parameter 9D389982-0E0B-4381-A9DE-A868B120F8F6:
[Job]
    ComponentAssembly=HandleObjectComponent
    ComponentClass=VI.JobService.JobComponents.HandleObjectComponent
    Task=FIREGENEVENT
    Executiontype=INTERNAL
[Parameters]
    ConnectionProvider=VI.DB.ViSqlFactory,VI.DB
    EventName=UpdateUTCOffset
    ObjectType=DialogTimeZone
    ProcID=625CBD73-3682-48EF-B1D5-438DD559FA2B
    WhereClause=ShortName = 'UTC'
    _paramName1=StopTime
    _paramValue1=2200-01-01 00:00:00.000
2015-08-25 03:06:17 -04:00 - VI.JobService.JobComponents.HandleObjectComponent - 9D389982-0E0B-4381-A9DE-A868B120F8F6: Successful
    The event  UpdateUTCOffset was triggered for 1 object(s) of type DialogTimeZone.
2015-08-25 03:07:47 -04:00 - Process step parameter 29aa953d-6309-4597-986e-c22bb1fde8e0:
[Job]
    ComponentAssembly=ScriptComponent
    ComponentClass=VI.JobService.JobComponents.ScriptComponent
    Task=ScriptExec
    Executiontype=EXTERNAL
[Parameters]
    ConnectionProvider=VI.DB.ViSqlFactory,VI.DB
    ProcID=625CBD73-3682-48EF-B1D5-438DD559FA2B
    ScriptName=VID_TimeZone_Update_UTCOffSet
2015-08-25 03:07:49 -04:00 - VI.JobService.JobComponents.ScriptComponent - 29aa953d-6309-4597-986e-c22bb1fde8e0: Successful
2015-08-25 03:07:49 -04:00 - Process step output parameter 29aa953d-6309-4597-986e-c22bb1fde8e0:
    Value=True

************************************LOG - End*****************************************************

Regards,
Sandeep

error_screenshot.jpg

  • most likely this is because when setting up the seorcedatabase the FQDN of the SQL server was used instead of the named instance version which si returned when select @@servername is executed in SQL.