TROUBLESHOOTING
Troubleshooting OWA For PDA
When you are configuring your OWA For PDA installation, it is usually easier to use the
Web browser that is installed on your PC.
If you see the Network Login dialog box three times, and then the login fails, your server
may be authenticating you against its own User accounts instead of the network's.
Try logging in with <DOMAIN_NAME>/<USERNAME> instead of just <USERNAME>, or
verify the default Authentication Domain for the Virtual Directory in IIS manager.
Also (for Exchange 5.5),
check that the 'Everyone' or 'Domain Users' group
has the 'Log On Locally' right on your IIS server.
The Exchange 5.5 version of these applications
make use of MS Collaboration Data Objects v1.21 (CDO.DLL),
which should be present on your OWA server.
If you encounter CDO errors, check that you have the latest version of CDO.DLL on your server.
There are definitely 'good' and 'bad' versions of CDO.DLL.
Here is a list of all the
CDO File Versions that I have encountered.
Some common error messages:
"This is a marker file generated by the precompilation tool,
and should not be deleted!"
This is sometimes encountered when the application is installed
in Windows Server 2008 (i.e. IIS7). It means that the installer
was unable to convert the web directory to an application.
You will need to find the owa-pda directory
in IIS Manager, and manually convert it to an application.
404 - Page Not Found
This sometimes happens with the Exchange 2007 version of the application.
It can be caused by the ASP.Net version not being correctly set in IIS Manager.
Normally, this setting will be inherited from the Default Web Site,
but if the DWS has no setting, then it will be necessary to look at
the properties of the OWA-PDA Virtual Directory in IIS Manager,
select the ASP.Net tab, and select v2 from the drop-down list.
The information store could not be opened.
[MAPI 1.0 - [MAPI_E_LOGON_FAILED(80040111)]]
- The user has supplied a non-existent mailbox name at the Mailbox Name page.
- The user has attempted to open a mailbox, but does not have the required permissions on it.
-
You have installed the product on a member server,
but the Default Authentication Domain is not correctly set in IIS Manager.
If you have an account on the member server with the same name as your Domain account,
you will be authenticated locally, but be unable to open you mailbox.
Try logging in with DOMAIN\USERNAME instead of just USERNAME,
or make sure that the Default Authentication Domain is set properly.
-
This error can also be caused by the CDO 'Ambiguous Mailbox Alias' effect
which is seen if there are two similarly named mailbox aliases present on the system.
Try supplying the mailbox SMTP address, or the Display Name, instead of the Alias.
You can supply any of these three at the Mailbox Name prompt on the login page.
- The mailbox is hidden from the GAL. Rare, but it happens!
Active Server Pages error 'ASP 0115'
and/or A trappable error (C0000005) occurred in an external object
-
If you have been using Outlook 2003,
it may have added extra fields to your Exchange Information Store
that will cause unpatched versions of CDO to fail.
Make sure that your server copy of CDO.DLL is the most recent version by doing this
CDO version check .
If you don't have the latest version,
visit the Microsoft Web site
and search for the latest CDO patch for your Exchange version.
[Collaboration Data Objects - [MAPI_E_NOT_INITIALIZED(80040605)]]
-
The user does not have the required NTFS permissions on the MAPI working directory,
or the working directory name is missing from the registry.
Check the following registry key:
HKLM\SOFTWARE\Microsoft\Windows Messaging Subsystem\ProfileDirectory
If you change this value,
you will need to restart IIS because MAPI will not read this key again
once it has started.
Collaboration Data Objects error - '000004f7'
[Collaboration Data Objects - [MAPI_E_NOT_FOUND(8004010F)]]
-
If you see this error when you first try to open a mailbox,
make sure that the profile directory
named in the previously mentioned ProfileDirectory key
has actually been created on the server.
HTTP Error 403 403.1 Forbidden: Execute Access Forbidden
- Script access has been disabled for the Web Site or Virtual Directory at the IIS server.
Directory Listing Denied
-
The site or virtual directory does not have Default.asp in its list of default documents.
Please add Default.asp to the list using IIS Manager if it is missing.
ASP 0129
Unknown scripting language.
The scripting language 'VBScript.Encode' is not found on the server.
-
The server is unable to decrypt the encrypted ASP source code.
This may happen if the server has an Internet Explorer version lower than v5.0 installed.
Please contact me if you get this error and are unable to upgrade to IE5.
If you encounter any other errors or problems in OWA-PDA,
please contact me. I am happy to receive technical enquiries
about this products from both registered and non-registered users.
It would help if you could tell me your Exchange Server version,
and any error numbers that you can see in your browser.
Copyright © 2003 - 2012 Lee Derbyshire. All rights reserved.
