|
|
|
Posts: 679
Joined: February 2011
|
|
#73186
08/17/2018 12:47 PM
|
Joined: Dec 2017
Posts: 123
Member
|
OP
Member
Joined: Dec 2017
Posts: 123 |
Recently I've been having issues where the SQL service keeps turning off. Tech support says its an issue with micro soft and there is an update that he reports is optional and that it will fix the problem. He wasn't able to give me more details on the update in regards to name or where I would be able to acquire it, only that it may have been in July. Any help would be appreciated.
Dru
|
|
|
|
|
Joined: Apr 2011
Posts: 2,316 Likes: 2
G Member
|
|
G Member
Joined: Apr 2011
Posts: 2,316 Likes: 2 |
Yea it's related to the port bindings for SQL Server. There is a way to manually fix it but installing the update is the easiest way. Though correcting the bindings may prove useful in future if Microsoft messes it up again.
It's actually a standard update now. AC is probably referencing the Preview July rollup update which also corrected the issue. But the update was finalized a few days ago in the August release. When you run Windows update, look for 2018-08 Security Monthly Quality Rollup for Windows.
Also strongly recommended to get that update installed before upgrading to V10 if you haven't already. If you do have orphaned bindings in the SQL settings, your V10 upgrade will fail.
|
|
|
|
|
Joined: Dec 2017
Posts: 123
Member
|
|
OP
Member
Joined: Dec 2017
Posts: 123 |
Sandeep
I appreciate the help. I just looked into this and it appears the update for windows 10 installed on 08/14/2018. My problems began on 08/16/2018. Although there may have been an issue soon after installing AC v10 on 07/18 in which tech support I believe had to restart the service along with some other issues. Question is are there any instructions on how to manually fix the port bindings. Also do you know if this is something that all EMR's are experiencing?
|
|
|
|
|
Joined: Apr 2011
Posts: 2,316 Likes: 2
G Member
|
|
G Member
Joined: Apr 2011
Posts: 2,316 Likes: 2 |
It was an issue for lots of SQL Servers. Basically any application that relies on a fixed port instead of dynamic ports. A previous update made it so that only one interface could listen to one port. So if you had IPV6 setup and it was bound to that instead of IPV4. The way to correct before the preview update was released was to disable all the other binding except the main one.
I wouldn't worry too much about it. The instructions would be different for everyone.
|
|
|
|
|
Joined: Dec 2017
Posts: 123
Member
|
|
OP
Member
Joined: Dec 2017
Posts: 123 |
|
|
|
|
0 members (),
104
guests, and
16
robots. |
|
Key:
Admin,
Global Mod,
Mod
|
|
|
|
|
|
.png "ACUF Donor I")