SQL Server Service is not reflecting to the new name.

Hi,
I just rename the computer and use the command below to rename the SQL Server but the SQL Server Service is not reflecting to the new name.
Is there a way to change the SQL Server Service and agent to reflect the new name or do I have to re-install sql server.
I am using SQL 2008 R2.
Thank you in advance.

If running "SELECT
@@servername" yields the old server name, it means the instance has not been renamed.
you must run statement to drop the old name of the instance and recreate it with the new name as the default (local) one..
EXEC master.dbo.sp_dropserver 'MACHINENAME\OLDINSTANCENAME'
go
EXEC master.dbo.sp_addserver 'MACHINENAME\newINSTANCENAME', 'local'
go
I took the code here:
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/c07ab906-dabf-4303-9737-d430d82c4f42/how-to-rename-instance-of-sql-server-2008-r2?forum=sqltools
Once you did this, look at your maintenance plans. I sometime end up having one or two still following the old name. Especially if you create this new server from a copy of another virtualized one.

Similar Messages

The specified credentials that were provided for the SQL Server service are not valid

after i enter account name and password for server configuration...the error appear...is it problem with acc name or password?help!!

Hi help933,
According to your description, when you use the Server Configuration page of the SQL Server Installation Wizard to assign login accounts to SQL Server services, you can
assign the same login account to all SQL Server services, or you can configure each service account individually. You can also specify whether services start automatically, are started manually, or are disabled.
For example, on Windows Vista and Windows Server 2008 ,most accounts are set to the default NETWORK SERVICE account.
For more information, see:
http://msdn.microsoft.com/en-us/library/cc281953.aspx
Also there is a similar issue about seivice account, you can review the following post.
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/c7139740-ab93-48c2-b357-31bb7935b83d/rc0-rs-installation-problem-the-credentials-you-provided-for-reporting-services-service-are?forum=sqlsetupandupgrade
Thanks,
Sofiya Li
Sofiya Li
TechNet Community Support

Sql Server service is not starting

Hi all,
in one of my client place, we were running SAP 4.0B on NT server with SQL 2000 server. from few days onwards.... if we happend to restart server after hardware maintenance (or any other job), SQL server Icon on task bar will be in red colour.
SQL service is not starting automatically.
i need to click and open the swl server icon, and then start it mannually.
but, this should not happen like this.
please suggest me how to approch to this problem.
thanking you in all,
by
raghav

Hi,
open
Control Panel -> Administrative Tools -> Services
and search from the service with the name
MSSQLSERVER
Set the startup mode to from manual to automatic by open the properties for the service.
Regards
Clas

SQL Server Service won't start on SQL Server 2008

Hi everyone,
I'm having trouble starting SQL Server service after stopping and starting the service. Before this happened, I created a Stored Procedure for marking all tables at once along with a maintenance plan for differential backup on all my databases based on the
recommendation from this link, http://msdn.microsoft.com/en-us/library/ms253070.aspx.
When I realized that the differential backup failed with some databases displaying (Restoring...) post-fix to the database name, I decided to stop SQL Server service and start it up. That is when I won't be able to start the service again.
Is there a fix for starting the SQL Server service? Any help is very much appreciated.
Additional information:
- With administrator permission granted.
- Service Pack 1 for SQL Server 2008 installed.
- Using default database instance.
- Tried C:\Program Files\Microsoft SQL Server\MSSQL.....\Binn>net start MSSQLSERVER /T3608 ( return msg: System error 5 has occurred. Access is denied.
- When I start SQL Server service, I keep getting this dialog msg:
"Windowns could not start the SQL Server (MSSQLSERVER) on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code 1814."
The event log does not explain or provide any hint on how to fix the problem.
- Log msg:
2010-07-22 10:30:25.09 Server      (c) 2005 Microsoft Corporation.
2010-07-22 10:30:25.09 Server      All rights reserved.
2010-07-22 10:30:25.09 Server      Server process ID is 6076.
2010-07-22 10:30:25.10 Server      Authentication mode is MIXED.
2010-07-22 10:30:25.10 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2010-07-22 10:30:25.11 Server      This instance of SQL Server last reported using a process ID of 5708 at 7/21/2010 3:27:01 PM (local) 7/21/2010 10:27:01 PM (UTC). This is an informational message only; no user action is required.
2010-07-22 10:30:25.11 Server      Registry startup parameters:
    -d C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\master.mdf
    -e C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Log\ERRORLOG
    -l C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2010-07-22 10:30:25.14 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2010-07-22 10:30:25.14 Server      Detected 4 CPUs. This is an informational message; no user action is required.
2010-07-22 10:30:25.23 Server      Using locked pages for buffer pool.
2010-07-22 10:30:25.43 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.
2010-07-22 10:30:25.73 Server      Node configuration: node 0: CPU mask: 0x000000000000000f Active CPU mask: 0x000000000000000f. This message provides a description of the NUMA configuration for this computer. This is an informational
message only. No user action is required.
2010-07-22 10:30:25.81 spid7s      Starting up database 'master'.
2010-07-22 10:30:26.14 spid7s      CHECKDB for database 'master' finished without errors on 2010-07-19 21:15:02.823 (local time). This is an informational message only; no user action is required.
2010-07-22 10:30:26.18 spid7s      Resource governor reconfiguration succeeded.
2010-07-22 10:30:26.18 spid7s      SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2010-07-22 10:30:26.18 spid7s      SQL Server Audit has started the audits. This is an informational message. No user action is required.
2010-07-22 10:30:26.19 spid7s      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2010-07-22 10:30:26.28 spid7s      SQL Trace ID 1 was started by login "sa".
2010-07-22 10:30:26.29 spid7s      Starting up database 'mssqlsystemresource'.
2010-07-22 10:30:26.31 spid7s      The resource database build version is 10.00.2531. This is an informational message only. No user action is required.
2010-07-22 10:30:26.43 spid10s     Starting up database 'model'.
2010-07-22 10:30:26.43 spid7s      Server name is 'XXXXXXXXXXXXXX'. This is an informational message only. No user action is required.
2010-07-22 10:30:26.47 spid10s     The database 'model' is marked RESTORING and is in a state that does not allow recovery to be run.
2010-07-22 10:30:26.47 spid10s     Error: 927, Severity: 14, State: 2.
2010-07-22 10:30:26.47 spid10s     Database 'model' cannot be opened. It is in the middle of a restore.
2010-07-22 10:30:26.59 spid10s     Could not create tempdb. You may not have enough disk space available. Free additional disk space by deleting other files on the tempdb drive and then restart SQL Server. Check for additional errors in
the event log that may indicate why the tempdb files could not be initialized.
2010-07-22 10:30:26.59 spid10s     SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.

Hello,
Could you please copy the model.mdf and modellog.ldf from
C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Binn\Templates
To
C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA
Rebuilding the system databases you will lose lose logins, jobs, SSIS packages. You may have to restore or attach user databases.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

SCVMM 2008 R2 - "The SQL Server service account does not have permission to access Active Directory Domain Services (AD DS)."

I know this question has been asked before, but never for R2, that I can tell, and the posted fixes aren't working. I have just installed SCVMM 2008 R2 on a Windows Server 2008 R2 server, using a remote SQL 2008 SP1 database. When I attempt to connect to SCVMM, I get the following error:
"The SQL Server service account does not have permission to access Active Directory Domain Services (AD DS).
Ensure that the SQL Server service is running under a domain account or a computer account that has permission to access AD DS. For more information, see "Some applications and APIs require access to authorization information on account objects" in the Microsoft Knowledge Base at http://go.microsoft.com/fwlink/?LinkId=121054.
ID: 2607"
What I've seen online is that this is usually becuase the domain account SCVMM is running as does not have the proper permissions on the SQL database. Here's what I've confirmed:
1) My SCVMM service account is a local admin on the SCVMM server
2) My SCVMM service account is a dbowner on the SCVMM database in SQL
3) My SQL service account is a dbowner on the SCVMM database in SQL
4) My SQL service account is a domain user (even made it a domain admin, just in case, and it still "doesn't have access to AD DS," which is obviously untrue)
5) Neither service account is locked out
Has anyone run in to this? It says in Technet that remote SQL 2008 is supported, as long as the SQL management studio is installed to the SCVMM server, and I installed and patched before I began the SCVMM installation. I just don't know what else to try - I have no errors in event logs, no issues during the installation itself...
Andrew Topp

