The whole storm of unknown errors while restarting my Sharepoint Server 2010?

Question

Well, these are errors that I cannot undo at all. So I was hoping you had an idea.

When I recently rebooted my server (the server is a home computer and only runs Windows 7 as a development machine) with Sharepoint 2010, a whole list of problems arose.

The main mistake was that when I deployed the Visual Studio 2010 project, it was not able to activate my function. This happens more often because I sometimes messed up in the function activation event handler. But when this happens, I can access the site and debug the error when activating the function manually.

However, this time it was different. My site didn’t even want to run? So I checked the IIS manager and said that the site was stopped. When starting manually, the following error occurred:

The process cannot access the file because it is being used by another process. (Exception from HRESULT: 0x80070020) 

I have no idea what this can mean? Which file? Web.config? I really do not know.

But I saw that the central administration of Sharepoint is working, so I decided to check there. However, this led to even more errors, well, there was one, but it really scared me:

 Cannot connect to the configuration database. 

Thus, not only my web server has errors, but also my database server. Checking event logs is what I thought.

And I'm a little stunned. There are so many mistakes, I don’t even know where to start. I'm just going to copy the ones that I think are important.

Unknown exception SQL -1. Additional error information from SQL Server is provided below. When connecting to SQL Server, a network-related or specific instance error occurred. The server was not found or was not available. Verify the instance name is correct and configure SQL Server to connect remotely. (provider: SQL network interfaces, error: 26 - server / instance location error)

The Sharepoint Foundation seems to be giving me this.

The World Wide Web Publishing Service (WWW service) did not register the URL prefix http: // *: 80 / for the site 908852174. The site was down. The data field contains the error number.

IIS-W3SVC seems to give me this.

I really don't know what could be. Since I cannot access the Central Administration, I cannot check for any health problems.

Anyone have any idea? I didn’t do anything funny, I believe. I thought it could be the updates that were installed, but the only installed updates were:

Security Update for the Microsoft Visual C ++ 2005 Redistributable Package Service Pack 1 (KB973923)

Update for Microsoft Security Essentials Update - KB972696 (Definition 1.93.855.0)

Definition Update for Microsoft Security Essentials - KB972696 (Definition 1.93.1040.0)

Definition update for Microsoft Security Essentials - KB972696 (definition 1.93.1148.0)

So that really could not be so. I have no ideas, and I really would like to solve this problem.

Thanks,

Mats

EDIT: Okay, I manually started the SQL service, and now the Central Administration is working. But the health reporting site began to scare me. There is a list of 8 items that require my attention.

NT AUTHORITY \ NETWORK SERVICE, the account used for the SharePoint Timer service and Central Administration site, is highly privileged and should not be used for any other services on any computers in the server farm. The following services were found to use this account: SharePoint - 80 (application pool) SPUserCodeV4 (Windows service) OSearch14 (Windows service) Web Analytics data processing service (Windows service)

All required products must be installed on all servers in the farm, and all products must have the same patch and update levels in the farm. An update is required on the MATS-PC server. Without an update, the server is not in a supported state.

The following databases have versions that are older than the current SharePoint software but are in the backward compatible range: SharePoint_Config_c5681991-3bec-45b3-9376-ea8c19c51b6a, SharePoint_AdminContent_39d0c8e9-214e-42b9-909e-ffbe414720_bss_stb, WSS, WSS, WSS, WSS, WSS, WSS, WSS.

Those that seemed most important. Hectometer I have no idea? Especially about modernization? I haven’t updated anything recently.

Answer 1

Especially about modernization? I haven’t updated anything recently.

This is similar to a Microsoft update. Service packs for SQL Server are included with Microsoft Update, and if you apply those that are not checked carefully, some of them create similar symptoms for what you are describing. SQL Server may take longer, and when that happens, sometimes antivirus software captures MDF / LDF files for scanning. This will cause the databases to be unavailable and other services to crash at startup.

When you start SQL manually, everything starts working again, but now you have problems with version dependency. However, you are lucky that SQL even starts, but I had clients with problems when SQL did not start after careless SP applications if, for example, they changed the SA login.

Answer 2

Errors that you received during the reboot, just because SQL Service did not start. No database = no SharePoint. It happens to me all the time.

Other messages in Central Administration have nothing to do with your SQL startup and most likely they have been there for some time.

Like any other developer on the same hosting server, you have the right to use one powerful account. The central administrator now detects this and gives you a warning.

It looks like the SharePoint versions of one or more of your server’s databases are not in sync with the 2010 version? It’s not entirely accurate how he got into this state, but for the dev box I wouldn’t be completely shy. Perhaps upgrading to a new service pack will be resolved.