June 12, 2020 at 3:28 pm
I have an SSIS package that is using Db2 driver to get to db on a mainframe. I setup a batch file and call it via DTExec. I use UNC naming conventions for paths and pass config file to it. When I run the batch file from my machine, all works well. When I run the same batch file from server, I get the error below. I've validated that the ODBC driver is setup properly and tested the connection on the server. I don't see any errors in the EventLog. The Firewall is disabled and I even disabled Symantec to try it. Does anyone have any others suggestions?
Error: 2020-06-12 11:19:34.32
Code: 0xC0202009
Source: MFTest Connection manager "Mainframe"
Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available. Source: "Microsoft OLE DB Service Components" Hresult: 0x80004005 Description: "Unspecified error".
End Error
For better, quicker answers, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
June 12, 2020 at 8:40 pm
My first thought is it the same version of DTExec on your machine and the server?
One thing I am reading about that particular error (0x800004005) makes it sound like error is related to a SQL Agent proxy, but you say you are running the bat file manually so I don't think that is the case. correct?
Are you running the bat file as the same user with the same permissions (ie if you are an admin on your workstation, you are an admin on the server)?
Next thought - what if you add "/consolelog" option to the execution of the package? that will show you logging to screen and may give you a better idea of what the problem is.
While looking this up I found this post:
http://www.sqlerudition.com/howto-fix-error-code-80004005-in-dts-caused-by-64-bit-db2-odbc-driver/
which suggests using 32-bit ODBC driver may help.
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
June 13, 2020 at 8:26 am
could be due to login not valid.
How are you setting up your connection string to DB2?
and is it using username/password or other method?
June 17, 2020 at 1:44 am
Yes, I have UserID and Password in the connection string. I'm logging in as myself, so we have same permissions and I'm admin on the box.
For better, quicker answers, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
June 17, 2020 at 2:02 am
I see this error in the ConsoleLog
Message: ExternalRequest_post: 'IDataInitialize::GetDataSource failed'. The external request has completed.
I did notice that I'm using 32 bit dtexec on my machine and 64 bit on server. I changed to use 32 bit and got same error
For better, quicker answers, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply