Deleting/updating won't work
I'm getting the next error when updating/deleting things, adding is working. ERROR: '--' is an unexpected token. The expected token is '>'. Line 81, position 5.
I enabled all Verbs on *.ashx And I don't use Windows logins.
How to fix?
TomV
· 1 |
|
Monday, June 28, 2010, 11:38:50 AM |
0
|
Please check that WebDav is not part of your site. Usually this is the issue. |
||||
|
0
|
WebDav was indeed enabled so we disabled it. But still the same error :( |
||||
|
0
|
Please send an emaill to support at countersoft dot com. We will remote in to see if we can solve the issue. |
||||
|
0
|
I am having a similar problem. I am using the API sample app with version 3.7.1. From the sample app, I did a get on an issue, change some text and clicked update. I get the same behavior in my own app when I try to update an issue. |
||||
|
0
|
Please make sure that you have enabled all verbs in IIS for the ASHX file handler for the Gemini site. |
||||
|
0
|
We just did a GotoMeeting with Tom and he's stuff is all OK! |
||||
|
0
|
Yes, and again, thank you very much The problem was that "server" hadn't enabled all verbs but the gemini-site did. So the server wouldn't pass them through to the gemini-part. |
||||
|
0
|
Hi, |
||||
|
0
|
It's probably because you have WebDav enabled on the site, remove it. |
||||
|
0
|
WebDav is marked as prohibited in Web Service Extensions on the server. Is that what you mean by "remove it" or is there something else? |
||||
|
0
|
Is it possible to use Fiddler (http://www.fiddler2.com/fiddler2/) to check the response from the server when you get this error? |
||||
|
0
|
It looks like a permission issue. We are using Windows authentication. I got my domain user added to the Administrators group on the server and it's working fine for me now. I obviously don't want to put all users in the Administrators group. Are there any additional permissions that users need to have in order to use the API to update issues? |
||||
|
0
|
Please try and give (everyone) permissions on the api folder only. |
||||
|
0
|
All users already had read, list and execute permissions on the api folder. I added Write permission for the user that needed it and it resolved the problem. Seems strange that a user would need to write to the api folder... but it works now and the change seems relatively harmless... I think... |
||||
|