Post reply

Weird wmi provider message when try to change sql service account

  • November 11, 2009 at 2:30 pm

    #213652

    Hello all,

    today I got a strange error message on one of our test environment database servers.

    First at all, sql server service failed to start due to inaccessible master.dbf file and so on.

    My 1st thought was: Well, maybe again something with the ntfs rights (I´ve made my experience with an SQL Hotfix which didn´t work properly and whiped the ntfs rights away...different story)

    But ntfs looked good.

    Next step was: change the service account to local system, apply and then change back. All with the SQL Server config manager.

    And then this message came up

    I´ve searched the net but found no real solution. My workaround for now is to run sql server service under a different windows account which is also local admin, but I want to change it back as soon as I can.

    Has anyone here ever got a similar error? What was the workaround?

    Tomorrow I´ll try a new service account.

    Regards

    Dirk

    --
    May you never suffer the sentiment of spending a day without any purpose.
    @DirkHondong on Twitter

  • November 11, 2009 at 3:56 pm

    #1078108

    Is your master.dbf on attached storage like ISCSI?

    Alex S

  • November 11, 2009 at 4:10 pm

    #1078112

    I am sure I have had that error and am racking brains to remember when.............

    I do think the error message bears no relation to the problem.

    the fact that it works under an account with local admin does suggest permissions. Have the local server accounts that SQL creates on install become orphaned? these would show up as greyed out accounts under sharing and security for the directories. You would need to re-add them with the correct permissions.

    ---------------------------------------------------------------------

  • November 11, 2009 at 11:37 pm

    #1078175

    Hi,

    thanks for the replies so far.

    Well, the local groups created by SQL Server are still there and no one´s orphaned.

    If I try a new local user account with no special permission, I´ll get the same error mentioned above.

    Also, if I choose the built in acc local service it does not work, if I choose local system, then it works. Network service again fails.

    I think it becomes an interesting troubleshooting-day...

    Regards

    Dirk

    --
    May you never suffer the sentiment of spending a day without any purpose.
    @DirkHondong on Twitter

  • November 13, 2009 at 5:56 am

    #1078857

    Might have a file level permission problem. Make sure the account has appropriate file level permissions and that it has been granted appropriate rights to run the service.

  • November 13, 2009 at 6:48 am

    #1078887

    Filemon and Regmon can be helpful to see file and registry permissions issues.

    You also might want to check Local Security Policy (under Administrative Tools on the start menu) and see that the ID has Log On as a Service rights.

    When we run a service under a domain user, we also usually restrict the ID to the machine. So you may want to see if the ID can just log into the machine first.

    Greg E

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply