CounterSoft User Forums

ran it, and got the following message in a pop-up window:

 

‘—‘ is an unexpected token.  The expected token is ‘>’.Line 81, position 5.

I presume that the URL is correct, can you please double check that?

---

Yes, the URL is correct. In fact, the user logged into Gemini via the web browser, and cut and pasted the URL.

Can you please try and add the following line:
serviceManager.UsersService.Credentials = System.Net.CredentialCache.DefaultCredentials;
After  the creation of the serviceManager (before the call to WhoAMI())

If this still fails please change it to:
serviceManager.UsersService.Credentials = new System.Net.NetworkCredential("USER", "PASSWORD");

and replace USER with the username (including domain) and the password for the user (windows password).

---

Both of those failed.

 

Just as an FYI, we installed Gemini desktop on another windows 7 machine, and are getting the same errors.

 

Is there some setting or permission that needs to be set that we are missing?

No need for any setting changes (in theory...).
Please send an email to support at countersoft dot com and we will schedule a remote session to see if we can spot anything.

---

We have done the email, and a couple of remote sessions, and still nothing. However, just to make things much more interesting, I have the following to report.

We have installed Gemini Desktop 3.6 on three other machines, 2 with Windows 7, one with Windows XP.

One of the Windows 7 machines is able to log into Gemini with no issues, the other Windows 7 and the XP machine can not log in at all except via the web.

The Windows 7 machine that can log in, is for a user who had been using Gemini Desktop with the previous version (3.5) prior to the upgrade, and then upgraded to 3.6 on her old machine.

None of the users who can't log in were using desktop or time tracker in the previous version.