Sign in
 
HomeProductsLibraryLearnDownloadsSupportForums
Microsoft Forefront TechCenter > Forefront Forums > Forefront Client Security > Error Message 81 - DTS package

Answered Error Message 81 - DTS package

    •  
      Tuesday, June 05, 2007 2:39 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

       

      Anyone seen this before? Cryptic.

       

      The description for Event ID ( 81 ) in Source ( DataTransformationServices ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event:

       

      Error Source: Microsoft Data Transformation Services (DTS) Package

      Error DescriptionStick out tongueackage failed because Step 'DTSStep_DTSTransferObjectsTask_1' failed.

      Error code: 80040428

      \Error Help FileTongue Tiedqldts80.hlp

      Error Help Context ID:700

       

       

      Package Name: Microsoft Forefront Client Security

      Package Description: Microsoft Forefront Client Security DTS

      Package ID: {4589F8C7-17D3-4A87-BB5B-0DBF47B6D00A}

      Package Version: {B7EBB012-DE23-42DB-97E4-BBADF471D7C3}

      Package Execution Lineage: {753C1667-5DFA-418B-9CF8-3D7DA0BA7AB7}

      Executed On: SVARIAVAP01T

      Executed By: zzSQLSvc

      Execution Started: 6/5/2007 1:15:01 AM

      Execution Completed: 6/5/2007 1:15:03 AM

      Total Execution Time: 2.359 seconds

       

      Package Steps execution information:

       

       

      Step 'DTSStep_DTSTransferObjectsTask_1' failed

       

      Step Error Source: Microsoft Data Transformation Services (DTS) Package

      Step Error Description:Invalid OLEVERB structure

       (Microsoft Data Transformation Services (DTS) Package (80040000): Invalid OLEVERB structure

      ) (Microsoft SQL-DMO (80004005): [SQL-DMO]CreateFile error on 'SVARIAVAP01T.OnePoint.LOG'. )

      Step Error code: 80040000

      Step Error Help FileTongue Tiedqldts80.hlp

      Step Error Help Context ID:1100

       

      Step Execution Started: 6/5/2007 1:15:01 AM

      Step Execution Completed: 6/5/2007 1:15:03 AM

      Total Step Execution Time: 1.859 seconds

      Progress count in Step: 0

       

      Step 'DTSStep_DTSTransferObjectsTask_3' was not executed

       

      Step 'DTSStep_DTSExecuteSQLTask_1' was not executed

       

      Step 'DTSStep_DTSDynamicPropertiesTask_1' succeeded

      Step Execution Started: 6/5/2007 1:15:01 AM

      Step Execution Completed: 6/5/2007 1:15:01 AM

      Total Step Execution Time: 0.078 seconds

      Progress count in Step: 0

       

      Step 'DTSStep_DTSExecuteSQLTask_2' succeeded

      Step Execution Started: 6/5/2007 1:15:01 AM

      Step Execution Completed: 6/5/2007 1:15:01 AM

      Total Step Execution Time: 0.281 seconds

      Progress count in Step: 0

       

      Step 'DTSStep_DTSExecuteSQLTask_3' was not executed.

       

       

       

      thx.

       

    Answers

    • Tuesday, June 05, 2007 5:03 PM
       
       Answered
      Sign In to Vote
      1
      Sign In to Vote

      Hello bkg,

       

      I have not personally seen this error, but it may be a problem with the ScriptFileDirectory settings for your DTS package. Please ensure that your ScriptFileDirectory for your DTS exists and is accessible to the account that your SQL Server Agent service is running under.

       

      You can find the ScriptFileDirectory value by doing this:

      1. Open up SQL Server Management Studio
      2. Connect to your server
      3. Navigate to Management->Legacy->Data Transformation Services
      4. Right-click on 'Microsoft Forefront Client Security' and choose 'Open'
      5. Click the 'Package' menu and choose 'Properties'
      6. Navigate to the 'Global Variables' tab and see what value is set for 'ScriptFileDirectory'.

      Once you have this value, ensure that the directory exists and the zzSQLSvc account has write access to this directory.

       

      Hope this helps!

       

    All Replies

    • Tuesday, June 05, 2007 5:03 PM
       
       Answered
      Sign In to Vote
      1
      Sign In to Vote

      Hello bkg,

       

      I have not personally seen this error, but it may be a problem with the ScriptFileDirectory settings for your DTS package. Please ensure that your ScriptFileDirectory for your DTS exists and is accessible to the account that your SQL Server Agent service is running under.

       

      You can find the ScriptFileDirectory value by doing this:

      1. Open up SQL Server Management Studio
      2. Connect to your server
      3. Navigate to Management->Legacy->Data Transformation Services
      4. Right-click on 'Microsoft Forefront Client Security' and choose 'Open'
      5. Click the 'Package' menu and choose 'Properties'
      6. Navigate to the 'Global Variables' tab and see what value is set for 'ScriptFileDirectory'.

      Once you have this value, ensure that the directory exists and the zzSQLSvc account has write access to this directory.

       

      Hope this helps!

       
    • Tuesday, June 05, 2007 7:14 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      This in conjunction with giving the sql service account greater rights to the folder took care of the problem (per Shain).

       

      Thanks,

      bkg

       
    • Tuesday, May 05, 2009 9:14 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      It helped Jeff!!

      I had the same error and when I was searchig I found this answer. It worked absolutely perfect for me.

      Thank You.
       
    • Tuesday, July 20, 2010 12:55 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      No joy for me I'm afraid... the 14 day report has failed to run for the past x amount of days displaying no data.

      I have exactly the same errors as listed here:  If I try and run the DtsSchedule manually, I can see the DTSWarehouse running as a process for literally 5 seconds - then it stops.  After this point, I check the History of the Scheduled task, and all processes have completed ok.  Its' only at 1am ish that I get the event in Windows Logs ...

      Today I have also reduced the data retention period on all tables to 300 days ?(I did notice that the Onepoint DB dropped about 6gb in size as it was 34 then down to 28 ... I know this has a 30gb limit)

      Can I clarify that the SQL account that needs access to the ScriptFile directory is the SVC account that runs the DTS job ... in this case its the default for me svc_das_xxx

      Please help - it's driving me mad and I am spending soooo much time trying to fix it!!!  If there is any other info I need to supply, please let me know.

      Many thanks.