Post reply

Unable to Schedule SSIS Package execution using Sql Agent in SSMS

  • September 16, 2013 at 8:41 am

    #282539

    Hi All,

    We have created a simple SSIS package on our servers and the Packge can be executed Manually. It gives no errors. However, When we try to schedule the package execution using Sql Agent Job, the job fails with the below error :

    Executed as user: domainname\some_service. Microsoft (R) SQL Server Execute Package Utility Version 10.50.4000.0 for 64-bit Copyright (C) Microsoft Corporation 2010. All rights reserved. Started: 7:03:31 PM Error: 2013-09-16 19:03:31.80 Code: 0xC0011007 Source: {35999CF7-5D5E-41EE-8EB8-ED0D45DCFFE8} Description: Unable to load the package as XML because of package does not have a valid XML format. A specific XML parser error will be posted. End Error Error: 2013-09-16 19:03:31.80 Code: 0xC0011002 Source: {35999CF7-5D5E-41EE-8EB8-ED0D45DCFFE8} Description: Failed to open package file "D:\SCT_SOME_ETL_PKG\Some_BFL_ETL\Some_BFL_ETL\bin\Deployment\Package2.dtsx" due to error 0x80070003 "The system cannot find the path specified.". This happens when loading a package and the file cannot be opened or loaded correctly into the XML document. This can be the result of either providing an incorrect file name was specified when calling LoadPackage or the XML file was specified and has an incorrect format. End Error Could not load package

    The service acccount with which we login is admin on the server and the job is scheduled using sysadmin proviliges.

    Also, Full COntrol has been given explicitly as well to the Folder where the package is present(Since its on the same local server).

    Can anyone please suggest something looking at the error message?

    Thanks in advance.!!

  • September 16, 2013 at 11:37 am

    #1650549

    Hi Rollercoaster43

    Please do following steps:

    Start BIDS as user: domainname\some_service, run the package and check the result, you will be sure the job executor account has the right to run this SSIS package.

    SSIS uses absolute paths to point to objects on the file system. Check the path D:\SCT_SOME_ETL_PKG\Some_BFL_ETL\Some_BFL_ETL\bin\Deployment\Package2.dtsx

    It's probably inaccessible from SQL Server Agent, try to copy Package2.dtsx i.e. to C:\TEMP on server and set in Job step.

    Regards

    Mike

  • September 17, 2013 at 2:40 am

    #1650699

    Thanks for the reply Mike.

    I will check this and get back to you today.

  • September 17, 2013 at 3:02 am

    #1650703

    try to rename ur package and schedule the new named package.

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply