cannot get past login screen!

[GoogleCodeExporter]

I have downloaded procurement 1.8.6, and whenever I try to login, I type in my 
info, hit login, the email/password fields become grey (so I cannot change 
them)... and then nothing happens. I have tried leaving it like this for up to 
half an hour and nothing changes. I have this same issue regardless of whether 
i type in my actual ID/password or just type in random characters for ID and 
password. I have also tried using the sessionID method of logging in and that 
does not work either, same issue.

I had this same issue a few weeks ago with the older version of Procurement as 
well. I am using Windows 7.

Please help! I want to explore and use this program but I can't even get off 
the ground.

Here is a picture of what I see when trying to log in, for reference:
http://i58.tinypic.com/zxmw4h.png

Original issue reported on code.google.com by gbor...@gmail.com on 10 Dec 2014 at 5:05

[GoogleCodeExporter]

Hmm, it seems odd that Procurement isn't even displaying "Authenticating 
<username>..."

Make sure you're running as administrator, and that a firewall or anti virus 
isn't blocking Procurement. I know a release or two ago Panda AV had an issue 
with Procurement, and Comodo blocks it by default.

If that doesn't work, you can also try updating .NET to 4.5 if it isn't already 
on 4.5

Original comment by stickymaddness on 12 Dec 2014 at 5:33

• Changed state: Accepted

[GoogleCodeExporter]

I had the exact same problem and running as administrator fixed the problem on 
Win 7.

Original comment by stupidsp...@gmail.com on 14 Dec 2014 at 1:37

[GoogleCodeExporter]

I have the same issue, running as admin also solved this.

Running on windows server 2012r2 x64.
Seems like its getting stuck on the creation of the folders if installed in 
protected directories, perhaps it needs some permissions changes on 
installation to Program Files directories? or a UAC prompt (dirty).

Original comment by Alexande...@gmail.com on 4 Jan 2015 at 8:27

[GoogleCodeExporter]

I had this too at first and it worked when run as admin. Also worked when run 
from a directory with write permissions.

A simple check whether the installation directory is writable, informing the 
user of the problem and exiting, would make it clear what the problem is and 
not confuse people.

Original comment by irfanadi...@gmail.com on 26 Feb 2015 at 10:11