I had SQL Server 2016 in one of our servers, then I decided to install SSIS AND SSAS for Bi purpose, and I tried to install these two services (SSAS AND SSRS) in another instance.
After installing the second Instance, I noticed that: I can't connect to the first instance SQL databases (It has been somehow replaced by the second instance).
I get this message when I connect to database:
I get this message while restarting the service:
In SQL Server configuration manager there no service for the first Instance:
That's the last records in my SQL log file:
2020-08-23 14:46:11.87 Backup RESTORE DATABASE successfully processed 96898 pages in 21.859 seconds (34.631 MB/sec).
2020-08-23 17:35:02.25 Server SQL Server is terminating because of a system shutdown. This is an informational message only. No user action is required.
2020-08-23 17:35:02.32 spid12s Always On: The availability replica manager is going offline because SQL Server is shutting down. This is an informational message only. No user action is required.
2020-08-23 17:35:02.53 spid40s Service Broker manager has shut down.
2020-08-23 17:35:02.53 spid40s Error: 17054, Severity: 16, State: 1.
2020-08-23 17:35:02.53 spid40s The current event was not reported to the operating system error log. Operating system error = (null). You may need to clear the operating system error log if it is full.
2020-08-23 17:35:02.53 spid12s .NET Framework runtime has been stopped.
2020-08-23 17:35:09.04 spid12s [INFO] Database ID: [18]. Cleaning up StorageArray. LastClosedCheckpointEndTs: '55'
Questions:
How can I get back to my previous state of SQL Server (the mdf and ldf files exist in their location but I can't find masterdb files)?
Is there a way to restore users and SQL jobs?
Just installed SQLServer (Express edition, ver. 14.0.3030) on Ubuntu 16.04.3.
Usual operations work without errors: client connections and queries, AD integrated logins, backup/restores.
I can't show logs with SSMS (ver. 17.8.1) from Windows 10 Pro 1709 x64: expanding "Management" --> "SQL Server Logs" I get the following error:
TITLE: Microsoft SQL Server Management Studio
------------------------------
Failed to retrieve data for this request. (Microsoft.SqlServer.Management.Sdk.Sfc)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&LinkId=20476
------------------------------
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)
------------------------------
A severe error occurred on the current command.
The results, if any, should be discarded. (Microsoft SQL Server, Error: 0)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&ProdVer=14.00.3030&EvtSrc=MSSQLServer&EvtID=0&LinkId=20476
A search on Google lead to posts that suggested to run sys.xp_readerrorlog.
Here's the output:
EXEC sys.xp_readerrorlog
Msg 22004, Level 16, State 1, Line 0
Failed to open loopback connection. Please see event log for more information.
Msg 22004, Level 16, State 1, Line 0
Error log location not found.
SQLServer logs in /var/opt/mssql/log show nothing interesting.
Any suggestion?
UPDATE: tried connecting both with SQL authentication and Integrated AD authentication: same error.
I have 2 SQL Server instances on my PC, MSSQLSERVER2012 and SQLEXPRESS2014 and both of them were working properly.
But suddenly, both of them stopped and I can't run them again at all.
I get this error:
The request failed or the service did not respond in a timely fashion
I checked tcp/ip setting, even disabled tcp/ip of both instances.
I guessed it might be related to VIA protocol, but I can't see VIA protocol in my configuration manager.
I'll post the error log that SQL Server generates when it failed to start.
2017-05-17 22:24:07.77 Server Microsoft SQL Server 2012 -
11.0.2100.60 (X64) Feb 10 2012 19:39:15 Copyright (c) Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 6.2
(Build 9200: )
2017-05-17 22:24:07.77 Server (c) Microsoft Corporation.
2017-05-17 22:24:07.77 Server All rights reserved. 2017-05-17
22:24:07.77 Server Server process ID is 6044. 2017-05-17
22:24:07.77 Server System Manufacturer: 'System manufacturer',
System Model: 'System Product Name'. 2017-05-17 22:24:07.77 Server
Authentication mode is MIXED. 2017-05-17 22:24:07.77 Server
Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL
Server\MSSQL11.MSSQLSERVER\MSSQL\Log\ERRORLOG'. 2017-05-17 22:24:07.77
Server The service account is 'WORKGROUP\HAMED-PC$'. This is an
informational message; no user action is required. 2017-05-17
22:24:07.77 Server
Registry startup parameters:
-d C:\Program> Files\Microsoft SQL server\MSSQL11.MSSQLSERVER\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Log\ERRORLOG
-l C:\Program
Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2017-05-17 22:24:07.77 Server Command Line Startup Parameters:
-s "MSSQLSERVER" 2017-05-17 22:24:07.91 Server SQL Server detected 1 sockets with 4 cores per socket and 4 logical processors
per socket, 4 total logical processors; using 4 logical processors
based on SQL Server licensing. This is an informational message; no
user action is required. 2017-05-17 22:24:07.91 Server SQL Server
is starting at normal priority base (=7). This is an informational
message only. No user action is required. 2017-05-17 22:24:07.91
Server Detected 4087 MB of RAM. This is an informational message;
no user action is required. 2017-05-17 22:24:07.91
Server Using conventional memory in the memory manager.
2017-05-17 22:24:07.94 Server Error: 9694, Severity: 16, State:27.
2017-05-17 22:24:07.94 Server Could not start Service Broker manager. Check the SQL Server error log and the Windows error log for
additional error messages.
2017-05-17 22:24:07.94 Server Error: 9643, Severity: 16, State:1.
2017-05-17 22:24:07.94 Server An error occurred in the Service
Broker/Database Mirroring transport manager: Error: 9694, State: 27.
2017-05-17 22:24:07.94 Server Error: 9694, Severity: 16, State:
30.
2017-05-17 22:24:07.94 Server Could not start Service Broker
manager. Check the SQL Server error log and the Windows error log for
additional error messages.
2017-05-17 22:24:07.94 Server SQL Server Audit failed to record
the SERVER SHUTDOWN action.
Now I will appreciate if someone can help me start my SQL Server instances again
I have the same problem.
Suddenly the services do not work anymore.. I suspect a windows update did this.
Or new group policies that not allow this account to use resources?
Two errors in the Event Viewer:
The SQL Server (SQLEXPRESS) service failed to start due to the
following error: The service did not start due to a logon failure.
And
The MSSQL$SQLEXPRESS service was unable to log on as NT
Service\MSSQL$SQLEXPRESS with the currently configured password due to
the following error: Logon failure: the user has not been granted the
requested logon type at this computer.
Service: MSSQL$SQLEXPRESS
Domain and account: NT Service\MSSQL$SQLEXPRESS
This service account not have the required user right "Log on as a service."
User Action
Assign "Log on as a service" to the service account on this
computer. You can use Local Security Settings (Secpol.msc) to do this.
If this computer is a node in a cluster, check that this user right is
assigned to the Cluster service account on all nodes in the cluster.
If you have already assigned this user right to the service account,
and the user right appears to be removed, check with your domain
administrator to find out if a Group Policy object associated with
this node might be removing the right.
Hope this helps to get more information..
A solution I don't trust is removing he password of the user.
Go to Services > SQL Server (SQLEXPRESS) > Properties > Log On > Remove password
But I don't think this solution is a permanent solution.
If you find anything please let me know.
==================================================
Edit 1
We found the reason, my administrator pushed a group policy 'Log on as a service' which overruled my computer users.. and bad things started to happen.
He removed the policy and the original users returned. Everything works again after a 'gpupdate /force' in the command line.
You can find the group policy:
Start > Local Security Policy > Security Settings > Local Policies > User Right Assignment > Log on as a service. If the button 'Add User or Group' is grayed then the Admins are pushing this..
Good luck!
Jonas
I am implementing a replication from Oracle 12c server to SQL Server 2014 Enterprise Edition.
I have set up the Publisher successfully. .
I am bringing in 2 table elements into SQL Server. These contain date fields
Refer Date Field Mapping done on Publisher
The Subscription gets created fine and when the replication agent runs for the first time, I am facing following error:
Replication-Replication Distribution Subsystem: agent ServerName-TNSNAME-PublisherName-1 failed. The process could not bulk copy into table '"dbo"."Destinationtable"'.
The SQL Logs at C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log contain the minidump of the process when it failed. They mention that SQLSERVR.exe faced a fatal exception
Dump File: SQLDump0004.mdmp : C:\LOgs\SQLDump0004.mdmp
Last Write Time: 5/12/2016 11:02:15 PM
Process Name: sqlservr.exe : C:\Program Files\Microsoft SQL
Exception Code: 0xC0000005 Exception Information: The thread tried to
read from or write to a virtual address for which it does not have the
appropriate access. SqlDumpExceptionHandler: Process 66 generated
fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is
terminating this process.
Need help going past this error.
SQL Server has been working fine but since Friday I have not been able to connect to the database engine in SSMS. This coincided with my having to power the laptop off during a Windows update because it appeared to be hanging (I don't know if these two are related).
Since then I have:
Gone back to a restore point before the failed update
Removed SQL Server 2008 from my machine
Installed SQL Server 2012 onto my machine. This failed during the load
Removed everything that was labelled SQL Server from my machine
Redone the failed Windows updates
Installed SQL Server 2012 which again failed on load
Created a self-signed certificate (http://technet.microsoft.com/en-us/library/cc753127(v=WS.10).aspx)
Tried to start SQL Server from both Services and SSCM with no luck
Tried various log on options for SQL Server - under the local system the service will start but I still can't connect to the database engine in SSMS
Read endless posts and articles
Can anyone help me get SQL Server started on my machine, then connect to the database engine using SSMS?
The failure log for the installation gave the following information:
2013-03-05 12:17:37.34 Server Microsoft SQL Server 2012 (SP1) - 11.0.3128.0 (X64) Dec 28 2012 20:23:12 Copyright (c) Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
2013-03-05 12:17:37.34 Server (c) Microsoft Corporation.
2013-03-05 12:17:37.34 Server All rights reserved.
2013-03-05 12:17:37.34 Server Server process ID is 5116.
2013-03-05 12:17:37.34 Server System Manufacturer: 'SAMSUNG ELECTRONICS CO., LTD.', System Model: 'RV411/RV511/E3511/S3511/RV711'.
2013-03-05 12:17:37.34 Server Authentication mode is WINDOWS-ONLY.
2013-03-05 12:17:37.34 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2013-03-05 12:17:37.34 Server The service account is 'NT Service\MSSQLSERVER'. This is an informational message; no user action is required.
2013-03-05 12:17:37.35 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2013-03-05 12:17:37.35 Server Command Line Startup Parameters:
-s "MSSQLSERVER"
-m "SqlSetup"
-Q
-q "Latin1_General_CI_AS"
-T 4022
-T 4010
-T 3659
-T 3610
-T 8015
-T 902
2013-03-05 12:17:37.69 Server SQL Server detected 1 sockets with 2 cores per socket and 4 logical processors per socket, 4 total logical processors; using 4 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2013-03-05 12:17:37.69 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2013-03-05 12:17:37.69 Server Detected 6004 MB of RAM. This is an informational message; no user action is required.
2013-03-05 12:17:37.69 Server Using conventional memory in the memory manager.
2013-03-05 12:17:38.02 Server Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
2013-03-05 12:17:38.73 Server Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2013-03-05 12:17:38.75 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2013-03-05 12:17:38.75 Server Database Mirroring Transport is disabled in the endpoint configuration.
2013-03-05 12:17:38.76 Server Software Usage Metrics is disabled.
2013-03-05 12:17:38.92 spid4s Warning
******************
2013-03-05 12:17:38.92 spid4s SQL Server started in single-user mode. This an informational message only. No user action is required.
2013-03-05 12:17:39.07 spid4s Starting up database 'master'.
2013-03-05 12:17:39.66 Server CLR version v4.0.30319 loaded.
2013-03-05 12:17:40.35 spid4s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2013-03-05 12:17:40.38 spid4s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2013-03-05 12:17:41.33 spid4s SQL Trace ID 1 was started by login "sa".
2013-03-05 12:17:41.60 spid4s Server name is 'E2E-LAPTOP'. This is an informational message only. No user action is required.
2013-03-05 12:17:41.82 spid12s Password policy update was successful.
2013-03-05 12:17:41.87 spid12s Error: 17190, Severity: 16, State: 1.
2013-03-05 12:17:41.87 spid12s Initializing the FallBack certificate failed with error code: 1, state: 20, error number: 0.
2013-03-05 12:17:41.87 spid12s Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
2013-03-05 12:17:42.00 spid12s Error: 17182, Severity: 16, State: 1.
2013-03-05 12:17:42.00 spid12s TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property.
2013-03-05 12:17:42.00 spid12s Error: 17182, Severity: 16, State: 1.
2013-03-05 12:17:42.00 spid12s TDSSNIClient initialization failed with error 0x80092004, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Cannot find object or property.
2013-03-05 12:17:42.00 spid12s Error: 17826, Severity: 18, State: 3.
2013-03-05 12:17:42.00 spid12s Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
2013-03-05 12:17:42.00 spid12s Error: 17120, Severity: 16, State: 1.
2013-03-05 12:17:42.00 spid12s SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
7th March 2013: I have now side stepped this problem by installing SQL Server on a shiny new Windows 8 laptop (using exactly the same procedure as I tried on the errant machine). When I have the energy I will come back and see if I can resolve this problem on my other machine. If I have any success I will update this post.
A colleague into a similar problem - with pretty much the same error log. Turned out the root cause was his attempt to install SQL server on a domain controller using a system account. If you MUST install SQL server on domain controller, let SQL server service run under a network account.
https://support.microsoft.com/en-us/kb/2032911
BACKUP YOUR REGISTRY
THIS IS ONLY AN OPTION - AND GENERALLY A LAST RESORT - WEIGH THE CONSEQUENCES ON YOUR OWN
DO NOT TAKE THIS ADVICE AS THOUGH I HAVE SEEN YOUR REGISTRY AND KNOW THE EXACT STATE OF YOUR MACHINE
In short, the very first error you're seeing:
2013-03-05 12:17:41.87 spid12s Error: 17190, Severity: 16, State: 1.
2013-03-05 12:17:41.87 spid12s Initializing the FallBack certificate failed with error code: 1, state: 20, error number: 0.
is surrounding issues with keys that already exist in your registry. So, do what I said first, backup your registry, and then delete the key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server
and then try to reinstall Microsoft SQL Server 2012. If this doesn't work - you're probably going to need to backup your machine data and rebuild it.
Your error seems to have to do with the certificate you installed.
This article suggests changing the service the SQL server will log in as, you can do this at install, or via the surface configuration management tool.
http://social.msdn.microsoft.com/Forums/en-US/sqlsecurity/thread/56f14665-3f00-41ff-b002-bb5e86b3f219/
I know it's probably too late to help with the original poster, but we had this same issue and nothing we tried resolved the problem. Finally, we opened a technical incident with Microsoft and this is the solution that we were provided:
Take backup of below registry key.
HKLM\SOFTWARE\Microsoft\Cryptography\MachineGuid
This key should ideally have the GUID of the machine without curly braces, so {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx} becomes xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
Then delete the braces.
Try to reboot and start the SQL service . If service don’t start then Uninstall and reinstall SQL.
The above solution worked on two separate machines exhibiting this problem.
Just saw this post, in short, you will need to apply the Service packs and the cumulative updates for it to work, on newer operating systems the SSL certificates are being changed to disable SSL2, SSL3, etc. using the newer TLS1.2 and SQL Server is not supporting it out of the gate, you need to apply the patches to enable its support and it will work again.