| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
The following command was issued and the error message is also given.
DECmcc (T1.1.0)
MCC> show domain *
Using default ALL IDENTIFIERS
The requested operation cannot be completed
MCC Routine Error = %DNS-E-NOCOMMUNICATION,
Unable to communicate with DNS server
Two questions:
1. Where do I find the explanation for this error message? (I searched
through the Error Messages manual)
2. What is that I have to do to correct this problem?
Thanks..
Kandha
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 599.1 | dns error | GOSTE::CALLANDER | Tue Jan 08 1991 16:13 | 12 | |
some of these messages are also explained in the dir use; but all
messages should be covered in the messages manual. What you will
find in the mesmsages manual is an entry for "The requested operation
cannot be completed" the routine error is a dns messages (%DNS)
and therefore would be in the dns manual set.
Check out the trouble shooting guide in the DIR use manual it might
help. This type of error can be caused by any number of problems,
for the most part all have to do with DNS either not available or
not configured for MCC usage.
| |||||
| 599.2 | Check DECnet resources.... | TOOK::CAREY | Wed Jan 09 1991 09:55 | 31 | |
"Unable to communicate with DNS server."
I have seen it for a lot of reasons. Our test platforms usually
feature DECmcc running on a DNS client system, and a lot of people
taking advantage of one properly configured namespace somewhere nearby.
Often, the error occurs on a network resource problem:
- no more available links for the DNS server
- no more process slots on the DNS server
things like that.
Check the release notes. There are a bunch of examples and samples in
there as well that might help out.
Sometimes it is more mysterious, but also seems to be resource related,
because retrying a failed request is soon successful.
As we sorted these issues out around here, we see less and less of this
error, but one thing that used to work successfully (sometimes, and I
have no idea why) was a different request to the DNS server when we
started seeing these communication problems. For example, if SHOW
DOMAIN * didn't work, we might try DIR NODE4 nodeid. I don't know a
lot about why this had any effect, and haven't needed to try it in
awhile because we've cleaned up our DNS environment a lot, but it might
be worth attempting.
-Jim
| |||||
| 599.3 | DNS license expired.. | BAGELS::ALAGAPPAN | Kandha Alagappan 226-5163 | Thu Jan 10 1991 15:06 | 6 |
The problem was due to the expiration of "DNS License".
Thanks a lot for the response...
Kandha
| |||||