Activation error in vista

Hi

Installed Objectdock 1.59 in the vista workgroup administrator account. When vista is connected to domain and objeckdock is run with a domain based account it indicates that it was activated on another computer, please re-activate now.
Checked permissions on program folder and gave domain account full rights.
The domain account has full local admin rights on vista PC and when I log back in using local pc admin account, objectdock works correctly.

Have never struck this before.

any suggestions ?

cheers
Murray

objectdock

Locked Post

Advanced Search

Watch this post

Do not email me updates for this post Email me updates for this post

Successfully updated karma reason!

nzvoyager: Try deleting the sig.bin file out of the (default) C:\Program Files\Stardock\ObjectDock directory and launching ObjectDock. When you open it again, it should launch the activation dialog and prompt for your email/serial#. After you enter this information, does it work at this point?

If it works, copy the sig.bin file out of the C:\Program Files\Stardock\ObjectDock directory for backup purposes. (Just copy this back in there again in the future if you encounter a problem)

If it doesn't work, close out of the dialog and follow -this guide- to activate by email. Should that be successful, you will receive an automatic response with your sig.bin (within a sig.zip) and instructions. Should that fail, you will receive a response indicating this, and your activation request will be forwarded to a support rep, so we may determine what the problem might be.

Hoping for the first outcome

-Mike
[Stardock Support]

Successfully updated karma reason!

Hi

Yes as you suggested it was possible to reactivate and now it works on the domain account, but now I have the same problem with local account.
However in XP I have never had to reactivate when going from a local install account to a domain account.

I did note that there was a permissions problem when trying to access OD, had to give admin privileges for the stardock directory before OD would run properly. It of course then asked to be reactivated.

It may be due to UAC that the problem is occurring, it’s just a puzzling nuisance.

Successfully updated karma reason!