FCReid

I found a solution to this. Logon to Stardock and go to your Downloads area. On products that you've purchased, if you see a "Manage" link to the immediate left of the Download button, click on that. This lists all product activations. Locate any with invalid information and click to Deactivate. After I removed a copy old copies of Fences I'd originally purchased separately from the Object Desktop subscription, the Object Desktop Manager immediately started to login properly.

Product key retrieval works perfectly and is pushed to my email address instantaneously. Other stardock.com pages also work fine. To reiterate, I'm pretty sure I'm hitting the authentication server, as when I deliberately bork my password, it recognizes the password is invalid. When I put in the correct password (which authenticates fine on stardock.com), it throws the error about connection problems. Whatever mechanism to parlay credentials to the ODM app must be different from the website a

BTW, I suspect I am reaching the server, because when I use an intentionally invalid password, I get an incorrect password error. When I use my known password, I get the error about a problem connecting mentioned above.

This remains unresolved for me. I've upgraded to the new ODM Beta with same results: "Login failed: There is currently a problem connecting to our servers. Please check your internet connection or try again later." Haven't also tried from a different source IP network and using a web proxy. Same results. I can find nothing logged locally that provides any clue what's failing.

Understand... one of the nicer ODM features is that it checks for product updates, which is something not easily done via the website. Would be great if we could get it fixed. :)

This is the error I get when attempting to authenticate.

Is there an issue with the authentication servers? My Object Desktop Manager hasn't been able to connect since last night. Web login works fine. Thanks!

I am seeing some unusual activity between the browser and www.stardock.com as shown in the capture below. That "ngg.js" is associated with an SQL injection bug and is referring to all kinds of unsavory places. Can the Stardock web folks take a look at this to see if their site has been compromised in some way? 000 : 47 45 54 20 2F 6E 67 67 2E 6A 73 20 48 54 54 50 GET /ngg.js HTTP 010 : 2F 31 2E 30 0D 0A 41 63 63 65 70 74 3A 20 2A 2F&