Results 1 to 2 of 2
  1. #1
    Join Date
    May 2002
    Posts
    1

    Unanswered: SQL30081N with Return code 17

    hi
    i was trying to connect my server i got theis message SQL30081N with Return code 17
    more explaination
    i am using MS SNA client to connect to MS SNA server i manage to connect but when i try to connect to my database using DB2 connect i got the following message :
    SQL30081N with Return code 17

  2. #2
    Join Date
    Apr 2002
    Posts
    18
    You can get further information from DB2. Go into your db2 prompt and enter

    ? SQL30081N.

    It will then tell you the possible cause of the problems. I have appended some of the output below which may help you to solve your problem.

    db2 => ? sql30081n

    SQL30081N A communication error has been detected.
    Communication protocol being used: <protocol>.
    Communication API being used: <interface>. Location
    where the error was detected: <location>.
    Communication function detecting the error:
    <function>. Protocol specific error code(s): <rc1>,
    <rc2>, <rc3>.

    Explanation: An error has been detected by the communication
    subsystem.




    If you are trying to establish a new connection, possible causes
    include the following:

    o The remote database server has not been cataloged correctly
    at the client.

    o The database manager configuration file at the server has not
    been configured with the proper communication parameters.

    o The communication subsystem at the client node or server node
    has not been configured correctly, or has not been started
    successfully.

    o The communication subsystem at the SOCKS server, if one is
    being used, has not been configured correctly, or has not
    been started successfully.

    o The DB2COMM environment variable at the server doesn't
    specify the communication protocol used by the client.

    o The database manager at the server has not been started, or
    has not been started successfully. One or more of the
    communication protocols specified by DB2COMM may not have
    been successfully started.


    There was loads more information, too much to print here unfortunately. I hope this is of use to you.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •