If this is your first visit, be sure to check out the FAQ by clicking the link above.
You may have to register before you can post: click the register link above to proceed.
To start viewing messages, select the forum that you want to visit from the selection below.
I just installed DB2 UDB 8.1.5 on Win NT 4.0 (sp6) and I'm getting a few warnings I do not understand on event viewer during startup. Can someone please explain what they mean and what to do if possible.
(these are in timed order...)
Source : DB2REMOTECMD
Type : Information
Description : rcmdTcpipListener : Failed to configure listener's socket address. Check for port (db2ccmsrv) in SERVICES file, rs=118423736
Source : DB2REMOTECMD
Type : Information
Description : rcmdTcpipListener : Monitor Server Listener Terminating
Source : DB2-0
Type : Warning
Description : 2004-04-06-15.58.33.453000 Instance: DB2 Node:000 PID:227(db2syscs.exe) TID:308 Appid:none base sys utilities DB2StartMain Probe:911
ADM7513W Database manager has started
Source : DB2-0
Type : Information
Description : db2start : SQL5043N Support for one or more comminications protocols failed to start successfully. However, core database manager functionality started successfully.
I just installed DB2 UDB 8.1.5 on Win NT 4.0 (sp6) and I'm getting a few warnings I do not understand on event viewer during startup. Can someone please explain what they mean and what to do if possible.
(these are in timed order...)
Source : DB2REMOTECMD
Type : Information
Description : rcmdTcpipListener : Failed to configure listener's socket address. Check for port (db2ccmsrv) in SERVICES file, rs=118423736
Source : DB2REMOTECMD
Type : Information
Description : rcmdTcpipListener : Monitor Server Listener Terminating
Source : DB2-0
Type : Warning
Description : 2004-04-06-15.58.33.453000 Instance: DB2 Node:000 PID:227(db2syscs.exe) TID:308 Appid:none base sys utilities DB2StartMain Probe:911
ADM7513W Database manager has started
Source : DB2-0
Type : Information
Description : db2start : SQL5043N Support for one or more comminications protocols failed to start successfully. However, core database manager functionality started successfully.
? Thanks for any possible help. - m
Sounds like a TCP/IP port conflict. Check which port(s) DB2 is configured to listen at and ensure that no other services use those ports.
Originally posted by n_i
Sounds like a TCP/IP port conflict. Check which port(s) DB2 is configured to listen at and ensure that no other services use those ports.