SSIS IBMDA400 driver error
Hi,
I've got an SSIS job which uses a IBMDA400 connection to our AS400 server.
The package runs fine in VS2008 on a XP or Windows 7 workstation but not on the Windows 2003 server.
The error in the SQL server history is:
"
The PrimeOutput method on component "Get iSeries Data" (1) returned error code 0xC0202009. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing.
"
Any ideas?
Thanks,
Mark
I've got an SSIS job which uses a IBMDA400 connection to our AS400 server.
The package runs fine in VS2008 on a XP or Windows 7 workstation but not on the Windows 2003 server.
The error in the SQL server history is:
"
The PrimeOutput method on component "Get iSeries Data" (1) returned error code 0xC0202009. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing.
"
Any ideas?
Thanks,
Mark
ASKER
Hi,
The trouble with that is I will need to redevelop the whole project and the .Net Provider does not allow me SQL Command From Variable and I need this as we have multiple data libraries for different test systems and I don't want to have to change the packages every time I deploy it to a different environment.
It is working fine running on my Windows 7 machine and my collegues XP machine, its just when we deploy it to the system test server Windows 2003 with SQL 2008.
Any other suggestions would be appreciated.
Thanks,
The trouble with that is I will need to redevelop the whole project and the .Net Provider does not allow me SQL Command From Variable and I need this as we have multiple data libraries for different test systems and I don't want to have to change the packages every time I deploy it to a different environment.
It is working fine running on my Windows 7 machine and my collegues XP machine, its just when we deploy it to the system test server Windows 2003 with SQL 2008.
Any other suggestions would be appreciated.
Thanks,
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Checked the Client Access Version on the machine running SSIS and noticed that it was a release behind, after updating it, the issues were resolved.
See this link. Replace with .NET provider
http://social.msdn.microsoft.com/Forums/en-US/sqlintegrationservices/thread/67112800-1096-44a0-b444-83b506eba087