Exchange Server 2003 / Exchange HTTP Virtual Server

**madmatt** · July 21st, 2005

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.

**kcnychief** · July 21st, 2005

I know this article is for Windows 2000...

http://support.microsoft.com/kb/838922

But it looks like the information is still relevant.....maybe?

I don't know much about your setup, but it makes sense.

**madmatt** · July 21st, 2005

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** · July 21st, 2005

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** · July 21st, 2005

Originally Posted by madmatt

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** · July 21st, 2005

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** · July 21st, 2005

Originally Posted by madmatt

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

**madmatt** · July 21st, 2005

Ha, Ha. Yes. F3 is my friend.

**kcnychief** · July 21st, 2005

Originally Posted by madmatt

Ha, Ha. Yes. F3 is my friend.

Me personally, I like to place F3 on the pillow next to me and cuddle with it at night

*has issues*

**madmatt** · July 21st, 2005

Don't we all (have issues).

**Bootsy** · July 22nd, 2005

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)

**kcnychief** · July 22nd, 2005

We should have a BBQ in the honor of F3

**madmatt** · July 23rd, 2005

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 · August 2nd, 2005

Originally Posted by madmatt

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** · August 3rd, 2005

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).

July 21st, 2005	Top \| #1
madmatt Bow Down to the King Joined: April 2002 Location: New York Posts: 13,312 Reputation: 4090 Power: 294	Exchange Server 2003 / Exchange HTTP Virtual Server 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.

July 21st, 2005	Top \| #2
kcnychief █▄█ ▀█▄ █ Joined: April 2005 Location: Massachusetts Posts: 16,949 Reputation: 4941 Power: 302	Re: Exchange Server 2003 / Exchange HTTP Virtual Server I know this article is for Windows 2000... http://support.microsoft.com/kb/838922 But it looks like the information is still relevant.....maybe? I don't know much about your setup, but it makes sense. XBOX Live Gamertag: kcnychief

July 21st, 2005	Top \| #3
madmatt Bow Down to the King Joined: April 2002 Location: New York Posts: 13,312 Reputation: 4090 Power: 294	Re: Exchange Server 2003 / Exchange HTTP Virtual Server 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?

July 21st, 2005	Top \| #4
madmatt Bow Down to the King Joined: April 2002 Location: New York Posts: 13,312 Reputation: 4090 Power: 294	Re: Exchange Server 2003 / Exchange HTTP Virtual Server 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.

July 21st, 2005	Top \| #5
kcnychief █▄█ ▀█▄ █ Joined: April 2005 Location: Massachusetts Posts: 16,949 Reputation: 4941 Power: 302	Re: Exchange Server 2003 / Exchange HTTP Virtual Server Originally Posted by madmatt 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 XBOX Live Gamertag: kcnychief

Latest News Posts

Latest Forum Posts

Latest Member Blogs

July 21st, 2005	Top \| #6
madmatt Bow Down to the King Joined: April 2002 Location: New York Posts: 13,312 Reputation: 4090 Power: 294	Re: Exchange Server 2003 / Exchange HTTP Virtual Server 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).

July 21st, 2005	Top \| #7
kcnychief █▄█ ▀█▄ █ Joined: April 2005 Location: Massachusetts Posts: 16,949 Reputation: 4941 Power: 302	Re: Exchange Server 2003 / Exchange HTTP Virtual Server Originally Posted by madmatt 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 XBOX Live Gamertag: kcnychief

July 21st, 2005	Top \| #8
madmatt Bow Down to the King Joined: April 2002 Location: New York Posts: 13,312 Reputation: 4090 Power: 294	Re: Exchange Server 2003 / Exchange HTTP Virtual Server Ha, Ha. Yes. F3 is my friend.

July 21st, 2005	Top \| #9
kcnychief █▄█ ▀█▄ █ Joined: April 2005 Location: Massachusetts Posts: 16,949 Reputation: 4941 Power: 302	Re: Exchange Server 2003 / Exchange HTTP Virtual Server Originally Posted by madmatt Ha, Ha. Yes. F3 is my friend. Me personally, I like to place F3 on the pillow next to me and cuddle with it at night has issues XBOX Live Gamertag: kcnychief

July 21st, 2005	Top \| #10
madmatt Bow Down to the King Joined: April 2002 Location: New York Posts: 13,312 Reputation: 4090 Power: 294	Re: Exchange Server 2003 / Exchange HTTP Virtual Server Don't we all (have issues).

July 22nd, 2005	Top \| #11
Bootsy Huh? Joined: February 2004 Location: Miami, Fl Posts: 1,124 Reputation: 50 Power: 109	Re: Exchange Server 2003 / Exchange HTTP Virtual Server 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)

July 22nd, 2005	Top \| #12
kcnychief █▄█ ▀█▄ █ Joined: April 2005 Location: Massachusetts Posts: 16,949 Reputation: 4941 Power: 302	Re: Exchange Server 2003 / Exchange HTTP Virtual Server We should have a BBQ in the honor of F3 XBOX Live Gamertag: kcnychief

July 23rd, 2005	Top \| #13
madmatt Bow Down to the King Joined: April 2002 Location: New York Posts: 13,312 Reputation: 4090 Power: 294	Re: Exchange Server 2003 / Exchange HTTP Virtual Server 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.

August 2nd, 2005	Top \| #14
markrich OSNN One Post Wonder Joined: August 2005 Posts: 1 Reputation: 0 Power: 0	Re: Exchange Server 2003 / Exchange HTTP Virtual Server Originally Posted by madmatt 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

August 3rd, 2005	Top \| #15
madmatt Bow Down to the King Joined: April 2002 Location: New York Posts: 13,312 Reputation: 4090 Power: 294	Re: Exchange Server 2003 / Exchange HTTP Virtual Server 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).

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
outlook keeps connecting to exchange server	Heeter	Windows Applications	6	April 6th, 2008 11:38pm
Server 2003 Exchange 2003 connection prob for clients!!	Troy	Windows Server Systems	1	February 28th, 2006 1:18pm
Exchange Server Cluster / SP2 Update	madmatt	Windows Server Systems	7	February 17th, 2006 1:52am
Exchange Server 2003 + Messaging	madmatt	Windows Server Systems	0	July 19th, 2005 7:49pm
Outlook - Add Route for Exchange Server...	Mainframeguy	Windows Desktop Systems	2	September 2nd, 2004 5:26pm