Home Forums Discussions Coding and Billing install of V6.09 keeps giving registry error

upgrading to 6.09 from 5.029;
keep getting the "run as administrator" response due to registry error; can' launch program
this has not solved the problem;
any ideas? ran into this with SQL SVR issue and replaced my server, now having same problem on workstation;
Registry Mechanic has repaired all errors;
reinstall has not solved the problem;
reboot has not solved the problem either

http://amazingcharts.com/support/i-want-to-help-myself/most-common-issues/

Try going through these error messages. While some look daunting, they really aren't. It's likely due to an unregistered .dll, which is easy to fix if you know which .dll it is.

You could try running some type of registry cleaner such as Registry Mechanic or CCCleaner.

What operating system is the main computer?

JamesNT

I can't recall, but if you run the installer again, since it is already installed, does it give you the option to repair the program?

OS is Win XP SP3;
ran Registry Mechanic but it didn't solve the error;
tried to uninstall V6 to reactivate 5.029, and the AC\AC.mdf file has exclusive access assigned, and Remove Program will not run;
kind of odd that the database tuner did run even though V6.09 was not active, but couldn't upload the db to server because my notebook is not operational with 6.09;
now at a cerebral endpoint; have my 5.029 backup, can't convert to 6.09;
it would be more logical to have database tuner on the server upload 5.029 and import the modified file directly into 6.09;
I know it has to be simple - can't be this labrythine?

also ran the Repair option; same error comes up "run as administrator due to registry error"

I have seen the dll registration conflict on an earlier version of AC, but I can't identify it with this install

Are you logged on as a system Administrator?

JamesNT

clee (Is that your name?),

I feel your pain. I had install problems with both 5.0.29 and 6.0.9. With 6 I got to exactly what you are describing, same error message, could not go back or forward. And yes, I was running as the administrator. It resulting in a lot of cursing and hair pulling. Eventually, I solved it. Here are a couple of things I learned. I don't know if they will help, but I offer them for you to try.

In the main AC folder there is a batch utility called registeritall. Double click to run it, and it will unregister, then re-register all the DLLs. If this is the problem as Bert suggests, it may help.

I had used an uninstaller that removed the AC data file,registry entries, and other files, and a registry cleaner at various points, and it turned out that they created problems by removing things that AC needed to install and run properly. If you can reverse your registry cleaning, it may restore the needed entries. It is nebulous in my mind now(as I have tried to forget the frustration),but it seems to me that with V6 it was a file that had .pf suffix (for prefetch) in it. After I restored that from my recycle bin, I was back in business. I really don't know what that is, but it did solve the problem, and allowed the install to proceed. Maybe this will mean something to the more technically savvy.

Forget about 6.0.9, go to 6.0.10, even thought it is technically a beta, it has less problems. Yes, it still has bugs, but nothing that is unmanageable in my use of it. It installed without any problems.

Good luck, don't give up.

Ok, good news: I got it installed on my server and all workstations, and my portable notebook;

What I learned:

do not uninstall SQL SVR and try to reinstall - this is how I lost program function on my previous server, and this is what AC support told me to do; what I did was repair the install on the server - not sure what file was written over, but it worked

importing the database from 5.029 into 6.09 is mysterious if you don't read the directions that the support site gives you - gotta follow the instructions; the step I overlooked was the Backup Restore Utility (the Lifesaver Ring icon) in the AC directory;
run that off the data backup (*.enc) just like the instructions say to; then run the Database Tuner; it was that simple to import the database

the other thing I did was log in as administrator (not as a power user with administrator settings); this seemed to make everything happen on day 4 of my learning process (gee whiz ...)

I will post next week on my success with Medisoft 17 and AC 6.09 interfacing using X-Link

Thank you to everyone - the AC forum support is great and we collectively are a terrific resource for each other

Donna, thanks for the heads-up on 6.0.10; haven't got there yet;
will post my luck with it when I get there