May 25, 2013 at 2:02 pm
Two problems, possibly related, both giving me heartburn as I'm going away for 2 weeks and don't want to leave a server in this state...
Problem 1:
When I try to run a backup to anywhere *EXCEPT* the default SQL backup folder (\program files\microsoft sql server\mssql10_50.mssqlserver\mssql\backup\) fails with a system error 5 (Access denied.) Now, the SQL Server service account is a member of the local Administrators group, and I've checked the permissions and there's nothing that should be blocking it.
Problem 2:
When I try to change the service account to any other account, I get a "wmi provider error - Access denied - 0x80070005" message. All the solutions I've seen for this say "click on the browse then key in the account name and "check name" and re-enter the password." Well, no dice, same error. Even if I try to use one of the local system accounts, same error.
I'm logging into the server with a local Administrator account, so I have the rights to do this stuff. It was all working before I installed some Windows updates, since then it's gone pear-shaped. I've tried uninstalling the updates, that hasn't helped. I've got 2 other SQL Servers, identical configurations (same OS version, same SQL version, heck everything is installed to the same places!) which are NOT having this problem.
I've been Googling this problem most of today, and it's PISSING ME OFF!
(sorry about that)
Any help, any suggestions will be deeply appreciated.
Thank you,
Jason
May 25, 2013 at 2:12 pm
Couple more things, about the same server:
I'm unable to create a new database (also throws an access denied)
OS: Server 2008 SP2
SQL: SQL Server 2008 R2 SP1
May 25, 2013 at 4:13 pm
What permissions does the SQL Server (not the agent) service account have on the server?
Joie Andrew
"Since 1982"
May 26, 2013 at 4:46 pm
the SQL Server service account is a member of the local Administrators group
May 26, 2013 at 9:16 pm
Run SQL Server Configuration Manager as Administrator (right click) and try again. What error is in the Windows Application log? What error in SQL log? What are the permission differences on the SQL folder, including the folder Ownership.
May 27, 2013 at 7:40 am
foxxo (5/26/2013)
Run SQL Server Configuration Manager as Administrator (right click) and try again.
Tried that early on, made no difference...
foxxo (5/26/2013)
What error is in the Windows Application log? What error in SQL log?
When trying to change the service account, no error is recorded in either the Windows or SQL logs...
When trying to run a backup (via T-SQL, not an Agent job) only the "Access denied" message.
foxxo (5/26/2013)
What are the permission differences on the SQL folder, including the folder Ownership.
I've looked at the permissions until my eyes have bled, no differences. Ditto ownership.
May 27, 2013 at 7:16 pm
Im wondering if some permissions were stuffed somehow after the Windows updates.
You need to narrow down the cause for the Access Is Denied WMI event. You can turn on a WMI trace in Windows event viewer, instructions here http://msdn.microsoft.com/en-us/library/windows/desktop/aa826686%28v=vs.85%29.aspx
Then try changing the service account again, there should be an event in the log, look for any errors.
May 28, 2013 at 7:48 am
Foxxco, thanks for the idea...
Now if only the guys I work with would text me back, so I could point them to your suggestion...
Kind of hard to work from an airport, especially when I don't have (and didn't bring) my work laptop.
Jason
June 12, 2013 at 6:38 am
I'm thinking permissions are beyond stuffed at this point...
I tried Foxxcos' idea, and there are NO errors / warnings / critical events logged in the WMI log when I try to change one of the service accounts. Lots of other stuff gets logged, but I've not yet taken the time to try to plow through and see if I can find my attempt at changing the service account.
As of now, last night we tried loading an OS update MS support suggested, as well as (the expected long shot) running chkdsk /f on the drives. Unfortunately, we're still in the same boat.
Also come to find out, this problem has managed to also break Full Text Indexing on the one DB using it, and Filestream on the DB using that...
Getting psyched up to start a "crash" migration to a new server, although I'd really rather avoid that right now (in the midst of a migration already from a Server 2003 / SQL 2005 Cluster to a new Server 2008 R2 / SQL 2008 R2)
Thanks,
Jason
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply