holcomb_frank
asked on
SBS 2011 Sharepoint problems
Recently we started getting multiple errors in our event logs, both system and application, related to SharePoint. And coincidently our backups stopped working at the same time.
e have an SBS 2011 server setup using the wizards, nothing special, and we do host our own email using Exchange. We do not use SharePoint however.
We started getting this error in our application logs;
SQL Database 'SharePoint_ConfigurationD
Cannot open database "SharePoint_ConfigurationD
What is the default password for the user spfarm on an SBS 2011 server? We didn't create or change one, so we are not sure what this would be?
We also get this error in our system logs;
The SharePoint 2010 Timer service terminated unexpectedly. It has done this x time(s). The following corrective action will be taken in 30000 milliseconds; Restart the service.
Everything else seems to be working fine. We would like to correct these errors and get our log files back to be clean again. Any suggestions would be greatly appreciated.
e have an SBS 2011 server setup using the wizards, nothing special, and we do host our own email using Exchange. We do not use SharePoint however.
We started getting this error in our application logs;
SQL Database 'SharePoint_ConfigurationD
Cannot open database "SharePoint_ConfigurationD
What is the default password for the user spfarm on an SBS 2011 server? We didn't create or change one, so we are not sure what this would be?
We also get this error in our system logs;
The SharePoint 2010 Timer service terminated unexpectedly. It has done this x time(s). The following corrective action will be taken in 30000 milliseconds; Restart the service.
Everything else seems to be working fine. We would like to correct these errors and get our log files back to be clean again. Any suggestions would be greatly appreciated.
ASKER
No they do not use the company web, but it's also not loading..... going to http://companyweb we get the following error. "Cannot connect to the configuration database"
When I load the Windows Powershell , it loads the SharePoint module already which I was able to confirm. So then trying your suggestion...it ask that I supply values for the following parameters: ExistingPassword: So this just errors out. Any other suggestions?
When I load the Windows Powershell , it loads the SharePoint module already which I was able to confirm. So then trying your suggestion...it ask that I supply values for the following parameters: ExistingPassword: So this just errors out. Any other suggestions?
Hm,
did never get this error before.
Could you please try the steps mentioned in the MS blog entry to repair the managed SharePoint accounts?
http://blogs.technet.com/b/sbs/archive/2011/08/17/http-error-503-accessing-company-web-on-sbs-2011-standard.aspx
HTH
Rainer
did never get this error before.
Could you please try the steps mentioned in the MS blog entry to repair the managed SharePoint accounts?
http://blogs.technet.com/b/sbs/archive/2011/08/17/http-error-503-accessing-company-web-on-sbs-2011-standard.aspx
HTH
Rainer
ASKER
Rainer,
I tried the suggested steps.... From a shell.... Repair-SPManagedAccountDep
Cannot access the local farm. Verify that the local farm is configured, currently available, and that you have the appropriate permissions to access the database before trying again.
I tried the suggested steps.... From a shell.... Repair-SPManagedAccountDep
Cannot access the local farm. Verify that the local farm is configured, currently available, and that you have the appropriate permissions to access the database before trying again.
Hi,
have you explicitly started the SharePoint Management Shell with "Run as Administrator"?
have you explicitly started the SharePoint Management Shell with "Run as Administrator"?
ASKER
Rainer,
Just to be clear..... I start the Windows Powershell , with "Run as Administrator" .... and I can see it load the SharePoint Management Shell commandlet as it loads. And if I try to start or install a SP Management Shell it tells me it's already running. So I'm assuming it is....it takes the commands. And yes to answer your question I'm using " Run as Administrator". If I don't it won't let the SP Management Shell and it doesn't take my commands. This is outside my usual work... so feel free to correct my procedure if I'm incorrect here.
Just to be clear..... I start the Windows Powershell , with "Run as Administrator" .... and I can see it load the SharePoint Management Shell commandlet as it loads. And if I try to start or install a SP Management Shell it tells me it's already running. So I'm assuming it is....it takes the commands. And yes to answer your question I'm using " Run as Administrator". If I don't it won't let the SP Management Shell and it doesn't take my commands. This is outside my usual work... so feel free to correct my procedure if I'm incorrect here.
Hi,
no thats right. But most persons which are unfamiliar with SharePoint run PowerShell with an administrative account but not with the extra "Run as Admin" and therefore get errors when executing SharePoint PowerShell commands.
As my SBS 2011 experience is that old, I just try to eliminate issues of this kind :-)
I have to have a look - will take some time until I am at home.
KR
Rainer
no thats right. But most persons which are unfamiliar with SharePoint run PowerShell with an administrative account but not with the extra "Run as Admin" and therefore get errors when executing SharePoint PowerShell commands.
As my SBS 2011 experience is that old, I just try to eliminate issues of this kind :-)
I have to have a look - will take some time until I am at home.
KR
Rainer
This is a pretty easy fix if the problem is as I suspect. There is a command that must be run on the SBS server every time you install a sharepoint update
https://social.technet.microsoft.com/Forums/en-us/94c5f178-f020-4d0f-ba7c-11c415d0d862/manually-running-psconfig-is-required-after-installing-sharepoint-foundation-2010-updates?forum=smallbusinessserver
1. Open an Administrative command prompt.
2. Change directory to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN
3. Run PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures
https://social.technet.microsoft.com/Forums/en-us/94c5f178-f020-4d0f-ba7c-11c415d0d862/manually-running-psconfig-is-required-after-installing-sharepoint-foundation-2010-updates?forum=smallbusinessserver
1. Open an Administrative command prompt.
2. Change directory to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN
3. Run PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures
ASKER
Chris,
A couple of things first I wanted to share..... no pun intended. I checked the updates and I don't see SP 1 for SharePoint listed as an installed update in control panel. I also checked the updates in the SBS Console..... SP2 for SharePoint is an available update to install though.
Trying your suggestion - running PSConfig.exe I get the following.....
Waiting to get a lock to upgrade the farm.
Failed to initialize SharePoint Products upgrade.
An exception of type System.Data.SqlClient.Sqql
Login failed for user 'Domain\Admin'.
Total number of configuration settings run: 1
Total number of successful configuration settings: 0
Total number of unsuccessful configuration settings: 5
Successfully stopped the configuration of SharePoint Products.
Configuration of SharePoint Products failed. Configuration must be performed before you use SharePoint Products. For further details, see the diagnostic log located at ........\Logs\PSCDiagnosti
It didn't work , and the /companyweb is still not working.....
It did stop all the SharePoint services on the server as well as the World Wide Web Publishing Service.... had to go on site to restart the services .
A couple of things first I wanted to share..... no pun intended. I checked the updates and I don't see SP 1 for SharePoint listed as an installed update in control panel. I also checked the updates in the SBS Console..... SP2 for SharePoint is an available update to install though.
Trying your suggestion - running PSConfig.exe I get the following.....
Waiting to get a lock to upgrade the farm.
Failed to initialize SharePoint Products upgrade.
An exception of type System.Data.SqlClient.Sqql
Login failed for user 'Domain\Admin'.
Total number of configuration settings run: 1
Total number of successful configuration settings: 0
Total number of unsuccessful configuration settings: 5
Successfully stopped the configuration of SharePoint Products.
Configuration of SharePoint Products failed. Configuration must be performed before you use SharePoint Products. For further details, see the diagnostic log located at ........\Logs\PSCDiagnosti
It didn't work , and the /companyweb is still not working.....
It did stop all the SharePoint services on the server as well as the World Wide Web Publishing Service.... had to go on site to restart the services .
I suggest that you check out this blog from the SBS product team regarding the sp passwords. I suspect with the previous instructions provided to you, that passwords are horked up a bit
ASKER
Chris,
As mentioned previously in this thread..... I did try the suggestion here as well....
"I tried the suggested steps.... From a shell.... Repair-SPManagedAccountDep
Cannot access the local farm. Verify that the local farm is configured, currently available, and that you have the appropriate permissions to access the database before trying again. "
So while it may indeed be an issue with passwords not syncing or out of whack as it is.... this method is not working to try to resolve it....
As mentioned previously in this thread..... I did try the suggestion here as well....
"I tried the suggested steps.... From a shell.... Repair-SPManagedAccountDep
Cannot access the local farm. Verify that the local farm is configured, currently available, and that you have the appropriate permissions to access the database before trying again. "
So while it may indeed be an issue with passwords not syncing or out of whack as it is.... this method is not working to try to resolve it....
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
the SharePoint accounts are created dynamically with managed Passwords - so you never know them.
Normally SharePoint takes care the the Passwords are updated on a regular base and that they are then synced.
You might try to run the following PowerShell command inside of a "SharePoint Management Shell":
Open in new window
You are not using Company Web?
HTH
Rainer