DB2 Connect Problems V7.1 FixPack 3 
Author Message
 DB2 Connect Problems V7.1 FixPack 3

Just migrated to DB2 Connect Enterprise Edition V7.1 FixPack 3 on my Windows
NT server. When I completed the fixpack 3 upgrade, my Java components (e.g.
Control Center) no longer work. The Control Center screen appears and then
just hangs. Also, my clients running the Runtime Client software on other
remote Windows workstations no longer can successfully connect to the
Connect Enterprise Edition. I receive a TCP/IP error (SQL30081N).

Anyone had a similar experience when migrating to FixPack 3? Also, when DB2
starts up each time I get a message that "one or more communication
protocols failed to start, however the database manager successfully
started". This may be the cause of the problems above, not sure.

--
Arthur Lastra




Sun, 23 Nov 2003 10:30:07 GMT
 DB2 Connect Problems V7.1 FixPack 3

Have you looked in the db2diag log for the startup errors? There is usually
useful information in there about this message.

James

Quote:

> Just migrated to DB2 Connect Enterprise Edition V7.1 FixPack 3 on my Windows
> NT server. When I completed the fixpack 3 upgrade, my Java components (e.g.
> Control Center) no longer work. The Control Center screen appears and then
> just hangs. Also, my clients running the Runtime Client software on other
> remote Windows workstations no longer can successfully connect to the
> Connect Enterprise Edition. I receive a TCP/IP error (SQL30081N).

> Anyone had a similar experience when migrating to FixPack 3? Also, when DB2
> starts up each time I get a message that "one or more communication
> protocols failed to start, however the database manager successfully
> started". This may be the cause of the problems above, not sure.

> --
> Arthur Lastra





Sun, 23 Nov 2003 17:01:35 GMT
 DB2 Connect Problems V7.1 FixPack 3
FYI . . I also applied FP3 to DB2 Connect v7.1 on NT and started to receive
the same "one or more communication protocols failed to start, however the
database manager successfully started" message whenever I start my instance.
I enabled DIAGLEVEL 4 but the message does not show up in the db2diag.log
file.  The message only appears in the NT Event Log and if I run db2start
from a command line, the message is displayed following the command.

I'd also appreciate any ideas.  Thanks.

P.S. My Java components do run, though, and I am able to connect through
DB2C EE.


Quote:
> Just migrated to DB2 Connect Enterprise Edition V7.1 FixPack 3 on my
Windows
> NT server. When I completed the fixpack 3 upgrade, my Java components
(e.g.
> Control Center) no longer work. The Control Center screen appears and then
> just hangs. Also, my clients running the Runtime Client software on other
> remote Windows workstations no longer can successfully connect to the
> Connect Enterprise Edition. I receive a TCP/IP error (SQL30081N).

> Anyone had a similar experience when migrating to FixPack 3? Also, when
DB2
> starts up each time I get a message that "one or more communication
> protocols failed to start, however the database manager successfully
> started". This may be the cause of the problems above, not sure.

> --
> Arthur Lastra





Mon, 24 Nov 2003 06:08:12 GMT
 
 [ 3 post ] 

 Relevant Pages 

1. DB2 CAE V5.2 (fixpack 15) and DB2 Connect EE V7.1

2. DB2 v7.1 Fixpack 7 experiences?

3. Installing Fixpack 6 for 32 version on Db2 Udb EEE v7.1 on solaris

4. DB2 v7.1 Fixpacks?

5. db2 v8 down level support to db2 connect v7 (SQL1334N)

6. Connecting to db2 v7.1(linux) from db2 5.2 cc(nt)

7. Problems with DB2 Connect V7

8. problem with importing blobs in DB2 7.2 fixpack 7

9. UDB/DB2 Fixpack 7 / JDBC : executeBatch problem

10. advanced requirements for installing v7.1 Fixpack 3

11. Connecting ADO recordset (DB2 UDB V7) to MSdatagrid 6.0 (sp3)

12. DB2 Connect EE V7 "automatic switching"


 
Powered by phpBB® Forum Software