July 12, 2017 at 8:03 am
Brandie Tarvin - Wednesday, July 12, 2017 4:57 AMThom A - Wednesday, July 12, 2017 2:20 AMNot a question for help, we fixed the problem, but just wondered if anyone knows of any updates "recently" that caused problem with the Log on as Service permissions. Our SQL server went through it's monthly restart last night, and we got in to find all of the services failed to restart. One of the errors being the below:The MSSQLSERVER service was unable to log on as [Service Account] with the currently configured password due to the following error:
Logon failure: the user has not been granted the requested logon type at this computer.Service: MSSQLSERVER
Domain and account: [Service Account]This service account does not have the required user right "Log on as a service."
User Action
Assign "Log on as a service" to the service account on this computer. You can use Local Security Settings (Secpol.msc) to do this. If this computer is a node in a cluster, check that this user right is assigned to the Cluster service account on all nodes in the cluster.
If you have already assigned this user right to the service account, and the user right appears to be removed, check with your domain administrator to find out if a Group Policy object associated with this node might be removing the right.
Considering we've had the server running fine for the last 4 years, with its restarts, we found it a little odd, and just trying to ensure that nothing else is going on behind the scenes. Network Team are having a look their end as well, however, they're not aware of any changes they think would have affected it in the last couple of months.
Thanks guys!
I can't say as if I've heard anything on this. But I do know some OS patches came through on my PC this week and overrode my Aero Peek settings (I had completely disabled it and suddenly, even though the box was unchecked, it started "working" again). So yeah, some weird stuff has been happening on some of these patches.
Don't you hate it when an OS patch gets installed and something stops working? Then we're left wondering what changed to cause the problem. :crazy:
July 12, 2017 at 8:14 am
Ed Wagner - Wednesday, July 12, 2017 8:03 AMBrandie Tarvin - Wednesday, July 12, 2017 4:57 AMThom A - Wednesday, July 12, 2017 2:20 AMNot a question for help, we fixed the problem, but just wondered if anyone knows of any updates "recently" that caused problem with the Log on as Service permissions. Our SQL server went through it's monthly restart last night, and we got in to find all of the services failed to restart. One of the errors being the below:The MSSQLSERVER service was unable to log on as [Service Account] with the currently configured password due to the following error:
Logon failure: the user has not been granted the requested logon type at this computer.Service: MSSQLSERVER
Domain and account: [Service Account]This service account does not have the required user right "Log on as a service."
User Action
Assign "Log on as a service" to the service account on this computer. You can use Local Security Settings (Secpol.msc) to do this. If this computer is a node in a cluster, check that this user right is assigned to the Cluster service account on all nodes in the cluster.
If you have already assigned this user right to the service account, and the user right appears to be removed, check with your domain administrator to find out if a Group Policy object associated with this node might be removing the right.
Considering we've had the server running fine for the last 4 years, with its restarts, we found it a little odd, and just trying to ensure that nothing else is going on behind the scenes. Network Team are having a look their end as well, however, they're not aware of any changes they think would have affected it in the last couple of months.
Thanks guys!
I can't say as if I've heard anything on this. But I do know some OS patches came through on my PC this week and overrode my Aero Peek settings (I had completely disabled it and suddenly, even though the box was unchecked, it started "working" again). So yeah, some weird stuff has been happening on some of these patches.
Don't you hate it when an OS patch gets installed and something stops working? Then we're left wondering what changed to cause the problem. :crazy:
Oh yeah! The production stack was patched last weekend. For whatever reason, the secondary AG server server stopped doing synchronous commits.
As I dug into it, the primary boxes were patched, the secondary wasn't set as active in WSUS and it never got patched or re-booted.
Michael L John
If you assassinate a DBA, would you pull a trigger?
To properly post on a forum:
http://www.sqlservercentral.com/articles/61537/
July 12, 2017 at 8:14 am
Brandie Tarvin - Tuesday, July 11, 2017 4:29 AMChris Harshman - Monday, July 10, 2017 2:56 PMBrandie Tarvin - Monday, July 10, 2017 5:30 AMI really hate it when coworkers say "I don't have time to figure that out right now" but think I have time to be working errors back and forth with them (until we stumble across the solution) later on.Are you by any chance working in an "Agile" environment? I hear that kind of talk around here all the time. :crazy:
Some people in other departments are. In my department, we tend to use a more rigid SDLC. About 5 years ago, we instituted a motto "get it right the first time" which has seriously improved a lot of things around here.
The annoying thing about this particular situation is that we're redirecting a feed from one department (that would roll our feed up into theirs before sending it onward) to the actual destination department. Everything in QC tested fine, but now in Prod, things are erroring out on special characters (that I know did exist in QC). So if I want to send the name O'Niell, I can't send the single quote with it. Thing is, the feed has never been scrubbed before from either us or the former department that used to send it. So either the destination department has been cleaning up manually without telling anyone or something has gone hinky with their system.
Worse, their system errors out a record on the first error and doesn't check for other errors, so if one record has 5 different "special characters", it's a crap shoot as if the correct record will pass or fail again 4 more times.
Either way, they don't have time to get me a list of special characters that can or can't be sent on the feed... And I find myself wondering why they don't know their system well enough to know this information already (or at least have a running documented list). It's not like I'm asking them to clean up my feed themselves. I just want to know what to scrub out so that it doesn't error on their side at all.
Is that too much to ask?
I have one of my mantras written at the top of my white board. "They want it real bad. It's our goal to NOT give it to them that way." 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
July 12, 2017 at 8:27 am
Ed Wagner - Wednesday, July 12, 2017 8:03 AMBrandie Tarvin - Wednesday, July 12, 2017 4:57 AMThom A - Wednesday, July 12, 2017 2:20 AMNot a question for help, we fixed the problem, but just wondered if anyone knows of any updates "recently" that caused problem with the Log on as Service permissions. Our SQL server went through it's monthly restart last night, and we got in to find all of the services failed to restart. One of the errors being the below:The MSSQLSERVER service was unable to log on as [Service Account] with the currently configured password due to the following error:
Logon failure: the user has not been granted the requested logon type at this computer.Service: MSSQLSERVER
Domain and account: [Service Account]This service account does not have the required user right "Log on as a service."
User Action
Assign "Log on as a service" to the service account on this computer. You can use Local Security Settings (Secpol.msc) to do this. If this computer is a node in a cluster, check that this user right is assigned to the Cluster service account on all nodes in the cluster.
If you have already assigned this user right to the service account, and the user right appears to be removed, check with your domain administrator to find out if a Group Policy object associated with this node might be removing the right.
Considering we've had the server running fine for the last 4 years, with its restarts, we found it a little odd, and just trying to ensure that nothing else is going on behind the scenes. Network Team are having a look their end as well, however, they're not aware of any changes they think would have affected it in the last couple of months.
Thanks guys!
I can't say as if I've heard anything on this. But I do know some OS patches came through on my PC this week and overrode my Aero Peek settings (I had completely disabled it and suddenly, even though the box was unchecked, it started "working" again). So yeah, some weird stuff has been happening on some of these patches.
Don't you hate it when an OS patch gets installed and something stops working? Then we're left wondering what changed to cause the problem. :crazy:
We have the same problem. We have a piece of code created by our telephone system vendor that converts a proprietary form of call recordings to WAV files. About a year ago, a Windows Update (which we do every bloody month to keep up with security patches) broke the code. We had to roll back a part of the update and have had to do so since then. We have two choices... continue to rollback or simply not install that particular update somewhat relying on documented tribal knowledge or pay out the nose for a rewrite. We'll eventually pay for the rewrite but, damn, between things like that and (frequently unnecessary, IMHO) deprecation lists in SQL Server, it can be a real pain.
Once again, "Change is inevitable... change for the better is not".
--Jeff Moden
Change is inevitable... Change for the better is not.
July 12, 2017 at 8:44 am
Thom A - Wednesday, July 12, 2017 2:20 AMNot a question for help, we fixed the problem, but just wondered if anyone knows of any updates "recently" that caused problem with the Log on as Service permissions. Our SQL server went through it's monthly restart last night, and we got in to find all of the services failed to restart. One of the errors being the below:The MSSQLSERVER service was unable to log on as [Service Account] with the currently configured password due to the following error:
Logon failure: the user has not been granted the requested logon type at this computer.Service: MSSQLSERVER
Domain and account: [Service Account]This service account does not have the required user right "Log on as a service."
User Action
Assign "Log on as a service" to the service account on this computer. You can use Local Security Settings (Secpol.msc) to do this. If this computer is a node in a cluster, check that this user right is assigned to the Cluster service account on all nodes in the cluster.
If you have already assigned this user right to the service account, and the user right appears to be removed, check with your domain administrator to find out if a Group Policy object associated with this node might be removing the right.
Considering we've had the server running fine for the last 4 years, with its restarts, we found it a little odd, and just trying to ensure that nothing else is going on behind the scenes. Network Team are having a look their end as well, however, they're not aware of any changes they think would have affected it in the last couple of months.
Thanks guys!
So to confirm something here, the current batch of MS updates were installed on the problem computer last night and it was then rebooted?
I ask because later this week / early next week when our network team gets around to making the patches available through SCCM I'm going to be updating. If one of the updates has cause someone else pain like this, I'll know to be careful and do one QA box first, and make sure it doesn't break anything.
Can you give any details of the box it happened to? OS, SQL version?
July 12, 2017 at 8:45 am
jasona.work - Wednesday, July 12, 2017 7:54 AMMust...
Touch...
Drive...
Oh you could touch them alright. You could leave fingerprints on the actual disks and the chances are it wouldn't matter. When the engineer tinkered with the drives he used to set the alignment of the r/w heads by sight alone - you could see daylight between the head and the disk. And those disks were about 60Mb if I remember rightly.
July 12, 2017 at 9:00 am
jasona.work - Wednesday, July 12, 2017 8:44 AMSo to confirm something here, the current batch of MS updates were installed on the problem computer last night and it was then rebooted?
I ask because later this week / early next week when our network team gets around to making the patches available through SCCM I'm going to be updating. If one of the updates has cause someone else pain like this, I'll know to be careful and do one QA box first, and make sure it doesn't break anything.Can you give any details of the box it happened to? OS, SQL version?
OS is Windows Server 2012 R2, and SQL Server 2012 (Standard).
As for what was patched, there's quite a few in the list. The KB's are:
KB4025336
KB3213640
KB890830
KB3213624
KB3203436
KB4023307
KB890830
KB3203460
KB4019114
KB3186539
KB4022726
Some of those are office updates, etc (I assume because we have the drivers installed), however, if I were to hazard a guess at what caused it, I would probably say KB3186539 or KB4025336. Those were the Security roll ups for June and July, and the problem was that the Logins lost their permissions to login as a service.
I'm still not ruling out that it was a network issue. We had someone from the Network team leave last month and although he didn't do anything malicious, he was one of the more knowledgeable members and had a habit of implementing before vocalising. Thus, I wouldn't be surprised if something he put in propagated, but then didn't actually come up till the server restart yesterday. Then, when I asked the network team about it, they had no idea, because it was something he'd just "done", without telling anyone and he has since left.
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
July 12, 2017 at 9:02 am
jonathan.crawford - Wednesday, July 12, 2017 8:01 AMjasona.work - Wednesday, July 12, 2017 7:54 AMBrainDonor - Wednesday, July 12, 2017 1:27 AMjasona.work - Tuesday, July 11, 2017 1:16 PMHmm, if every server in a rack started and stopped it's fans in sync, would they be able to start rocking the rack side-to-side?
And if they did the same with the disk drives, and got the timing right, would they also be able to get it to "walk" forward?Many, many years ago I used to watch our ICL hard-drives shuffle along the floor when the data was badly fragmented. Occasionally our engineer would shuffle them back into place once they'd calmed down.
Must...
Touch...
Drive...spills coffee, drops pen from shirt pocket while leaning over the machine.....*crackle*...."Houston, we have a problem"....
/Me slinks back to my desk, begins working on resume
July 12, 2017 at 9:56 am
BrainDonor - Wednesday, July 12, 2017 8:47 AMIs anybody else getting email notifications to let them know that somebody they're following has posted, when in fact they aren't following them?
Did you do QA testing for the site and maybe follow them then?
July 12, 2017 at 10:46 am
I'm not sure how useful this will be but...
July 12, 2017 at 11:53 am
Thom A - Wednesday, July 12, 2017 9:00 AMjasona.work - Wednesday, July 12, 2017 8:44 AMSo to confirm something here, the current batch of MS updates were installed on the problem computer last night and it was then rebooted?
I ask because later this week / early next week when our network team gets around to making the patches available through SCCM I'm going to be updating. If one of the updates has cause someone else pain like this, I'll know to be careful and do one QA box first, and make sure it doesn't break anything.Can you give any details of the box it happened to? OS, SQL version?
OS is Windows Server 2012 R2, and SQL Server 2012 (Standard).
As for what was patched, there's quite a few in the list. The KB's are:
KB4025336
KB3213640
KB890830
KB3213624
KB3203436
KB4023307
KB890830
KB3203460
KB4019114
KB3186539
KB4022726
Some of those are office updates, etc (I assume because we have the drivers installed), however, if I were to hazard a guess at what caused it, I would probably say KB3186539 or KB4025336. Those were the Security roll ups for June and July, and the problem was that the Logins lost their permissions to login as a service.I'm still not ruling out that it was a network issue. We had someone from the Network team leave last month and although he didn't do anything malicious, he was one of the more knowledgeable members and had a habit of implementing before vocalising. Thus, I wouldn't be surprised if something he put in propagated, but then didn't actually come up till the server restart yesterday. Then, when I asked the network team about it, they had no idea, because it was something he'd just "done", without telling anyone and he has since left.
Thank you for this, Thom. Our OS patches get installed in the wee hours of tomorrow morning, so it's especially timely for us.
Thanks again. It's appreciated. I'll post back if we get his by the same thing.
July 13, 2017 at 1:30 am
Brandie Tarvin - Wednesday, July 12, 2017 9:56 AMBrainDonor - Wednesday, July 12, 2017 8:47 AMIs anybody else getting email notifications to let them know that somebody they're following has posted, when in fact they aren't following them?Did you do QA testing for the site and maybe follow them then?
Nope. It only happens occasionally, so it is only mildly irritating - I was just curious to see if others have this.
July 13, 2017 at 4:03 am
BrainDonor - Thursday, July 13, 2017 1:30 AMBrandie Tarvin - Wednesday, July 12, 2017 9:56 AMBrainDonor - Wednesday, July 12, 2017 8:47 AMIs anybody else getting email notifications to let them know that somebody they're following has posted, when in fact they aren't following them?Did you do QA testing for the site and maybe follow them then?
Nope. It only happens occasionally, so it is only mildly irritating - I was just curious to see if others have this.
Not me. Maybe email the webmaster to have them look into it? I know others besides Steve monitor that box.
July 13, 2017 at 7:59 am
I feel really daft for posting this, but does anyone know where you find SQL Server 2012 Developer? I've got to set up a couple more instances for our new UAT and DEV environments and for the life of me no amount of Googling seems to be telling me where to go.... :blush:
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
Viewing 15 posts - 59,221 through 59,235 (of 66,712 total)
You must be logged in to reply to this topic. Login to reply