would it be possible to configuration database(SharePoint_Config not content database) for mirroring?
View Complete Post
when i open my central administation i get this error:
Cannot connect to the configuration database
Recently I have migrated my SharePoint BackEnd (Database) Server to new hard drive. The reason of migration was to deploy and configure real time database replication by
Symantec Veritas. After migration activity I was getting following error message
" cannot connect to the configuration database ".
But when I execute following steps, this errors message gone and everything got fine
1. Enable Named Pipe from SQL Server Configuration Manager >
Protocols for MSSQLSERVER
SQL Server (MSSQLSERVER) service (Note: This service was already running and status was set to automatic ) and
3. Start SharePoint Configuration Wizard
Now I need to know why every time I have to restart this service?
When I turned on my sharepoint server machines in the moring I have to restart this service ( SQL Server (MSSQLSERVER) otherwise same error message appears (cannot connect to the configuration database). After restarting this service everything
Any help in this regard will be greatly appreciated.
I have just recently installed a standalone instance of SharePoint 2010 on Windows 7 64-bit. Everything was working fine, however, as part of joining my computer to the domain, my computer was renamed. Now that the computer has been renamed,
I am no longer able to connect to my locally installed SharePoint instance. I receive an error message stating "Cannot connect to the configuration database."
I found this article on renaming a server for SharePoint Foundation:
http://technet.microsoft.com/en-us/library/cc288510.aspx. However, it seems like the article is assuming that the rename operation occurred while SharePoint was still running. However, I am running SharePoint Portal Server 2010 and now that
I cannot connect to the configuration database, I cannot make any alterations to the SharePoint instance at all.
In addition, my instance of SQL Server as well as the standalone SharePoint instance was installed prior to the computer rename. What are the steps that are required to address this situation?
We have a brand new installation of Windows Server 2008 R2, SQL Server 2008 R2, and SharePoint 2010, and configuration of SharePoint 2010 at end of installation.
So far after all of this was installed the only thing we've accomplished so far is this:
Accessing the website: 503 Service Unavailable.
Accessing admin site: 503 Service Unavailable and/or Cannot connect to configuation database.
I've installed teh recommended hotfixes. I've rebooted. I've reconfigured to ensure it was hitting the right database and everything else. Googled and searched here, ALL to no avail.
Suggestions? I'm at my wits end and won't spend another second on what, but all appearances, is turning out to be a crappy product that our company spent thousands on. I've had better luck (100% success) running just the services.
When installing Sharepoint, I accidentally selected to install it as a SQLEXPESS server located at ComputerName\Sharepoint and didn't notice. When my site hit the 4 gig limit, I moved the content database to another server quite easily.
Now I'm wondering if it is best practice to make sure that everything is on the same server. Poking around in Central Administration I notice quite a few references to the Sharepoint server, and then my Content Database which is off on it's own. Is there
an easy way to migrate everything over to my new server (a cursory glance around google hasn't turned up anything yet) or should I leave it fragmented as it is?
I'm not sure if this is the right place to ask this. If I am creating a website that will host a service for multiple companies, should I create separate databases for each company or host them all on one database and just keep track of them in code?
I have a three server environment – T1 – a domain controller and T2 and T3 for SharePoint and SQL Server 08 and respectively, where each is a virtual machine.
These servers are on a domain separate from our company domain.
While installing sharepoint on t2, I get the following error at the step that creates a config database (on T3 SQL Server)
Failed to create the configuration database.
An exception of type System.SystemExcep
I know this has been a common issue in the past after updates, patches, SPs etc. Tried several of the online "cures" no luck. I've got a standalone instance of WSS 3.0. Anyone else with this issue after yesterday's updates? If so, any luck?
Update: ran WSS 3.0 configuration wizard, held my breath, and voila it worked!
The database server which our sharepoint installation is currently using is going to be shutdown and a new one is going to be put in production.
I read in some post that the configuration database cannot be moved (while the same operation type is documented for content database). Is this correct?
Isn't there a way by which I can modify my current moss installation to define the use of another sql server for configuration (and then later for content) databases?
Any other workaround or procedure?
After an IIS reset or rebooting the machine.ÃÂ If I then open up a sharepoint website the message isÃÂ Cannot connect to the configuration database. as detailed belowÃÂ
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.Source Error:
I tried re-running the configuration Wizard to no avail. I can't even get to the Central Admin page. When running the config wizard it tells me that it can't connect to the farm (it's a standalone install) and to disconnect from the farm to continue.
I disconnected from the farm and now it says that it can't get to the config database.
Running psconfig -cmd upgrade -inplace b2b and I get this error message:
No connection string to a WSS configuration database detected.
I'm at a loss.
I have an existing sp 2010 enterprise server hosting websites and central administration. I have a seperate sql 2008 r2 server holding the databases. My goal is to setup another sp 2010 enterprise server to provide redundancy for the websites
and central admin. I believe I am able to accomplish this by adding another web front end to the farm. On the second server, I install sp 2010, run the config wizard and connect to the config database located on the sql server, however, I
am interrupted at step 3 when I am notified of the following:
Failed to connect to the configuration database.
An exception of type System.InvalidOperationException was thrown. Additional exception information: There was an error encrypting or decrypting credentials. Either a credential update is currently being performed, or you must update the farm account credentials
on this server before you can perform this task.
System.InvalidOperationException: There was an error encrypting or decrypting credentials. Either a credential update is currently being performed, or you must update the farm account credentials on this server before you can perform this task.