| View previous topic :: View next topic |
| Author |
Message |
geyojo Not too shy to talk
Joined: 14 Aug 2008 Posts: 6 Location: Den Haag / The Netherlands
|
| Posted: Fri Jan 28, 2011 2:26 pm Post subject: suddenly a Sign OWA 440 error |
|
|
Hi,
Since a few days we have no OWA sign. Nothing has been changed on the servers or the OWAUSER account.
The reg settings were cleaned and reset, we even reran the caspol string. IIS server has been reset too...
Username and password of the OWAUSER were reset/checked. This user has its own mailbox and has fullcontrol on the folder were the signowa and sign.exe files are located.
Please help.....
Gérard |
|
| Back to top |
|
 |
joestern Not too shy to talk
Joined: 23 Mar 2010 Posts: 9 Location: Philadelphia, PA
|
| Posted: Fri Jan 28, 2011 4:07 pm Post subject: |
|
|
SignOWA also stopped working for us. when I run signowa.exe with or without the -v option, I see no results. No error, no output at all.
I am running the beta version of 7.5. |
|
| Back to top |
|
 |
Bjarne Mess Certified Professional


Joined: 01 May 2007 Posts: 735 Location: Copenhagen
|
| Posted: Tue Feb 01, 2011 10:32 pm Post subject: |
|
|
Thanks for reporting this in. However, it does not stop running out of the blue, so something must have happened in either case. There is no time block either
Please send your own log (normal sign.exe log and signOWA) to support@brandedmails.com so we can have a look at it. There is always a (quite simple) explanation to "signOWA stops working"..
Thanks. |
|
| Back to top |
|
 |
joestern Not too shy to talk
Joined: 23 Mar 2010 Posts: 9 Location: Philadelphia, PA
|
| Posted: Wed Feb 02, 2011 2:10 pm Post subject: |
|
|
My apologies. It turns out the user in question had not run sign.exe in a while, and thus signowa had no new signature to propogate.
Also, I wasn't running signowa.exe under the right credentials when I was testing it, which is why no results appeared. |
|
| Back to top |
|
 |
geyojo Not too shy to talk
Joined: 14 Aug 2008 Posts: 6 Location: Den Haag / The Netherlands
|
| Posted: Thu Feb 03, 2011 8:07 am Post subject: SignOwa |
|
|
| Bjarne Mess wrote: | Thanks for reporting this in. However, it does not stop running out of the blue, so something must have happened in either case. There is no time block either
Please send your own log (normal sign.exe log and signOWA) to support@brandedmails.com so we can have a look at it. There is always a (quite simple) explanation to "signOWA stops working"..
Thanks. |
Hello Bjarne,
For some reason, SignOWA.exe thinks that the OWAUSER has no rights to run it. It's strange, becouse this user has full control. We use sign.exe 7.0.0.0 and same version for signowa.exe.
Sample..
SignOWA, Version=7.0.0.0, Culture=neutral, PublicKeyToken=56390b2257d4df72
30-10-2009 10:06:32
Using the url: https://SDBMAIL01/EXCHANGE/
Setting signature for user: ADAMOL
Mailbox name: a.moller@sdbgroep.nl
Sending HTTP request to: https://SDBMAIL01/EXCHANGE/a.moller@sdbgroep.nl/
The remote server returned an error: (440) Login Timeout.
-----------------------------------
Please help us..
Thank you.
Gérard |
|
| Back to top |
|
 |
Bjarne Mess Certified Professional


Joined: 01 May 2007 Posts: 735 Location: Copenhagen
|
|
| Back to top |
|
 |
Jakob Christensen Certified Professional

Joined: 27 Apr 2007 Posts: 60 Location: Copenhagen, Denmark
|
| Posted: Fri Feb 04, 2011 9:19 am Post subject: Re: SignOwa |
|
|
| Quote: |
Hello Bjarne,
For some reason, SignOWA.exe thinks that the OWAUSER has no rights to run it. It's strange, becouse this user has full control. We use sign.exe 7.0.0.0 and same version for signowa.exe.
Sample..
SignOWA, Version=7.0.0.0, Culture=neutral, PublicKeyToken=56390b2257d4df72
30-10-2009 10:06:32
Using the url: https://SDBMAIL01/EXCHANGE/
Setting signature for user: ADAMOL
Mailbox name: a.moller@sdbgroep.nl
Sending HTTP request to: https://SDBMAIL01/EXCHANGE/a.moller@sdbgroep.nl/
The remote server returned an error: (440) Login Timeout.
-----------------------------------
Please help us..
Thank you.
Gérard |
Hi Gérard,
The (404) Login Timeout usually means that your Exchange web site is set up to use Forms Based Authentication (FBA) but signOWA is set up to use Windows Authentication. You can verify the authentication scheme for the Exchange web site in the Exchange Management Console.
Note that for Exchange 2007 there are two different web sites which are called OWA and Exchange. SignOWA uses the Exchange web site and hence signOWA only depends on the authentication set up for the Exchange web site. This means that even though your users might be using Windows Authentication when logging into OWA, signOWA might use another authentication method.
Thanks,
Jakob. |
|
| Back to top |
|
 |
|