That answer was very unhelpful fr33m4n. The individual mentions that they've received the error that points to the KB article. I currently receive the same error -- there seems to be no resolution. I've run the Microsoft VBS script to add TAUG to the WAAG
as suggested by 331951, and that made absolutely no difference.
1) My SCVMM service account is a local admin on the SCVMM server
2) My SCVMM service account is a dbowner on the SCVMM database in SQL
3) My SQL service account is a dbowner on the SCVMM database in SQL
4) My SQL service account is a domain user (even made it a domain admin, just in case, and it still
"doesn't have access to AD DS," which is obviously untrue)
The user is also a member of WAAG, the machines have delegated authority to each other. Is there any other solution?

[Forum FAQ] Troubleshooting error "The specified SQL server instance is not valid" when installing SCOM reporting service

Symptom
If you have failed to install SCOM reporting service, you may encounter below error when you reinstall it:
“The specified SQL server instance is not valid”.
(Figure 1)
Figure 1.
Reason
This issue may be caused by multiple reasons, for example the reasons in Figure 1.
However, you may find that SSRS and Report Server website are configured correctly and no SSL or proxy Server is used. In these scenario, you can open the log file under path
to find the root reason:
C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\LogFiles
Later, you will find the error as below:
ERROR: Throwing Microsoft.ReportingServices.Library.ReportServerDisabledException: , Microsoft.ReportingServices.Library.ReportServerDisabledException:
The report server cannot decrypt the symmetric key that is used to access sensitive or encrypted data in a report server database. You must either restore a backup key or delete all encrypted content. ---> System.Runtime.InteropServices.COMException
(0x80090016): Keyset does not exist (Exception from HRESULT: 0x80090016)
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at RSManagedCrypto.RSCrypto.ReencryptSymmetricKey(Byte[] symKeyBlob, Byte[] pPublicKeyBlob)
at Microsoft.ReportingServices.Library.ConnectionManager.<GetEncryptionKey>b__2()
--- End of inner exception stack trace ---;
Solution
According to the error message, you can delete encrypted content by following the steps below:
Open SQL Reporting Services Configuration Manager.
Select “Encryption Keys”.
Click “Delete” to delete all encrypted content. (Figure 2)
Figure 2.
After that, we can install SCOM reporting service again, after successfully install reporting service, we should see the SCOM operation console as below:
Figure 3.
In addition, you may also encounter other errors when installing SCOM reporting service, and the troubleshooting steps may be different. However, we can also check SQL reporting
service logs to find the root reason.
Here are some articles that would be helpful for SCOM reporting service installation and troubleshooting:
How to Install the Operations Manager Reporting Server
http://technet.microsoft.com/en-us/library/hh298611.aspx
Unable to install SCOM 2012 Reporting Services
http://blogs.technet.com/b/mdegre/archive/2013/05/27/unable-to-install-scom-2012-reporting-services.aspx
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Hello,
I'm afraid you must use a dedicated instance of SQL Server for each site(SCOM/SCCM). Some similar issues were disscussed on this forum:
SCCM and SCOM - SQL Server
http://social.technet.microsoft.com/Forums/en-US/configmanagergeneral/thread/bfa14da9-4692-4c64-a107-e085c967d259
SCOM, SCCM, SQL on same server?
http://social.technet.microsoft.com/Forums/en-US/configmgrsetup/thread/b5373aa7-5233-4b1f-9b39-b86e481e04d5
Thanks,
Yog Li
TechNet Community Support

Setup problem - sql server 2014 - "could not find the database engine startup handle" - 0x851a0019

