ANCARE
asked on
ESM 2000, Unable to expand Public Folder in System manager
(The error below displays in ESM after about 10 minutes of the hour glass appearing) I have found the MS answer below but am not sure how to check or impliment the fix. Any assistance would be greatly appreciated.
Windows 2000 Server (SP4) Exchange 2000 Server (SP3+rollup package)
ISA on Separate server than Exchange
========================== ========== ========== =====
Error ID number: c007274c
Error Message
Facility: Win32
A connection attempt failed because the connected party did not respond after a period of time, or established connection failed because connected host has failed to respond.
Possible Causes
• Incorrect host headers defined on clustered virtual server.
Troubleshooting
• Add or remove the correct host headers to Exchange virtual server in Internet Information Services (IIS) Manager
Windows 2000 Server (SP4) Exchange 2000 Server (SP3+rollup package)
ISA on Separate server than Exchange
==========================
Error ID number: c007274c
Error Message
Facility: Win32
A connection attempt failed because the connected party did not respond after a period of time, or established connection failed because connected host has failed to respond.
Possible Causes
• Incorrect host headers defined on clustered virtual server.
Troubleshooting
• Add or remove the correct host headers to Exchange virtual server in Internet Information Services (IIS) Manager
Check the following article from MS
Troubleshooting Microsoft Exchange System Manager Public Folder Expansion Problems
http://www.microsoft.com/technet/prodtechnol/exchange/2003/insider/publicfolders.mspx
Troubleshooting Microsoft Exchange System Manager Public Folder Expansion Problems
http://www.microsoft.com/technet/prodtechnol/exchange/2003/insider/publicfolders.mspx
ASKER
Amit - I checked the IP address within IS, advanced - it was set to 'all unassigned'. I selected the specific IP of the Exchange server, restarted IS and still will not expand Public Folders in ESM.
I have also checked the publicfolders troubleshooting article from Microsoft - Host headers field is completely empty.
I have also checked the publicfolders troubleshooting article from Microsoft - Host headers field is completely empty.
Did you check the properties of the SMTP Virtual server in ESM or the properties of the default Web site in Internet Service Manager?
ASKER
I cheked the IIS properties of the default web site (advanced)
How many websites do you have in IIS.. and how many exchange servers?
ASKER
Just the one "default web site" and two exchange servers - located on separate sites.
Try this ->
Right click on "Public Folders" object in Exchange System Manager and choose "Connect to" and then select a different PF store from the list (if you have more than 1 PF stores in your organization) and then try to expand it.
Thanks,
Amit Aggarwal
Right click on "Public Folders" object in Exchange System Manager and choose "Connect to" and then select a different PF store from the list (if you have more than 1 PF stores in your organization) and then try to expand it.
Thanks,
Amit Aggarwal
ASKER
Amit
That was interesting. I am able to expand the public folders for the other Exchange server. When I then try and connect to public folders for the original Exchange server I receive.
The SSL certificate server name is incorrect ID no: c103b404
I then found the following MS support article which resolved the problem.
http://support.microsoft.com/Default.aspx?id=324345
It involves switching off SSL however which I am not sure if that is a good idea.
thank you.
Chris
That was interesting. I am able to expand the public folders for the other Exchange server. When I then try and connect to public folders for the original Exchange server I receive.
The SSL certificate server name is incorrect ID no: c103b404
I then found the following MS support article which resolved the problem.
http://support.microsoft.com/Default.aspx?id=324345
It involves switching off SSL however which I am not sure if that is a good idea.
thank you.
Chris
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
will do- thank you very much for your help.
If the Web site that the Exadmin virtual directory is a member of does not have a blank host header name, you may receive the error message that is mentioned in the "Symptoms" section.
To resolve this issue, verify that the Web site has a blank host header name. To do this, follow these steps:1. Start Internet Services Manager, and then open the properties of the default Web site.
2. Click Advanced.
3. Make sure that a valid IP address has been entered and that the host header name is blank.
The Exchange System Manager uses the network basic input/output system (NetBIOS) name of the computer to try to connect to its management server by using HTTP. In Exchange-based cluster servers, if host headers are configured, they should be the NetBIOS names of the Exchange virtual servers or the NetBIOS names of the nodes.
Thanks,
Amit Aggarwal.