[chaos40]

Any help is greatly appreciated!

We have an Exchange 2000 server and another server hosting OWA via Exchange 2003 front-end. This has been working perfectly for over a year. Last week, after a reboot of both machines, we are getting the following error. And the website is obviously not working.

Our Exchange server is working fine and mail is flowing normally.

Here is the error...
Event Type: Warning

Event Source: W3SVC

Event Category: None

Event ID: 101

Date: 3/4/2007

Time: 9:52:19 AM

User: N/A

Computer: UXBS-OWA

Description:

The server was unable to add the virtual root '/Public' for the directory '\\\\.\\BackOfficeStorage\\actech-lenze.com\\Public Folders' due to the following error: The system cannot find the path specified. The data is the error code.

For additional information specific to this message please visit the Microsoft Online Support site located at: http://www.microsoft.com/contentredirect.asp.

Data:

0000: 03 00 00 00 ....

 

[SoBe8503]

Quote:

The server was unable to add the virtual root '/Public' for the directory '\\\\.\\BackOfficeStorage\\actech-lenze.com\\Public Folders' due to the following error: The system cannot find the path specified. The data is the error code.

Whats with the . in the slashes?? that doesn't look right.

 

[kc-tr]

It apears as though your directory is wrong.

Quote:

\\\\.\\BackOfficeStorage\\actech-lenze.com\\Public Folders

If you have this drive mapped, then it is wrong. You have the . as the computer or share name. This is fine if that is what it is. But if not then thats the problem.
Normally it would be something similar to this

Quote:

\\\\ServerName\\BackOfficeStorage\\actech-lenze.com\\Public Folders

If its a mapped network drive

Quote:

X:\\BackOfficeStorage\\actech-lenze.com\\Public Folders

Rather than

Quote:

\\\\.\\BackOfficeStorage\\actech-lenze.com\\Public Folders

 

[chaos40]

After about 11 hours on the phone with MS (over two days), it is working but broken. If you look in IIS Manager, the two virtual webs responsible for users' mailboxes and access to public folders appear broken.

However, if you connect to OWA through a web browser it performs flawlessly. MS closed my ~$250 support case because I opened it with a too generic "Outlook Web Access is not working". Since Outlook Web Access is now working and the errors are technically in IIS (and somehow harmless?!) they won't continue to work the case.

Lovely.

 

[Zeus]

Quote:

Originally Posted by SoBe8503 Whats with the . in the slashes?? that doesn't look right.

The dot in the slashes means the local machine