I tried to install ,deleted and re-installed several times and no help at all.
visual studio 2013 with update 2 rc and adk installed in my computer.
error code: 0x851a0019
error messege in setup: could not find the database engine startup handle
edition: Microsoft SQL Server 2014 Enterprise (Evaluation)
logs:
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2061893607
Start time: 2014-04-03 13:53:29
End time: 2014-04-03 14:47:48
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for RS: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for SQLEngine: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for DQ: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for FullText: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for Replication: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Machine Properties:
Machine name: ARIELUBA-PC
Machine processor count: 8
OS version: Windows 8
OS service pack:
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered Configured
SQL Server 2012 SQLEXPRESS MSSQL11.SQLEXPRESS Database Engine Services 1033
Express Edition 11.1.3128.0 No Yes
SQL Server 2012 SQLEXPRESS MSSQL11.SQLEXPRESS SQL Server Replication 1033
Express Edition 11.1.3128.0 No Yes
SQL Server 2012 ADK MSSQL11.ADK Database Engine Services
1033 Express Edition 11.0.2100.60 No Yes
SQL Server 2012 ADK MSSQL11.ADK SQL Server Replication
1033 Express Edition 11.0.2100.60 No Yes
SQL Server 2012 LocalDB
1033 Express Edition 11.1.3412.0 No Yes
Package properties:
Description: Microsoft SQL Server 2014
ProductName: SQL Server 2014
Type: RTM
Version: 12
SPLevel: 0
Installation location: C:\Users\Arie Luba\Downloads\WS2012R2DC\SQLServer2014-x64-ENU\x64\setup\
Installation edition: Evaluation
Product Update Status:
None discovered.
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: true
AGTSVCACCOUNT: NT Service\SQLSERVERAGENT
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Backup
ASCOLLATION: Hebrew_CI_AS
ASCONFIGDIR: C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Config
ASDATADIR: C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Data
ASLOGDIR: C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT: NT Service\MSSQLServerOLAPService
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: ARIELUBA-PC\Arie Luba
ASTEMPDIR: C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Temp
BROWSERSVCSTARTUPTYPE: Automatic
CLTCTLRNAME:
CLTRESULTDIR: C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir\
CLTSTARTUPTYPE: Manual
CLTSVCACCOUNT: NT Service\SQL Server Distributed Replay Client
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\WorkingDir\
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140403_135327\ConfigurationFile.ini
CTLRSTARTUPTYPE: Manual
CTLRSVCACCOUNT: NT Service\SQL Server Distributed Replay Controller
CTLRSVCPASSWORD: <empty>
CTLRUSERS: ARIELUBA-PC\Arie Luba
ENABLERANU: false
ENU: true
ERRORREPORTING: false
FEATURES: SQLENGINE, REPLICATION, FULLTEXT, DQ, AS, RS, RS_SHP, RS_SHPWFE, DQC, CONN, IS, BC, SDK, BOL, SSMS, ADV_SSMS, DREPLAY_CTLR, DREPLAY_CLT, MDS
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT Service\MSSQLFDLauncher
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTSQLSERVERLICENSETERMS: true
INDICATEPROGRESS: false
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT Service\MsDtsServer120
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: AllFeatures_WithDefaults
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: SharePointFilesOnlyMode
RSSVCACCOUNT: NT Service\ReportServer
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: <empty>
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: Hebrew_CI_AS
SQLSVCACCOUNT: NT Service\MSSQLSERVER
SQLSVCPASSWORD: <empty>
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: ARIELUBA-PC\Arie Luba
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: false
TCPENABLED: 1
UIMODE: Normal
UpdateEnabled: true
UpdateSource: MU
USEMICROSOFTUPDATE: false
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140403_135327\ConfigurationFile.ini
Detailed results:
Feature: Management Tools - Complete
Status: Passed
Feature: Client Tools Connectivity
Status: Passed
Feature: Client Tools SDK
Status: Passed
Feature: Client Tools Backwards Compatibility
Status: Passed
Feature: Management Tools - Basic
Status: Passed
Feature: Reporting Services - Native
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A0019
Error description: Could not find the Database Engine startup handle.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A0019
Error description: Could not find the Database Engine startup handle.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
Feature: Data Quality Services
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A0019
Error description: Could not find the Database Engine startup handle.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
Feature: Full-Text and Semantic Extractions for Search
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A0019
Error description: Could not find the Database Engine startup handle.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
Feature: SQL Server Replication
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A0019
Error description: Could not find the Database Engine startup handle.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
Feature: Master Data Services
Status: Passed
Feature: Distributed Replay Client
Status: Passed
Feature: Distributed Replay Controller
Status: Passed
Feature: Integration Services
Status: Passed
Feature: Data Quality Client
Status: Passed
Feature: Analysis Services
Status: Passed
Feature: Reporting Services - SharePoint
Status: Passed
Feature: Reporting Services Add-in for SharePoint Products
Status: Passed
Feature: SQL Browser
Status: Passed
Feature: Documentation Components
Status: Passed
Feature: SQL Writer
Status: Passed
Feature: Setup Support Files
Status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140403_135327\SystemConfigurationCheck_Report.htm
2014-04-03 14:14:28.01 Server Microsoft SQL Server 2014 - 12.0.2000.8 (X64)
Feb 20 2014 20:04:26
Copyright (c) Microsoft Corporation
Enterprise Evaluation Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: ) (Hypervisor)
2014-04-03 14:14:28.01 Server UTC adjustment: 3:00
2014-04-03 14:14:28.01 Server (c) Microsoft Corporation.
2014-04-03 14:14:28.01 Server All rights reserved.
2014-04-03 14:14:28.01 Server Server process ID is 7148.
2014-04-03 14:14:28.01 Server System Manufacturer: 'Dell Inc.', System Model: 'Inspiron N5110'.
2014-04-03 14:14:28.01 Server Authentication mode is WINDOWS-ONLY.
2014-04-03 14:14:28.01 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2014-04-03 14:14:28.01 Server The service account is 'NT Service\MSSQLSERVER'. This is an informational message; no user action is required.
2014-04-03 14:14:28.01 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2014-04-03 14:14:28.01 Server Command Line Startup Parameters:
-s "MSSQLSERVER"
-m "SqlSetup"
-Q
-q "Hebrew_CI_AS"
-T 4022
-T 4010
-T 3659
-T 3610
-T 8015
2014-04-03 14:14:28.28 Server SQL Server detected 1 sockets with 4 cores per socket and 8 logical processors per socket, 8 total logical processors; using 8 logical processors based on SQL Server licensing. This is an informational message;
no user action is required.
2014-04-03 14:14:28.28 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2014-04-03 14:14:28.28 Server Detected 8099 MB of RAM. This is an informational message; no user action is required.
2014-04-03 14:14:28.28 Server Using conventional memory in the memory manager.
2014-04-03 14:14:28.31 Server Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
2014-04-03 14:14:28.34 Server Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
2014-04-03 14:14:28.36 Server Query Store settings initialized with enabled = 1,
2014-04-03 14:14:28.36 Server The maximum number of dedicated administrator connections for this instance is '1'
2014-04-03 14:14:28.36 Server Node configuration: node 0: CPU mask: 0x00000000000000ff:0 Active CPU mask: 0x00000000000000ff:0. This message provides a description of the NUMA configuration for this computer. This is an informational message
only. No user action is required.
2014-04-03 14:14:28.38 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.
2014-04-03 14:14:28.39 Server Database Mirroring Transport is disabled in the endpoint configuration.
2014-04-03 14:14:28.39 spid8s Warning ******************
2014-04-03 14:14:28.39 spid8s SQL Server started in single-user mode. This an informational message only. No user action is required.
2014-04-03 14:14:28.40 spid8s Starting up database 'master'.
2014-04-03 14:14:28.42 Server Software Usage Metrics is disabled.
2014-04-03 14:14:28.48 Server CLR version v4.0.30319 loaded.
2014-04-03 14:14:28.56 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2014-04-03 14:14:28.62 spid8s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2014-04-03 14:14:28.63 spid8s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2014-04-03 14:14:28.64 spid8s SQL Trace ID 1 was started by login "sa".
2014-04-03 14:14:28.64 spid8s Server name is 'ARIELUBA-PC'. This is an informational message only. No user action is required.
2014-04-03 14:14:28.65 spid16s Password policy update was successful.
2014-04-03 14:14:28.66 spid16s Error: 17190, Severity: 16, State: 1.
2014-04-03 14:14:28.66 spid16s Initializing the FallBack certificate failed with error code: 1, state: 20, error number: 0.
2014-04-03 14:14:28.66 spid16s Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
2014-04-03 14:14:28.66 spid16s Error: 17182, Severity: 16, State: 1.
2014-04-03 14:14:28.66 spid16s TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property.
2014-04-03 14:14:28.66 spid16s Error: 17182, Severity: 16, State: 1.
2014-04-03 14:14:28.66 spid16s 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.
2014-04-03 14:14:28.66 spid16s Error: 17826, Severity: 18, State: 3.
2014-04-03 14:14:28.66 spid16s 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.
2014-04-03 14:14:28.67 spid16s Error: 17120, Severity: 16, State: 1.
2014-04-03 14:14:28.67 spid16s SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
________________________________________________________________________________________________

