Announcement

Collapse
No announcement yet.

Windows Internal Database Service Account Changed

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Windows Internal Database Service Account Changed

    Gang,

    I accidentally changed the service account credentials for the Windows Internal Database (microsoft##ssee) from "Network Service" to "Local system". Now, I get SharePoint database login failure messages for the configuration database and unknown microsoft##ssee errors in the application event log (I can provide specifics if needed). I tried to change the service back to "Network Service" through the SQL 2005 Configuration Manager, but it won't change back (I receive an error - 0x8007056c WMI Provider Error). I don't even get an option to change it to "Network Service" through "services.msc". I cannot change it to "local service" either otherwise I get the same error. How can I fix this? WSUS seems to still be working fine aside from its web service (event 12032), but my SBSMonitoring invalid TCP/IP configuration messages are back and SharePoint is broken. When I go to http://companyweb now, I get an IIS7 page (the SharePoint config database cannot be loaded)! Please help!


    Derek

  • #2
    Re: Windows Internal Database Service Account Changed

    I edited the "microsoft##ssee" service in the registry and was able to enter the Network Service credentials. The "microsoft##ssee" service now starts as "Network Service"! Most events have been resolved for services other than SharePoint. I still cannot connect to the "companyweb" site. I still get an IIS7 web page. I checked the event viewer again and found event ID 3355:

    "Log Name: Application
    Source: Windows SharePoint Services 3
    Date: 7/21/2009 2:33:50 PM
    Event ID: 3355
    Task Category: Database
    Level: Error
    Keywords: Classic
    User: N/A
    Computer: SERVER.mydomain.local
    Description:
    Cannot connect to SQL Server. np:\\.\pipe\MSSQL$Microsoft##SSEE\sql\query not found. Additional error information from SQL Server is included below.

    Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
    Event Xml:



    3355
    2
    484
    0x80000000000000

    190275
    Application
    SERVER.mydomain.local



    np:\\.\pipe\MSSQL$Microsoft##SSEE\sql\query
    Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.



    AND THEN AFTER THAT ERROR I RECEIVED THE FOLLOWING:


    Log Name: Application
    Source: Windows SharePoint Services 3 Search
    Date: 7/21/2009 2:51:08 PM
    Event ID: 10036
    Task Category: Gatherer
    Level: Error
    Keywords: Classic
    User: N/A
    Computer: SERVER.mydomain.local
    Description:
    A database error occurred.

    Source: Microsoft OLE DB Provider for SQL Server
    Code: 0 occurred 1 time(s)
    Description: Timeout expired
    Event Xml:



    10036
    2
    3
    0x80000000000000

    190298
    Application
    SERVER.mydomain.local





    Microsoft OLE DB Provider for SQL Server
    0
    1
    Timeout expired



    Any ideas? Thanks, in advance, for your assistance.

    D

    Comment


    • #3
      Re: Windows Internal Database Service Account Changed

      Gang,

      I have not received a response to my question re: repair or restoration of the "Windows Internal Database" in SBS2008. I am receiving the following errors now that the "microsoft##ssee" service has been successfully changed back to "NT Authoity\Network Service":



      Source: Microsoft-Windows-Perflib
      Date: 7/21/2009 4:37:57 PM
      Event ID: 2003
      Task Category: None
      Level: Warning
      Keywords: Classic
      User: N/A
      Computer: SERVER.mydomain.local
      Description:
      The configuration information of the performance library "C:\Windows\system32\sqlctr90.dll" for the "MSSQL$MICROSOFT##SSEE" service does not match the trusted performance library information stored in the registry. The functions in this library will not be treated as trusted.


      Log Name: Application
      Source: Windows SharePoint Services 3 Search
      Date: 7/23/2009 5:00:21 PM
      Event ID: 2442
      Task Category: Gatherer
      Level: Warning
      Keywords: Classic
      User: N/A
      Computer: SERVER.mydomain.local
      Description:
      The index was paused.

      Context: Application 'Search', Catalog 'index file on the search server Search'


      Log Name: Application




      Log Name: Application
      Source: Windows SharePoint Services 3
      Date: 7/21/2009 2:33:50 PM
      Event ID: 3355
      Task Category: Database
      Level: Error
      Keywords: Classic
      User: N/A
      Computer: SERVER.mydomain.local
      Description:
      Cannot connect to SQL Server. np:\\.\pipe\MSSQL$Microsoft##SSEE\sql\query not found. Additional error information from SQL Server is included below.

      Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

      Any ideas on how to resolve these? I don't want to have to restore if at all possible. Please advise and thanks again!

      D

      Comment


      • #4
        Re: Windows Internal Database Service Account Changed

        Have you re-run the SharePoint Products and Technologies Configuration Wizard. It fixes a lot of errors. If it fails, make a note of what step it failed on and post the log here as an attachment.

        Have you run SQL BPA. Run it against the instance \\.\pipe\mssql$microsoft##ssee\sql\query See what it says about the consistance of your databases.

        Comment


        • #5
          Re: Windows Internal Database Service Account Changed

          Originally posted by BigStan View Post
          Have you re-run the SharePoint Products and Technologies Configuration Wizard. It fixes a lot of errors. If it fails, make a note of what step it failed on and post the log here as an attachment.

          Have you run SQL BPA. Run it against the instance \\.\pipe\mssql$microsoft##ssee\sql\query See what it says about the consistance of your databases.
          I ran the wizard with no luck. I am still getting an IIS7 page displayed when the clients visit http://companyweb. I still have the following events on the server related to this issue:

          Log Name: Application
          Source: SQLBrowser
          Date: 7/30/2009 10:45:48 AM
          Event ID: 3
          Task Category: None
          Level: Warning
          Keywords: Classic
          User: N/A
          Computer: SERVER.mydomain.local
          Description:
          The configuration of the AdminConnection\TCP protocol in the SQL instance SBSMONITORING is not valid.


          Log Name: Application
          Source: MSSQL$SBSMONITORING
          Date: 7/30/2009 10:47:25 AM
          Event ID: 17187
          Task Category: (4)
          Level: Error
          Keywords: Classic
          User: N/A
          Computer: SERVER.mydomain.local
          Description:
          SQL Server is not ready to accept new client connections. Wait a few minutes before trying again. If you have access to the error log, look for the informational message that indicates that SQL Server is ready before trying to connect again. [CLIENT: XXX.XXX.XXX.XXX]


          Log Name: Application
          Source: Windows SharePoint Services 3
          Date: 7/30/2009 10:47:36 AM
          Event ID: 3355
          Task Category: Database
          Level: Error
          Keywords: Classic
          User: N/A
          Computer: SERVER.mydomain.local
          Description:
          Cannot connect to SQL Server. np:\\.\pipe\MSSQL$Microsoft##SSEE\sql\query not found. Additional error information from SQL Server is included below.

          Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.


          Log Name: Application
          Source: Windows SharePoint Services 3
          Date: 7/30/2009 10:51:07 AM
          Event ID: 3760
          Task Category: Database
          Level: Error
          Keywords: Classic
          User: N/A
          Computer: SERVER.mydomain.local
          Description:
          SQL Database 'ShareWebDb' on SQL Server instance 'np:\\.\pipe\MSSQL$Microsoft##SSEE\sql\query' not found. Additional error information from SQL Server is included below.

          Cannot open database "ShareWebDb" requested by the login. The login failed.
          Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.


          I then ran the SQL 2005 BPA and received only the following error:

          Service [SQLBrowser] on host [] is found to be running under LocalSystem account. We recommend that SQL Server services should not run under LocalSystem account.


          This leads me to believe that the service account is wrong for the SQLBrowser service. What should it be? Could this issue cause the problems I am experiencing? WSUS seems to be working fine and its database is also house in the "Microsoft##ssee" "Windows Internal Database" instance. Thanks for your advice and please advise!

          Comment


          • #6
            Re: Windows Internal Database Service Account Changed

            Open SQL Server Management. Connect to \\.\pipe\mssql$microsoft##ssee\sql\query

            Expand Security and Logins. Double click on NT Authority/Network Service

            Under Server Roles, Public and sysadmin should be checked

            Under User Mappings, everything should be checked except the 4 default SQL databases.

            Under Status, They should both be enabled.

            How do yours look?

            Comment


            • #7
              Re: Windows Internal Database Service Account Changed

              Originally posted by BigStan View Post
              Under Server Roles, Public and sysadmin should be checked.
              Under Server Roles, "dbcreator", "public" and "securityadmin" are checked. There is no check by "sysadmin" at all. I take it there should be?

              Originally posted by BigStan View Post
              Under User Mappings, everything should be checked except the 4 default SQL databases.
              Under user mappings, "master", "model", "msdb" and "tempdb" (the 4 default dbs) are not checked. Everything else is.

              Originally posted by BigStan View Post
              Under Status, They should both be enabled.
              The "grant" radio button is selected under "Permission to connect to database engine" and "Login" is "enabled".

              Please advise and thanks for your help!!

              D

              Comment


              • #8
                Re: Windows Internal Database Service Account Changed

                Check these settings. Except, where it says "Security accounts" it really means "Service Account"

                http://technet.microsoft.com/en-us/l.../cc561047.aspx

                Comment


                • #9
                  Re: Windows Internal Database Service Account Changed

                  I will check the TechNet post settings ASAP.

                  Then the SQLBrowser service being localsystem is not a problem (per the BPA)?!

                  Also, not having the "sysadmin" checked is not a problem?!

                  D

                  Comment


                  • #10
                    Re: Windows Internal Database Service Account Changed

                    Originally posted by RaeKWoNCHeF View Post
                    I will check the TechNet post settings ASAP.

                    Then the SQLBrowser service being localsystem is not a problem (per the BPA)?!

                    Also, not having the "sysadmin" checked is not a problem?!

                    D
                    Neither of those are problems. That's how mine is set. Except I set my Network Service to Admin a while back because I thought it might be a good idea. Not in response to any error.

                    Comment


                    • #11
                      Re: Windows Internal Database Service Account Changed

                      Thanks for the help again. I checked those settings. Both App Pool Accounts are set to "Network Service". I checked the SQL settings and the only DB missing the "Network Service" account under the "db_owner" role is the "WSS_Search_SERVER" database. I cannot add the "Network Service" account to its list because the account is hidden. I am not sure if that matters, or not.

                      When I get to try to run the stsadm command, I get the following:

                      C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN>Stsadm.exe -o enumsites

                      Missing required argument: url.

                      stsadm.exe -o enumsites
                      -url <virtual server url>
                      -showlocks
                      -redirectedsites
                      [-databasename <database name>]

                      so I can go now further. Please advise.

                      D

                      P.S. Sorry if I am being a noob about this, but I have very little SQL Server/SharePoint experience. Being SBS2008 loads everything up nicely for the installer, I haven't had to dive into the technicalities of the software yet. I appreciate your help and patience.
                      Last edited by RaeKWoNCHeF; 30th July 2009, 20:07.

                      Comment


                      • #12
                        Re: Windows Internal Database Service Account Changed

                        I've just about run out of ideas. Let me sleep on it and get back to you.

                        Comment


                        • #13
                          Re: Windows Internal Database Service Account Changed

                          Gang,

                          Can anyone else advise? BigStan? I need to resolve this ASAP, so I might just need to run a repair, or restore from backup. Any advice? I have never done either of these before. What should be my next suggested step?

                          D

                          Comment


                          • #14
                            Re: Windows Internal Database Service Account Changed

                            I don't have any ideas on the top of my head. Here are some musings.

                            I ran across this blog. On the Feb 19th post he references the same error. Unfortunatly he doesn't have a solution. Might ping him to see if he learned anything new.

                            http://simultaneouspancakes.com/Less...gory/sbs-2008/

                            Also ran across this technet article "Repair other issues in Windows SharePoint Services". If you look at the 1., 2., 3., 4., they link to other articles to repair Sharepoint. This particular article is the "catchall". If the first 4 don't resolve the issue, you can try this one. My impression is that is it detaching the databases, recreating the web applications, and re-attaching the database. That will in effect create new applicaton with the default settings. Don't know if this is easier than restoring.

                            http://technet.microsoft.com/en-us/l...21(WS.10).aspx

                            Wish I could help more, but you definitely have a tough one here.

                            Comment


                            • #15
                              Re: Windows Internal Database Service Account Changed

                              BigStan,

                              You ARE helping me by trying. I really appreciate everything you have suggested thus far. I'll work through what I can and will advise.

                              If anyone else has anything that might be of assistance, please let me know. Thanks!!

                              D

                              Comment

                              Working...
                              X