Problem browsing to Unity admin pages...

[darren-newman]

Question: When attempting to administer Unity from a remote PC using IE6.0

or even 5.5 sp1, the customer gets the following error: This Following Page could not be displayed...This is only when they click on a subscriber to bring up the specific properties of the subscriber. (happens to all subscribers) In other words,

They can navigate to http://172.16.1.12/saweb/ (the main page), then to the Subscribers Page, but when clicking on a specific subscriber, the error pops up. When browsing locally from the Unity server, this does not happen.

Unity is version3.1.3a Any ideas, suggestions are greatly appreciated...thank you

[lindborg]

So this only happens on subscriber, not call handlers or any other objects?

This sounds vaguely familiar to an error in the SA logic where it was expecting SQL access via ADO in some odd case or another that caused something like this. When you were logged into the local Unity box you were running under an account with local admin rights which had read/write access to SQL so you didn't see it.

[lindborg]

Hmmm... the bug I was thinking of is CSCdw85596 which doesn't look like a good match here (i.e. you couldn't fire up the SA at all in that case and it was fixed in 3.1(3) which you're running).

[6mcure]

Jeff,

I've seen this before when the client does not have the means to resolve the Unity machine name in the Global Location field. A user can browse to the page using the IP address, as in the example above, but when the subscriber page pops up, the URL is http://... A workaround seems to be to put whatever the global location name is into the hosts or lmhosts file or change the global location value to a fully qualified name and add that name to the appropriate dns server. -matt

[jschless]

This is the exact behavior if there is no DNS or means to resolve the name. You can get away with going to the initial web page using the IP address, but as soon as you attempt to choose a subscriber from a query, you will bomb out because the DNS-friendly name is pushed to the url. If there is no DNS/HOSTS entry to resolve the machine or fully qualified name to IP address, we are going to see that generic, "Cannot display page" message. Setup DNS or edit the HOSTS file and it should work.

Jeff Schlesser