Registry Key Error

[RuralWeb]

Not seen this one before. I have just recovered from a complete crash of V8 due to a potential clients error - "Oh yes the snapshot did say it had 182 errors but I didnt think it was important"

Anyway I had to reinstall V8 which went OK - now however when I open a site it says that the Registry key is not compatable with the new version of V8 also when I do a snapshot of the site I get an error for every other site I have licenced eg

(File ExportSite.cpp, Line 1637) - Registry error 2, key Software\Actinic\Catalog8\Sites\Sanderson Dixon\Catalog - The system cannot find the file specified.

This is repeated 40 times, one for each site I am working on.

[jont]

<cue>Twilight Zone theme tune </cue>

Had the same exact error last night. I licensed a new site with the exact same name as was shown in the error and that resolved subsequent snapshots in other sites I was working on.

The site causing the error was a temp site used for testing when Actinic went belly up with a sitemap function I was testing and then refused to open - had to launch from the command prompt into another site. I deleted the site manually in explorer and then received the errors. Re-instating the site name has sorted.

HTH

[RuralWeb]

SPOOKY Im working through relicencing all the sites so hopefully that will sort it.

[RuralWeb]

OK - once all the sites are relicenced the error vanishes - how odd

[jont]

Aye - I thought it strange how one site was affecting the backup of another... another Actinic foible to add to the "fed up" thread

Maybe this is associated with my long-term wish list of Actinic remembering the last snapshot done rather than being site specific in MultiSite / Developer?

[TraceyG]

Hi Malcolm,

Can you tell me what you did after you re-installed to get all your sites back in (ie license new sites and then import snapshots or license new sites and copy the site folders in)?



Hi Jont,

Did you delete the site from 'File | Sites'? If not, then you won't have deleted the site from the registry.

[RuralWeb]

Can you tell me what you did after you re-installed to get all your sites back in (ie license new sites and then import snapshots or license new sites and copy the site folders in)?

My brain is going "Wibbbbbble" at the moment so I dont remember what I did

But I can tell you that a similar thing happened today with a design snapshot - once imported it would not import again due to registry errors.

AND when I upgraded to 8.5 I lost all my sites and had to licence new ones then import a snapshot to get them back after the 8.5 patch killed my V8.

Ive not had a good day really

[chris ashdown]

AND when I upgraded to 8.5 I lost all my sites and had to licence new ones then import a snapshot to get them back after the 8.5 patch killed my V8.

Thanks Malcolm, Maybe I will wait a bit longer before I update to 8.5

[BrianHill]

This is ridiculous, if V8 were an animal it would have been put to sleep by now. Why are they releasing patches that then immediately need a fix.

We have been waiting patiently for the Epos Link (Sept 06 was the intended date) as we stupidly invested just short of 10k on an Actinic Epos system with a view to linking to V8. There is no way on earth that we are going to become Actinic's crash test dummy on that one when they can't seem to get anything right. Anybody know any DECENT Epos software that will link to a website.

[RuralWeb]

I will wait a bit longer before I update to 8.5

The problems I had seem to linked to sites that use an external design. Others that have upgraded without external designs seem to be having no problems.

If you have two PCs it would be worth loading up your sites and seeing how it goes as a test.

[RuralWeb]

Why are they releasing patches that then immediately need a fix.

They are not - as I said above if your site is standard Actinic then all goes well. The problem that I and others are having relate to registered designs with DW - this is likely only to affect website designers who will have the skills to work round any problem as I did yesterday. This was an area that has been enhanced in 8.5 so things can only get better.

All my sites are now working Ok as are everyone elses that has posted upgrade results.

[BrianHill]

Glad you can be so certain that a fix won't be needed on 8.5 what odds will you give me on that?

[RuralWeb]

Glad you can be so certain that a fix won't be needed on 8.5

Im not saying that - all Im saying is that the upgrade problems I had relate to a specific part of V8. What software does not have fixes - take Vista as an example!

Actinic are bombarded with user requests most days and are IMO one of the few companies that listen to thier customers and so upgrade thier software regularly. people do not have to upgrade - there are V4 shops still working well.

[jont]

Hi Jont,

Did you delete the site from 'File | Sites'? If not, then you won't have deleted the site from the registry.

Hi Tracey,

I recall the error started as follows:

1. Actinic died whilst I was working on site1 (test site) and refused to launch from the usual desktop icon

2. I launched Actinic via CMD into site2 - a live site

3. I removed the site1 in File | Sites inside Actinic

4. Snapshotting site2 caused the error Malcolm posted

5. I deleted the remnants of site1 folder using Explorer but still received the error when snapshotting

6. I licensed a new site with the exact same name as the error site and backup was then allowed

I have not dare remove the new temp site in case it dies again.

As an aside - it may be worth adding a "recover" batch routine to run from the command prompt as a standard install. This problem has cropped up several times and I wager the vast majority of users have never used DOS to launch programs and not being able to launch via Windows is a daunting prospect if you are unable to get to your site.

[RuralWeb]

I recall the error

Glad you did