These error codes might help you during deployment of OWA email signatures (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.:
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.
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.