MDSPROC error that shuts down the PG

[bruce.finney]

I am setting up a lab environment that duplicates our production system which is a 6.0 enterprise system.

I've successfully configured the A side PG and have made calls through the system. On the B side PG I get an error in the "MDSPROC" process window that is as follows:

"the requested address is not valid in its context"

also

"MDS overseer EMTlisten failed"

WTF? I've checked the website again and again for any hint of these error messages. Has anybody out there run into these errors? Reachability is not an issue.

Thanks in advance for any help.

Bruce

[wiwebb]

What are the entries for the private addresses on the B side PG in ICM Setup? Are they hostnames? If so, are they FQDNs?

Basically you want to check to see that the entries you have there can be pinged using the same name and context, and that the correct address is returned.

If you can avoid FQDN entries in Setup, it is usually preferred. Use your Windows Network Settings to list out the Domain suffixes you might be using (if there is more than one).

- Bill