It sounds date related. Or at least related to something date related.

I'd like to hear from everyone in this post with the following info:

1. When did you first notice the problem?
2. What version of Windows are you using?
3. What version of Absolute are you using?
4. Have you recently installed any Windows updates or other software packages?
5. Was Absolute running when these packages were installed?

If your purchase date allows, try updating to at least version 3.00. 3.00 and above don't seem to have this problem at all. At least none reported.

For us, it started on Nov.15th. So far after re-installing 2.0, no problems.
Windows XP
Absolute version 2.0
Will get back to you on the last two questions...

Thanks...

[size=1][ November 18, 2005, 04:12 PM: Message edited by: rjburer ][/size]

1. When did you first notice the problem?
-Tuesday, Nov. 15
2. What version of Windows are you using?
-Windows XP SP2 and Windows 2000 SP4
3. What version of Absolute are you using?
-Version 2.12
4. Have you recently installed any Windows updates or other software packages?
-Yes, they happen automatically, and the last one on my system was Monday, Nov. 14. I uninstalled it but the problem persisted. The problem has gone away on 4 of the 5 systems after multiple reinstall attempts, but I don't know why.
5. Was Absolute running when these packages were installed?
-Some systems probably yes, some no.

I cannot try 3.x because of purchase date. I also cannot get my license to show up online.

Thanks,

Ray Colbert
Boys Town IT

Ray,

The only license in the system from boystown was from 'fullerj'. Was that yours?

Brian

Yes, I remember now that you say that, John Fuller ended up purchasing the license.

On the 5th system that had this problem, I just upgraded it to 2.13 and the problem went away. Again, the problem has gone away on the other 4 systems and they are 2.12, and I'm not sure why it went away. I did notice on the other systems that during the installation that happened to fix the problem, the install program said that it was replacing an older version, even though it was going from 2.12 to 2.12. When the installation did not fix the problem, it didn't give that message.

Ray

Our users have desktop/laptops with Windows XP Professional, version 2002 with SP1

Can we also upgrade to 3.0 from our current 2.0...?? Would there be a cost associated with this upgrade...?

Thanks ..
Rudy

[size=1][ November 21, 2005, 03:00 PM: Message edited by: rjburer ][/size]

FYI -
I just had to re-install the software a second time for a user. It was fine for 4 business days (11/17).

Thanks..

Rudy

I have the same problem: Yesterday I could work with the software (I think it was version 2.13), but when I tried to open a new window I suddenly got the registry-missing message. Now it don`t likes to work anymore.

I have bought the license in October 2001 - so my license doesn't work with version 3...

Also version 3 is not able to handle my key with passphrase (this worked in version 2 and seems to be fixed in 3.11)

So I think I have two possibilites: Update to version 4 for about 19.95 (how long will this version work?) or use another software 🙁

Or do you have another idea?
Frank

We have just had 2 systems have the problem reoccur.

Ray

I'm also having this problem, and 2.13 is the last version I'm allowed to use. I don't think your procedure to update the license will work, because my license is old.

The problem seems to be either date related, or related to some phone-home property that your software may have.

I had this problem earlier when this message was posted, but assumed it was something else causing problems.. Now, today, the same thing happens again.

Reinstalling the software seems to fix it but this is quite far from an acceptable solution, considering this behaviour is new.

Running Absolute Telnet 2.13, Win XP SP2 + all patches. No idea if Abs Telnet was up while patched. I would say I first noticed this, maybe, months ago.

[size=1][ November 30, 2005, 10:53 AM: Message edited by: mjstumpf ][/size]

Now the rest of our systems have had the error return. Reinstalling 2.13 appears to fix it for a short time, but the error comes back.

Is there any news on a solution?

Ray

My best guess, given how many customers are experiencing this is that some windows update is interfering. Some have reported that reinstalling 2.13 fixes the problem, while others have it reoccur even after reinstalling. The only thing that seems to work is to upgrade to at least 3.0.

Brian

Error just popped up again. Seems to be time related; everyone is having the same problem at the same time. My Abs Telnet instances were up and running fine, but trying to invoke new ones causes problems.

I am having this same issue (suddenly) on one laptop. The other is not experiencing any issues. You get the same 'Registry' error as described in previous posts.

A couple of observations;
1. Auto-upgrade has been disabled on this system right after install, so no OS upgrades have happened behind my back.
2. No new software was recently added.
3. No other app complains about the registry being corrupted or changed.
4. I used a commercial registry analysis tool to check the registry. To do this, I totally removed all parts of Absolute T, cleaned out any further registry entries for it. Ran the scanner with positive results. Re-installed AT, re-ran the scan, and was , as others have noted, able to launch 1 session. After attempting to launch again, the error returned. Subsiquent checking of the registry detected NO changes or corruptions.

Without a more detailed scan to actually check the VALUES I am confident that the registry itself is not being corrupted. Further, based on this , it appears that the AT software itself is probably modifying the values, since it always will launch 1 time without issue, but the second time dies.

This version is 1.84. An older one to be sure, but the issue seems core to the software and not the OS.

Please dont get me wrong; the software has worked brilliantly for YEARS without issue; certainly we got our value out of it for the price. And paying for the upgrade is not what I consider out of line at this point. Brian, I hope you can pursue why this happened and ensure that vs. 3.x is not going to suffer the same fate.

Cheers...

I can confirm this same problem with version 184 and 213, both with Windows 2000 and Windows XP. I'm sure it's been more than a year since my purchase. Any chance at a patch?