We help IT Professionals succeed at work.

We've partnered with Certified Experts, Carl Webster and Richard Faulkner, to bring you a podcast all about Citrix Workspace, moving to the cloud, and analytics & intelligence. Episode 2 coming soon!Listen Now

x

OWA 2003 - Can only view Inbox and Calendar

gigco
gigco asked
on
Medium Priority
879 Views
Last Modified: 2008-01-09
Server 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!
Comment
Watch Question

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 :-)

http://support.microsoft.com/kb/833340

Let me know how you go

Rob
CERTIFIED EXPERT

Commented:
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?

Author

Commented:
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>




CERTIFIED EXPERT

Commented:
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.

Author

Commented:
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_szXMLDOMProgID);objViewXML.transformNodeToObject(objTransFormXSL.documentElement, objXML);if (0 != objXML.parseError.errorCode)

Line 1018:
var szHTML = m_objXML.transformNode(m_oXSLNodes.item(m_icurGrpLevel - 1));if (m_bIsCardView)

CERTIFIED EXPERT

Commented:
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.dll .  If so, then from a CMD prompt, type:

CD \WINDOWS\system32
regsvr32 msxml3.dll

Hopefully, you will get a 'succeeded' alert.  It ought to work okay, then.

Author

Commented:
Succeeded, but still no go. Same error message.

The crazy thing with this is that everything worked a few weeks ago - and on several PC's. Now it globally doesn't work for any user from any PC.
CERTIFIED EXPERT

Commented:
Does it always say the same 'Class not registered'?  Is that the same error that the debugger showed, too?  I am just wondering why it was originally line 538, not 520.  Of course, this number might depend on what folder you are viewing.

Author

Commented:
Line 1019: Invalid Procedure call or argument
Line 537/538: Class not registered
Line 521: Invalid Procedure call or argument

The line number does vary depending on the folder.
CERTIFIED EXPERT

Commented:
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?

Author

Commented:
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.
CERTIFIED EXPERT

Commented:
And does your client computer have this registry key?:

HKEY_CLASSES_ROOT\Microsoft.XMLDOM

This is the class that it is saying isn't registered, even though you made sure it was with regsvr32 .

Author

Commented:
Yes the clients have that key as well.
CERTIFIED EXPERT

Commented:
It's a bit of a mystery then, since the class obviously is registered.  I wonder if there is some kind of restriction on the js capabilities of the browser.  When you go to OWA, does it show the server to be in the Local Intranet zone in the bottom right of the IE status bar?

Author

Commented:
It depends - If local to the server then yes it shows as Local Intranet, outside of the office it shows as Trusted Site. Both act/error out exactly the same.
CERTIFIED EXPERT

Commented:
Does whichever zone it appears in, on any computer, have Active Scripting enabled in the IE Security Zone configurations?

Author

Commented:
Both zones have active scripting enabled.
CERTIFIED EXPERT

Commented:
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/display.asp?eventid=36&eventno=12&source=W3SVC&phase=1

Author

Commented:
Oddly as I have added more accounts - each account seems to be slightly different - some can access their calendar and some cannot.
CERTIFIED EXPERT

Commented:
And I guess there is no obvious difference between the accounts, otherwise you'd have noticed it?

Author

Commented:
Nope, just a new account and then another and so on. But then when accessing them - some have folders that work whereas others have different folders. Very strange.
CERTIFIED EXPERT

Commented:
I have to admit that I'm totally baffled by this one.  Maybe if you started a new thread, then you would get some different suggestions.  But I have a feeling that this is going to be very hard to fix.

Author

Commented:
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.

PAQed with points refunded (400)

Computer101
EE Admin

Not the solution you were looking for? Getting a personalized solution is easy.

Ask the Experts
Access more of Experts Exchange with a free account
Thanks for using Experts Exchange.

Create a free account to continue.

Limited access with a free account allows you to:

  • View three pieces of content (articles, solutions, posts, and videos)
  • Ask the experts questions (counted toward content limit)
  • Customize your dashboard and profile

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.