Home Forums Discussions Problems V4 Installations Woes.

I understand that Guardian Support/Techs are pretty swamped right now, I thought I'd try my luck here.

I decided to go ahead and upgrade to v4 over the weekend, and the process went smoothly on my 2003 Server. When I came in the office on Sun to install on our clients, it was unable to find the database on the first client I tried. I realized that the default install for the SQL databases was 'C:' (local) instead of where we always keep our AC stuff 'S:' (shared).

Today I've uninstalled v4 from the server, and attempted to reinstall it (numerous times). The installer will not even get a minute into unpacking files before it hits me with errors. It simply refuses to install on the 'S' shared drive, which is where it HAS to be to function on our network.

It gives me 'error 1926. Could not set file security for file.' Its asking me to verify sufficient privileges to modify security permissions for the file. I am the system admin, and I'm logging in as such on the server. It then rolls back the progress and kicks me out of the installer.

I am beyond frustration at this point, and we have a waiting room FULL of patients with no EMR. Any help would be appreciated.

Install your prior version from backup ASAP and try again next weekend! Use your paper based process backup to complete your notes until system is up again.

Whenever you perform a major upgrade like this, you need to set a "point of no return", say 8:00pm the night before, for yourself so you can get restore your old version back to where you were by business start on Monday. The time for this depends on how long the restore process takes.

If you don't have a backup available, just use the paper based method and stack them for re-entry until you can get your system back where it was. Hopefully, the installer didn't change your existing S drive database files.

yeah, i'm working on reinstalling the last version prior to 4. I'm confused as to where other users are installing the program though. I'm sure most people are using a server, and the program itself has always defaulted into the C drive. From that point you can point it to wherever the databases are, but apparently v4 doesn't work that way.

wow.

ok so going backwards doesn't appear to be working, since the .mdb database files have been converted for use in V4's SQL server. This means I am unable to establish a relationship with prior versions of AC, nor am I able to run the restore function to at least get through today. Essentially I'm stuck between versions and I still can't get through to support. Emailed, called, and live chatted.

V4 does not like NAS units for the databases, they need to be on the server. I would reinstall on the server and search for the old V3 files to import.

I have the same issue. I installed it on our main computer of our Peer to Peer network and it seemed to work fine. That is until I logged in and all my data was gone. I too use an S: Drive to house my database for us to share on our network. I reverted back to V 3.7 so I could get some work done.

Anyone have a suggestion?

Also, what are we going to back up? I have been used to making a backup of the imported folder and the 6 .mdb files. How is everyone else backing up their data on V4?

Version 4 has a built in backup utility - it compresses all files including the imported items in a single file and saves it in the ac folder, offsite if you subscribe and on any other drive you want. Great because you can save it to desktop and write to DVD, save to flash drive, NAS or whatever.

Thanks Steven.

How do I access the Backup Utility? I don't see it as an option in the menus and the help section talks about it, but doesn't tell you how to run it.

Go to Amazing Charts programs under your start menu - there should be Amazing Utilities,Amazing Charts, Amazing Synchronizer and Amazing Backup - in addition there is what is called the Amazing Automator under backup - you can set it up to do auto backups every day.

I'm sorry for the difficulties getting your exisiting system up and running. Hopefully we've been able to get back to you - if not, we certainly will.

Here is an update on V4, and the issues we've found. First, though - Amazing Charts not only backs up your exising data before updating, it also doesn't delete your old .mdb databases, even if it thinks it updated successfully. They are there, and we can find them, so if your issue isn't solved yet - don't panic and don't try to revert or roll back until we are in contact.

Here is an update on where we are at with the V4 release:

