The URL should match to the URL you are using in a browser.

When you say you are getting a 401.2 when is that?

Aer you using windows authentication? If so please make sure that you do not allow anonymous access to the Gemini site in IIS.

I have tried windows integrated authentication and I get the same result as when I don't.  The anonymous access is turned off to the gemini site.

The error that I am getting is in the subject of this note.  But the actual site is returning a 401.2 error page - which I can tell by using fidder.

Jim

When in Forms authentication try and allow anonymous access, does it work?
If not, please allow access to the API folder.

I have users logging on with windows authentication from various clients.  So I need to keep the windows auth alive.  However, I also need to log in to a gemini created account to the gemini api and access the gemini api.

I don't know what rights to set on the api folder - but I believe they are correct.  Instructions like 'give rights to api folder' are helpful, but I need more detail.  Like what kind of rights and which account to give them to.

I am using the test harness and it is not working.  However, about 1 times out of 10 it will connect to the api.

Using fiddler, I can see that the other 9 times out of 10 the api is returning a 401.2 error.  Also, a keepalive command is called against the api (outside of my control) and this command fails with 401.2 followed by a success 200.

I would like some help on this issue - how can we talk directly?

Jim

Are you saying that sometimes the test harness works? Can you explain which clients do work?
In the service manager, did you set windows authentication to true?

Please send an email to support at countersoft dot com if you feel that this is not helping.

I have set the windows auth flag to true and to false attempting this both ways.  It does not make a difference.

The test harness, will rarely connect successfully and give me a result to the whoamI method call.

The other 9 out of 10 times it will not.

I can run the harness, get a good response from whoami and then immediately run it again and get a failure.  No changes to the server and no changes to code.

I believe the problem is with servers settings of some kind.

After talking to you on the phone, I have attempted to set the site to forms authentication.  This does resolve the problem.  However, we are not able to use this as a solution due to the fact that we need to operate under windows authentication.

I will try installing a separate gemini site using forms auth but pointing to the same database and see what happens.

By the way,

The test harness works fine on some client machines, but not on others.

So there must be some setting that is different for one machine then it is for another.

We have found the issue with the service manager (not your configuration) and should release a fix this week with 3.6.4.