All kinds of problems.
Saw you had kindly fixed the 'Follow Section' and added 'Duplicate.' Thank you!
But the packaged on windows failed on install twice, said it was 'rolling back,' but when I started HN2 it said I must authorize. Tried to authorize and it states I've reached maximum installs.
Help!
Prado
Please contact support. This is not a bug. "All kinds of problems" can be resolved in a second.
Suptertonic ... "all kinds of problems" referred to the cummulative frustrations of the day with HN2 culminating in the apparent failure of the install.
The bug, in my mind, was the fact that the install update failed twice (and each time gave two error messages stating the install was unsuccessful) in the same manner and I still don't know why? Maybe this is a 'meta bug?' Anyway, I appreciated the rapid support response. The authorization window states it is 2.6.2 ... so presumably all is in order despite those error messages.
As a final relatively on topic issue ... while the problems in the installation package are not because of me, I forget if one is required to deactivate before upgrading. If this is the case and I have needlessly wasted your time, I apologize, but I do have a suggestion.
Many programs have 'warnings' or 'advisements' on the install with a little screen to, for an example, tell you not to plug in your USB device until after the driver is installed, etc.
Is an upgrade supposed to upgrade without first deactivating?
If deactivation is required, how about a screen in the installer package warning to stop upgrade until deactivation is complete?
Prado
Yes, deactivation is not required.
The error message is related to Windows MSI Installer. Maybe something was not updated correctly with your Windows registry. Or something fundamental has changed with your Windows installation. This is out of our control.
If you check your windows event viewer either the application log or the system log should show the failure with the msi installer or msiexec. This might give you an error code that will help diagnose the prbem.....hopefully.
I remember that @Prado he uses Windows XP ..old
In xp I think you can get to the event viewer by right clicking my computer and selecting manage. Or in the control panel if it isn't on the menu. Event viewer will be there just a matter of finding it. Sorry all of this is from my poor memory.
Who is old? .... ;)
Thanks blacksun for trying to help. There are no error messages that mirror the times I tried to install and my clock is properly set. The error messages appeared to come from the installation package, not the system. I've installed other things recently without issues.
You're right. R Click 'My Computer' icon and select 'Manage.'
Since no one else is reporting any issues ... (or am I the only one left installing on XP?), I must assume it is a local issue.
Prado
On macs, you just install on top of old program. no issues, nothing special to do. don't see why PC's would be any difference. I sometimes do updates with program running and there is no issue.. I believe ILOK has to be plugged in to do an update, but Andre and Supertonic can give the official correct response.
markstyles
What, have you been in a storm-induced time warp, or something, Mark? ;)
I got the word that it is supposed to install directly on an upgrade from 'Der Honchos.'
Prado
On Windows every update has its own GUID, that is some worldwide unique code that looks like a huge serial number. If this GUID is already registered, the installer refuses to update again. Then you need to uninstall first.
Are you meaning the GUID is "already registered" as part of the HN2 authorization or somewhere else?
I have not encountered other difficulties installing.
And do you mean if I had this problem I need to uninstall HN2 prior to upgrading, not just deactivate it?
Thank you.
Prado
Registered means the windows registry written to by the MSI installer. All Microsoft tools, Cognitone not involved.
If this happens (rarely) an uninstall and reinstall of HN2 may help.
You never need to deactivate before an update.
Thank you for clarifying.
The reason I was thinking about deactivating before upgrades with this problem is that if I did have it reoccur, then I wouldn't have to request a reset of the installs if anything went wrong.
Sort of my own 'fall back' security plan.
Prado