Home Forums Discussions General Discussion Notes on installing V6.3.3

Well I felt like doing something a little wild and crazy this weekend, so I decided to upgrade to V6.3.3 from home, using Logmein. Yup, I really like to live on the edge. All went well, though I did later have to come in to restart one machine that shut down during the process. It took about an hour to do all 6 machines on our P2P network.

The install went smoothly, with a few minor hiccups.

1. Whether you enter via the ?client sign in? on the AC website, or from your version of AC itself (?click here to upgrade to the newest version?), you will be told (at the bottom of the upgrade page) ?do not upgrade from the link above?. But you do. The instructions regarding the database tuner are improved, but this part is circular. After entering your user name and password, just click the download button and follow the instructions from there; ignore the ?do not upgrade from here? message.
2. I got an assortment of messages ?Could not install correctly? and ?cannot install while other programs are running?, as well as a random error message or two. I simply clicked through them all, apparently without any significant problems.
3. I did not run any additional back-ups prior to the install. I figured our usual scheduled Friday after-work back-up would be sufficient.

I know some of this will appall the purists, but hey?it worked. I post this primarily to point out some things you can probably safely ignore. At least, I ignored them with no untoward effects seen yet.

They did change a few things with v6.3.3. Especially with the permissions on the AmazingCharts.mdf, AmazingCharts.ldf. They clear existing permissions and automatically add Everyone to the list. This can cause errors on a domain network. I'd imagine adding Everyone was to resolve connection issues for P2P users.

Okay, I've confirmed it with another practice too. AC's permissions were set perfectly before, after the upgrade, you get a miscellaneous error telling you to try 2 or 3 things like opening SQL Port 61067 or something, checking connection to the main.

For any other domain users out there. The way to get it working is to edit the permissions for the AmazingCharts.mdf/ldf, Meds.mdf/ldf, Codes.mdf,ldf

There are no secrets to success. It is the result of preparation, hard work, and learning from failure.

-----------------------------
MapleStory Mesos|WOW Gold|Runescape Gold

Well, then you should learn from this, because you are going to fail to remain on this board.

I turned down your application the first time. You may want to use a different username next time.

Bert cant you delete him? He is just spamming selling gold for role playing games.

I recently upgraded to v6.3.3, up to that point aevery was working fine. Now one client keeps getting error message referencing Port 61067 & SQL errors: 3 step suggested solution ending with cutting of firewalls. I attempted all solutions and clitent still cannot comunicate with main nor will it allow completion of upgrade.

I attempted to go into amamzingcharts.mdf as you had suggested but no access was allowed to that file.

I looked into the permissions for the firewall for the main which shows TCP & UDP allowed for any in both directions. I did not have any problems with the communication for this client until I did the most recent upgrade to v6.3.3. When I attempeted to ask AC tech support they said that it was my network problem, i.e. a personal problem to which they were not responsible despite the occurence only as a result of the upgrade and apparently others have had this same "personal" problem evidence by this thread.

Check the file permissions as Sandeep noted above, and then check to see if the user login from that machine is listed as a permitted user/login.

One easy way to check that is create a user account on that machine that has access elsewhere, then try that user from the troubled machine.

I believe they are right about the network issue. Your computers can't be remotely accessed. Nor can they run remote access software. Please email me when you see this.

Anyone seeing this error when checking a patient's med history?

"Unhandled exception has occurred in a component in your application. If you click Continue, the application will ignore this error and attempt to Continue. Attempted to read or write protected memory. This is often an indication that other memory is corrupt."

We just upgraded (last night) to 6.3.3 and we're seeing this error on 2 computers (out of 5 I've checked so far). Clicking continue just starts an endless loop with the error, and I have to do an End Task from the Task Manager to get out of it.

Will check with Guardian Support, but live chat is offline right now. Figured I'd throw it out here to see if anyone else has already seen and solved this issue. Thanks.

FYI

The answer is: turn off hardware acceleration.

For Eric, the networking issue was a result of Symantec being over zealous. I'd recommend Microsoft Security Essentials as a excellent free alternative for up to 10 users in a commercial environment. The best antivirus is safer browsing practices, i.e. using Firefox with noscript when you go to sketchy sites among other things. If you're extremely careful, open sketchy links in virtual machines.