search

vivekiyer / corporateaddressbook

1 stars 1 forks source link

Error logging in error 200 #111

Open vivekiyer opened 10 years ago

vivekiyer commented 10 years ago

From weatherc...@gmail.com on February 01, 2013 06:21:35

What steps will reproduce the problem? 1. trying to just log in 2. 3. What is the expected output? What do you see instead? when submitting log in, get error 200 What version of the product are you using? tried s.0.7 and 2.0.8 dev What version of Android are you running? 4.1.1 What version of Exchange are you connecting to? 2010 Please provide any additional information below. tried the latest stable client from play store. and also the latest dev released today. I can't get it to ever log in. using a galaxy note 2 1605

Original issue: http://code.google.com/p/corporateaddressbook/issues/detail?id=111

vivekiyer commented 10 years ago

From dan.matt...@gmail.com on February 01, 2013 08:59:20

Thank you, this is very useful. Unfortunately, ProvisionStatus=2 means "Protocol error" which indicates that there is something wrong with the request we send - hard to believe since it works with the vast majority of servers out there.

I will upload a new version w/ some minor tweaks to the request and then notify you. Please try that one.

I really appreciate your efforts to help us out in improving the app!

Status: Started
Owner: dan.matt...@gmail.com
Labels: -Priority-Medium Priority-Critical 2.1.0

vivekiyer commented 10 years ago

From dan.matt...@gmail.com on February 02, 2013 02:37:35

Weird issue since the request does seem to be legit. I've added some extended error handling and logging in addition to some minor tweaks, please try version 2.1.0-dev-3: http://code.google.com/p/corporateaddressbook/downloads/detail?name=Corporate_AddressBook_2.1.0-dev-3.apk

vivekiyer commented 10 years ago

From dan.matt...@gmail.com on February 04, 2013 07:24:46

No luck in troubleshooting - very hard to know what your Exchange server finds to be a "Protocol Error".

I'd like to ask you to do logging on the server, that's normally pretty detailed and should explain the issue. Please see "Providing logs" here: https://code.google.com/p/corporateaddressbook/wiki/Troubleshooting

vivekiyer commented 10 years ago

From dan.matt...@gmail.com on February 04, 2013 07:51:33

Also: if you're not comfortable with uploading the logs here you can send them to corporateaddressbook@googlegroups.com which is a closed group visible only for the developers.

vivekiyer commented 10 years ago

From dan.matt...@gmail.com on February 04, 2013 14:22:54

Thank you for the logs - puzzling as they are. It says "AccessState: Allowed" as it should but then it claims that there is a protocol error. Comparing the server view of the request to the examples provided by Microsoft shows that they're essentially the same.

The only thing I could think of right now is to try to change the credentials: if you're using name@domain.com as user name, switch to DOMAIN\username instead or the other way around.

vivekiyer commented 10 years ago

From weatherc...@gmail.com on February 04, 2013 14:43:08

tried that as well

vivekiyer commented 10 years ago

From dan.matt...@gmail.com on February 21, 2013 00:29:21

Sorry for the lack of response, I've tried to reproduce the error without any success.

As much as it pains me to say "sorry, we can't help" that's where we land. The only remaining option I can think of is to talk to your Exchange administrator to have a look at the server logs to determine why it is regarded as a protocol error.