Manage Email Signatures Centrally - For All Users

CarolineLee · Posted: Wed Nov 21, 2007 4:10 pm Post subject: OWA - error 409 Conflict

I am getting the following error in the OWA log file

The remote server returned an error: (409) Conflict.

Any ideas?

Bjarne Mess · Posted: Thu Nov 22, 2007 2:14 pm Post subject:

Can you confirm that you are using Exchange 2003.

Do you have a certificate and are you using SSL?

CarolineLee · Posted: Thu Nov 22, 2007 2:37 pm Post subject: 409 Conflict

We are on Exchange 2003 SP2

We do have a certificate and are using SSL.

I have tried setting up OWA for 2 users. One user gets the error "The remote server returned an error: (409) Conflict.

The other users OWA status is NULL.

Neither users get the signature in OWA but the correct data is in the SQL table.

It works for both users on Outlook client.

Bjarne Mess · Posted: Thu Nov 22, 2007 2:43 pm Post subject:

409 is often related to a wrong URL. Please ensure that you don't have http:// og ..s:// in the owa key. Please also try to run signOWS.exe -v (that is in verbose mode)and s theflog

Thanks,
Bjarne

CarolineLee · Posted: Thu Nov 22, 2007 3:07 pm Post subject: 409 conflict error

Confirmed that there is no http or https in the url.

Not sure what you mean by verbose mode - I have tried run signOWA.exe -v on two clients - one crashes the other just runs the signOWA.exe and closes the window.

Jakob Christensen · Posted: Fri Nov 23, 2007 8:32 am Post subject: Re: 409 conflict error

Hi Caroline,

I will need some more debug information. To do this you need to run signOWA manually from a cmd prompt. Start a cmd prompt by pressing "Start" and "Run...". Then enter "cmd" and press "Ok".

Now change the directory to the directory where signOWA.exe is located. Then type "signowa -v" and press enter.

When signowa has run, copy the output and post it here.

Thank you for your help.

Kind regards, Jakob.

CarolineLee · Posted: Fri Nov 23, 2007 9:24 am Post subject:

Can you confirm that I am supposed to be running the signowa on the server and not the client?

Here is the result from running it on the server

C:\eMail>signOWA -v
Using the url: https://mwa.wragge.com/
Setting signature for user: AMAR
Mailbox name: Amar_Munir
Sending HTTP request to: https://mwa.wragge.com/Amar_Munir/
Failed to login to OWA. Be sure your domain and password are correct.
Setting signature for user: CAROLINE
Mailbox name: Caroline_Lee
Sending HTTP request to: https://mwa.wragge.com/Caroline_Lee/
Failed to login to OWA. Be sure your domain and password are correct.
Setting signature for user: COMPLETION3
Mailbox name: _COMPLETION3
Sending HTTP request to: https://mwa.wragge.com/_COMPLETION3/
Failed to login to OWA. The following error occured: The operation has timed out

Jakob Christensen · Posted: Fri Nov 23, 2007 10:02 am Post subject:

Running signowa on a server is the right way.

Maybe you need to use the url mwa.wragge.com/exchange instead? OWA is usually deployed to the exchange directory.

A couple of questions:
Are you using Forms Bases Authentication, Windows Authentication, or Basic Authentication?
Did you set the username, password, and domain in the registry?
Did you set the "Receive as" right on the mail store for that user?

Kind regards, Jakob.

CarolineLee · Posted: Fri Nov 23, 2007 10:14 am Post subject:

Changed the url to mwa.wragge.com/exchange just to try it but got the same errors.

Yes we are using Forms Based Authentication so I have set OWAfba to 1
Yes the Username, password and domain are set in the registry
Yes the user that is set in the registry has receive as rights

Bjarne Mess · Posted: Fri Nov 23, 2007 10:17 am Post subject:

Can you also confirm that you don't have the deny checkbox greyed out with a checkmark in it as this deny was inhertied for that user?

Jakob Christensen · Posted: Fri Nov 23, 2007 10:37 am Post subject:

When I enter your url into a browser, I am presented with somethink that looks like a proxy login form. Is this also the case if you enter the url into a browser locally on your server?

CarolineLee · Posted: Fri Nov 23, 2007 10:41 am Post subject:

Reply - yes you always get that i-chain login to access OWA - both external and internal.

CarolineLee · Posted: Fri Nov 23, 2007 10:42 am Post subject:

I am unable to confirm the settings for the user on Exchange as our exchange administrator is on a days leave today and I do not have access.

Jakob Christensen · Posted: Fri Nov 23, 2007 11:40 am Post subject:

CarolineLee · Posted: Fri Nov 23, 2007 11:44 am Post subject: I-Chain

Oh dear that will cause us a major problem then.

Some users use Citrix others only use OWA.