Moss Error Cannot Connect To The Configuration Database
Contents |
22, 2011February 22, 2012 Mike Cantin Content Administrationconfiguration, database, error, firewall, named pipes, settings, tcp I was doing some testing and found out that our development servers went haywire and started randomly giving me that error. If I did
Cannot Connect To The Configuration Database. Sharepoint 2010 Central Admin
a refresh, it looks like sometimes it would go through and other times cannot connect to the configuration database. sharepoint 2013 it wouldn't. Here are a couple things to try out if you haven't already… 1. Verify that the SQL Services are
Cannot Connect To Configuration Database Sharepoint 2007
running on the database server. 2. Make sure the service account of the central administration app pool has dbo rights to the database. 3. Did you or someone change the service account password? Change webpartpageuserexception: cannot connect to the configuration database it back to the old password if you can. 4. Check your firewall settings. you should be able to ping the database server from your application or web servers, and vise versa. Make sure that the Inbound Rules have a Rule that states TCP port 1433 and UDP port 1434 open on your database servers. 5. Make sure Named Pipes is ON. Go to your SQL Server Configuration Manager cannot connect to the configuration database sharepoint 2007 central administration on your database server. Under your SQL Server Network Configuration, select your SharePoint instance (most of the time its the default instance). Make sure Named Pipes is enabled. Many people think this isn't necessary, but I've found it to be a must. 6. Another thing people miss is the TCP/IP ports. If you right click the TCP/IP protocol in the same setting as above, goto properties. Go to IP Addresses and make sure that the instance TCP Port on all IP1-IP5 is on 1433. If you have any other suggestions you would like to input, I'd be happy to add them from comments… 30.522658 -90.482741 Rate this:Share my blog! -Tweet Related Post navigation ← sps3 search crawl Error: "Access is denied. Verify that either the Default Content Access Account has access to this repository, or add a crawl rule to crawl this repository." PerformancePoint and KerberosWoes → Leave a Reply Cancel reply Enter your comment here... Fill in your details below or click an icon to log in: Email (required) (Address never made public) Name (required) Website You are commenting using your WordPress.com account. (LogOut/Change) You are commenting using your Twitter account. (LogOut/Change) You are commenting using your Facebook account. (LogOut/Change) You are commentin
for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers
Sbs 2011 Cannot Connect To The Configuration Database
or posting ads with us SharePoint Questions Tags Users Badges Unanswered Ask Question _ SharePoint sharepoint cannot connect to the configuration database sbs 2008 Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute: Sign up Here's how it
Verify That Iis Is Not Running In Iis 5.0 Isolation Mode
works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top “Cannot connect to the configuration database” Error while accessing Sharepoint Central Admin 2010 up vote 3 down vote favorite https://mikessharepoint.wordpress.com/2011/11/22/cannot-connect-to-the-configuration-database-error-of-central-administration/ I'm working with Sharepoint 2010. It was working perfectly until one day it didn't let me access the Sharepoint central admin. I found out that my Sharepoint service account and farm account (sp_farm and sp_serviceapp) in AD got deleted somehow. So I created the users again to see if it works. But whenever I try to access sharepoint central administration, I get the error saying "Cannot connect to the configuration database" . The SQL database (MSSQLSERVER) is running. http://sharepoint.stackexchange.com/questions/81333/cannot-connect-to-the-configuration-database-error-while-accessing-sharepoint I dont know what to do. Any help is greatly appreciated! 2010 share|improve this question asked Nov 7 '13 at 23:27 user20645 16112 do they have the same password as they did before? –Mike Nov 7 '13 at 23:31 1 If they were deleted and recreated, they'd have a different SID and not be the same wouldn't they? –Eric Alexander♦ Nov 7 '13 at 23:43 @PirateEric - You are correct Eric. A username is uniquely identified by its SID and its GUID. The SID is known to change when the user changes domain, while the GUID remains the same. See article SID vs. GUID –TempaC Nov 8 '13 at 8:44 fail back to server on always on if secondary is not synced and does not have config db stackoverflow.com/questions/8753197/… –imanabidi Jun 25 '15 at 7:30 add a comment| 3 Answers 3 active oldest votes up vote 2 down vote Do you have access to the SharePoint 2010 Management Shell? Because the SharePoint Farm Account got deleted and then recreated, the SID will probably be different. Because the SID in Central Admin and the Configuration Database don't match, they are considered different users. You might regain access by making sure the SID in Central Admin is the same as the SID of the account that has access to the Configuration Database In the SharePoint
happened a couple of times that the computer hangs and the Sharepoint Configuration dabatase remains in a corrupted state. When I try to access the Sharepoint local site from the browser it gives the following error: Cannot connect to the configuration database. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: Microsoft.SharePoint.WebPartPages.WebPartPageUserException: Cannot connect to the configuration database. So, how did I fix it? I first used this addselftosqlsysadmin.cmd script to add my account to the SQLServer sysadmin group. Then performed the following commands from SQL Server Management Studio: select state_desc from master.sys.databases where name = 'SharePoint_Config_5ffca14b-db6f-4b30-9dd8-8317ee0f4f45' The result was: SUSPECT, confirming we had a problem. Then run: ALTER DATABASE [SharePoint_Config_5ffca14b-db6f-4b30-9dd8-8317ee0f4f45] SET EMERGENCY; GO ALTER DATABASE [SharePoint_Config_5ffca14b-db6f-4b30-9dd8-8317ee0f4f45] SET SINGLE_USER; GO DBCC CHECKDB ([SharePoint_Config_5ffca14b-db6f-4b30-9dd8-8317ee0f4f45] , REPAIR_ALLOW_DATA_LOSS) WITH NO_INFOMSGS, ALL_ERRORMSGS; GO ALTER DATABASE [SharePoint_Config_5ffca14b-db6f-4b30-9dd8-8317ee0f4f45] SET MULTI_USER; GO That’s it! I run the state_desc command again and this time it says: ONLINE Solved! 1 Comment Why care about data loss right? Cheers, Wes webbes - Monday, June 20, 2011 8:54:58 AM Comments have been disabled for this content. Terms Of Use - Powered by Orchard