I am currently migrating a database from an old SQL Server 2012 to a new system running SQL Server 2019. In addition to the database I am also migrating several SQL Server Agent Jobs.
One of these jobs consists of multiple different steps, one that just runs a PowerShell script and two other steps that are implemented as an SSIS package. When I execute one of the steps that are implemented as SSIS package, I get the following error:
The process could not be created for step 2 of job <long hexadecimal number> (reason: The system cannot find the file specified). The step failed.
How am I supposed to diagnose this error? I have no idea which file cannot be found and why. Is there no way to get any additional information about this error? I already checked all files involved in the SSIS package such as the package file itself, the configuration file and all files that are accessed during the execution of the step but I cannot find the reason for this error.
Could there be a compatibility issue since the packages are executed in a new SQL Server 2019 instead of the older SQL Server 2012? If so, how can I check if this is actually the case?
Thanks a lot in advance!
Having the exact same issue.
Found a workaround, don't like it, but it did get the package run.
Change "Type" from SQL Server Integration Services Package" to "Transact-SQL script (T-SQL)"
Make your SQL Statement something like:
EXEC xp_cmdshell '""C:\Program Files\Microsoft SQL Server\150\DTS\Binn\DTExec.exe" /FILE "\"<Path To Package>\<PackageName>.dtsx\"" /WARNASERROR /X86 /CHECKPOINTING OFF /REPORTING E'
Note that the start of the command '"" is NOT a type-o, neither is the \"" right after the .dtsx package name.
Don't like this answer, but until the correct solution comes along... it is working.
Related
I have generated several packages with BIML but none of them load into the SSIS designer. Every one shows a white screen with the error message: Error loading 'Stage_BNSCHED.dtsx' : The package failed to load due to error 0x80070057 "The parameter is incorrect.". This occurs when CPackage::LoadFromXML fails. I can't even figure out where to start on this one. The BIML script will compile just fine and the packages are created, but I can't open them. Also, Visual Studio won't let me save the project or solution because of this error.
BIMLExpress 2019 Build 5.4.64108.0
SQL Server Data Tools for Visual Studio 2017 version 15.9.21
SQL Server 2017 Standard Edition 14.0.3281.6
Appreciate any suggestion on where to start.
As I removed pieces to find the offending section of code, I came across the problem. I was attempting to do an update in an OLE DB Command, where I was updating a key value that was also in the WHERE clause. Once I rewrote that section to only list the non-key fields, everything worked as planned. I think technically that's legal in SQL but SSIS sure doesn't like it.
I know similar questions have been asked before...
I am working on a remediation project which requires to migrate an existing SSIS package from SQL Server 2008 32-bits to 2014 64 bits. The data source is an Ingres database (32-bit server, 2 tables). Some CRUD statements are performed in SSIS because updates a couple of tables on the SQL Server side.
It works beautifully on the previous platforms but with the SQL Server upgrade to 2014-64 bit it does not work anymore, with the famous error
The specified DSN contains an architecture mismatch between the Driver and Application
I have tried to set the "Run64bitRunTime" flag in the SSIS package to false, but then the OLEDB driver on SQL Server 2014 complains
An OLE DB error has occurred.... An OLE DB record is available.The AcquireConnection method call to the connection manager “” failed...
Out of curiosity when I tried to use the SQL Server Import and Export 32-bits program I can communicate with both Ingres and SQL Server 2014 and transfer data across from Ingres to SQL with no problem. I can save the Import-and-Export into a package but I really don't want to add all the SQL transformation statements from the original package to the new one (consider it is a remediation project).
I am now confused why the new package fails, but the Import and Export wizard works? Is there something I need to change in the new package to make it works in the new environment (apart from altering the Run64bitRunTime flag)
More information: I have tried to install the SSIS package as a file, or as part of the Integration Services Catalog, but both fail.
Any more information required please let me know. Thanks in advance.
I have resolved my problem by editing the SSIS package to make the SQL server data source to become OLEDB. It was painful to remap all the data columns though.
I am trying to set up a new SQL Agent job on a SQL2012 server. At the point of defining the job step type = SSIS package, the sql agent setup crashes and I get the following error:
the type initializer for ‘’ threw an exception. (SQLManagerUI) Additional information: Attempted to read or write protected memory. This is often an indication that other memory is corrupt. (DTEParseMgd)
Other posts suggest that the only workaround is to install SQL2014 or 2016, or return to SQL2008. None of these options are possible for us.
We have to move away from SQL2008 for security reasons. We cannot move to SQL2014 because we use access adp project front ends which need the SQLOLEDB data provider which is obsolete in SQL2014.
Does anyone know if Microsoft have released a service patch for SQL2012 which fixes this issue for good?
That memory error sounds like a server issue, but until you track that down, here's a workaround: set the job step type to "Operating System (CmdExec)", and use DTEXEC, for example:
DTExec /DTS "\<ssisPkgName>" /DECRYPT <pkgPass> /MAXCONCURRENT " -1 " /CHECKPOINTING OFF
Note that if the SSIS package requires 32-BIT execution (true for exporting to Excel, for example), then use the DTEXEC utility in "Program Files (x86)" by fully qualifying it. Example, where the SQL Server application was installed on an "E:" drive, and where SQL Server 2014 is being used:
E:\Program Files (x86)\Microsoft SQL Server\120\DTS\Binn\DTExec.exe" /DTS "\<ssisPkgName>" /DECRYPT <pkgPass> /MAXCONCURRENT " -1 " /CHECKPOINTING OFF
If your SSIS packages are in the file system (as ".dtsx" files), then replace "/DTS" with "/FILE".
If your SSIS packages were placed in SSISDB (using the "project deployment model", which is available starting with SQL Server 2012, instead of the older "package deployment model"), then replace "/DTS" with "/ISSERVER"
Lastly, consider your job step's "Run as": if your job step's "Run as" was already set to a proxy, then you already made that proxy "active" to the subsystem "SQL Server Integration Services Package". Now, to do command lines like the above, check that proxy's properties, and make sure it is also "active" to the subsystem "Operating system (CmdExec)". (If you're not using a proxy, then you may need to add "Operating system (CmdExec)" for the SQL job agent... but a proxy is better for security: why grant stuff to the agent, that you will only use in specific circumstances?)
(P.S. side benefit: with the above, I find it easier to get logging from the SSIS package.)
We have a new SQL 2008 R2 instance that's part of a cluster (active/passive) on Windows 2008. I'm testing an SSIS package on the SQL instance that calls many child packages. It's been dying on random packages (rarely the same one twice) with the following error:
Error 0x80004003 while preparing to load the package. Invalid pointer.
I can run the individual package from the SSIS package store just fine. I can also run the master package from BIDS and it'll run perfectly.
I've tried a repair on the SQL instance but there was no difference. I also tried removing and reimporting all the packages to the SSIS package store, with no change. My google-fu is weak, because I can't find anything useful in the cloud.
Nothing is in either the SQL server error logs or any Windows error logs.
Anyone have any ideas?
I have the same issue.
I closed the visual studio and restart it as an administrator (Shift + Right Click using the Mouse) and it worked fine with me.
What worked for me was chaging the protection level on the packages. I set the protection level on the parent and all the child packages to DontSaveSensitive, and re-deployed. No longer received the errors.
Hope this helps someone.
Rebuilding the master package from the ground up fixed the issue. Still, if someone has an idea, I'd love to hear it; rebuilding it is a pain on a good day.
I was facing same problem. I used Execute package Utility (EPU) to run Parent package created from BIDS 2008. somehow It gave me error
Error 0x80004003 while loading the package. Invalid pointer.
The issue was having two SQL Server, 2008 R2 and 2012. By default, "EPU" run from SQL Server 2012 which is failed because package created from BIDS 2008. You have to run EPU from SQL Server 2008 folder which execute package successfully.
I hope this help you.
Yatin Patel
I had this package which been running fine since a year or more. All of sudden it has thrown below error. Though on restart it was success. How to debug this issue and prevent from happening again.
Executed as user: xxxxx. Microsoft (R) SQL Server Execute Package Utility Version
10.0.2531.0 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved.
Started: 7:15:08 AM Error: 2011-07-07 07:15:08.62 Code: 0xC0010018 Source:
Description: Error loading value "
<DTS:VariableValue xmlns:DTS="www.microsoft.com/SqlServer/Dts"
DTS:DataSubType="ManagedSerializable"
DTS:DataType="13"><SOAP-ENV:Envelope
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:SOAP-ENC="htt" from node "DTS:VariableValue".
End Error
Error: 2011-07-07 07:15:08.62 Code: 0xC0010018 Source:
Description: Error loading value
"<DTS:Variable xmlns:DTS="www.microsoft.com/SqlServer/Dts">
<DTS:Property DTS:Name="Expression"></DTS:Property>
<DTS:Property DTS:Name="EvaluateAsExpression">0</DTS:Property>
<DTS:Property DTS:Name="Namespace">User</DTS:Property>
<DTS:Property DTS:Name=" from node "DTS:Variable".
End Error
Could not load package "d:\edw\edw\trunk\src\etlHandler\HDL\DropZoneJobHandler.dtsx"
because of error 0xC0010014.
Description: The package failed to load due to error 0xC0010014 "One or more
error occurred. There should be more specific errors preceding this one that
explains the details of the errors. This message is used as a return value
from functions that encounter errors.". This occurs when CPackage::LoadFromXML fails.
Source: Started: 7:15:08 AM Finished: 7:15:08 AM Elapsed: 0.609 seconds.
The package could not be loaded. The step failed.
I have had this issue on Visual Studio 2015 when creating SSIS Packages.
To resolve it, I changed the TargetServerVersion to SQL Server and that resolved the error.
I was using SSIS package which was upgraded to SSIS 2012, and the SSMS that I was using was 2008. This was the issue that I faced, and I opened the SSMS 2012 and it stopped throwing this error.
I hope this is the case, although with what I have researched, this error could be thrown for various other reasons as well.
For me the error came from a bad password when opening the package. It's strange because usually it just asked me to type in the password again, but since last VS2017 update, the package just fails.
I was getting this 0xC0010014 error when I used a VS 2017 ent build with a dtexec on a server. I set server to SQLServer2014 and the job started to run, but for a while it would throw the 0xC0010014 at the top of the ssis log but still run successfully. I think if you have EncryptSensitiveWithPassword you have to reset the package password after you make the SQLServernnnn change. You have to be aware of what version of dtexec you have on the server, what version the package might have been built in originally (many packages run for years without touching them and may have been built with vs 2015 or vs 2012) and what version of VS you are building with (easier to keep a laptop up to date, maybe you have VS 2017 or VS 2019). You might have a really current Visual Studio to do your builds, but be running in a really old server/dtexec environment.
I have resolved this issue by changing a connection that was referencing to one of my DSN entries that was not created.
After removing the connection, I was able to view the package and then I created a new connection after the new DSN was created.
Please let me know if you need more details and i will provide.
Thanks.
I encountered this error when attempting to schedule an SSIS job to run using SQL Agent. The error came up after I'd selected the package and clicked OK to exit the setup of the step in SQL Agent.
In my environment, I develop SSIS jobs on server A, and schedule jobs in SQL Agent from my local computer. SQL is hosted on server B.
I'm usually able to schedule jobs without error using SSMS on my local computer. However, this particular SSIS package uses the Sharepoint List Adapater, which I'd installed on server A for the SSIS development.
The solution was to install that adapter on my local computer. I also installed it on server B, which hosts our SQL instance.
The solution for this scenario was asking customer change the debug option Run64BitRuntime from True to False. With this Run64BitRuntime=False setting, all works as in 32bit mode. See below link:
https://blogs.msdn.microsoft.com/farukcelik/2010/06/16/why-package-load-error-0xc0010014-in-cpackageloadfromxml-error-appears-while-trying-to-run-an-ssis-package/
I had similar issue when I try to setup Import/Export process on SQL server and save it as SSIS package. I was using excel(.xlxs) as source file.
I resolved it by installing https://www.microsoft.com/en-pk/download/confirmation.aspx?id=4438 (Access 2007 Runtime) on sever).
I created a new project in VS 2019, added a couple tasks and tried to upload and got this error.
Solution: SQL Server was 2012 and the project was set as SQL Server 2017. Changed the project to 2012 saved everything and it worked.
Please take a look at the following link from social.msdn.microsoft.com discussing about a similar error message. Hope that helps.
CPackage::LoadFromXML Failure