Is it okay? (see below)
;SQL Server 2014 Configuration File
[OPTIONS]
; Specifies a Setup work flow, like INSTALL, UNINSTALL, or UPGRADE. This is a required parameter.
ACTION="Install"
; Detailed help for command line argument ROLE has not been defined yet.
ROLE="AllFeatures_WithDefaults"
; Use the /ENU parameter to install the English version of SQL Server on your localized Windows operating system.
ENU="True"
; Parameter that controls the user interface behavior. Valid values are Normal for the full UI,AutoAdvance for a simplied UI, and EnableUIOnServerCore for bypassing Server Core setup GUI block.
UIMODE="Normal"
; Setup will not display any user interface.
QUIET="False"
; Setup will display progress only, without any user interaction.
QUIETSIMPLE="False"
; Specify whether SQL Server Setup should discover and include product updates. The valid values are True and False or 1 and 0. By default SQL Server Setup will include updates that are found.
UpdateEnabled="True"
; Specify if errors can be reported to Microsoft to improve future SQL Server releases. Specify 1 or True to enable and 0 or False to disable this feature.
ERRORREPORTING="False"
; If this parameter is provided, then this computer will use Microsoft Update to check for updates.
USEMICROSOFTUPDATE="False"
; Specifies features to install, uninstall, or upgrade. The list of top-level features include SQL, AS, RS, IS, MDS, and Tools. The SQL feature will install the Database Engine, Replication, Full-Text, and Data Quality Services (DQS) server. The Tools feature
will install Management Tools, Books online components, SQL Server Data Tools, and other shared components.
FEATURES=SQLENGINE,REPLICATION,FULLTEXT,DQ,AS,RS,RS_SHP,RS_SHPWFE,DQC,CONN,IS,BC,SDK,BOL,SSMS,ADV_SSMS,DREPLAY_CTLR,DREPLAY_CLT,MDS
; Specify the location where SQL Server Setup will obtain product updates. The valid values are "MU" to search Microsoft Update, a valid folder path, a relative path such as .\MyUpdates or a UNC share. By default SQL Server Setup will search Microsoft Update
or a Windows Update service through the Window Server Update Services.
UpdateSource="MU"
; Displays the command line parameters usage
HELP="False"
; Specifies that the detailed Setup log should be piped to the console.
INDICATEPROGRESS="False"
; Specifies that Setup should install into WOW64. This command line argument is not supported on an IA64 or a 32-bit system.
X86="False"
; Specify the root installation directory for shared components. This directory remains unchanged after shared components are already installed.
INSTALLSHAREDDIR="C:\Program Files\Microsoft SQL Server"
; Specify the root installation directory for the WOW64 shared components. This directory remains unchanged after WOW64 shared components are already installed.
INSTALLSHAREDWOWDIR="C:\Program Files (x86)\Microsoft SQL Server"
; Specify a default or named instance. MSSQLSERVER is the default instance for non-Express editions and SQLExpress for Express editions. This parameter is required when installing the SQL Server Database Engine (SQL), Analysis Services (AS), or Reporting Services
(RS).
INSTANCENAME="MSSQLSERVER"
; Specify that SQL Server feature usage data can be collected and sent to Microsoft. Specify 1 or True to enable and 0 or False to disable this feature.
SQMREPORTING="False"
; Specify the Instance ID for the SQL Server features you have specified. SQL Server directory structure, registry structure, and service names will incorporate the instance ID of the SQL Server instance.
INSTANCEID="MSSQLSERVER"
; The computer name that the client communicates with for the Distributed Replay Controller service.
CLTCTLRNAME="SQLDRC"
; The Windows account(s) used to grant permission to the Distributed Replay Controller service.
CTLRUSERS="ARIELUBA-PC\Arie Luba"
; The account used by the Distributed Replay Controller service.
CTLRSVCACCOUNT="NT Service\SQL Server Distributed Replay Controller"
; The startup type for the Distributed Replay Controller service.
CTLRSTARTUPTYPE="Manual"
; The account used by the Distributed Replay Client service.
CLTSVCACCOUNT="NT Service\SQL Server Distributed Replay Client"
; The startup type for the Distributed Replay Client service.
CLTSTARTUPTYPE="Manual"
; The result directory for the Distributed Replay Client service.
CLTRESULTDIR="C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir"
; The working directory for the Distributed Replay Client service.
CLTWORKINGDIR="C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\WorkingDir"
; RSInputSettings_RSInstallMode_Description
RSINSTALLMODE="DefaultNativeMode"
; RSInputSettings_RSInstallMode_Description
RSSHPINSTALLMODE="SharePointFilesOnlyMode"
; Specify the installation directory.
INSTANCEDIR="C:\Program Files\Microsoft SQL Server"
; Agent account name
AGTSVCACCOUNT="NT Service\SQLSERVERAGENT"
; Auto-start service after installation.
AGTSVCSTARTUPTYPE="Manual"
; Startup type for Integration Services.
ISSVCSTARTUPTYPE="Automatic"
; Account for Integration Services: Domain\User or system account.
ISSVCACCOUNT="NT Service\MsDtsServer120"
; The name of the account that the Analysis Services service runs under.
ASSVCACCOUNT="NT Service\MSSQLServerOLAPService"
; Controls the service startup type setting after the service has been created.
ASSVCSTARTUPTYPE="Automatic"
; The collation to be used by Analysis Services.
ASCOLLATION="Hebrew_CI_AS"
; The location for the Analysis Services data files.
ASDATADIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Data"
; The location for the Analysis Services log files.
ASLOGDIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Log"
; The location for the Analysis Services backup files.
ASBACKUPDIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Backup"
; The location for the Analysis Services temporary files.
ASTEMPDIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Temp"
; The location for the Analysis Services configuration files.
ASCONFIGDIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Config"
; Specifies whether or not the MSOLAP provider is allowed to run in process.
ASPROVIDERMSOLAP="1"
; Specifies the list of administrator accounts that need to be provisioned.
ASSYSADMINACCOUNTS="ARIELUBA-PC\Arie Luba"
; Specifies the server mode of the Analysis Services instance. Valid values are MULTIDIMENSIONAL and TABULAR. The default value is MULTIDIMENSIONAL.
ASSERVERMODE="MULTIDIMENSIONAL"
; CM brick TCP communication port
COMMFABRICPORT="0"
; How matrix will use private networks
COMMFABRICNETWORKLEVEL="0"
; How inter brick communication will be protected
COMMFABRICENCRYPTION="0"
; TCP port used by the CM brick
MATRIXCMBRICKCOMMPORT="0"
; Startup type for the SQL Server service.
SQLSVCSTARTUPTYPE="Automatic"
; Level to enable FILESTREAM feature at (0, 1, 2 or 3).
FILESTREAMLEVEL="0"
; Set to "1" to enable RANU for SQL Server Express.
ENABLERANU="False"
; Specifies a Windows collation or an SQL collation to use for the Database Engine.
SQLCOLLATION="Hebrew_CI_AS"
; Account for SQL Server service: Domain\User or system account.
SQLSVCACCOUNT="NT Service\MSSQLSERVER"
; Windows account(s) to provision as SQL Server system administrators.
SQLSYSADMINACCOUNTS="ARIELUBA-PC\Arie Luba"
; Provision current user as a Database Engine system administrator for %SQL_PRODUCT_SHORT_NAME% Express.
ADDCURRENTUSERASSQLADMIN="True"
; Specify 0 to disable or 1 to enable the TCP/IP protocol.
TCPENABLED="1"
; Specify 0 to disable or 1 to enable the Named Pipes protocol.
NPENABLED="0"
; Startup type for Browser Service.
BROWSERSVCSTARTUPTYPE="Automatic"
; Specifies which account the report server NT service should execute under. When omitted or when the value is empty string, the default built-in account for the current operating system.
; The username part of RSSVCACCOUNT is a maximum of 20 characters long and
; The domain part of RSSVCACCOUNT is a maximum of 254 characters long.
RSSVCACCOUNT="NT Service\ReportServer"
; Specifies how the startup mode of the report server NT service. When
; Manual - Service startup is manual mode (default).
; Automatic - Service startup is automatic mode.
; Disabled - Service is disabled
RSSVCSTARTUPTYPE="Automatic"
; Add description of input argument FTSVCACCOUNT
FTSVCACCOUNT="NT Service\MSSQLFDLauncher"

