Activation keeps coming up...

try this thread. https://forums.stardock.com/311958

Thanks for the link, but I did't find any help there  :NOTSURE: 

In Impulse try right clicking on the serial number next to Icon Packager and removing it. Then replace it with your Object Desktop serial number. After that restart Impulse and let us know if the problem persists.

I'm having the same prob... that's interesting...

Hello SeaBass:
Still a no go. Here's another detail regarding my problem with IP. When I try to change an individual icon, say the DVD-RAM icon, through the menu 'properties-icon-change icon', it will allow me to select an icon. However, when I try to apply the change IP prompts me to activate the program. When I enter the info, it activates and allows the change BUT when I want to run the IP program on its own through Control Panel or from the Startup menu, it prompts activation again. When I enter the e-mail/serial it activates BUT then I can't change an individual icon without being prompted to activate again. Thus continues the vicious cycle again.
 (:( 

Goose

Just out of curiosity (since I am having a hard time getting this issue to occur on my end) can you go to the Icon Packager folder and right click on the Icon Explorer.exe and then click run as administrator? Then when it asks for activation just do the normal activation. Restart your machine and let me know if the same thing happens.

Ok, it happened to me. I reached the maximum activations   
So I couldn't do what you asked me. However, here's another detail I discovered. The IP serial in Impulse is my old IP serial (which the activation would not accept) and I couldn't change in Impulse. Also, FYI my Stardock Central shows that I have two versions of IP. IP4 and just plain IP but both show version 4.00.165
Anyway, I'm stuck. Can someone get me out of this maximum activation thing? and SeaBass if you have any other suggestions I am very open to what you might have for me?

Goose

Instead of your Icon Packager serial number right click on the registration in Impulse for the software and input your Object Desktop serial number. That should clear the issue for you.

I have also reset your activation count so you can.

Let me know if you have further troubles.

Hello SeaBass:
I tried your suggestion. Impulse says that my registration (OD)is invalid.
Goose

Goose that isn't what I wanted to hear. Now post here with good info please.....

Just kidding (kinda). Ok well to take this further we need to talk with some of your account info and that isn't possible in the forums. Please contact me at support@stardock.com and link this thread there. I will be happy to help!

Ok. Done
Thanks,

Goose

that does not work,. i've been having this issue since .165 came out. it was the last update that caused this issue. stardock needs to put out a new fix..

There is a new update for IconPackager in Impulse that should clear up this issue.

Hello SeaBass:
In case you are thinking the update was the solution... (:(  it twasn't. Any other ideas?

Goose

I'm not sure why I never checked on this but have you tried a simple uninstall > restart > reinstall> restart again before running the program?

Try that out and if you still have the same trouble THEN try replacing the serial numbers again. I intend to beat the solution out of your machine if I have to.

Thanks. I'll give it a try. (You're right I didn't think of that either   , although it's not my favorite thing to do)

I'm off to beat my compu...
Goose

SeaBass:

I uninstalled, removed the old registration for IP, then downloaded and installed IP4. All looked well. Loaded and ran without a hitch...until I tried to change one icon (through Explorer-Properties-Icon-Change Icon...etc, and I got this: Windows cannot find 'C:\Documents and Settings \[...]\IconPackager\Activate.exe'. Make sure you typed the name correctly, and then try again. To search for a file, click the Start button, and then click Search.

Dooooh!

???

Goose

That's actually ok. It's ok in the sense that we did know about that problem and we are already working on it. Since the new release of Icon Packager 4 there were about 3 bugs that got out and I am happy to say we knocked out two of them and that one you have there is the third. Just give our developers some more time and the update will be made available after testing through Impluse as soon as possible.

Hello SeaBass:
Just a quick question, was this recent update suppose to fix my problem or should I expect another update? Yes, BTW I'm still with this problem.

THX
Goose

I received word that the developers handed down a new .dll file as a fix for the current troubles with IP4. This is in testing right now and we hope to publish it as soon as we are able. This, of course, is provided that it comes through testing as a fully functional fix. We won't publish a fix that mostly works. There is no time line for this beyond ASAP.

I had a similar prob.

Try clicking on the EDIT REGTISTRATIONS button in the top right corner of the impulse browser.

Then resubmit the current registration codes for Object Desktop.

Hope this helps.

That solution often works for many people. This effect also happens when you reset your XML data.

You have to right click on the serial number and remove the registration to replace it with Object Desktop serial number or allow Impulse to do it for you when you log in again.

Thanks for the suggestions guys. HOWEVER, it will not accept the serial change. The weird thing is that my IP serial is the IP-17xxxxxxxx. When I try to set up a new registration for IP4 with the OD serial I get the "The serial numbers you have entered is not recognized by Impulse..." (ref. 2)

Strange thing too is that it does it with IP-17xxxxxxxx serial as well.

I'm still patient though. Eagerly waiting for the special DLL   

Goose

same problem here -I am OD registered user. Not using impulse.I need to reactivate every time I run the app.

Ruben

This issue has existed since the release of IP4, and the thing that surprises me the most is that the issue still exists at all.

In my case I reported it 20 may, still have the issue, and in 14 days it's my 2 month anniversary with it.