Home Forums Discussions IT, Networking, PCs and more Beta install 11.2

This was my experience with the beta install for 11.2. Maybe I am missing something. I know there was something about passwords with the SQL install or the latest version. But, AC sent me the beta versions. So, I assumed I could install it. No one has been able to install it yet at least on my server. I know that there are beta testers out there. AC support couldn't. BUT THAT HAD SOMETHING TO DO WITH ANOHTER INSTANCE ON SQL AND THEY DIDN'T WANT TO DELETE THAT. Understandable. I knew what it was so I uninstalled it. I tried to install it about six weeks ago, but it ended with an error message I couldn't get by so I went back to the checkpoint on the server. (Thanks God for checkpoints, because I don't know if it would have been able to roll back). It has been a while, but I thought that installer would change SQL.

So flash forward to today. (Last night I installed SQL Server 2016 Express so I figured I would try it again) So, my usual routine: I have a list of these steps I check off because I tend to forget one, especially the checkpoints.

1. Do all the updates on the server
2. Do a backup of the VMs
3. Do the AC backup if needed
4. Set my checkpoints on the VM.
5. Start the install

The installer immediately wanted a reboot. I guess that is just automatic because I had just reboot after the updates. It went fairly smoothly -- one error message that it ignored. Thirty minutes in, I get the error message something to the effect of: The install cannot continue as it doesn't know the sa username. OMG. Really? I thought there was an option to install this yourself. The installer could have the sa username hard coded, but each practice has a unique sa username I believe. So, if that is the case, then AC would have to install every one. Because they aren't going to give you the sa username to SQL.

So, I selected OK, and it started to roll back. Then it said finished. Awfully quick rollback. I was completely confused. It stated it was 11.1.4 which is what I started with. It would open but only after the error we have all seen at some point, "can't find windows" (or something to that effect). But you can click through it. Of course, that part of opening AC is annoying and it can be fixed by either starting a service that is not started or restarting one. But, the service was missing. I believe two were. My eyes start to water when looking at all the services in services.msc.

So, I had to make a decision. Go with 11.1.4 working with that error and talking to support about the service(s) or reverting to the checkpoint. A checkpoint on a VM is pretty solid, but this would be the fourth time I have trusted going back to a checkpoint after trying to install AC. I remember Windows Restore. That one was maybe 70/30. But, I decided to go back, and it was as it was before I started the install.

To be fair, maybe I wasn't supposed to install it on my own. With all of this install by yourself but you need passwords so AC has to do it, but if AC does it, you have to pay a certain amount of money and supposedly you have to upgrade SQL Server first which I did, I am so confused I have no idea. Run on sentence intended. It seems you could just run the installer, and it would upgrade everything flawlessly. But, going through the SQL upgrade, it would seem the installer would really have to be on top of things to go through the steps. I have no idea.

I suppose I will ask James or my friend who works with SQL.

I don't mean this to be a critical post, I just thought it would be helpful for everyone including support. But, I am simply staying with v11.1.4 which is currently the official release but using SQL Server 2016 Express, which I think keeps me hidden from the HIPAA police.

I will be installing v11.2 over the weekend. I will let you know how it goes.

Well, how did it go?

Not good. I am just going to let AC install it.

Yuck, if you are having problems then that is not a good sign! Is this still considered the Beta?

Yes, it is. There are people beta testing it, so I guess some were able to install it. I think it is the perfect storm of needing the SQL Server 2016 Express upgrade and a new version install. However, I believe due to the new SQL, it has to be recredentialed which is what torpedoed by attempt last evening.

The other thing I worry about is once you switch I believe NC has to be informed so there can be a switch in prescribing. That is supposedly done behind the scenes automatically.

Oh well, we shall see. I think AC will have to help on some of these if only because of the credentialing portion.

Nope. Two squalls which were predicted months in advance but arrive around the same time do not add up to a perfect storm.