Report Subscription by email error - The SQL Agent service is not running

Hello All,
This may be an easy answer, so please excuse my ignorance if I am overlooking something simple. I a simply trying to setup Report Subscriptions to be emailed to me. We currently have essentially 3 servers in use in our environment - a CAS, a Site server
and a SQL 2012.
I have configured the email settings in Reporting Services Configuration Manager on the Site server and was finally able to see the email option in the Create Subscription Wizard, but it errors out with:
System.Web.Services.Protocols.SoapException: The SQL Agent service is not running. This operation requires the SQL Agent service. ---> Microsoft.ReportingServices.Diagnostics.Utilities.SchedulerNotRespondingException: The SQL Agent service is not running.
This operation requires the SQL Agent service. at Microsoft.ReportingServices.Library.ReportingService2005Impl.CreateSubscription(String Report, ExtensionSettings ExtensionSettings, Boolean isDataDriven, DataRetrievalPlan DataRetrievalPlan, String
Description, String EventType, String MatchData, ParameterValueOrFieldReference[] Parameters, Guid batchId, String& SubscriptionID) at Microsoft.ReportingServices.WebServer.ReportingService2005.CreateSubscription(String Report, ExtensionSettings
ExtensionSettings, String Description, String EventType, String MatchData, ParameterValue[] Parameters, String& SubscriptionID)
We do not have SQL installed locally, therefore it makes sense that the Agent service is not running. How do I subscribe to alerts in SCCM without a local installation of SQL?
-Brad

I am positive - see screenshots below of services on the SQL server:
Yes, reports work perfectly otherwise... Just cannot subscribe.
-Brad

Sql server services give error the remote procedure call failed [0x800706be] in sql server 2008

sql server services give error the remote procedure call failed [0x800706be] in sql server 2008.
To resolve this issue, I executed the following mofcomp command in command prompt to re-register the *.mof files:
mofcomp.exe "C:\Program Files (x86)\Microsoft SQL Server\100\Shared\sqlmgmproviderxpsp2up.mof".
but it does not work.
Plz give the exact soln to solve this error.

sql server services give error the remote procedure call failed [0x800706be] in sql server 2008.
To resolve this issue, I executed the following mofcomp command in command prompt to re-register the *.mof files:
mofcomp.exe "C:\Program Files (x86)\Microsoft SQL Server\100\Shared\sqlmgmproviderxpsp2up.mof".
but it does not work.
Plz give the exact soln to solve this error.
So when you tried starting SQL server service it gave the error right ? or when you click on SQL server services in SQL server configuration manager(SSCM) you get this error. Can you be more clear. As far as I read your question it has something
to do with permission. Close SSCM window and this time right click on SQL server configuration manager and select run as administrator and check if you can see SQL server services
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Articles

Suppress Powershell Warning in agent job "WARNING: Could not obtain SQL Server Service information"

Hi
I get this warning running through powershell_ise but through sql agent it just errors out.
The code does everything it is supposed to and I tried everything to completely resolve the warning to no avail.
How do I supress it so sql agent wont error out running powershell code?
Thanks!
WARNING: Could not obtain SQL Server Service information. An attempt to connect to WMI on 'server_name' failed with the following error: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
Warning only present when it connects to remote servers, it doesn't produce it for local server. And it does get all info from the remote servers.
Paula

Hi paulata,
According to your description, when you run powershell scripts about the remote machine
in SQL Server Agent job, the warning error will occur. “The common error message is Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)).” This suggests that your credentials aren't sufficient for accessing the
remote system. If you have an account that has sufficient permissions for the query, there's a simple workaround for this problem in the form of PowerShell's Get-Credential command and the script's Credential parameter. I recommend you check if your account
has permission on remote machine and it can execute the powershell scripts.
In addition, if you want to run query statement on the remote machine , I recommend you create Linked Server, then do some related operations. There is a similar issue about access denied, you can review the following article.
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/157f536d-6716-4547-bdb4-9e3c8451cb95/sql-agent-service-account-permissions-sql-server-2008?forum=sqlgetstarted
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

SQL Server service not automatically starting (logon failure)

I just installed SQL Server 2012 on a machine. To run "SQL Server" as well as "SQL Server Agent" service I have created a domain account called SQLADMIN. This account is a service account and has no other rights like logon locally or
local administrator.
When the machine restarts, "SQL Server" service doesn't start automatically. When I click Start then it says "Logon Failure". Now if I simply enter the password again under tab "Log On" and then start service then it starts. Why
doesn't it start automatically?

Hello,
Please read the following article about permissions required by service accounts.
http://msdn.microsoft.com/en-us/library/ms143504(v=sql.110).aspx#Serv_Perm
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com
I do not see any special permission that is needed as per the article. For e.g. as per below:
SQL Server Service
Permissions granted by SQL Server Setup
SQL Server Database Engine:
(All rights are granted to the per-service SID. Default instance: NT SERVICE\MSSQLSERVER. Named instance: NT SERVICE\MSSQL$InstanceName.)
Log on as a service (SeServiceLogonRight)
Replace a process-level token(SeAssignPrimaryTokenPrivilege)
Bypass traverse checking (SeChangeNotifyPrivilege)
Adjust memory quotas for a process(SeIncreaseQuotaPrivilege)
Permission to start SQL Writer
Permission to read the Event Log service
Permission to read the Remote Procedure Call service
I am running Database Engine service as DOMAIN\SQLADMIN account which can Log On As A Service. Other 3 permissions mentioned in article are not given so let me assign it and then see how it goes.
Could this issue be due to some domain policy? Because there is another SQL Server machine which shows same behaviour.

Sql server service crashes a few times yesterday, however, there is no .MDMP file generated in the log folder

hi there:
I've experienced several sql server service crashes yesterday, service was brought up after a few secs as we have an autostart feature.
Today, I'd like to dig more into the errors and on the event viewer -> Application, I saw errors below
"Faulting application sqlservr.exe, version 2009.100.4302.0, time stamp 0x52f5d194, faulting module ntdll.dll, version 6.0.6001.18538, time stamp 0x4cb73957, exception code 0xc0000374, fault offset 0x00000000000a7857, process id 0x15ec, application
start time 0x01cfd7e72b2997d3.
People suggested to check dump file inside C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQL2008R2\MSSQL\Log
However, the lastest .mdmp file was on April 11, 2014. Do I need to turn on some settings on sql server in order to have this dump file?
Thanks
Hui
--Currently using Reporting Service 2000; Visual Studio .NET 2003; Visual Source Safe SSIS 2008 SSAS 2008, SVN --

