I removed old sql server from PC. Then I installed new sql server. After this sql server service doesn't start. When I am running service from sql server config manager - I receive error msg:
"The request failed or the service did not respond in a timely
fashion. Consult the event log or other applicable error logs for
details."
this command: sqlservr.exe -s MSSQL -e C:\1.txt returned logs:
2017-05-09 18:32:55.05 Server Microsoft SQL Server 2016 (RTM) - 13.0.1601.5 (X64)
Apr 29 2016 23:23:58
Copyright (c) Microsoft Corporation
Enterprise Edition (64-bit) on Windows 10 Enterprise 6.3 <X64> (Build 10586: )
2017-05-09 18:32:55.05 Server UTC adjustment: 3:00
2017-05-09 18:32:55.05 Server (c) Microsoft Corporation.
2017-05-09 18:32:55.05 Server All rights reserved.
2017-05-09 18:32:55.05 Server Server process ID is 7956.
2017-05-09 18:32:55.05 Server System Manufacturer: 'ASUSTeK COMPUTER INC.', System Model: 'X550JX'.
2017-05-09 18:32:55.06 Server Authentication mode is WINDOWS-ONLY.
2017-05-09 18:32:55.06 Server Logging SQL Server messages in file 'C:\1.txt'.
2017-05-09 18:32:55.06 Server The service account is 'USER-PC\User'. This is an informational message; no user action is required.
2017-05-09 18:32:55.06 Server Command Line Startup Parameters:
-s "MSSQL"
-e "C:\1.txt"
2017-05-09 18:32:55.06 Server Error: 17113, Severity: 16, State: 1.
2017-05-09 18:32:55.06 Server Error 3(The system cannot find the path specified.) occurred while opening file 'master.mdf' to obtain configuration information at startup. An invalid startup option might have caused the error. Verify your startup options, and correct or remove them if necessary.
2017-05-09 18:32:55.07 Server SQL Server shutdown has been initiated
I tried to add permissions for windows user, local system and local service but it didn't help.
The error log gives you the information about the failure: Error 3(The system cannot find the path specified.) occurred while opening file 'master.mdf' to obtain configuration information at startup. An invalid startup option might have caused the error.
You should check your startup parameters.
Start Configuration Manager -> SQL Server Services -> your instance -> Properties -> Advanced -> Startup Parameters.
It should contain paths to master.mdf, mastlog.ldf and errorlog
Related
While trying to install SQL server 2016 in my machine I came across following error:
Msg 18456, Severity: 14, State: 38
Please have a look at the log:
2017-10-12 11:24:15.51 Server Microsoft SQL Server 2016 (SP1) (KB3182545) - 13.0.4001.0 (X64)
Oct 28 2016 18:17:30
Copyright (c) Microsoft Corporation
Express Edition (64-bit) on Windows 10 Enterprise 6.3 <X64> (Build 15063: )
2017-10-12 11:24:15.54 Server UTC adjustment: 5:30
2017-10-12 11:24:15.54 Server (c) Microsoft Corporation.
2017-10-12 11:24:15.54 Server All rights reserved.
2017-10-12 11:24:15.54 Server Server process ID is 4824.
2017-10-12 11:24:15.54 Server System Manufacturer: 'Dell Inc.', System Model: 'Precision Tower 7810'.
2017-10-12 11:24:15.54 Server Authentication mode is WINDOWS-ONLY.
2017-10-12 11:24:15.54 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL13.SQLEXPRESS\MSSQL\Log\ERRORLOG'.
2017-10-12 11:24:15.54 Server The service account is 'NT Service\MSSQL$SQLEXPRESS'. This is an informational message; no user action is required.
2017-10-12 11:24:15.55 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL13.SQLEXPRESS\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL13.SQLEXPRESS\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL13.SQLEXPRESS\MSSQL\DATA\mastlog.ldf
2017-10-12 11:24:15.55 Server Command Line Startup Parameters:
-s "SQLEXPRESS"
2017-10-12 11:24:17.64 Server SQL Server detected 2 sockets with 6 cores per socket and 6 logical processors per socket, 12 total logical processors; using 4 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2017-10-12 11:24:17.64 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2017-10-12 11:24:17.65 Server Detected 32692 MB of RAM. This is an informational message; no user action is required.
2017-10-12 11:24:17.66 Server Using conventional memory in the memory manager.
2017-10-12 11:24:18.14 Server Default collation: Latin1_General_CI_AI (us_english 1033)
2017-10-12 11:24:18.78 Server Buffer pool extension is already disabled. No action is necessary.
2017-10-12 11:24:19.62 Server InitializeExternalUserGroupSid failed. Implied authentication will be disabled.
2017-10-12 11:24:19.62 Server Implied authentication manager initialization failed. Implied authentication will be disabled.
2017-10-12 11:24:20.73 Server The maximum number of dedicated administrator connections for this instance is '1'
2017-10-12 11:24:20.75 Server This instance of SQL Server last reported using a process ID of 2476 at 12-10-2017 11:22:51 (local) 12-10-2017 05:52:51 (UTC). This is an informational message only; no user action is required.
2017-10-12 11:24:20.82 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.
2017-10-12 11:24:20.95 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.
2017-10-12 11:24:21.05 Server Database Instant File Initialization: enabled. For security and performance considerations see the topic 'Database Instant File Initialization' in SQL Server Books Online. This is an informational message only. No user action is required.
2017-10-12 11:24:21.38 Server Query Store settings initialized with enabled = 1,
2017-10-12 11:24:21.82 spid5s Starting up database 'master'.
2017-10-12 11:24:24.04 Server CLR version v4.0.30319 loaded.
2017-10-12 11:24:24.57 spid5s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2017-10-12 11:24:24.62 spid5s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2017-10-12 11:24:25.29 spid5s SQL Trace ID 1 was started by login "sa".
2017-10-12 11:24:25.38 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2017-10-12 11:24:25.41 spid5s Server name is 'I7724\SQLEXPRESS'. This is an informational message only. No user action is required.
2017-10-12 11:24:25.55 spid5s Starting up database 'msdb'.
2017-10-12 11:24:25.56 spid6s Starting up database 'mssqlsystemresource'.
2017-10-12 11:24:25.63 spid6s The resource database build version is 13.00.4001. This is an informational message only. No user action is required.
2017-10-12 11:24:25.99 spid6s Starting up database 'model'.
2017-10-12 11:24:26.22 spid10s A self-generated certificate was successfully loaded for encryption.
2017-10-12 11:24:26.23 spid10s Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQLEXPRESS ].
2017-10-12 11:24:26.24 Server Software Usage Metrics is disabled.
2017-10-12 11:24:26.24 spid10s Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$SQLEXPRESS\sql\query ].
2017-10-12 11:24:26.26 spid10s Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag 7806. This is an informational message only. No user action is required.
2017-10-12 11:24:26.26 spid10s SQL Server is now ready for client connections. This is an informational message; no user action is required.
2017-10-12 11:24:26.26 Server SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This is an informational message. No user action is required.
2017-10-12 11:24:26.37 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/I7724.ptcnet.ptc.com:SQLEXPRESS ] for the SQL Server service. Windows return code: 0x200b, state: 15. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered.
2017-10-12 11:24:26.40 spid6s Polybase feature disabled.
2017-10-12 11:24:26.40 spid6s Clearing tempdb database.
2017-10-12 11:24:27.04 spid6s Starting up database 'tempdb'.
2017-10-12 11:24:27.43 spid18s The Service Broker endpoint is in disabled or stopped state.
2017-10-12 11:24:27.43 spid18s The Database Mirroring endpoint is in disabled or stopped state.
2017-10-12 11:24:27.62 spid18s Service Broker manager has started.
2017-10-12 11:24:27.62 spid5s Recovery is complete. This is an informational message only. No user action is required.
2017-10-12 11:29:41.85 spid51 Attempting to load library 'xplog70.dll' into memory. This is an informational message only. No user action is required.
2017-10-12 11:29:41.98 spid51 Using 'xplog70.dll' version '2015.130.1601' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.
2017-10-12 11:49:26.09 Logon Error: 18456, Severity: 14, State: 38.
2017-10-12 11:49:26.09 Logon Login failed for user 'PTCNET\I7724$'. Reason: Failed to open the explicitly specified database 'WM'. [CLIENT: <local machine>]
But When I am trying to install SQL Server 2012 just to verify where could be the possible error, I am getting the below log and in this case I am able to install SQl Server 2012.
2017-10-12 15:31:05.57 Server Microsoft SQL Server 2012 - 11.0.2100.60 (Intel X86)
Feb 10 2012 19:13:17
Copyright (c) Microsoft Corporation
Express Edition on Windows NT 6.2 <X64> (Build 9200: ) (WOW64)
2017-10-12 15:31:05.57 Server (c) Microsoft Corporation.
2017-10-12 15:31:05.57 Server All rights reserved.
2017-10-12 15:31:05.57 Server Server process ID is 9680.
2017-10-12 15:31:05.57 Server System Manufacturer: 'Dell Inc.', System Model: 'Precision Tower 7810'.
2017-10-12 15:31:05.57 Server Authentication mode is WINDOWS-ONLY.
2017-10-12 15:31:05.57 Server Logging SQL Server messages in file 'C:\Program Files (x86)\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\Log\ERRORLOG'.
2017-10-12 15:31:05.57 Server The service account is 'PTCNET\I7724$'. This is an informational message; no user action is required.
2017-10-12 15:31:05.57 Server Registry startup parameters:
-d C:\Program Files (x86)\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\DATA\master.mdf
-e C:\Program Files (x86)\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\Log\ERRORLOG
-l C:\Program Files (x86)\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\DATA\mastlog.ldf
2017-10-12 15:31:05.57 Server Command Line Startup Parameters:
-s "SQLEXPRESS"
2017-10-12 15:31:05.84 Server SQL Server detected 2 sockets with 6 cores per socket and 6 logical processors per socket, 12 total logical processors; using 4 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2017-10-12 15:31:05.84 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2017-10-12 15:31:05.84 Server Detected 32692 MB of RAM. This is an informational message; no user action is required.
2017-10-12 15:31:05.84 Server Using conventional memory in the memory manager.
2017-10-12 15:31:05.96 Server This instance of SQL Server last reported using a process ID of 8320 at 10/12/2017 3:31:02 PM (local) 10/12/2017 10:01:02 AM (UTC). This is an informational message only; no user action is required.
2017-10-12 15:31:05.96 Server Node configuration: node 0: CPU mask: 0x0000000f:0 Active CPU mask: 0x0000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2017-10-12 15:31:05.97 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.
2017-10-12 15:31:05.99 Server Software Usage Metrics is disabled.
2017-10-12 15:31:06.00 spid4s Starting up database 'master'.
2017-10-12 15:31:06.07 Server CLR version v4.0.30319 loaded.
2017-10-12 15:31:06.18 spid4s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2017-10-12 15:31:06.18 spid4s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2017-10-12 15:31:06.19 spid4s SQL Trace ID 1 was started by login "sa".
2017-10-12 15:31:06.20 spid4s Server name is 'I7724\SQLEXPRESS'. This is an informational message only. No user action is required.
2017-10-12 15:31:06.21 spid4s Failed to verify Authenticode signature on DLL 'C:\Program Files (x86)\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\Binn\ftimport.dll'.
2017-10-12 15:31:06.21 spid9s Starting up database 'mssqlsystemresource'.
2017-10-12 15:31:06.21 spid4s Starting up database 'msdb'.
2017-10-12 15:31:06.23 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework\v4.0.30319\.
2017-10-12 15:31:06.27 spid9s The resource database build version is 11.00.2100. This is an informational message only. No user action is required.
2017-10-12 15:31:06.36 spid12s A self-generated certificate was successfully loaded for encryption.
2017-10-12 15:31:06.36 spid12s Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQLEXPRESS ].
2017-10-12 15:31:06.36 spid12s Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$SQLEXPRESS\sql\query ].
2017-10-12 15:31:06.36 spid12s Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag 7806. This is an informational message only. No user action is required.
2017-10-12 15:31:06.36 spid12s SQL Server is now ready for client connections. This is an informational message; no user action is required.
2017-10-12 15:31:06.36 Server SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This is an informational message. No user action is required.
2017-10-12 15:31:06.38 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/I7724.ptcnet.ptc.com:SQLEXPRESS ] for the SQL Server service. Windows return code: 0x200b, state: 15. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered.
2017-10-12 15:31:06.46 spid9s Starting up database 'model'.
2017-10-12 15:31:06.59 spid9s Clearing tempdb database.
2017-10-12 15:31:06.84 spid9s Starting up database 'tempdb'.
One thing which I observed is the difference in Service account name which is "PTCNET\I7724$" for SQL server 2012 whereas for SQL Server 2016 it is "NT Service\MSSQL$SQLEXPRESS".
Not sure if this is the reason for that and from where it is picking the different Service name. Any input will be highly appreciated.
I am trying to execute a job from SQL Server Agent however receiving the error:
The login is from an untrusted domain and cannot be used with Windows authentication.
The Sql server 2016 with Sql server Agent and SSIS where a credential account proxy is linking to windows admin account. The proxy is set SSIS package excecution:
The job has only 1 step to run SSIS package. This package is developed/tested/deployed from VS 2016+Data tools.
Here is the step:
and the error:
Right click on the job to view History. Here is the error:
Executed as user: MACHINE_NAME\admin_user. Microsoft (R) SQL Server Execute Package Utility Version 13.0.1601.5 for 64-bit Copyright (C) 2016 Microsoft. All rights reserved. Started: 2:15:10 PM Failed to execute IS server package because of error 0x80131904. Server: xxx, Package path: \SSISDB\Practise 1\SSIS 1\Package.dtsx, Environment reference Id: NULL. Description: Login failed. The login is from an untrusted domain and cannot be used with Windows authentication. Source: .Net SqlClient Data Provider Started: 2:15:10 PM Finished: 2:15:10 PM Elapsed: 0.188 seconds. The package execution failed. The step failed.
The Sql server agent, which is running on the local machine, could not resolve the server name tcp:xxx.cloudapp.azure.com in the step. As the agent is local so just set the server name to .. Resolved.
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 installed Oracle 11g on Ubuntu 14.04 by review this reference links. When installing, I do not see any step to create username and password
After that, I configured as below
$# sudo /etc/init.d/oracle-xe configure
Oracle Database 11g Express Edition Configuration
This will configure on-boot properties of Oracle Database 11g Express Edition. The following questions will determine whether the database should be starting upon system boot, the ports it will use, and the passwords that will be used for database accounts. Press <Enter> to accept the defaults.
Ctrl-C will abort.
Specify the HTTP port that will be used for Oracle Application Express [8080]:8080
Specify a port that will be used for the database listener [1521]:1522
Specify a password to be used for database accounts. Note that the same password will be used for SYS and SYSTEM. Oracle recommends the use of different passwords for each database account. This can be done after initial configuration:
Confirm the password:
Do you want Oracle Database 11g Express Edition to be started on boot (y/n) [y]:y
Starting Oracle Net Listener...Done
Configuring database...Done
Starting Oracle Database 11g Express Edition instance...Done
Installation completed successfully.
I tried to login to apex using http://localhost:8080/apex/f?p=4950 ==> Unable to connect. Firefox can't establish a connection to the server at localhost:8080.
I try to connect using SQL Developer
Error: Status : Failure -Test failed: Listener refused the connection with the following error:ORA-12505, TNS:listener does not currently know of SID given in connect descriptor
More information:
$ lsnrctl status
rgm#Motown:~$ lsnrctl status
LSNRCTL for Linux: Version 11.2.0.2.0 - Production on 25-JUL-2015 08:49:19
Copyright (c) 1991, 2011, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC_FOR_XE))) STATUS of the LISTENER
------------------------
Alias LISTENER
Version TNSLSNR for Linux: Version 11.2.0.2.0 - Production
Start Date 23-JUL-2015 17:21:04
Uptime 1 days 15 hr. 28 min. 14 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Default Service XE
Listener Parameter File /u01/app/oracle/product/11.2.0/xe/network/admin/listener.ora
Listener Log File /u01/app/oracle/diag/tnslsnr/Motown/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC_FOR_XE)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=Motown)(PORT=1521)))
Services Summary...
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
listener.ora file
# listener.ora Network Configuration File:
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = /u01/app/oracle/product/11.2.0/xe)
(PROGRAM = extproc)
)
)
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC_FOR_XE))
(ADDRESS = (PROTOCOL = TCP)(HOST = Motown)(PORT = 1521))
)
)
DEFAULT_SERVICE_LISTENER = (XE)
Login SqlPlus using SYSTEM
rgm#Motown:~$ sqlplus / as sysdba
SQL*Plus: Release 11.2.0.2.0 Production on Sat Jul 25 09:00:29 2015
Copyright (c) 1982, 2011, Oracle. All rights reserved.
ERROR:
ORA-01031: insufficient privileges
Enter user-name: SYSTEM
Enter password:
ERROR:
ORA-01033: ORACLE initialization or shutdown in progress
Process ID: 0
Session ID: 0 Serial number: 0
Enter user-name: oracle
Enter password:
ERROR:
ORA-01033: ORACLE initialization or shutdown in progress
Process ID: 0
Session ID: 0 Serial number: 0
SP2-0157: unable to CONNECT to ORACLE after 3 attempts, exiting SQL*Plus
Login SqlPlus using oracle (su to oracle user)
rgm#Motown:~$ su oracle
Password:
oracle#Motown:/home/rgm$ sqlplus / as sysdba
SQL*Plus: Release 11.2.0.2.0 Production on Sat Jul 25 09:02:19 2015
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Express Edition Release 11.2.0.2.0 - 64bit Production
SQL>
SQL>
Please help me to fix the problem to login SQL using Apex and SQL Developer.
Thanks
Your SQL Developer screenshot, you are not using tnsnames.ora - which is fine.
How about using service name = XE, instead of SID. And localhost to Motown.
Before doing this - Go to the command and see if you can tnsping Motown.
c:\ tnsping motown
You should see OK somewhere on the last line. I'm assuming you have installed the Oracle client tools
In your install log it shows a port of 1522 instead of the default 1521.
Specify a port that will be used for the database listener [1521]:1522
In your SQL Developer screenshot you showed a connection dialog using the default of 1521. At least getting the port number right will move you closer if not solve it.
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.