August 24, 2015 at 7:05 pm
Hi All ,
This is pretty Urgent , I was patching SQL server and now I can’t start SQL server instance and SQL Server agent also can’t be started . Before patching SQL is fine
When I tried to connect to SQl server via Management studio it shows “ A network – related or instance – specific error occurred while establishing a connection to SQL server , The server was not found or was not accessible , Verify that the instance name is correct and that the SQL server is configured to allow remote connections (provider : named piped provider , error : 40 – Could not open a connection to SQL server “
I applied SP3 in SQL server 2008 R2 . TCP/IP is enable
Much appreciate on your kind help
Thank you
August 24, 2015 at 7:56 pm
guys i check in SQL log
it says " Database 'mssqlsystemresource' cannot be opened due to inaccessible files or insufficient memory or disk space."
How do i fix this please ?
August 25, 2015 at 12:51 am
Hi,
Is something happened during the SP installation? Do you have enough resources (mem, disk etc), did you check the db files?
Take a look in this article (and many others for this error message)
Basically this is your best shot (use the same version of SQL and SP):
I applied the Service Pack on another instance which completed successfully. Then I copied the mssqlsystemresource.mdf and mssqlsystemresource.ldf files from that instance and overwrote those files in the C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLData folder of the instance having trouble starting. And SQL Server started without any issues.
________________________________________________________________
"Accept conditions as they exist, or accept the responsibility for changing them."
August 25, 2015 at 1:07 am
It worked !!
I copy mdf and ldf from another server to this problematic server , I successfully start the engine and applied patching !!
August 25, 2015 at 9:41 am
mssqlresource is the same on every instance at a particular version. You can copy these over from instance to instance if they're corrupted or damaged.
August 26, 2015 at 7:17 pm
actually what is the benefit of having that db?
August 27, 2015 at 3:39 pm
The DB stores some internal SQL Server stuff. What, I'm not exactly sure, and why in a DB? No idea.
However it's a stable resource for a particular build.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply