Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 616
  • Last Modified:

How to recreate Vdirs for Exchange 2003 in IIS5

Hi,

I have a problem with an exchange 2003 server running on Windows 2000. Basically OMA has stopped working with the user seeing The specified module could not be found. In a browser, and their device not syncing. On the server, if we are lucky, we see ;

Event Type:        Warning
Event Source:    Server ActiveSync
Event Category:                None
Event ID:              3007
Date:                     23/10/2008
Time:                     14:38:05
User:                     DOMAIN\USER
Computer:          SERVER NAME
Description:
Exchange mailbox Server response timeout: Server: [FQDN goes here] User: [user email goes here]. Exchange ActiveSync Server failed to communicate with the Exchange mailbox server in a timely manner. Verify that the Exchange mailbox Server is working correctly and is not overloaded.  

Im pretty certain that the Virtual Dirs have become corrupt somehow as the entries in the application mapping section of the OMA virtual directory entry had simply vanished. While adding them back has got things moving we are now stuck where we are.

Theres loads of guides on how to recreate the v-dirs for II6 and Exchange 2003, but not II5 and Exchange 2003. Anyone know if I can use the ones for IIS6, which involve scripts and metabase things which may be specific to IIS6 ?

Olly

--
***Company Name and URL Removed by TechSoEasy -- EE Zone Advisor***
0
stonneway
Asked:
stonneway
  • 2
1 Solution
 
Exchange_GeekCommented:
Have you taken a backup of IIS recently ??
0
 
stonnewayAuthor Commented:
Of the metabase? Yes. I've tried restoring that, which is from 7 days ago, but the same thing happens. It could well be that this hasn't worked for a while as they have only just moved to Exchange push email from blackberrys using IMAP.
0
 
Exchange_GeekCommented:
These are the same steps out-lined for E2k3 on W2k - nothing much differs with respect to Exchange functionality within IIS Virtual directories apart from authentication and permission - which gets restored using the following link.

Ref: http://www.msexchange.org/tutorials/Resetting-OWA-Folder-IIS-security-permissions-Exchange-2003.html.  

1.Start IIS on the Exchange server.
2.Backup the metabase just in case. Right-click Default Web Site, click All Tasks, and then click Save Configuration to a File. Type a filename for the file and click OK.
3.Expand Default Web Site, and then delete the following virtual directories:
4.Microsoft-Server-ActiveSync
OMA
Exadmin
Exchange
Public
ExchWeb
5.Close IIS
Start Metabase Explorer. Click Start, All Programs, IIS Resources, and then click Metabase Explorer.
6.Expand the LM key, right-click the DS2MB key, and then click Delete.
7.Close Metabase Explorer.
8.Restart the Microsoft Exchange System Attendant service. This will re-create the virtual directories in IIS.
9.Check the security permissions in Internet Information Services (IIS)
10.Open IIS. Expand the default website. Right Click the Exchange Virtual Directory. Ensure there is a Check next to Basic Authentication, Click OK twice.
11.Right click the ExchWeb Virtual Directory. Ensure there is a Check next to Anonymous access.
12.Check the folder security permissions using windows explorer
13.Right-click the Exchweb folder, and then click Properties. Click the Security tab.
14.Verify that the Authenticated Users group has the following permissions:
Read and execute
List folder contents
Read
15.If the Authenticated Users group is not listed in the Access Control List, click Add to add the Authenticated Users group. Add the correct permissions as listed in step 14.
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now