Navigation¶

• Main Page
• All Pages
• Categories
  
  

eMailSignature Guides¶

• Installing
• Upgrade to V8
• Administering
• Basic Technical Info
• Glossary of Terms
  

eMailSignature Modules¶

• PhoneBook - FREE!
• Mobile
• BlackBerry Integration
• Assistant
• Outlook Web
• Marketing
• vCards
• AD Update
• Disclaimer
• Integration
  

eMailSignature Versions¶

• eMailSignature Version 8.0.2
• eMailSignature v8.0
• eMailSignature v7.5
  

Find an Answer¶

»

Troubleshooting Outlook Web Module for eMailSignature

Troubleshooting¶

Table of Contents [Hide/Show] Troubleshooting eMailSignature Versions    404 Not Found    403 Forbidden    401 Unauthorized    440 Login Time-out    signOWA.exe only deploys signatures to a few users

eMailSignature Versions¶

Versions 7.x

If you experience errors, please check your security settings and registry settings, and evaluate the following possible solutions carefully. If none of these solutions help the problem, please search for more solutions on www.emailsignature.eu website.

404 Not Found¶

WebDAV in Exchange 2002 or 2007 or EWS in Exchange 2010 has been disabled for IIS on the server running OWA.

If WebDAV/EWS is enabled, the URL may be wrong. Please review your OWA URL settings:

1. Open the Modules tab in the Cockpit and click Configuration button for Outlook Web Access. The Basic Configuration window appears.
2. Enter the URL of your Exchange OWA server in the OWA URL field. Leave out HTTP and HTTPS before the URL.
   If you are using Exchange 2003, append "exchange" to the URL as in the following example: "myserver.mydomain.local/exchange/".
   If you are using Exchange 2007 or 2010, do not append anything as in the following example: "myserver.mydomain.local". (E.g. do NOT add /owa or /exchange)
3. Click Save to keep the updated settings.
   

The security settings on the Exchange server for the user running signOWA may also be incorrect. Review the settings as described in the "Setting account rights for the account running signOWA.exe" section of this document.

403 Forbidden¶

Make sure that the version of the Exchange Server is specified correctly:

1. Open the Modules tab in the Cockpit and click Configuration button for Outlook Web Access. The Basic Configuration window appears.
2. Select the Exchange Server version that you are running:
   • Exchange 2003
   • Exchange 2007
   • Exchange 2010.
3. Click Save to keep the updated settings.
   

The error may also indicate that you are not using SSL (HTTPS) when required. Please make sure that HTTPS/SSL is checked in the Cockpit if you are using SSL:

1. Open the Modules tab in the Cockpit and click Configuration button for Outlook Web Access. The Basic Configuration window appears.
2. Check the Secure Socket Layer (https) option if you are using HTTPS to connect to OWA.
3. Click Save to keep the updated settings.
   

401 Unauthorized¶

Your OWA server is not set up to use Forms Based Authentication. Please configure signOWA to use Integrated Windows Authentication instead:

1. Open the Modules tab in the Cockpit and click Configuration button for Outlook Web Access. The Basic Configuration window appears.
2. In the Authentication Method section, select Integrated Windows Authentication for OWA option.
3. Click Save to keep the updated settings.
   

Other causes may be an incorrect OWA URL or wrong user name/password.

Security Warning: We recommend to write the internal address of the OWA server to avoid any possible security issues.

Please review your OWA URL settings:

1. Open the Modules tab in the Cockpit and click Configuration button for Outlook Web Access. The Basic Configuration window appears.
2. Enter the URL of your Exchange OWA server in the OWA URL field. Leave out HTTP and HTTPS before the URL.
   If you are using Exchange 2003, append "exchange" to the URL as in the following example: "myserver.mydomain.local/exchange/".
   If you are using Exchange 2007 or 2010, do not append anything as in the following example: "myserver.mydomain.local". (E.g. do NOT add /owa or /exchange)
3. Click Save to keep the updated settings.
   

Also, review your settings for OWAuid, OWApwd, and OWAdomain registry keys, as described in section Setting up security for Exchange Server of this guide.

440 Login Time-out¶

This error is usually seen when trying to use Forms Based Authentication while having specified an incorrect URL.

Review your settings for Authentication Method and OWA URL, as described in section Configuring OWA settings in the Cockpit of this guide.

signOWA.exe only deploys signatures to a few users¶

Make sure that you have cleared all users after testing:

1. Open the Modules tab in the Cockpit and click Configuration button for Outlook Web Access. The Basic Configuration window appears.
2. If there are any user names in the Test before going 'Live' field, clear them. Leave this field blank to deploy signatures to all OWA users.
3. Click Save to keep the updated settings.
   

Up to Outlook Web Access Module for eMailSignature

Back to Tips and Tricks