iSeries Access ODBC Driver Error

pts.
Tags:
AS/400
Data analysis
Data Mining
DataCenter
I'm trying to run a stored procedure on MS SQL Query Analyzer but continue to get the following error: Server: Msg 7399, Level 16, State 1, Line 1 OLE DB provider 'MSDASQL' reported an error. [OLE/DB provider returned message: [IBM][iSeries Access ODBC Driver][DB2 UDB]PWS0005 - Error occurred in the OS/400 database server code.] OLE DB error trace [OLE/DB Provider 'MSDASQL' ICommandPrepare::Prepare returned 0x80004005: ]. I can successfully run this stored proc on another server running SQL Server. I've checked to see how the iSeries ODBC is configured and it is the same on both machines. Any clue as to how to fix this will be a great help. Thanks

Answer Wiki

Thanks. We'll let you know when a new response is added.

Installing the latest iSeries Access Fix Pack helps.
Also, make sure that all required TCP/IP ports
are enabled in your network. Security may have
you locked out. Use *AllOBJ authority in you
profile or login using the QSECOFR profile.
Hope this helps………
RB

Discuss This Question: 2  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • TomLiotta
    Note that *ALLOBJ in a profile and QSECOFR should make connections more difficult, not easier, if the remote system has any rational security configuration at all. Tom
    125,585 pointsBadges:
    report
  • Brijesh
    Hi,

    IBM also has a troubleshooter for this type of problem:


    If you need more help, suggest you post your ODBC DSN config, the failing section of code (make sure you include the connection establishment code), and an ODBC trace showing the failure. Might also be useful to start an IBM i SQL Performance monitor to capture the failing SQL statement there.  Also check the job log of QZDASOINIT job handling the database connection and see if there is anything interesting there. 

    10,185 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following