When you say 'it only allows' Inbox and Calendar, do you mean that the links to other folders do not even appear; or that they appear, but an error is displayed when you try to use them?
Main Topics
Browse All TopicsServer is hosting both Exchange and the OWA
Running Exchange 2003
Outlook full clients work without issue
But OWA only allows viewing/editing of Inbox and Calendar.
Something has to have changed - as all feature were working several weeks ago.
Any ideas? Thanks!
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Rob,
I tried your suggestion and to no avail.
Lee,
Everything looks complete on the initial page, the side is loading and showing all folders and such - but when clicking on any folder other than "Inbox" or "Calendar" I just get a Loading in the main panel of the page. There is also an error that IE gives in the status window - the error states:
Line: 538 (This varies depending on the folder)
Char: 1
Error: Class not registered
Code: 0
URL: <our full url here>/exchange/<username>
Hmm, a JavaScript error. It's hard to be sure where these come from. The line 538 probably refers to one of the .js files loaded by OWA. It would help if you could enable script debugging in IE, since then the exact problem statement will be highlighted in the debugger. Have a look in your IE options, and uncheck Disable Script Debugging. Then next time you see the error, it should ask if you want to debug the error.
Upon a closer look - it appears these are the only two lines that ever give me an error code.
Line 520:
{objXML = new ActiveXObject(m_szXMLDOMPr
Line 1018:
var szHTML = m_objXML.transformNode(m_o
It looks like the client doesn't know how to instantiate the Microsoft.XMLDOM object. First, make sure that you have the file named C:\WINDOWS\system32\msxml3
CD \WINDOWS\system32
regsvr32 msxml3.dll
Hopefully, you will get a 'succeeded' alert. It ought to work okay, then.
When you are looking at the error line 520 or 521 in the debugger, can you scroll up to the top of the file and make sure that there is a part (probably in the middle of a longer line) that contains the text:
var m_szXMLDOMProgID = "Microsoft.xmldom";
It is important that both the variable name and the text string appear as above.
Also, do you have a FE/BE setup?
I have the exact line you posted on the second line of the debug on error 520. And as you said it was in the middle of a longer statement containing other declarations/commands.
This server is the only server. So I guess that makes it the FE - either way it is doing IIS/OWA/OMA and all the storage of the email.
I'm a bit stuck, now. I know a bit about JavaScript, but not enough to solve this problem. This error is mentioned here - it might help:
http://www.eventid.net/dis
Problem solved!
By referring to the article KB883380, I reset the default virtual directories that are required to provide Outlook Web Access, Exchange ActiveSync, and Outlook Mobile Access services in Exchange Server 2003.
Configured OWA to use SSL.
After that, when accessing the OWA would get the error ""440 Login Timeout". Reset the password of the user IUSER_SCPNFSERV and appled it to the default website.
Hopefully this will help someone in the future.
Thanks for all the help Lee - this one got a little weird - and we still don't know what happened to start the whole issue.
Business Accounts
Answer for Membership
by: robjeevesPosted on 2006-11-02 at 02:17:34ID: 17856800
Ok mate this a loooooooooong shot but I use a feature called Outlook Segmentation. Here is a link but basically you specify within ADSI edit a number and that number specifys what features in OWA are available. Is this one user or everyone? Take a look at the attributes of one user to rule this out as the cause. Long shot but quite interesting anyway :-)
om/kb/8333 40
http://support.microsoft.c
Let me know how you go
Rob