Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
|Source: Windows SharePoint Services 2.0|
|Maintenance: Recommended tasks for Microsoft SharePoint Server maintenance|
#50070: Unable to connect to the database <database name>. Check the database connection information and make sure that the database server is running.
|English: This information is only available to subscribers. An example of English, please!|
Make sure your SQL Server is properly joined to the domain. I had lost connectivity to the domain and therefore any sort of domain based security would not work, creating this error in the system logs (See "Is the SQL Server is in the domain?").
From a newsgroup post: "I started getting this error after I installed the .NET Framework version 3.0 on a new SBS 2003 R2 server. In the same time I was getting event id 18456 source from MSSQL$SHAREPOINT for user "NT AUTHORITY\NETWORK SERVICE". After a few restarts both errors dissapeared".
Chris Gideon's WebLog post "50070: Unable to connect to the database <Database Name>" contains a list with 20 potential reasons for this problem. See the link below.
I found that in [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\SBSMONITORING\MSSQLServer\Parameters], SQLArg0 and SQLArg2 contained double dir entries (MSSQL$SBSMONITORING\MSSQL$SBSMONITORING\) so SQL would not start.
The "SharePoint Timer Service" service was running logged on as "NT AUTHORITY\NETWORK SERVICE". This was changed to the service account "domain_name\Sharepoint_Admin_account". The problem is now gone.
I received this error when I tried to create a Database instance for SharePoint Services 2.0 with SP2 in SQL 2000 Enterprise edition with SP4. I am running Windows Server 2003 with SP1 as a member server. I tried the option of using the predefined "Network Service" account for the DB creation purpose. The "NT Authority\Network Service" is a member of the local system group IIS_WPG. This group IIS_WPG is found in the local groups of application servers running IIS 6.0. The problem was resolved when I granted the Database Server Role of "Create Database" in SQL Enterprise Manager -> My Server -> Security -> Logins for the group IIS_WPG.
Check to see if your Sharepoint search feature is running and trying (but failing) to connect to the database to perform a "crawl and index" type function. We were performing a "Training" crawl, where you "teach" Sharepoint how to search and build categories. I fixed this and stopped this error by performing the following steps: Open your Windows Task Manager and kill the "sdAdminSvc.exe" process. This will automatically restart and free up the server from the continuous attempts to connect.
- Event description: "Adding user "<user name>" to OU "<organizational unit name>" in domain "<domain name>" failed with HRESULT -2147023541" - See ME828813.
As per Microsoft: "This problem may occur when a user cannot successfully connect to a database on the server that is running SharePoint Portal Server 2003". See ME911285 for a hotfix applicable to Microsoft Office SharePoint Portal Server 2003.
This issue can occur after you remove an MSDE 2000 SP4 instance, a SQL Server 2000 Desktop Engine (Windows) SP4 instance, or a SQL Server 2000 SP4 instance. See ME920899 to solve this problem.
I ran into this problem on an SBS 2003 Server after applying SBS SP1 (and all of its prerequisites). I checked the OLEDB version and it was good. I set the dependency but still no luck. The event log said it cannot connect to the STS_Config database so I checked to see if there is a STS_Config database. Turned out it was there but the directory had been renamed to "Data Backup - 20060617111405". I copied the directory, renamed it to "Data" and the problem was solved. Make sure you have a "Data" directory in this folder: C:\Program Files\Microsoft SQL Server\MSSQL$SHAREPOINT.
If you have this event and are not able to view your companyweb page due to the error message "You are not authorized to view this page", please refer to the Microsoft article ME832880 for information on this problem.
The Sharepoint SQL database may not be registered in the SQL Server Enterprise Manager. By registering the Sharepoint database, the error will disappear. To register the database, open SQL Enterprise manager. Click the Server Group that should contain the Sharepoint database. Click Action and then click New SQL Server Registration. If the wizard appears, select that you no longer want to use the wizard for this operation.
In the dialog-box Registered SQL Server Properties, you should type the servername\Sharepoint in the Server field, and then select the proper options for that SQL server. Then click OK and after a short delay the Sharepoint database should appear in the Servergroup you selected in the Registered SQL Server Properties dialog-box.
This is what I did to resolve my issue. I started experiencing this problem after installing SP2 for Sharepoint services. To resolve the problem, disable the loopback check. Follow these steps:
1. Click Start, click Run, type regedit, and then click OK.
2. In the Registry editor, locate and then click the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa.
3. Right-click Lsa, point to New, and create a DWORD Value.
4. Type DisableLoopbackCheck, and then press Enter.
5. Right-click DisableLoopbackCheck, and then click Modify.
6. In the Value data box, type 1, and then click OK.
7. Quit the Registry editor, and then restart your computer.
See ME830342, ME833183, ME835225, ME840685, ME843184, ME867811, and ME900498 for information on how to fix this problem.
From a newsgroup post: "
Receive the following error in Application Log:
Source: Windows SharePoint Services 2.0
Event ID: 1000
Description: #50070: Unable to connect to the database STS_Config on SBS\SharePoint. Check the database connection information and make sure that the database server is running.
Timing issue. SharePoint Timer Service tried to contact SharePoint database while the SBS is rebooting, or shutting down.
You can safely ignore the error as long as you can access the SharePoint (http://companyweb). As a workaround, create DependOnService key in SPTimer:
Data: MSSQL$SHAREPOINT ”.
- Event description: "Microsoft SharePoint: Adding user "<user>" to OU "SharepointUsers" in domain "<domain>" FAILED with HRESULT 0x80004005" - From a newsgroup post: "Here is how I got it to work, Open Active Directory Users and Groups. In the View menu select “Advanced Features”. Right click on the OU you want WSS to manage and select “Delegate Control”. Assign the user that runs your applications pools "Create, delete and manage user accounts" and "Read all user information" rights. Then right click on the OU again and select “Properties”. Under the Security tab highlight the same user and assign it Read, Write, Create and Delete access".
- Event description: "Request failed" - From a newsgroup post: From your description, it seems your Sharepoint data is corrupt. If so, you might have to reinstall the intranet component on SBS 2003. You can strictly follow the steps below.
Generally speaking, if you want to completely reinstall companyweb on SBS 2003 SP1, you need to follow the article ME829114 below, but it might ask you to insert the SBS SP1 CD3, so you need to extract SBS SP1 installation folders, and then point the SBS Integrated setup program to the folder for the 'SP1 CD3' contents. The extraction process is listed below, please do follow the exact steps or the extracted files will be removed:
1. Start a cmd prompt and change directory to the SP1 download folder (or the SBS03_SP1 folder on PKG_CD2).
2. Then type "<path>\SBS2003-KB885918-SP1-X86-ENU.EXE /x" (with no quotation marks) and press Enter.
3. Specify a path for the extracted files (such as C:\SBSSP1).
4. Run the SBS Integrated setup, and when the setup program prompts for the CD3, point it to the folder created above.
We also have a KB article, which can be used to backup and restore companyweb data; it might be useful to you in the future. The article is ME829113.
As I know, on SBS 2003 we have a document that can make a full backup and restore for the whole system. Please follow the article to backup your system to prevent any unexpected issue in future. The article is called “Backing Up and Restoring Windows Small Business Server 2003“.
- Event description: "#96013 Time-out occurred" - This problem might appear if you upload big files to the server. Read McAfee Solution ID: kb41204 for additional information on this particular problem. Search for kb41204 on the McAfee Knowledge Search page to find the solution.
- Event description: "#50070 "Unable to connect to the database" - Read McAfee Solution kb43607 on the McAfee Knowledge Search page.
I received this exact error and I was not able to browse to the SharePoint Services web site. I Opened up SQL Enterprise manager and saw that the STS Database was in single user mode (must have occurred during database backup). I removed the access restrictions in the database “Options” section and that resolved the issue.
|Private comment: Subscribers only. See example of private comment|
|Links: Backing Up and Restoring Windows Small Business Server 2003, McAfee Knowledge Search, Chris Gideon WebLog, Is the SQL Server is in the domain?|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
|Custom search for *****: Google - Bing - Microsoft - Yahoo|
Send comments or solutions
- Notify me when updated