Topic
  • 3 replies
  • Latest Post - ‏2014-08-19T14:37:19Z by trader089
trader089
trader089
3 Posts

Pinned topic ibm cli driver sql1042c sqlstate=58004 (#-1042)

‏2014-08-18T12:57:35Z |

Hello everybody,

I already have read several topics to this question, but, as a mater of fact, I am not getting any clues out of these.
I only do set up odbc connections to db2, otherwise I am not knowing anything about db2, except, it is a database

Here my facts:

MS Win 2008 R2 SP1 fully patched x64
RTCL 9.7.900.250 x86

I have succesfully cataloged node and database and then set up the system odbc connection.  Connection Test > successfull!

As soon I use an application to connect over this odbc-Connection, I get the above error-message ibm cli driver sql1042c unexpected system error sqlstate=58004 (#-1042)

I have no idea, if I can trace something and how.

  • mor
    mor
    570 Posts

    Re: ibm cli driver sql1042c sqlstate=58004 (#-1042)

    ‏2014-08-18T13:59:51Z  

    Can you successfully connect from the db2cwadmin (db2cmd.exe) command line to the remote database?

     

    When you connect to the database (via your application), are you using the exact same userid and password that you used when testing the odbc-connection?

     

    What is the db2-server version (of the remote database) and its operating system name and version ?  (for example, are you connecting to a mainframe, another windows-server, an AUX/Linux/Solaris box etc)?  You can ask your DBA on the db2-server to adivse if there are errors visible at the server end when your application connects.

    Is the application using CLI? or is it a Java application (using jdbc)? Give details. 

    You can use a CLI trace (provided the application is using CLI) if you get stuck, see the on-line knowledge-centre for details:

    http://www-01.ibm.com/support/knowledgecenter/SSEPGG_9.7.0/com.ibm.db2.luw.admin.trb.doc/doc/c0008936.html?lang=en

     

  • trader089
    trader089
    3 Posts

    Re: ibm cli driver sql1042c sqlstate=58004 (#-1042)

    ‏2014-08-19T10:56:23Z  
    • mor
    • ‏2014-08-18T13:59:51Z

    Can you successfully connect from the db2cwadmin (db2cmd.exe) command line to the remote database?

     

    When you connect to the database (via your application), are you using the exact same userid and password that you used when testing the odbc-connection?

     

    What is the db2-server version (of the remote database) and its operating system name and version ?  (for example, are you connecting to a mainframe, another windows-server, an AUX/Linux/Solaris box etc)?  You can ask your DBA on the db2-server to adivse if there are errors visible at the server end when your application connects.

    Is the application using CLI? or is it a Java application (using jdbc)? Give details. 

    You can use a CLI trace (provided the application is using CLI) if you get stuck, see the on-line knowledge-centre for details:

    http://www-01.ibm.com/support/knowledgecenter/SSEPGG_9.7.0/com.ibm.db2.luw.admin.trb.doc/doc/c0008936.html?lang=en

     

    Hi Mor,

    thanks for helping, I'm gathering info in the moment
    later mor

    karl

  • trader089
    trader089
    3 Posts

    Re: ibm cli driver sql1042c sqlstate=58004 (#-1042)

    ‏2014-08-19T14:37:19Z  
    • mor
    • ‏2014-08-18T13:59:51Z

    Can you successfully connect from the db2cwadmin (db2cmd.exe) command line to the remote database?

     

    When you connect to the database (via your application), are you using the exact same userid and password that you used when testing the odbc-connection?

     

    What is the db2-server version (of the remote database) and its operating system name and version ?  (for example, are you connecting to a mainframe, another windows-server, an AUX/Linux/Solaris box etc)?  You can ask your DBA on the db2-server to adivse if there are errors visible at the server end when your application connects.

    Is the application using CLI? or is it a Java application (using jdbc)? Give details. 

    You can use a CLI trace (provided the application is using CLI) if you get stuck, see the on-line knowledge-centre for details:

    http://www-01.ibm.com/support/knowledgecenter/SSEPGG_9.7.0/com.ibm.db2.luw.admin.trb.doc/doc/c0008936.html?lang=en

     

    OK Problem solved, it was an issue of rights management depending on a corrupt sid of the local administrators group. 

    as soon I put the users into the local db2admin group, everthing worked fine. After renewing the machine account in the ads, it worked properly again with only the local administrator group. Unfortunatly didn't we have any problems to logon to the domain, so the security log was the least I thougt upon. Checking this out of pure feelings, I could see the mess immidiatly.

    sorry for molesting

    karl