none
Cannot insert log file Event 1017, ACT LPS RRS feed

  • Question

  • Im using ACT 5.5, and all status*.xml files are moved to the failed directory.
    All other files BKT*.xml are correctly processed.

    Does anyone got any ideas why the status*.xml files are not processed?

    I see the following error in the event viewer (i removed server and sharename from the log):

    Log Name:      Application
    Source:        ACT-LPS
    Date:          29-1-2010 15:58:07
    Event ID:      1017
    Task Category: None
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      mnghw01.KAO.SBWINFRA.NL
    Description:
    [queuer.exe] [Queuer] Cannot insert log file \\[servername]\[sharename]\Uncompressed\STATUS-CZC61436KD{2F595241-18B2-4E23-86A9-B003157F8774}.xml to the database!  Details:

    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="ACT-LPS" />
        <EventID Qualifiers="32768">1017</EventID>
        <Level>3</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2010-01-29T14:58:07.000Z" />
        <EventRecordID>3293</EventRecordID>
        <Channel>Application</Channel>
        <Computer>mnghw01.KAO.SBWINFRA.NL</Computer>
        <Security />
      </System>
      <EventData>
        <Data>[queuer.exe] [Queuer] Cannot insert log file \\MNGHW01\ACT$\Uncompressed\STATUS-CZC61436KD{2F595241-18B2-4E23-86A9-B003157F8774}.xml to the database!  Details:
    </Data>
        <Binary>41002D005100550045005500450052002D007B00460033003500430037003500410035002D0043003200430036002D0034006100660036002D0038003800350044002D003800410044003000370042004500430032004400430031007D00</Binary>
      </EventData>
    </Event>

    Friday, January 29, 2010 3:09 PM

Answers

  • Are you trying to run a data collection package that has been imported into the App Compat Manager instance? This is a known issue with the current version of ACT. As a result, the network share that the package is writing to isn't updated in the ACT database when you import a package.

    There is a slightly involved database-level fix you can put in (mail back if you're interested in trying this), but otherwise, this shouldn't impact the deployment or the issue detection. The status logs are just to update you on how far along the data collection packages are in their collection in your environment.

    -Ajith
    Friday, March 12, 2010 2:53 AM

All replies


  • Do you have FIPS enabled on your collection server? You can check via these two methods:

    1. Use regedit.exe and check the following registry key value:

    HKLM\System\CurrentControlSet\Control\Lsa\FipsAlgorithmPolicy, Enabled=0,1

    2. Use secpol.msc navigate to and check Local Policies\Security Options, System cryptography: Use FIPS compliant algorithms for encryption, hashing and signing

    If FIPS is enabled=1, it could be the culprit. Try enabled=0 via regedit.exe or setting it to disabled in the Local Security Policy console.
    Wednesday, March 3, 2010 12:27 AM
  • Thanks for you're reply.
    FIPS is already disabled
    Tried to enable, then disable again, but same result, sadly.
    Wednesday, March 3, 2010 12:01 PM
  • Are you trying to run a data collection package that has been imported into the App Compat Manager instance? This is a known issue with the current version of ACT. As a result, the network share that the package is writing to isn't updated in the ACT database when you import a package.

    There is a slightly involved database-level fix you can put in (mail back if you're interested in trying this), but otherwise, this shouldn't impact the deployment or the issue detection. The status logs are just to update you on how far along the data collection packages are in their collection in your environment.

    -Ajith
    Friday, March 12, 2010 2:53 AM
  • I had a similar issue.  Here is what caused the problem and how I fixed it.

     

    We had a few people setup ACT 5.5 on their workstation.  instead of selecting View and reporting only, they chose the Enterprise install, and then pointed at the existing database and LPS share.  This changed the security on the LPS share to where the log processor on the server could no longer process the logs. 

    I fixed the problem by resetting the LPS Share in ACT.  When respecifing the LPS Share, make sure you don't change the share, just change a character in the share name from upper to lower case or vice-versa.  Click Apply and move ALL the logs from the FAILED folder to the parent folder and the logs should start being processed.  You have to move all the logs at one time so the log processor will process them in the correct order.

    Let me know if this helps.

    Tuesday, May 18, 2010 7:17 PM
  • This requires some SQL work.   Use this KB to correct the issue.

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

    Friday, November 30, 2012 2:38 AM