Results after sp_readerrorlog 1
LogDate ProcessInfo
Text
2014-09-24 04:03:28.460 Server
Microsoft SQL Server 2008 R2 (SP2) - 10.50.4302.0 (X64)
Feb 7 2014 17:23:24
Copyright (c) Microsoft Corporation
Enterprise Edition (64-bit) on Windows NT 6.0 <X64> (Build 6001: Service Pack 1)
2014-09-24 04:03:28.460 Server
(c) Microsoft Corporation.
2014-09-24 04:03:28.460 Server
All rights reserved.
2014-09-24 04:03:28.460 Server
Server process ID is 5612.
2014-09-24 04:03:28.460 Server
System Manufacturer: 'IBM', System Model: 'IBM System x3650 -[7979AC1]-'.
2014-09-24 04:03:28.460 Server
Authentication mode is MIXED.
2014-09-24 04:03:28.460 Server
Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQL2008R2\MSSQL\Log\ERRORLOG'.
2014-09-24 04:03:28.460 Server
This instance of SQL Server last reported using a process ID of 6780 at 9/24/2014 4:03:20 AM (local) 9/24/2014 11:03:20 AM (UTC). This is an informational message only; no user action is required.
2014-09-24 04:03:28.460 Server
Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQL2008R2\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQL2008R2\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQL2008R2\MSSQL\DATA\mastlog.ldf
2014-09-24 04:03:28.480 Server
SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2014-09-24 04:03:28.480 Server
Detected 4 CPUs. This is an informational message; no user action is required.
2014-09-24 04:03:28.480 Server
Cannot use Large Page Extensions: lock memory privilege was not granted.
2014-09-24 04:03:28.580 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.
2014-09-24 04:03:28.700 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.
2014-09-24 04:03:28.870 spid7s
Starting up database 'master'.
2014-09-24 04:03:28.940 spid7s
1 transactions rolled forward in database 'master' (1). This is an informational message only. No user action is required.
2014-09-24 04:03:28.940 spid7s
0 transactions rolled back in database 'master' (1). This is an informational message only. No user action is required.
2014-09-24 04:03:28.940 spid7s
Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2014-09-24 04:03:29.040 spid7s
CHECKDB for database 'master' finished without errors on 2014-09-20 12:00:01.697 (local time). This is an informational message only; no user action is required.
2014-09-24 04:03:29.050 spid7s
Resource governor reconfiguration succeeded.
2014-09-24 04:03:29.050 spid7s
SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2014-09-24 04:03:29.050 spid7s
SQL Server Audit has started the audits. This is an informational message. No user action is required.
2014-09-24 04:03:29.050 spid7s
FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'SQL2008R2'.
2014-09-24 04:03:29.070 spid7s
SQL Trace ID 1 was started by login "sa".
2014-09-24 04:03:29.070 spid7s
Starting up database 'mssqlsystemresource'.
2014-09-24 04:03:29.090 spid7s
The resource database build version is 10.50.4302. This is an informational message only. No user action is required.
2014-09-24 04:03:29.600 spid10s
Starting up database 'model'.
2014-09-24 04:03:29.600 spid7s
Server name is 'BPWDB046\SQL2008R2'. This is an informational message only. No user action is required.
2014-09-24 04:03:29.880 spid13s
A new instance of the full-text filter daemon host process has been successfully started.
2014-09-24 04:03:29.960 spid14s
Starting up database 'msdb'.
2014-09-24 04:03:29.960 spid17s
Starting up database 'DW_Detail'.
2014-09-24 04:03:29.960 spid16s
Starting up database 'ReportServer_MSSQLSSRSTempDB'.
2014-09-24 04:03:29.960 spid13s
Starting up database 'Billing_Rep'.
2014-09-24 04:03:29.960 spid15s
Starting up database 'ReportServer_MSSQLSSRS'.
2014-09-24 04:03:29.960 spid18s
Starting up database 'BCBio_DW'.
2014-09-24 04:03:29.960 spid19s
Starting up database 'ODS'.
2014-09-24 04:03:29.960 spid20s
Starting up database 'ReportServer$SQL2008'.
2014-09-24 04:03:29.970 spid21s
Starting up database 'ReportServer$SQL2008TempDB'.
2014-09-24 04:03:29.970 spid22s
Starting up database 'Billing'.
2014-09-24 04:03:29.970 spid23s
Starting up database 'Billing_Snap'.
2014-09-24 04:03:29.970 spid24s
Starting up database 'DBA'.
2014-09-24 04:03:30.000 Server
A self-generated certificate was successfully loaded for encryption.
2014-09-24 04:03:30.000 Server
Server is listening on [ 'any' <ipv6> 52328].
2014-09-24 04:03:30.000 Server
Server is listening on [ 'any' <ipv4> 52328].
2014-09-24 04:03:30.000 Server
Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQL2008R2 ].
2014-09-24 04:03:30.000 Server
Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$SQL2008R2\sql\query ].
2014-09-24 04:03:30.010 Server
Server is listening on [ ::1 <ipv6> 52329].
2014-09-24 04:03:30.010 Server
Server is listening on [ 127.0.0.1 <ipv4> 52329].
2014-09-24 04:03:30.010 Server
Dedicated admin connection support was established for listening locally on port 52329.
2014-09-24 04:03:30.060 spid10s
CHECKDB for database 'model' finished without errors on 2014-09-20 12:00:17.583 (local time). This is an informational message only; no user action is required.
2014-09-24 04:03:30.060 spid10s
Clearing tempdb database.
2014-09-24 04:03:30.140 Server
The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/BPWDB046.bcbio.org:SQL2008R2 ] for the SQL Server service.
2014-09-24 04:03:30.140 Server
The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/BPWDB046.bcbio.org:52328 ] for the SQL Server service.
2014-09-24 04:03:30.140 Server
SQL Server is now ready for client connections. This is an informational message; no user action is required.
2014-09-24 04:03:30.480 spid21s
CHECKDB for database 'ReportServer$SQL2008TempDB' finished without errors on 2014-09-20 16:13:10.043 (local time). This is an informational message only; no user action is required.
2014-09-24 04:03:30.520 spid14s
2933 transactions rolled forward in database 'msdb' (4). This is an informational message only. No user action is required.
2014-09-24 04:03:30.650 spid7s
0 transactions rolled back in database 'msdb' (4). This is an informational message only. No user action is required.
2014-09-24 04:03:30.650 spid7s
Recovery is writing a checkpoint in database 'msdb' (4). This is an informational message only. No user action is required.
2014-09-24 04:03:30.770 spid14s
CHECKDB for database 'msdb' finished without errors on 2014-09-20 12:00:18.473 (local time). This is an informational message only; no user action is required.
2014-09-24 04:03:30.950 spid10s
Starting up database 'tempdb'.
2014-09-24 04:03:30.990 spid52
Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
2014-09-24 04:03:31.010 spid52
Using 'xpstar.dll' version '2009.100.1600' to execute extended stored procedure 'xp_sqlagent_monitor'. This is an informational message only; no user action is required.
2014-09-24 04:03:31.060 spid14s
The Service Broker protocol transport is disabled or not configured.
2014-09-24 04:03:31.060 spid14s
The Database Mirroring protocol transport is disabled or not configured.
2014-09-24 04:03:31.070 spid14s
Service Broker manager has started.
2014-09-24 04:03:31.330 spid16s
CHECKDB for database 'ReportServer_MSSQLSSRSTempDB' finished without errors on 2014-09-20 12:00:39.873 (local time). This is an informational message only; no user action is required.
2014-09-24 04:03:31.500 spid20s
2 transactions rolled forward in database 'ReportServer$SQL2008' (11). This is an informational message only. No user action is required.
2014-09-24 04:03:31.960 spid7s
0 transactions rolled back in database 'ReportServer$SQL2008' (11). This is an informational message only. No user action is required.
2014-09-24 04:03:31.960 spid7s
Recovery is writing a checkpoint in database 'ReportServer$SQL2008' (11). This is an informational message only. No user action is required.
2014-09-24 04:03:32.150 spid20s
CHECKDB for database 'ReportServer$SQL2008' finished without errors on 2014-09-20 16:13:07.583 (local time). This is an informational message only; no user action is required.
2014-09-24 04:03:33.170 spid24s
CHECKDB for database 'DBA' finished without errors on 2014-09-20 16:22:41.603 (local time). This is an informational message only; no user action is required.
2014-09-24 04:03:33.600 spid13s
Recovery of database 'Billing_Rep' (8) is 0% complete (approximately 1537 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
2014-09-24 04:03:34.820 spid15s
CHECKDB for database 'ReportServer_MSSQLSSRS' finished without errors on 2014-09-20 12:00:32.067 (local time). This is an informational message only; no user action is required.
2014-09-24 04:03:48.290 spid13s
Recovery of database 'Billing_Rep' (8) is 1% complete (approximately 1488 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
2014-09-24 04:03:49.520 spid17s
1 transactions rolled forward in database 'DW_Detail' (7). This is an informational message only. No user action is required.
2014-09-24 04:03:50.070 spid7s
0 transactions rolled back in database 'DW_Detail' (7). This is an informational message only. No user action is required.
2014-09-24 04:03:50.070 spid7s
Recovery is writing a checkpoint in database 'DW_Detail' (7). This is an informational message only. No user action is required.
2014-09-24 04:03:50.070 spid7s
Recovery completed for database DW_Detail (database ID 7) in 5 second(s) (analysis 251 ms, redo 4314 ms, undo 44 ms.) This is an informational message only. No user action is required.
2014-09-24 04:03:50.520 spid22s
CHECKDB for database 'Billing' finished without errors on 2013-04-25 18:47:20.743 (local time). This is an informational message only; no user action is required.
2014-09-24 04:03:51.620 spid17s
CHECKDB for database 'DW_Detail' finished without errors on 2014-09-20 12:00:46.917 (local time). This is an informational message only; no user action is required.
2014-09-24 04:04:03.740 spid13s
Recovery of database 'Billing_Rep' (8) is 2% complete (approximately 1493 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:13.040 spid13s
Recovery of database 'Billing_Rep' (8) is 0% complete (approximately 8052 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:23.220 spid18s
Database BCBio_DW has more than 1000 virtual log files which is excessive. Too many virtual log files can cause long startup and backup times. Consider shrinking the log and using a different growth increment to reduce the number of virtual log files.
2014-09-24 04:04:23.420 spid18s
Recovery of database 'BCBio_DW' (9) is 0% complete (approximately 4664 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:25.640 spid18s
Recovery of database 'BCBio_DW' (9) is 0% complete (approximately 4954 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:25.640 spid18s
Recovery of database 'BCBio_DW' (9) is 3% complete (approximately 74 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:25.730 spid18s
Recovery of database 'BCBio_DW' (9) is 2% complete (approximately 98 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:26.000 spid18s
Recovery of database 'BCBio_DW' (9) is 12% complete (approximately 18 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:28.000 spid19s
Database ODS has more than 1000 virtual log files which is excessive. Too many virtual log files can cause long startup and backup times. Consider shrinking the log and using a different growth increment to reduce the number of virtual log files.
2014-09-24 04:04:28.350 spid19s
CHECKDB for database 'ODS' finished without errors on 2014-09-20 16:07:22.603 (local time). This is an informational message only; no user action is required.
2014-09-24 04:04:29.370 spid18s
Recovery of database 'BCBio_DW' (9) is 19% complete (approximately 24 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:31.380 spid18s
Recovery of database 'BCBio_DW' (9) is 25% complete (approximately 22 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:32.490 spid18s
Recovery of database 'BCBio_DW' (9) is 32% complete (approximately 18 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:33.150 spid13s
Recovery of database 'Billing_Rep' (8) is 0% complete (approximately 9805 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:33.860 Logon
Error: 18456, Severity: 14, State: 38.
2014-09-24 04:04:33.860 Logon
Login failed for user 'ETLAdmin'. Reason: Failed to open the explicitly specified database. [CLIENT: 172.20.101.33]
2014-09-24 04:04:34.040 spid18s
Recovery of database 'BCBio_DW' (9) is 39% complete (approximately 15 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:35.600 spid18s
Recovery of database 'BCBio_DW' (9) is 46% complete (approximately 13 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:36.740 spid18s
Recovery of database 'BCBio_DW' (9) is 53% complete (approximately 10 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:37.220 spid13s
Recovery of database 'Billing_Rep' (8) is 0% complete (approximately 10106 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:37.230 spid13s
Recovery of database 'Billing_Rep' (8) is 2% complete (approximately 2587 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:37.360 spid13s
Recovery of database 'Billing_Rep' (8) is 1% complete (approximately 3654 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:37.560 spid13s
Recovery of database 'Billing_Rep' (8) is 3% complete (approximately 1564 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:38.070 spid13s
Recovery of database 'Billing_Rep' (8) is 4% complete (approximately 1328 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:38.830 spid18s
Recovery of database 'BCBio_DW' (9) is 61% complete (approximately 8 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:40.080 spid13s
Recovery of database 'Billing_Rep' (8) is 5% complete (approximately 1268 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:40.680 spid18s
Recovery of database 'BCBio_DW' (9) is 69% complete (approximately 6 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:42.960 spid18s
Recovery of database 'BCBio_DW' (9) is 77% complete (approximately 4 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:44.870 spid18s
Recovery of database 'BCBio_DW' (9) is 85% complete (approximately 3 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:44.870 spid18s
3 transactions rolled forward in database 'BCBio_DW' (9). This is an informational message only. No user action is required.
2014-09-24 04:04:45.120 spid18s
Recovery of database 'BCBio_DW' (9) is 85% complete (approximately 3 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:46.870 spid7s
0 transactions rolled back in database 'BCBio_DW' (9). This is an informational message only. No user action is required.
2014-09-24 04:04:46.870 spid7s
Recovery is writing a checkpoint in database 'BCBio_DW' (9). This is an informational message only. No user action is required.
2014-09-24 04:04:46.870 spid7s
Recovery completed for database BCBio_DW (database ID 9) in 23 second(s) (analysis 2417 ms, redo 19227 ms, undo 1745 ms.) This is an informational message only. No user action is required.
2014-09-24 04:04:47.610 spid18s
CHECKDB for database 'BCBio_DW' finished without errors on 2014-09-20 14:02:10.680 (local time). This is an informational message only; no user action is required.
2014-09-24 04:04:47.820 spid23s
Database Billing_Snap has more than 1000 virtual log files which is excessive. Too many virtual log files can cause long startup and backup times. Consider shrinking the log and using a different growth increment to reduce the number of virtual log files.
2014-09-24 04:04:48.570 spid23s
CHECKDB for database 'Billing_Snap' finished without errors on 2014-09-20 16:13:11.037 (local time). This is an informational message only; no user action is required.
2014-09-24 04:04:52.970 spid13s
Recovery of database 'Billing_Rep' (8) is 6% complete (approximately 1247 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:05:05.540 spid13s
Recovery of database 'Billing_Rep' (8) is 7% complete (approximately 1224 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:05:17.980 spid13s
Recovery of database 'Billing_Rep' (8) is 8% complete (approximately 1202 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:05:22.450 spid13s
Recovery of database 'Billing_Rep' (8) is 8% complete (approximately 1196 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:05:22.450 spid13s
1 transactions rolled forward in database 'Billing_Rep' (8). This is an informational message only. No user action is required.
2014-09-24 04:05:22.560 spid13s
Recovery of database 'Billing_Rep' (8) is 8% complete (approximately 1196 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
2014-09-24 04:05:22.710 spid13s
CHECKDB for database 'Billing_Rep' finished without errors on 2014-09-20 13:25:01.597 (local time). This is an informational message only; no user action is required.
2014-09-24 04:05:22.720 spid13s
0 transactions rolled back in database 'Billing_Rep' (8). This is an informational message only. No user action is required.
2014-09-24 04:05:22.720 spid13s
Recovery is writing a checkpoint in database 'Billing_Rep' (8). This is an informational message only. No user action is required.
2014-09-24 04:05:22.730 spid13s
Recovery completed for database Billing_Rep (database ID 8) in 109 second(s) (analysis 63983 ms, redo 45211 ms, undo 154 ms.) This is an informational message only. No user action is required.
2014-09-24 04:05:22.750 spid7s
Recovery is complete. This is an informational message only. No user action is required.
2014-09-24 07:00:06.930 spid53
Common language runtime (CLR) functionality initialized using CLR version v2.0.50727 from C:\Windows\Microsoft.NET\Framework64\v2.0.50727\.
2014-09-24 07:00:07.720 spid53
AppDomain 2 (mssqlsystemresource.sys[runtime].1) created.
2014-09-24 07:13:38.590 spid51
SQL Server blocked access to STATEMENT 'OpenRowset/OpenDatasource' of component 'Ad Hoc Distributed Queries' because this component is turned off as part of the security configuration for this server. A system administrator can enable the use of 'Ad
Hoc Distributed Queries' by using sp_configure. For more information about enabling 'Ad Hoc Distributed Queries', see "Surface Area Configuration" in SQL Server Books Online.
2014-09-24 07:13:53.870 Logon
Error: 18456, Severity: 14, State: 38.
2014-09-24 07:13:53.870 Logon
Login failed for user 'BCBIO\sqlservice'. Reason: Failed to open the explicitly specified database. [CLIENT: 172.20.100.6]
2014-09-24 07:13:56.560 Logon
Error: 18456, Severity: 14, State: 38.
2014-09-24 07:13:56.560 Logon
Login failed for user 'BCBIO\sqlservice'. Reason: Failed to open the explicitly specified database. [CLIENT: 172.20.100.6]
2014-09-24 07:13:57.460 Logon
Error: 18456, Severity: 14, State: 38.
2014-09-24 07:13:57.460 Logon
Login failed for user 'BCBIO\sqlservice'. Reason: Failed to open the explicitly specified database. [CLIENT: 172.20.100.6]
2014-09-24 07:13:57.560 Logon
Error: 18456, Severity: 14, State: 38.
2014-09-24 07:13:57.560 Logon
Login failed for user 'BCBIO\sqlservice'. Reason: Failed to open the explicitly specified database. [CLIENT: 172.20.100.6]
2014-09-24 07:13:57.950 Logon
Error: 18456, Severity: 14, State: 38.
2014-09-24 07:13:57.950 Logon
Login failed for user 'BCBIO\sqlservice'. Reason: Failed to open the explicitly specified database. [CLIENT: 172.20.100.6]
2014-09-24 07:14:04.410 Logon
Error: 18456, Severity: 14, State: 38.
2014-09-24 07:14:04.410 Logon
Login failed for user 'BCBIO\sqlservice'. Reason: Failed to open the explicitly specified database. [CLIENT: 172.20.100.6]
2014-09-24 07:14:04.960 Logon
Error: 18456, Severity: 14, State: 38.
2014-09-24 07:14:04.960 Logon
Login failed for user 'BCBIO\sqlservice'. Reason: Failed to open the explicitly specified database. [CLIENT: 172.20.100.6]
2014-09-24 07:34:13.330 spid54
Error: 17053, Severity: 16, State: 1.
2014-09-24 07:34:13.330 spid54
V:\log\templog.ldf: Operating system error 112(There is not enough space on the disk.) encountered.
2014-09-24 07:34:14.430 spid54
Error: 9002, Severity: 17, State: 4.
2014-09-24 07:34:14.430 spid54
The transaction log for database 'tempdb' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases
--Currently using Reporting Service 2000; Visual Studio .NET 2003; Visual Source Safe SSIS 2008 SSAS 2008, SVN --

SQL server service reboot cause the Buffer Data to flush

Could someone please let me know if I just reboot SQL service on Production SQL Server that Causes to remove all Data cached in Buffer cache ? Is reboot SQL service also flush Procedure cache ?
Thank you for in advance for your help .
Daizy

Hi Daizy,
Restart of SQL Server Service is the similar with restarting of the applications. All your caches will be flushed.
Usually, you would not experience any data loss (transaction log records are hardened on the disk synchronously) with exception of transactions with delayed durability in SQL Server 2014. However, all your uncommitted transactions would be rolled back.
Do not forget that reboot would cause performance degradation (data and plans are not cached), database restarts and a few other things. It could be more efficient to use one of the DBCC
commands to cleanup specific cache rather than reboot the service.
Thank you!
Dmitri V. Korotkevitch (MVP, MCM, MCPD)
My blog: http://aboutsqlserver.com

SQL Server service not starting

Hi,
In my environment we have configured SQL server clustering. Currently we are getting the following error and the service is not starting up.
ERROR: TDSSNIClient initialization failed with error 0x2741, status code 0x1.

Hi winoa,
According to your description, you come across the error that TDSSNIClient initialization failed with error 0x2741. Please help to post the full error message from both SQL Server error log and cluster log for further analysis.
Based on my research, this issue could happen due to setting up SQL Server failover cluster over different subnets using these three SQL Server versions(SQL Server 2005, SQL Server 2008, or SQL Server 2008 r2), hardware issue, or that disk and network name
are offline.
Please pay attention to the points below to troubleshoot your issue.
•If you set up SQL Server failover cluster over multiple subnets using the versions of SQL Server 2005, SQL Server 2008 or SQL Server 2008 r2, please make all the nodes in the same subnet, since SQL Server multi-subnet failover cluster is not supported among
those three versions of SQL Server. If possible, you could use the later versions (SQL Server 2012 or 2014) for SQL Server multi-subnet failover cluster.
• Make sure that disk and network name are online.
Regards,
Michelle Li

After change port for TCPIP PORT for default SQL Server instance (MSSQLSERVER), sql service and sql agent service did not started again

Hi
-when i install default instance MSSQLSERVER i added a domain account as a service account,
- when i change port for TCPIP PORT , and after sql service and sql agent service did not started again.
it thrown error
The SQL Server (MSSQLSERVER) service failed to start due to the following error:
The service did not start due to a logon failure.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
<EventID Qualifiers="49152">7000</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
but when i add domain\sqservice account in administrators group these services started,
1) here why this change behavior happened
2i changed the port 1500
adil

HI
the sql instance service is running with domain/sqlservice account ,
- i stopped the sql service service
- when i start it not started again and i found below error message
Domain and account: MOJPORTAL\spsqlservice
This service account does 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.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
<EventID Qualifiers="49152">7041</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2015-04-24T17:12:58.326973300Z" />
<EventRecordID>2177</EventRecordID>
<Correlation />
<Execution ProcessID="520" ThreadID="4044" />
<Channel>System</Channel>
<Computer>PORTALSQL1.mojportal.com</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">MSSQL$xSQL</Data>
<Data Name="param2">xxxL\spsqlservice</Data>
</EventData>
</Event>
adil

SQL Server Service is not reflecting to the new name.

Similar Messages

Maybe you are looking for