| View previous topic :: View next topic |
| Author |
Message |
Jakob Christensen Certified Professional

Joined: 27 Apr 2007 Posts: 60 Location: Copenhagen, Denmark
|
| Posted: Thu Mar 10, 2011 5:53 pm Post subject: |
|
|
| witwicki wrote: | | cthauber wrote: | The mailbox must be deleted and recreated (export to a PST before deleting using Outlook, and import back in after re-creating, again, using Outlook).
That was the only way I waas able to get the few users I had with issues to start working again.
However, I only had to deal with 3 users that needed it... |
I have many users that are affected I need to know how to clear these sigs.
Thanks
Adam |
One of the newer versions of signOWA introduced a workaround for corrupted mailboxes caused by having '&' in the signature (I cannot remember which version).
If you run the following command, signOWA will attempt to clear the OWA signature for all users unless you have specified a number of test users in the cockpit:
signowa -v -fix
Please make sure that you have a sufficient backup of your Exchange mail store before running the fix. |
|
| Back to top |
|
 |
witwicki Quite a regular
Joined: 03 Jun 2009 Posts: 14 Location: UK
|
| Posted: Fri Mar 11, 2011 8:45 am Post subject: |
|
|
My SignOWA is version 3.3.2.1, which does not have the -fix switch.
Any chance I can have a version that does?
Thanks
Adam |
|
| Back to top |
|
 |
Bjarne Mess Certified Professional


Joined: 01 May 2007 Posts: 735 Location: Copenhagen
|
| Posted: Fri Mar 11, 2011 9:06 am Post subject: |
|
|
Yes it is indeed very relevant and the new signowa can fix this. This is related to a well known Exchange issue when updating text based OWA signatures.
Thanks, Bjarne |
|
| Back to top |
|
 |
witwicki Quite a regular
Joined: 03 Jun 2009 Posts: 14 Location: UK
|
| Posted: Fri Mar 11, 2011 9:08 am Post subject: |
|
|
And how do i get a later version?
Thanks |
|
| Back to top |
|
 |
witwicki Quite a regular
Joined: 03 Jun 2009 Posts: 14 Location: UK
|
| Posted: Fri Mar 11, 2011 9:29 am Post subject: |
|
|
Trying the latest version now...
D:\Program Files\Test SignOWA>SignOWA.exe -v -fix
SignOWA, Version=7.0.5.1, Culture=neutral, PublicKeyToken=56390b2257d4df72
28/02/2011 15:47:10
Unhandled Exception: System.ArgumentNullException: Value cannot be null.
Parameter name: signOWA has not been properly configured. The field 'removeimgta
g' is empty.
at OA.SignOWA.OleDbDataGateway.GetDbInt(OleDbDataReader reader, String fieldN
ame)
at OA.SignOWA.OleDbDataGateway.GetSettings()
at SignOWA.Program.Main(String[] args)
What am i doing wrong? |
|
| Back to top |
|
 |
witwicki Quite a regular
Joined: 03 Jun 2009 Posts: 14 Location: UK
|
| Posted: Fri Mar 11, 2011 9:49 am Post subject: !!! |
|
|
Ok fixed that with help of another post
But know when i run it it dosnt work
"Failed to login to OWA. The following error occured: Unable to connect to the remote server"
This using the same settings as the old version and ignoring the OWAUSERS key!!!!
I dont want to affect all users just ONE!!!
How can one little program cause such serious issues!
Thanks
Adam |
|
| Back to top |
|
 |
Bjarne Mess Certified Professional


Joined: 01 May 2007 Posts: 735 Location: Copenhagen
|
| Posted: Fri Mar 11, 2011 3:05 pm Post subject: |
|
|
Serious stuff is going on when running these files.
Make sure that you are running the latest version of eMailSignature also. You need to be running the latest version 7.5, I assumed that you have upgraded.
Thanks. |
|
| Back to top |
|
 |
witwicki Quite a regular
Joined: 03 Jun 2009 Posts: 14 Location: UK
|
| Posted: Fri Mar 11, 2011 3:07 pm Post subject: |
|
|
| Running 7.3.0 |
|
| Back to top |
|
 |
Bjarne Mess Certified Professional


Joined: 01 May 2007 Posts: 735 Location: Copenhagen
|
| Posted: Fri Mar 11, 2011 3:51 pm Post subject: |
|
|
Please upgrade to 7.5.
Also make sure that you have your information from signOWA registry entered in the Cockpit because the new signOWA reads the credentials and users set from within the Cockpit and not registry. |
|
| Back to top |
|
 |
witwicki Quite a regular
Joined: 03 Jun 2009 Posts: 14 Location: UK
|
| Posted: Mon Mar 14, 2011 11:11 am Post subject: |
|
|
| Bjarne Mess wrote: | Please upgrade to 7.5.
Also make sure that you have your information from signOWA registry entered in the Cockpit because the new signOWA reads the credentials and users set from within the Cockpit and not registry. |
I cant use the cockpit it says the module isnt licenced.... was this missed when i was sent the upgrade for cockpit?
Thanks |
|
| Back to top |
|
 |
witwicki Quite a regular
Joined: 03 Jun 2009 Posts: 14 Location: UK
|
| Posted: Tue Mar 15, 2011 4:01 pm Post subject: |
|
|
Looks like this is now resolved using the latest version (using -fix switch)
I have been able to login to the affected users accounts.
Thanks for your help.
Adam |
|
| Back to top |
|
 |
Jakob Christensen Certified Professional

Joined: 27 Apr 2007 Posts: 60 Location: Copenhagen, Denmark
|
| Posted: Wed Mar 16, 2011 2:14 pm Post subject: |
|
|
| witwicki wrote: | Looks like this is now resolved using the latest version (using -fix switch)
I have been able to login to the affected users accounts.
Thanks for your help.
Adam |
Glad to hear it.
Regards,
Jakob. |
|
| Back to top |
|
 |
|