October 23, 2008 at 3:40 pm
Hi I have an SSIS Package which is running fine. I need to schedule this package in MS SQL Server 2005 JOB but that is throwing error........
Currently the Protection Level is set to : EncryptSensetiveWithUserKey, Though I have changes it to DontSaveSensitive also still not working.... Here is the error I am getting
Message
Executed as user: USAPH103A\SYSTEM. ...n 9.00.3042.00 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 5:37:53 PM Error: 2008-10-23 17:37:53.28 Code: 0xC0011007 Source: {806675FF-65B8-4649-983C-25F16EDCF3F2} 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: 2008-10-23 17:37:53.28 Code: 0xC0011002 Source: {806675FF-65B8-4649-983C-25F16EDCF3F2} Description: Failed to open package file "C:\BIProj\HeaderBOM_DW\HeaderBOM_DW\bin\Package.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 Err... The package could not be f... The step failed.
Can any one tell the sep by step method to schedule this package ?
Thanks
October 23, 2008 at 5:10 pm
You'll need to change ProtectionLevel to EncryptAllWithPassword or EncryptSensitiveWithPassword, supply the password in the command line in the job step or in a config file, and grant the login that runs SQL Agent access to the folder where the .dtx file is located.
When a package is executed in a job, it is executed by the job owner, usually the SQL Agent account.
Greg
October 24, 2008 at 8:57 am
Thanks Greg.........
I have done as you suggested still the error persists.........
Message
Executed as user: USAPH103A\SYSTEM. ...n 9.00.3042.00 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 10:29:13 AM Error: 2008-10-24 10:29:13.29 Code: 0xC0011007 Source: {FA1D5AF7-EED7-4B44-B90E-44EF2125757F} 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: 2008-10-24 10:29:13.29 Code: 0xC0011002 Source: {FA1D5AF7-EED7-4B44-B90E-44EF2125757F} Description: Failed to open package file "C:\BIProj\HeaderBOM_DW\HeaderBOM_DW\bin\Package.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 Er... The package could not be f... The step failed.
Any idea , what can be done to resolve this....
October 24, 2008 at 10:03 am
have you imported the package to the file system or package store on the server
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
October 24, 2008 at 10:14 am
I am quite a novice and learning SSIS. The package is stored on the local machine and the Database server is the different machine. I am accessing the data base machine from my machine and scheduling job.
I would appreciate if you please tell me the step by step method to do this.
Thanks in advance...
October 29, 2009 at 1:52 pm
Hi,
I am also facing this same problem.
Executed as user: NA\svc-sqlinst30-clst22. ...3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 2:40:02 PM Error: 2009-10-29 14:40:02.90 Code: 0xC0011007 Source: {0DF55DB1-0DEA-4A6D-AFED-EBA0DA693C1B} 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: 2009-10-29 14:40:02.90 Code: 0xC0011002 Source: {0DF55DB1-0DEA-4A6D-AFED-EBA0DA693C1B} Description: Failed to open package file "\\xxx.xxx.xxx.xx\text_transfer\VACP_Info_Schema_R1.dtsx" due to error 0x8007052E "Logon failure: unknown user name or bad password.". 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... The package could not be f... The step failed.
The Folder (\xxx.xxx.xxx.xx\text_transfer) has to all
October 29, 2009 at 2:17 pm
RV-813525 (10/24/2008)
I am quite a novice and learning SSIS. The package is stored on the local machine and the Database server is the different machine. I am accessing the data base machine from my machine and scheduling job.I would appreciate if you please tell me the step by step method to do this.
Thanks in advance...
This may not be the most exhaustive list of steps, but wanted to help.
1.First move your Package to the SSIS Server where you are going to run the Packages.
2.Try to see that all the package dependents are available on that SSIS Server Such as Configuration, Log Files etc. ( I suspect one such thing may be causing the error)
3. As already mentioned, use either of the choices to store the sensitive data by password.
Save the package and test it by executing the package.
For now this should let us know some more info, if not we would need to next deploy it onto the server by building the package I would explain after your feedback what happened when you tried with the first 3 steps.
Blog -- LearnSQLWithBru
Join on Facebook Page Facebook.comLearnSQLWithBru
Twitter -- BruMedishetty
June 9, 2011 at 10:07 am
Medishetty's reply helps me alot. Once i move the SSIS package and source file to same server, it works. Now, I just have to figure out how I can put my mapped drive path in the command since all my source file and SSIS package in another location.
June 10, 2011 at 2:41 am
You can, assuming your agent account is running with appropriate permissions, put the files on a UNC path (\\MyOtherServer\c$\xxxx)
To test it, it is easier to enable xp_cmdshell and run exec xp_cmdshell 'dir \\MyOtherServer\c$\xxxx'
if you get a valid listing or access denied, you know which way the account goes...
Cheers,CrispinI can't die, there are too many people who still have to meet me!It's not a bug, SQL just misunderstood me!
February 29, 2012 at 8:44 am
Thanks SSC Eights!!!
your command shell comment put me on the right track...
Using file system to store my package, I was importing the package into my Integration Services server but using the file on the network, that I was importing, in my Sql Job.
Once you import the file into you Integration Services Server, (right click import in SSIS under file system) you can access your Package locally... which, in my case, it can be found under C:\Program Files\Microsoft SQL Server\90\DTS\Packages...
Thanks again!
🙂
February 29, 2012 at 8:54 am
Thanks SSC Eights!!!
His real name is Crispin 🙂
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
February 29, 2012 at 9:00 am
Oooopps!!!! :w00t:
My eyes played tricks on me ... I guess my eyes are used to the name being under the pic... LOL
I guess an official thanks to Crispin Proctor is due!!!
Thanks Crispin
:hehe:
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply