• This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.

Exchange Server 2003 / Exchange HTTP Virtual Server

madmatt

Bow Down to the King
Political User
#1
I am running a two node cluster for Exchange Server 2003.

I tried to access OWA tonight and the site timed out. So I logged into the server to check the event log. I see the following error:

"Exchange HTTP Virtual Server Instance 100 (GRENO-EXCHANGE): Failed to get the protocol IP address and port bindings from the metabase."

I open Cluster Administrator and try to bring the resource online but it fails and provides the same event error as above.

Firstly, what would have caused this?

Secondly, how do I resolve this issue?

Any help is appreciated. Thank you.
 

madmatt

Bow Down to the King
Political User
#3
No headers have been added. I've found documentation on Microsoft's newsgroups saying the metabase.bin file may have become corrupt. Which doesn't sound like a fun fix.

Any other ideas?
 

madmatt

Bow Down to the King
Political User
#4
The problem has been resolved.

In the process of configuring the HTTP protocol through Exchange System Manager it made changes to the MetaBase XML file (configuration). Some how the "ServerBindings" property was removed from Exchange Virtual Server configuration. To resolve the issue I had to shutdown IIS on the inactive node and edit the file in a plain text editor and add the "ServerBindings" property back in with the correct information. After which I restarted the server and then failed over the cluster to this node.

Making the change on one server affected both so no further work was needed.

I hope this helps someone else if they run into this problem.
 

kcnychief

█▄█ ▀█▄ █
Political User
#5
madmatt said:
The problem has been resolved.

In the process of configuring the HTTP protocol through Exchange System Manager it made changes to the MetaBase XML file (configuration). Some how the "ServerBindings" property was removed from Exchange Virtual Server configuration. To resolve the issue I had to shutdown IIS on the inactive node and edit the file in a plain text editor and add the "ServerBindings" property back in with the correct information. After which I restarted the server and then failed over the cluster to this node.

Making the change on one server affected both so no further work was needed.

I hope this helps someone else if they run into this problem.
Interesting fix, it appears they replicated to eachother which in essence caused the problem and at the same time, fixed it :)
 

madmatt

Bow Down to the King
Political User
#6
It makes sense that the replicated the configuration since the web site is a virtual server.

It took some digging and I just got too tired dealing with it last night. But this morning I got on the right track with the XML file (a 1000+ line XML file is a lot of fun to dig through looking for discrepancies).
 

kcnychief

█▄█ ▀█▄ █
Political User
#7
madmatt said:
It makes sense that the replicated the configuration since the web site is a virtual server.

It took some digging and I just got too tired dealing with it last night. But this morning I got on the right track with the XML file (a 1000+ line XML file is a lot of fun to dig through looking for discrepancies).

Sometimes it is best to leave it and come back with a fresh head. You are lucky your the admin, in some places i restrict the F3 search feature. I bet that comes in handy for 1,000 lines
 
#11
Interesting problem, glad you found a fix for it, I was going to suggest to look into the connections...I was way off hehe.

(lovin F3 as well)
 

madmatt

Bow Down to the King
Political User
#13
For anyone who was following this thread.

I was wrong. The XML config file did not replicate to both nodes. Once it failed back over to the first node the settings were lost. I had to make the changes to both XML configs for it to work correctly.
 

markrich

OSNN One Post Wonder
#14
madmatt said:
The problem has been resolved.

In the process of configuring the HTTP protocol through Exchange System Manager it made changes to the MetaBase XML file (configuration). Some how the "ServerBindings" property was removed from Exchange Virtual Server configuration. To resolve the issue I had to shutdown IIS on the inactive node and edit the file in a plain text editor and add the "ServerBindings" property back in with the correct information. After which I restarted the server and then failed over the cluster to this node.

Making the change on one server affected both so no further work was needed.

I hope this helps someone else if they run into this problem.
We have begun to experinence this problem also. I am unsure what to look for in metabase.xml but all seems well. The correct IP addresses and other references to servers are all in there. In our case the HTTP Virtual Server Instance 100 refuses to load on the second node causing the services to all bounce back again.

How did manage to fix this problem. It's driving me insane.

Marky
 

madmatt

Bow Down to the King
Political User
#15
You want to make sure the IP address (to the virtual server) and port 443 are bound to the Exchange Virtual Server in the IIS manager.

If it is then I will need more information, such as event errors (event viewer).
 

Members online

No members online now.

Latest posts

Latest profile posts

Hello, is there anybody in there? Just nod if you can hear me ...
Xie
What a long strange trip it's been. =)

Forum statistics

Threads
61,960
Messages
673,237
Members
89,011
Latest member
grovo_test