none
ACTUpdate error (failed logs are accumulating) RRS feed

  • Question

  • I am currently testing an ACT install (using SQL express) on 2 virtual machines (1 DC vm and 1 Vista vm).

    Everything installed fine, created a DCP but the report data is empty even though my DCP completed its run on the VIsta client.

    Can anyone help? thanks!

     

    Below is a transcript of the error from the application event log:

     

    Log Name:      Application
    Source:        ACTUpload
    Date:          12/8/2008 1:20:54 AM
    Event ID:      0
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      LAB2DC1X86.lab2.local
    Description:
    ACTUPLOAD: Microsoft.ApplicationExperience.Common.ObjectFramework.PersistenceException: Persistence_FlushSqlError ---> System.Data.SqlClient.SqlException: The INSERT statement conflicted with the FOREIGN KEY constraint "Logical_Machine_OS_ForeignKey". The conflict occurred in database "ACTDB1", table "dbo.OS", column 'osID'.
    Stale Data
    The statement has been terminated.
       at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
       at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
       at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
       at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
       at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()
       at System.Data.SqlClient.SqlDataReader.get_MetaData()
       at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
       at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
       at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
       at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
       at System.Data.SqlClient.SqlCommand.ExecuteScalar()
       at Microsoft.ApplicationExperience.Common.ObjectFramework.SqlCommandBatch.ExecuteBatch()
       --- End of inner exception stack trace ---
       at Microsoft.ApplicationExperience.Common.ObjectFramework.SqlCommandBatch.ExecuteBatch()
       at Microsoft.ApplicationExperience.Common.ObjectFramework.SqlCommandBatch.AddToBatch(SqlCommand aCommand, ObjectInfo relatedObjectInfo)
       at Microsoft.ApplicationExperience.Common.ObjectFramework.SqlPersistenceService.InsertObject(SqlConnection aConnection, SqlTransaction trans, ObjectInfo objectToInsert, ISqlCommandHandler commandBatch, IAudit auditor)
       at Microsoft.ApplicationExperience.Common.ObjectFramework.SqlPersistenceService.FlushAllAdded(SqlConnection aConnection, SqlTransaction trans, ObjectInfoCollection insertedObjects, IAudit auditor)
       at Microsoft.ApplicationExperience.Common.ObjectFramework.SqlPersistenceService.Flush(IdentityMap theCache, AssociationCache anAssociationCache, IAudit auditor, Role currentRole, SqlConnection myConnection, SqlTransaction trans, PostEnumerationCallback snapshot)
       at Microsoft.ApplicationExperience.Common.ObjectFramework.SqlPersistenceService.FlushCache(IdentityMap theCache, AssociationCache anAssociationCache, IAudit auditor, Boolean useSeparateConnection, PostEnumerationCallback callback)
       at Microsoft.ApplicationExperience.Common.ObjectFramework.ObjectContext.Flush(Boolean useSeparateConnection, PostEnumerationCallback snapshot)
       at Microsoft.ApplicationExperience.Common.DataManipulation.XmlDataProcessor.FlushXmlDocument(PostEnumerationCallback snapshot)
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="ACTUpload" />
        <EventID Qualifiers="0">0</EventID>
        <Level>2</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2008-12-08T07:20:54.000Z" />
        <EventRecordID>1085</EventRecordID>
        <Channel>Application</Channel>
        <Computer>LAB2DC1X86.lab2.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data>ACTUPLOAD: Microsoft.ApplicationExperience.Common.ObjectFramework.PersistenceException: Persistence_FlushSqlError ---&gt; System.Data.SqlClient.SqlException: The INSERT statement conflicted with the FOREIGN KEY constraint "Logical_Machine_OS_ForeignKey". The conflict occurred in database "ACTDB1", table "dbo.OS", column 'osID'.
    Stale Data
    The statement has been terminated.
       at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
       at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
       at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
       at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
       at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()
       at System.Data.SqlClient.SqlDataReader.get_MetaData()
       at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
       at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
       at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
       at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
       at System.Data.SqlClient.SqlCommand.ExecuteScalar()
       at Microsoft.ApplicationExperience.Common.ObjectFramework.SqlCommandBatch.ExecuteBatch()
       --- End of inner exception stack trace ---
       at Microsoft.ApplicationExperience.Common.ObjectFramework.SqlCommandBatch.ExecuteBatch()
       at Microsoft.ApplicationExperience.Common.ObjectFramework.SqlCommandBatch.AddToBatch(SqlCommand aCommand, ObjectInfo relatedObjectInfo)
       at Microsoft.ApplicationExperience.Common.ObjectFramework.SqlPersistenceService.InsertObject(SqlConnection aConnection, SqlTransaction trans, ObjectInfo objectToInsert, ISqlCommandHandler commandBatch, IAudit auditor)
       at Microsoft.ApplicationExperience.Common.ObjectFramework.SqlPersistenceService.FlushAllAdded(SqlConnection aConnection, SqlTransaction trans, ObjectInfoCollection insertedObjects, IAudit auditor)
       at Microsoft.ApplicationExperience.Common.ObjectFramework.SqlPersistenceService.Flush(IdentityMap theCache, AssociationCache anAssociationCache, IAudit auditor, Role currentRole, SqlConnection myConnection, SqlTransaction trans, PostEnumerationCallback snapshot)
       at Microsoft.ApplicationExperience.Common.ObjectFramework.SqlPersistenceService.FlushCache(IdentityMap theCache, AssociationCache anAssociationCache, IAudit auditor, Boolean useSeparateConnection, PostEnumerationCallback callback)
       at Microsoft.ApplicationExperience.Common.ObjectFramework.ObjectContext.Flush(Boolean useSeparateConnection, PostEnumerationCallback snapshot)
       at Microsoft.ApplicationExperience.Common.DataManipulation.XmlDataProcessor.FlushXmlDocument(PostEnumerationCallback snapshot)</Data>
      </EventData>
    </Event>
    Monday, December 8, 2008 7:29 AM

