BGilhooley
asked on
Exchange 2003 Public folder access problem
Hi.
I am preparing to do an exchange migration from Win2000 server/Exchange 2003 standard to a new Win2003 server/Exchange 2003 standard box. We have 90 users.
I will be using Simons/Seembes migration guide, this is my firts time to do one.
However before I have even gotten started I have an issue with public folders. Basically, we dont use public folders here in the business. However, they can be accessed in MS Outlook and we are using OWA here and it works fine for the mailboxes but the public folders cannot be accessed in OWA.
In ESM/Administrative Groups/First Administrative group when I try to expand the public folders i get the following error:
"Could not expand the root folder, ensure that your default virtual server is running and is configured correctly" it mentions IIS lockdown and URL scanning tools. Error ID is c103b405.
As I mentioned we dont use public folders so I'm not concerned from that perspective, however, as per Seebees guide i need to replicate some System Folders over to my new server when the time comes and because of this issue I cannot access the system folder list.
In IIS under the default website there are 3 red error indicators which are shown in the atached screenshot. The second site, XXX Mail contains our user mailboxes plus ExchWeb folder. I'm guessing something here is configured wrong but not sure?
obviously I need to get this straightened out before commencing with a migration.
Thanks in advance for your help.
iis.bmp
I am preparing to do an exchange migration from Win2000 server/Exchange 2003 standard to a new Win2003 server/Exchange 2003 standard box. We have 90 users.
I will be using Simons/Seembes migration guide, this is my firts time to do one.
However before I have even gotten started I have an issue with public folders. Basically, we dont use public folders here in the business. However, they can be accessed in MS Outlook and we are using OWA here and it works fine for the mailboxes but the public folders cannot be accessed in OWA.
In ESM/Administrative Groups/First Administrative group when I try to expand the public folders i get the following error:
"Could not expand the root folder, ensure that your default virtual server is running and is configured correctly" it mentions IIS lockdown and URL scanning tools. Error ID is c103b405.
As I mentioned we dont use public folders so I'm not concerned from that perspective, however, as per Seebees guide i need to replicate some System Folders over to my new server when the time comes and because of this issue I cannot access the system folder list.
In IIS under the default website there are 3 red error indicators which are shown in the atached screenshot. The second site, XXX Mail contains our user mailboxes plus ExchWeb folder. I'm guessing something here is configured wrong but not sure?
obviously I need to get this straightened out before commencing with a migration.
Thanks in advance for your help.
iis.bmp
ASKER
Anyone out there with suggestions? I have to have this migration done for our return to work in the New Year so its pretty urgent, thanks
Are you using ESM on your computer or on the server? If on yours try the on the server and see if you get the same error.
Does the keepalive settting resolve this for you? (http://technet.microsoft.com/en-us/library/aa996098(EXCHG.65).aspx#Errorc103b405)
Does the keepalive settting resolve this for you? (http://technet.microsoft.com/en-us/library/aa996098(EXCHG.65).aspx#Errorc103b405)
ASKER
Thanks for getting involved Robrandon.
I am using ESM on server.
Also, the keepalive setting is already as specified in the technet document.
I am using ESM on server.
Also, the keepalive setting is already as specified in the technet document.
Error ID number: c103b405
Error Message
Could not locate the root folder. Ensure that your default virtual server is running and it is configured correctly. If you have used the IIS Lockdown or URL Scanning security tools on your server, go to http://suport.microsoft.com for more information about running these tools.
Possible Causes The exadmin virtual directory local path is set to a value other than \\.\BackOfficeStorage
This error can occur if the following are true.
Multiple IP addresses are bound to the NIC card.
Multiple Web sites are configured on the Exchange server.
The default Web site is bound to the secondary IP address that is bound to the NIC card.
No DNS mapping for the second IP that maps to the FQDN of the server.
....
I wonder if that has to do with it.
Curious if you would get the error if you stopped the other sites? Is that possible to try?
Also, do you have more than one NIC in there?
ASKER
Multiple websites are configured yes. I stopped the others but no joy, same messgae.
The guy that configured this isnt round anymore so im not sure of the background but heres how it is.
The default website is IP address is a 193.x.x.x address. Port 8080. Our LAN is 192..x.x.x.
There is a website called 'OurCompanyName'Mail and its IP is the 192.x.x.x address of the LAN card in server. Port 80.
The last website is Symantec Mail Security for MS Exchange. IP is All unassigned and port 8080.
NICs. there are 2 yes. One with our 192 lan address. the second with a static address provided by ISP as our mail comes in via a DSL connection, through DSL router/firewall.
The guy that configured this isnt round anymore so im not sure of the background but heres how it is.
The default website is IP address is a 193.x.x.x address. Port 8080. Our LAN is 192..x.x.x.
There is a website called 'OurCompanyName'Mail and its IP is the 192.x.x.x address of the LAN card in server. Port 80.
The last website is Symantec Mail Security for MS Exchange. IP is All unassigned and port 8080.
NICs. there are 2 yes. One with our 192 lan address. the second with a static address provided by ISP as our mail comes in via a DSL connection, through DSL router/firewall.
Does either NIC have more than one IP assigned to it? You can see that in the properties of the network connection, TCP/IP Properties, Advanced.
Also, I know this is for Exchange 2000, but it may be applicable. Are you using SSL for the ExAdmin virtual root? (http://support.microsoft.com/?id=324345)
Remove SSL from the Exadmin virtual root in IIS: Click Start, point to Programs, click Administrative Tools, and then click Internet Services Manager.
Click your server, and then expand the Web site that contains the Exadmin virtual root (the default Web site is "Default Web Site").
Right-click Exadmin, and then click Properties.
Click the Directory Security tab.
Under Secure Communications, click Edit.
Click to clear the Require secure channel (SSL) check box. If Require 128-bit encryption is shaded, click to select Require secure channel (SSL), click to clear Require 128-bit encryption, and then click to clear the Require secure channel (SSL) check box again.
Click OK two times.
Restart Exchange System Manager.
Also, I know this is for Exchange 2000, but it may be applicable. Are you using SSL for the ExAdmin virtual root? (http://support.microsoft.com/?id=324345)
Remove SSL from the Exadmin virtual root in IIS: Click Start, point to Programs, click Administrative Tools, and then click Internet Services Manager.
Click your server, and then expand the Web site that contains the Exadmin virtual root (the default Web site is "Default Web Site").
Right-click Exadmin, and then click Properties.
Click the Directory Security tab.
Under Secure Communications, click Edit.
Click to clear the Require secure channel (SSL) check box. If Require 128-bit encryption is shaded, click to select Require secure channel (SSL), click to clear Require 128-bit encryption, and then click to clear the Require secure channel (SSL) check box again.
Click OK two times.
Restart Exchange System Manager.
Sorry, that was a crappy cut and paste job. The text came from the provided link.
ASKER
Thats alright.
No each NIC has just the one IP assigned.
No SSL, the 'secure communications' buttons are greyed out.
No each NIC has just the one IP assigned.
No SSL, the 'secure communications' buttons are greyed out.
Give this a shot:
1. Open IIS Manager (Start->run->inetmgr)
2. Click on Web Service Extensions.
3. Make sure status of all below web service extensions is Allow .
Active Server Pages
ASP .NET v1.1.4322
Microsoft Exchange Server
4. If any web service extension is in Prohibited status, change it to Allowed
5. Once done, you should be able to expand public folder hierarchy through ESM.
1. Open IIS Manager (Start->run->inetmgr)
2. Click on Web Service Extensions.
3. Make sure status of all below web service extensions is Allow .
Active Server Pages
ASP .NET v1.1.4322
Microsoft Exchange Server
4. If any web service extension is in Prohibited status, change it to Allowed
5. Once done, you should be able to expand public folder hierarchy through ESM.
Also, in ESM, right-click the Public Folders and choose Connect To. Select your Exchange server. Maybe it's been trying to connect to an old one?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks Rob, will post back tomorrow...
ASKER
In ESM I am connecting to the correct server, its the only one listed.
What should the default website settings generally be?
What should the default website settings generally be?
ASKER
No web service extensions. It is IIS 5.
Not sure if you saw this related EE article. There maybe some ideas there to try:
https://www.experts-exchange.com/questions/23209371/Cannot-expand-Public-Folders-in-System-Manager-c1030af1.html
https://www.experts-exchange.com/questions/23209371/Cannot-expand-Public-Folders-in-System-Manager-c1030af1.html
ASKER
Thanks Robrandon, i have been out of office for a few days so i am looking at this post now, be back with findings shortly...
ASKER
I am going to try a few of those suggestions over the holidays when office closes. I havent tried much tweaking yet as its our live system and im wary of breaking it. My Exchange knowledge is only basic enough so thats why im wary. i have postponed migration until January until I resolve this..
ASKER
Hi.
Apologies on the delay in updating this. I was out of the office unexpectedly and have only gotten back to it this week. Anyway, after trawling through articles I came across an article that is linked to something rob mentioned above. Involved editing the urlscan.ini file. This is the article I came across http://support.microsoft.com/?kbid=837365. in the AllowExtensions listing in urlscan.ini the .com was missing. I added in .com, restarted IIS and hey presto I can now expand the public and system folders. Great!
However, as a result of this change my OWA no longer works, either internally or externally. obviously linked to adding in the .com extension but surely theres should be a config that allows all to work together..
Apologies on the delay in updating this. I was out of the office unexpectedly and have only gotten back to it this week. Anyway, after trawling through articles I came across an article that is linked to something rob mentioned above. Involved editing the urlscan.ini file. This is the article I came across http://support.microsoft.com/?kbid=837365. in the AllowExtensions listing in urlscan.ini the .com was missing. I added in .com, restarted IIS and hey presto I can now expand the public and system folders. Great!
However, as a result of this change my OWA no longer works, either internally or externally. obviously linked to adding in the .com extension but surely theres should be a config that allows all to work together..
ASKER
Gave me pointer to finding the resolution in another article thelink of which I have posted in my last comment. thanks Robrandon for all your efforts on this. Editing the urlscan.ini file allowed me access to the folders.
ASKER
FYI folks.
Just came across this previous question https://www.experts-exchange.com/questions/21583463/Public-Exchange-and-Exadmin-folders-showing-ERROR.html?eeSearch=true
which states that the red errors are normal and that restarting IIS resolves that. I did and they are cleared. Still my main issue remains and I assume is to do with the way the IIS was setup originally.