* V4 alpha (4.0.36) was released on 9/25/08
* V4 beta (4.0.58) was released 2/9/09
* V4 (4.0.58) was officially released on 2/19 (Thu) at 1PM along with the Update Alert Notice (UAN). The UAN is the alert that pops up every 15 days saying if the version being used is up to date, or if there is a newer version available.
* Because of a significant call volume increase and a delay getting back to users needing help, UAN was turned OFF on 2/23 (Mon) around 6PM (although V4 is still officially released - we just aren't alerting people that it is until we can address the issues that are making some installations tricky).

The most common issues we are finding are:
* People installing AC to a different location than their existing version. For example installing AC V4 to Drive C when it is actually elsewhere - making it appear that imported items are now gone (they aren't- they just aren't in the correct directory and need to be manually moved by us).
* Many different network configurations, a good number are not the expected set up of AC (which is at C:\Program Files\Amazing Charts on the main computer).
* People not logged in as admin during installation and migration.
* Migration difficulties with some users' exisiting data - some users have gotten various errors and can't proceed with migration. Once migration is denied they aren't sure how to go back and start the migration process again, or roll back to a working version - so they are stuck and can't use AC until they can reach us. (We are looking at the rare database (less than 5% of migrations) that aren't automatically migrating.
* Permission issues with SBS 2003/2008

Thus, we are working now to make the migration process smoother - though as discussed elsewhere, most folks are able to migrate without issue, and are much happier with V4. For now, if you are considering updating, I'd wait a bit as we determine how best to handle the increased need for help in case you are one of the folks who run into trouble.

Jon

Jon,

Stick by your stuff. You are providing a valuable service. I just wish soome of the bickering would die down. Any big endeavor worth it's while will not be without bumps. Let's everybody realize it is only temporary and get a glimpse again of the big picture.

Many thanks!

I loaded 4.0 Sunday and everything went great until I realized I had loaded it on the "C" drive rather than "S". It went down hill from there. Monday I did manage to get through to AC and had Claire from IT on the phone for over 2 hours. Finally just out of frustration she deleted 4.0, found the 3.7 program loader and got it back and running. Then just for kicks, she reloaded 4.0 and voila, it loaded correctly on the S drive. I got all my local machines except one to find it and work correctly. My one laptop keeps sending me messages that says that Microsoft.NET has to close down. I tried updating it with service pack 1 but it won't load either. Any ideas? I hate to bother the IT folks again if this is a simple fix. Thanks Dave Athens, OH

I installed 4.0 Sunday on my Dell server SC 1430 running MS windows 2003. I have set up 3 partitions in my hard drive: c(OS), d(data), and b (backup). The process went smoothly but took 4 hours (big database). Afterwards I installed the clients but could not find the database, plus I could not find the imports on the server. I realized AC had installed the databases to C, whereas I had it set up to go to d:\amazingcharts. I did not know which are the databases as they now have different extensions. But, I figured that it must be the ones that have a large files. I moved these:
Amazingchart.xml
amazingchart.mdf,
codes.mdf,
Meds.mdf,
amazingchart.ldf,
codes.ldf, and
meds.ldf
to my D:\amazingcharts folder, reset the path in the server and clients, and so far everything is moving fine. I also now have my imports back. However, I have noted that I am missing many cpt codes. I wonder if I missed a database. Anyone else having the same problem? Is there another file / folder that should be moved over the the D:\amazingcharts folder?

Thanks in advance

Gerardo Carcamo, MD

So am I to understand that there are currently issues with SBS 2003 installation and it is best to wait it out? Thank you in advance.

"* Permission issues with SBS 2003/2008"

Christy, I do not expect your quote implies issues with SBS, but implies issues with the given practices SBS permissions. I have installed v.4 beta and have had no problems. Only thing, I am watching the discussion of missing CPT codes.

I had no issues with the installation, just the codes. It did take me a while to figure out the database thing and I hope I got it right. Seems to be working ok. It is fast! The office staff loves it.

Not an unexpected consequence of the jump to hyperspace! We were lucky in our timing, we made the jump before the rush, support was not overwhelmed and we did it on a Friday during business hours, with a weekend to tinker. Still needed a few minutes on the following Wednesday to resolve a few things with our own network and finding the printers. My 2 cents worth, if you haven't made the jump yet be patient, this will be like a snake swallowing an egg. It will take a while for support to choke it all down, but it will get done and it is TRULY worth it. I didn't realize how much I would love the color coded messages. For me the Red must be done before the next patient is seen, Blue are saved for lunch or the end of the day.
This is painfully obvious, but I am so ignorant, maybe it will help others. When you do make the transition, RUN YOUR BACKUPS the night before, (saves time) and do the download before hand. On our internet connection it took hours to down load version 4. It installs quickly once you have it, but it could be downloaded at night weeks before! Just a thought.
Be patient, it is worth it.