Answers

  • Hi,

     

    I have the following suggestions.

     

    1.Create a new database to test the problem.

    2.Completely Turn off Windows Firewall, before setting up ACT LOG Processing share. Or continue using Windows Firewall but enable the File Sharing option.

    3.Then, please refer to the following document to check if it is a connection issue.

     

    ACT 5 Step by Step Guides (Please refer to ACT_Configuration_and_Troubleshooting)

    http://www.microsoft.com/downloads/details.aspx?FamilyID=BC931BFD-D279-4060-B370-08FA52F97A8D&displaylang=en

     

    Hope it helps.

     

    Tuesday, December 9, 2008 8:24 AM
    Moderator

All replies

  • Hi,

     

    I have the following suggestions.

     

    1.Create a new database to test the problem.

    2.Completely Turn off Windows Firewall, before setting up ACT LOG Processing share. Or continue using Windows Firewall but enable the File Sharing option.

    3.Then, please refer to the following document to check if it is a connection issue.

     

    ACT 5 Step by Step Guides (Please refer to ACT_Configuration_and_Troubleshooting)

    http://www.microsoft.com/downloads/details.aspx?FamilyID=BC931BFD-D279-4060-B370-08FA52F97A8D&displaylang=en

     

    Hope it helps.

     

    Tuesday, December 9, 2008 8:24 AM
    Moderator
  • I have exactly the same problem - running ACT 5.6 evaluating a Windows XP computer. I think there must be some bad data (out of range, wrong format etc) in the XML file but have no idea where. I have tested the offending XML file on two completely different implementations of ACT with the same result. Anyone with any ideas?
    • Proposed as answer by Paul Harfield Thursday, June 14, 2012 1:50 PM
    • Unproposed as answer by Paul Harfield Thursday, June 14, 2012 1:50 PM
    Tuesday, April 12, 2011 11:24 AM
  • I know this reply is a long time after the fact but had the same issue,

    Root cause was the version of windows the agent was running on was 6.1.1 (Win 7 sp1 ) which was not an entry in the DB.OS table.

    Updated the XML manually to 6.1.0 and dropped the failed files into the parent folder to re-process and it works

    Paul

    • Proposed as answer by Paul Harfield Thursday, June 14, 2012 1:52 PM
    Thursday, June 14, 2012 1:52 PM
  • Here is an alternative method that does not require you to modify all of your XML files:

    http://msincic.wordpress.com/2011/09/06/error-in-microsoft-act-5-6-with-windows-7-and-2008-r2-sp1/

    based on this article:

    http://support.microsoft.com/kb/2533953

    • Proposed as answer by terminic Saturday, August 18, 2012 12:33 PM
    Saturday, August 18, 2012 12:33 PM