Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Destination\s+dispatcher\s+unavailable\s*$/: 5 ]

Total 5 documents matching your query.

1. Destination dispatcher unavailable (score: 1)
Author: Winfried.Gehrig AT skf DOT com
Date: Wed, 12 Apr 2000 11:48:12 +0100
Hello Peter, I had similiar problems on our AIX-platform. The missing entry for the Management-station in /etc/host caused the same error-message. A workaround to start the Tivoli-desktop from IBM wa
/usr/local/webapp/mharc-adsm.org/html/nv-l/2000-04/msg00144.html (11,663 bytes)

2. destination dispatcher unavailable (score: 1)
Author: Bob Buehler <bob.buehler AT CPA.STATE.TX DOT US>
Date: Mon, 25 Jan 1999 16:47:04 -0600
We want to do a new NV/6000 5.1 install - no migration. We have installed TME10 framework version 3.6 on aix 4.3.2.0 The directions in the "TME10 Netview v5r1 for Unix release notes" state that after
/usr/local/webapp/mharc-adsm.org/html/nv-l/1999-01/msg00372.html (11,147 bytes)

3. Re: destination dispatcher unavailable (score: 1)
Author: Vladimir Petr <petr AT DATASYS DOT CZ>
Date: Tue, 26 Jan 1999 08:55:38 +0100
Hello, Bob; Recently, the same problem has been posted to the list. First check if there is some free space in $DBDIR and /tmp. Look at $DBDIR/oservlog for oserv's error messages that may help you ge
/usr/local/webapp/mharc-adsm.org/html/nv-l/1999-01/msg00378.html (11,782 bytes)

4. Re: destination dispatcher unavailable (score: 1)
Author: Bob Buehler <bob.buehler AT CPA.STATE.TX DOT US>
Date: Tue, 26 Jan 1999 09:09:17 -0600
Thanks Carla and Vladimir. I did review previous emails on the list, but they are not helping. The command: /etc/Tivoli/oserv.rc start results in: $Database mismatch (from venus.dev.tivoli.com/146.84
/usr/local/webapp/mharc-adsm.org/html/nv-l/1999-01/msg00384.html (13,532 bytes)

5. Re: destination dispatcher unavailable (score: 1)
Author: Vladimir Petr <petr AT DATASYS DOT CZ>
Date: Tue, 26 Jan 1999 16:54:31 +0100
Hello, Bob; Really, it seems one of the crucial objects is severely corrupted. I have seen many "odlist init failed" messages but not this one so I unfortunately cannot give you any particular piece
/usr/local/webapp/mharc-adsm.org/html/nv-l/1999-01/msg00389.html (15,164 bytes)


This search system is powered by Namazu