asked on

SharePoint Foundation error 5057 5059

I have a SharePoint Foundation site for our intranet. Port 80 is the default site and it is running fine. I also have other sites on the same server using ports 8001, 8002 etc for specific departments. None of those will run. I get "HTTP Error 503. The service is unavailable." when I go to the site. The application pools for some of these subsites show they are stopped. I can start the pool but it won't stay started.

I am using a custom account and the logon and password are valid, I can log onto a PC with them and nothing has changed on them recently. If I change the Identity under Process Model for one of the pools then the error for the site changes to 'Cannot find configuration database'.

I am seeing event IDs 50, 5021, 5057 and 5059 in System, and 6398, 3760 and 5586 in Application.

LarryDAH

ASKER

The Central Config for my SP server shows this also:

Title Databases running in compatibility range, upgrade recommended.
Severity 2 - Warning
Category Configuration
Explanation The following databases have versions that are older than the current SharePoint software, but are within the backwards compatible range:

... all my subsites are listed

Remedy To achieve optimal results from these databases, use Upgrade-SPContentDatabase to upgrade Content databases, or psconfig.exe to upgrade other databases. For more information about this rule, see "http://go.microsoft.com/fwlink/?LinkID=142697".
Failing Servers
Failing Services SPTimerService (SPTimerV4)

LarryDAH

ASKER

I check my SQL server and I have SQL 2008 R2 SP1. Will installing SP2 fix the problem, or at least get rid of the warning in SP Health Check?

ASKER CERTIFIED SOLUTION

Mohit Nair

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

LarryDAH

ASKER

Thanks, found that it did want to upgrade but it fails, gives me this towards end of log:

<snip>

04/15/2014 08:32:12 11 INF Setting the upgrade mode to inplace
04/15/2014 08:32:12 11 INF Leaving function TaskCommon.TraceToPsconfigLogAndUpgradeManagerLog
04/15/2014 08:32:12 11 INF Creating security token service application for this farm ...
04/15/2014 08:32:15 11 INF Successfully created security token service application
04/15/2014 08:32:15 11 INF Creating service connection point for this farm ...
04/15/2014 08:32:15 11 WRN Failed to add the service connection point for this farm
04/15/2014 08:32:15 11 INF Entering function StringResourceManager.GetResourceString
04/15/2014 08:32:15 11 INF Resource id to be retrieved is ServiceConnectionPointNotCreatedEventLog for language English (United States)
04/15/2014 08:32:15 11 INF Resource retrieved id ServiceConnectionPointNotCreatedEventLog is Unable to create a Service Connection Point in the current Active Directory domain. Verify that the SharePoint container exists in the current domain and that you have rights to write to it.
04/15/2014 08:32:15 11 INF Leaving function StringResourceManager.GetResourceString
04/15/2014 08:32:15 11 WRN Unable to create a Service Connection Point in the current Active Directory domain. Verify that the SharePoint container exists in the current domain and that you have rights to write to it.
Microsoft.SharePoint.SPException: The object LDAP://CN=Microsoft SharePoint Products,CN=System,DC=arkansasheritage,DC=org doesn't exist in the directory.
at Microsoft.SharePoint.Administration.SPServiceConnectionPoint.Ensure(String serviceBindingInformation)
at Microsoft.SharePoint.PostSetupConfiguration.UpgradeTask.Run()
04/15/2014 08:32:21 11 INF Entering function TaskCommon.TraceToPsconfigLogAndUpgradeManagerLog
04/15/2014 08:32:21 11 INF Spawing off the upgrade job
04/15/2014 08:32:21 11 INF Leaving function

</snip>

Not sure what the issue is, it was running fine last week.

LarryDAH

ASKER

Running the update will be a long term solution, but for the immediate fix I took my web server out of the domain and brought it back and all is well now.