|
Manage Email Signatures centrally from your Desktop - For All Users
extend your brand and promote your products, services, special events and news
|
| View previous topic :: View next topic |
| Author |
Message |
Bjarne Mess
Certified Professional
Joined: 01 May 2007
Posts: 723
Location: Copenhagen
|
| Posted: Thu Nov 15, 2007 11:41 am Post subject: SignOWA.exe Error Codes |
 |
|
These error codes might help you during deployment of eMailSignature for OWA (find them by right-clicking a user in the Status Monitor and choose 'OWA log'):
HTTP/1.1 200 OK
Deployment was successful for this user.
401: The remote server returned an error: (401) Unauthorized.
Make sure you have the key OWfba set to 0 and not 1 if you are not using FBA. It cannot log you on. Please ensure that you have the correct security permissions to do this.
The remote server returned an error: (401) Unauthorized.
You have put in a wrong username or password in OWAuid or OWApwd.
Unable to connect to the remote server
Please make sure that you have the key OWAssl set to 0 if you don't use HTTPS or SSL.
The remote server returned an error: (501) Not Implemented.
Please make sure that the OWA URL is correct in the key OWAurl.
Please make sure that WebDAV is enabled on the server.
Format of the initialization string does not conform to specification at index 0.
The error message means that the connection string saved in registry is invalid.
The ConnectionString property has not been initialized.
Check connection string in signOWA.reg and make sure that no single '\' are used as they are escape codes in a reg-file. E.g.:
| Code: | | "Settingsdatabase"="Provider=Microsoft.Jet.OLEDB.4.0;Data Source=\\\\server\\share\\settings.mdb" |
The remote server returned an error: (440) Login Timeout.
The admin running SignOWA.exe does not have permission to run Sign.exe.
The remote server returned an error: (404) Not Found.
Please make sure that WEBDAV is enabled on the website and Exchange Server. Learn more in this post.
<a:href> not found.
The user has not logged on to OWA.
Object reference not set to an instance of an object
The user has not created a signature in Outlook Web Access.
Unhandled Exception - Learn more in this post
Signowa crashes with "Unhandled Exception" error.
You will see this error if OWAuseencryption in the registry settings has been set to 1 manually but OWAuid and OWApwd have not been previously encrypted. In this case set OWAuseencryption to 0.
You will also see this error if you encrypted the username and password on one machine and then copied the registry settings to another machine. In this case you need to re-run the encryption on the new machine.
Finally you may get this error if you are using encryption and your eMailSignature license key has been updated. In this case re-run the encryption. |
|
| Back to top |
|
 |
Mathias Kiesler
Certified Professional
Joined: 26 Mar 2007
Posts: 186
Location: Osnabrücker Land
|
| Posted: Tue Jul 29, 2008 12:51 pm Post subject: OWA Fehlermeldungen Deutsch |
|
|
An dieser Stelle werden Fehlermeldungen in Deutsch protokolliert:
Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
Der Anwender existiert nicht mehr im AD.
Lösung: Über den Statusmonitor im Cockpit den User aus der Settings.db von eMailSignature löschen, oder dieses Tool zum Freigeben von Lizenzen benutzen. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Register
Profile
Log in to check your private messages
Log in
Manage Email Signatures centrally from your Desktop - For All Users Forum Index
-> OWA/Exchange 2003, 2007 and 2010 Support
|
About Us |
Terms and conditions |
© 2012 eMailSignature Aps.