SSMS SQL 2012 (11.0.5058.0) - WIN7 32BITS - ASIDE WITH SSMS SQL 2008R2 TAKES NEARLY 12s to launch
Hello, just install SSMS 2012 on a Win7 box aside with SSMS 2008R2. When I launch the program, it takes nearly 12s before I have the SQL Splash screen. Any idea why is it so slow ? How can troubleshoot this issue ? Thank's for help. Olivier
Hello,
Try running SSMS with the /nosplash or -nosplash switch to see if it takes less time to start.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com
Similar Messages
-
How to set SQL Server Login MUST_CHANGE, CHECK_POLICY, CHECK_EXPIRATION all to OFF with T-SQL
How to set SQL Server Login MUST_CHANGE, CHECK_POLICY, CHECK_EXPIRATION all to OFF with T-SQL. SSMS will not allow me to change policies to OFF. Error: 15128 - The CHECK_POLICY and CHECK_EXPIRATION options cannot be turned OFF when MUST_CHANGE is
on. I am attempting to change these options in a test environment. Thanks, RichardIt appears you have to change the password first(it could the same password but an alter command needs to be done)
check this : http://www.sqldbadiaries.com/2010/11/07/the-check_policy-and-check_expiration-options-cannot-be-turned-off-when-must_change-is-on/
http://sqldbpool.com/2012/10/08/the-check_policy-and-check_expiration-options-cannot-be-turned-off-when-must_change-is-on-microsoft-sql-server-error-15128/
Hope it Helps!! -
Sql 2012 server for SCCM 2012 - Agent not starting
Hi ,
In our environment we have a Sql 2012, and it was working fine till now. but after installation of RDP role and subsequent installation of certificates for remote desktop in the SCCM server ( SQL 2012 is
installed in it)
we are facing the issue - Sql server management studio not connecting ( windows authenticaltion)
1) A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - No process is on the other end of the pipe.) (Microsoft SQL Server, Error: 233)A
2) I tried starting the sql agent service in services.msc and the below error came
The SQL Server Agent (MSSQLSERVER) service on Local Computer started and then stopped.
Some services stop automatically if they are not in use by other services or programs.
3) In the Sql Server configuration manager also tried starting the sql agent but
The request failed or the service did not respond in a timely fashion.
Consult the event log or other applicable error logs for details.
The widows event logs show this error
A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection.
The TLS protocol defined fatal error code is 20. The Windows SChannel error state is 960.
We have removed the certificate and the RDP role in that .
Can anyone please help on this
Anand MI would check for error messages in the SQL Server ERROLOG file and also Agent's SQLAGENT.OUT file.
Tibor Karaszi, SQL Server MVP |
web | blog -
VS2012 Wont Connect to SQL 2012 Server Location
When I attempt to connect to a SQL 2012 Instance, VS2012 crashes. I can connect fine using SQL Management Studio to the SQL 2012 instance, and my VS2012 connects no problem to my SQL 2008 R2 Instances.
Any suggestions?Hello,
Have you applied Update 4 for VS 2012?
http://www.microsoft.com/en-us/download/details.aspx?id=39305
Could you try to reset VS settings?
Devenv.exe /ResetSettings
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com -
SQL 2012 installation Error-The MOF compiler could not connect with the WMI server
Hi all,
I am getting below error while installing SQL 2012 Dev edition in Win 8.1 Pro.
I am facing lot of issues while installing SQL 2012 in Win 8.1 Pro.Any other steps we need to take to install SQL 2012 in Win 8.1.
Thanks in advance.Installation:
Installation for SQL Server 2012
Hardware and Software Requirements for Installing SQL Server 2012
Installing the .NET Framework 3.5 on Windows 8 or 8.1
About "The MOF compiler could not connected with the WMI server" error message:
Please, verify the Windows Management Instrumentation has status "started" and is set with Startup Type "Automatic". (Alberto Morillo, SQLCoffee.com).
José Diz Belo Horizonte, MG - Brasil -
Quick description of setup: I have 4 total SharePoint servers, 2WFE's, 2APP's, and a SQL Cluster. I am using SQL 2012, + I have installed the reporting services add-in for SQL 2012 and have gone through the entire setup. Everything works,
KCD, stored credentials, I am able to create reports within report builder, launch report builder and so on... When I publish the site using UAG, report builder fails to connect to the report server, in this case either of the WFE's in the farm. I thought
initially it was "body parsing" since looking at the diagnostic logs I noticed that the request coming in looked as if the /_vti_bin/ReportServer/ portion was missing and all I saw was "sitename.something.local:443/ReportService2010.asmx". I added some
entries to skip body parsing and that didnt seem to work at all.
Running FIDDLER - I noticed that when I launch report builder, there is a 302 redirect to the main trunk, or the trunk to which the site is published on. I see a bunch of 302's, and it just stops.. never connects. When I try to connect from within
report builder, I get an error saying "cannot connect to https://sitename.fqdn" make sure the url is correct and or you have permissions.
It seems to me that report builder does not work through UAG. Can anyone suggest a fix?Hello,
I have a same issue, after search, they are saying to make delegation if you are using Kerberos but it didn't work either, so is there any configuration needed.
Regards, -
Upgrade Process from SQL 2005 to SQL 2012
Hi All,
I have gone thru multiple threads and would like to understand some steps in detail for me to upgrade SQL 2005 to SQL 2012.
Below is my understanding and questions around it, I would be setting up a new environment with OS 2007/2008 with SQL 2012:
Environment Readiness - Ensure new environment is ready with Win 2007/2008 with SQL 2012 Server
Run Upgrade Advisor on the new environment and point to SQL 2005 instance
Find the breaking/discontinued changes to be done before or After Upgrade
<Question>: Over here I would like to know what should be our approach to make the required changes
<Question>: Obviously I should not be making changes directly on the Production SQL 2005 server, then in that case should I take a backup/restore on the new SQL Server 2012 and then make the required changes to the database objects
like (Table schema(changing column names/datatypes etc.), Stored Procedure, Functions & Views)
<Question>: When I do a backup/restore I would also get the data along with it, so is this a recommended approach or should we only run/use the table schema creation scripts, fix the issues identified by UA and then do an Table to Table import,
any thoughts on this ?
<Question>: If I have to do a table to table Import then I should ensure there's a downtime during the Import or would I have any other better approach
So, basically my questions are around the approach of fixing the issues identified by UA and moving the database to SQL Server 2012 environment, I have around 300 databased to me upgraded.
Please do let me know what should be a good/proven approach ? Pl. do let me know if you would need any more details from me.
---UmeshThanks all for the replies.
I am trying summarize what I have understood here:
Document SQL Server 2005 environment details, Is there any tool which could give us all relevant details
I would take the backup from the SQL Server 2005 Production environment and then restore the same in a test environment which again has SQL Server 2005 and Run Upgrade Advisor on that
Probbaly run SQL Profiler as well to find out the deprecated changes to be done
I should fix all the breaking, discontinued changes on the Test system identified by UA
I should fix all the deprecated changes on the Test system identified by SQL Profiler
Steps 3 & 4 should give me the changed scripts for all database objects (i.e. Table Schema, Stored Procedures, Functions & Views)
<Question> Perform test, I understand this acitivity test can be captured by having SQL profiler running in the background on the SQL Server 2005 production environment where we can identify some days in a week or a month where maximum activity is
expected to ensure we cover most the scenarios, let me know is this approach looks fine or is there a better approach
Now, with regards to acutal upgrade I need to identify a time window where in less activity is done during which I could have a downtime for the actual SQL Server 2005 production environment
Post downtine, I should do a BackUp for all databases from SQL Server 2005 production environment
Test on environment readiness of SQL Server 2012 can be compared against the documentation done as part of the first Step
<Question> Ideally I should a restore first in the new environment which has SQL Server 2012
<Question> Then run the Scripted changes where we fixed all the breaking, discontinued & deprecated changes
<Question> Does above sequence of Step 9 & 10 make sense or is there a better approach of doing it
<Question> Post Upgrade and running of changed scripts, I should run the Upgrade Advisor again and see if everything looks fine
<Question> Perform test again which we ran on SQL Server 2005 Test environment
<Question> These steps should complete the Upgrade process.
Please do let me know if the above sequence look ok to all of you and does it really work in a practical scenario, do let me know your feedback or any change in sequence/process or any other tools that can be used here.
Thanks Again ... -
Sql 2008 r2 cluster side by side with sql 2012 cluster on Windows 2008 R2
We have a SQL 2008R2 active/passive SQL cluster running on Windows 2008 R2 cluster.
I would like to add a SQL 2012 clustered instance to the same Winows 2008 R2 cluster.
Are there any issues involved having a SQL 2008 R2 clustered instance running side by side with a SQL 2012 instance in same Windows 2008 R2 cluster?
Are there any pitfalls/"gotchas" to watch for with SQL 2012 cluster install?
Thank you so much!Hello,
Two instances, one SQL Server 2008 and the other SQL Server 2012, side-by-side, is fully supported.
I would like to recommend you to assign a different port (not port 1433) to the non-default instance
to avoid an IP address conflict between both instances.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com -
MOSS 2007 native mode on SQL 2012 with compatibility mode?
We are on MOSS 2007 SP 3 64-bit (just native, it is not SSRS integration mode) running on SQL 2008 R2 SP2 64-bit. Can the databases move to SQL 2012 with compatibility mode?
Hi,
As far as I know, SQL 2012 is not listed as compatible with SharePoint 2007 on the
technet articles. If you want to upgrade to SharePoint 2010, then you can move the databases and upgrade the database. If you just want to use SQL 2012 with SharePoint 2007, I think it is not applicable.
For more information, please refer to these sites:
SQL Server 2012 not supported on WSS 3.0/MOSS 2007 and versions previous than SharePoint 2010 SP1:
http://blogs.msdn.com/b/calvarro/archive/2012/04/27/sql-2012-not-supported-on-wss-3-0-moss-2007.aspx
SQL Server 2012 support:
http://social.technet.microsoft.com/Forums/en-US/sharepointadmin/thread/02fd7238-9cc2-43fc-a46c-afbfca21210b
Thanks,
Entan Ming
TechNet Subscriber Support in forum
If you have any feedback on our support, please [email protected]
Entan Ming
TechNet Community Support
Will it work with the database set with the compatibility mode ?
/* Server Support Specialist */ -
It's impossible work with SSMS 2012/2014 on SQL Azure
Is several days that it has become impossible to work
with the management studio ons qlazure, the connection freezes
every few seconds.
SSMS
crashes with error "AppHangB1"
Why?
Nome evento problema: AppHangB1
Nome applicazione: Ssms.exe
Versione applicazione: 2014.120.1524.0
Timestamp applicazione: 524df8b2
Firma di blocco: fd4b
Tipo interruzione: 0
Versione SO: 6.1.7601.2.1.0.256.48
ID impostazioni locali: 1040
Firma blocco aggiuntiva 1: fd4bf5877192b1e9296496f42ae1500e
Firma blocco aggiuntiva 2: 19bc
Firma blocco aggiuntiva 3: 19bc3ac82e35c44895e391c584e7a31e
Firma blocco aggiuntiva 4: fd4b
Firma blocco aggiuntiva 5: fd4bf5877192b1e9296496f42ae1500e
Firma blocco aggiuntiva 6: 19bc
Firma blocco aggiuntiva 7: 19bc3ac82e35c44895e391c584e7a31e
Thanks a lot.Hi Flamario,
Did the issue persists? Based on my test, I can connect to SQL database with SQL Server 2014 CTP2 SSMS (11.0.9206). For further analysis, please post the complete application error in the Event Viewer.
Can you connect to on-premise SQL Server instance with SSMS 2014? If the issue reproduce, this may be related to the SSMS rather than the SQL Database connected to. You can try to reinstall SSMS as Mike post above.
Regards,
Fanny Liu
Fanny Liu
TechNet Community Support -
Error during unattended install of SQL 2012 (..setting 'CLTRESULTDIR' does not exist.)
Hi ALl,
I'm trying an automated install of SQL 2012 on WIndows 2012, but I keep running into this error (using a configuration.ini file generated by running through setup and grabbing it just before I clicked 'OK')
Contents of summary log:
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2068578304
Exit facility code: 1204
Exit error code: 0
Exit message: The specified directory 'C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir' for setting 'CLTRESULTDIR' does not
exist.
Start time: 2015-01-09 10:19:12
End time: 2015-01-09 10:20:07
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for SQLEngine: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for Replication: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for FullText: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for DQ: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for AS: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for RS: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for RS_SHP: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for RS_SHPWFE: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for DQC: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for IS: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for Conn: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for Adv_SSMS: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for SDK: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for BC: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for DREPLAY_CTLR: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for DREPLAY_CLT: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for BIDS: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for SSMS: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for SNAC: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for SNAC_SDK: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for Writer: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for BOL: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for Browser: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Machine Properties:
Machine name: IDCSQLTST11
Machine processor count: 2
OS version: Future Windows Version
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
Package properties:
Description: Microsoft SQL Server 2012
ProductName: SQL Server 2012
Type: RTM
Version: 11
SPLevel: 0
Installation location: E:\SQL_Server_2012_StandardEdition\x64\setup\
Installation edition: Standard
Product Update Status:
None discovered.
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: false
AGTSVCACCOUNT: NT Service\SQLSERVERAGENT
AGTSVCPASSWORD: <empty>
AGTSVCSTARTUPTYPE: Automatic
ASBACKUPDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Config
ASDATADIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Data
ASLOGDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT: NT Service\MSSQLServerOLAPService
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Manual
ASSYSADMINACCOUNTS: DOMAINAA\SQLADMINS
ASTEMPDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Temp
BROWSERSVCSTARTUPTYPE: Disabled
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: E:\SQL_Server_2012_StandardEdition\ConfigurationFile.ini
CTLRSTARTUPTYPE: Manual
CTLRSVCACCOUNT: NT Service\SQL Server Distributed Replay Controller
CTLRSVCPASSWORD: <empty>
CTLRUSERS: DOMAINAA\user12345
ENABLERANU: false
ENU: true
ERRORREPORTING: false
FEATURES: SQLENGINE, REPLICATION, FULLTEXT, DQ, AS, RS, RS_SHP, RS_SHPWFE, DQC, BIDS, CONN, IS, BC, SDK, BOL, SSMS, ADV_SSMS,
DREPLAY_CTLR, DREPLAY_CLT, SNAC_SDK
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT Service\MSSQLFDLauncher
FTSVCPASSWORD: <empty>
HELP: false
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\MsDtsServer110
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: true
QUIETSIMPLE: false
ROLE:
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: SharePointFilesOnlyMode
RSSVCACCOUNT: NT Service\ReportServer
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Manual
SAPWD: <empty>
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: Latin1_General_CI_AS
SQLSVCACCOUNT: NT Service\MSSQLSERVER
SQLSVCPASSWORD: <empty>
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: DOMAINAA\SQLADMINS
SQLTEMPDBDIR: F:\TempDB
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: E:\SQLData
SQLUSERDBLOGDIR: D:\SQLLog
SQMREPORTING: false
TCPENABLED: 1
UIMODE: Normal
UpdateEnabled: true
UpdateSource: MU
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20150109_101753\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: SQL Server Replication
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: Full-Text and Semantic Extractions for Search
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: Data Quality Services
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: Analysis Services
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: Reporting Services - Native
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: Reporting Services - SharePoint
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: Reporting Services Add-in for SharePoint Products
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: Data Quality Client
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: Integration Services
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: Client Tools Connectivity
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: Management Tools - Complete
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: Client Tools SDK
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: Client Tools Backwards Compatibility
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: Distributed Replay Controller
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: Distributed Replay Client
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: SQL Server Data Tools
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: Management Tools - Basic
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: SQL Client Connectivity
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: SQL Client Connectivity SDK
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: SQL Writer
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: Documentation Components
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: SQL Browser
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20150109_101753\SystemConfigurationCheck_Report.htm
Exception summary:
The following is an exception stack listing the exceptions in outermost to innermost order
Inner exceptions are being indented
Exception type: Microsoft.SqlServer.Chainer.Infrastructure.InputSettingValidationException
Message:
The specified directory 'C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir' for setting 'CLTRESULTDIR' does not exist.
HResult : 0x84b40000
FacilityCode : 1204 (4b4)
ErrorCode : 0 (0000)
Data:
SQL.Setup.FailureCategory = InputSettingValidationFailure
DisableWatson = true
Stack:
at Microsoft.SqlServer.Chainer.Infrastructure.InputSettingService.LogAllValidationErrorsAndThrowFirstOne(ValidationState vs)
at Microsoft.SqlServer.Configuration.SetupExtension.ValidateFeatureSettingsAction.ExecuteAction(String actionId)
at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun, ServiceContainer context)
Inner exception type: Microsoft.SqlServer.Configuration.DistributedReplayExtension.DirectoryNotExistException
Message:
The specified directory 'C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir' for setting 'CLTRESULTDIR' does not exist.
HResult : 0x87d00006
FacilityCode : 2000 (7d0)
ErrorCode : 6 (0006)
Data:
DirectoryPath = C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir
SettingName = CLTRESULTDIR
WatsonData =
Microsoft.SqlServer.Configuration.DistributedReplayExtension.DirectoryNotExistException@6Hello,
Open the configuration file with notepad, then go to the “features” variable. On the following article you will find what
means each parameter:
http://msdn.microsoft.com/en-us/library/ms144259(v=sql.110).aspx#Feature
You will also find the list of features supported by each edition on the following article:
http://msdn.microsoft.com/en-us/library/Cc645993(v=sql.110).aspx
For example, it seems you have DQ and DQC on that configuration file, please remove them with their corresponding commas.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com
Thanks Albert that worked when I just selected the main features and excluded ones like DQ and DRC. Thing is why would the standard media allow you to install enterprise features, create a configuration file with these enterprise features and then fail?? Why
would Microsoft tease you like that? Frustrating since I spent hours on this .. -
Unable to restore a .bak file in SQL 2012
Environment: SQL 2012 SP1 Standard on Windows Server 2012 R2 Standard (Hyper-V instance on 2012 Standard)
I've been trying to restore a backup file that was updated on another system by our vendor (Omnify)
I'm getting the error: Omnify5.mdf cannot be overwritten. It is being used by the database Omnify5
I've tried putting the database in single user mode, Ive tried taking the database offline
I've tried rebooting
I've tried the following code:
use
Master;
GO
alter
database omnify5
set
single_user
with
rollback immediate;
alter
database omnify5
set
multi_user;
Go
And I've checked file permissions
I've verified the BAK file
I've re-created a backup to see if I could restore using it and still no joy.
Anyone have another idea?
Thanks
Jim Bogart "bogart dot james at gmail dot com"It looks like the file is still accessed by some other process, make sure that the file is no longer connected with any other database
select name,physical_name from sys.master_files
Take the database to single_user
Take the database offline
Put the database in multi_user mode
Restore the database with overwrite option ( You can either use SSMS or Restore command)
RESTORE DATABASE PowerSQL
FROM DISK = 'f:\PowerSQL\PowerSQL.bak'
WITH MOVE 'YourMDFLogicalName' TO 'F:\SQLData\PowerSQL_Data.mdf',
MOVE 'YourLDFLogicalName' TO 'F:\SQLLog\PowerSQL_Log.ldf'
WTIH REPLACE, MOVE
-Prashanth -
SQL 2012 Management Studio Remote Servers Service Status Slow/Stops Working
This is a huge annoyance. I manage about 50 SQL instances of SQL Server versions 2005-2012 and I noticed that it takes 1-2 seconds to load the service status (green arrow) on each individual server. If you then connect to a server, you have to
wait for all the statuses to be loaded first in the Registered Servers list before it loads the statuses for servers in the Object Explorer. This happens whether the servers are registered in Local Server Groups or Central Management Servers, and whether
I have access to all servers (as windows local administrator and sa), or not. It also happens regardless of whether I run as Administrator or normally on my instance of SSMS (which is SQL 2012 Development on Windows Server 2008 R2).
These servers are also registered in alphabetical order by group and server name, which means that if I have "DEV" groups, they will be registered before "PROD", unless I rename accordingly. It sometimes takes a few minutes, if
I'm lucky, to get a server I connect to to load, which means I can't use SSMS to really manage any remote servers and start/stop/pause/resume/restart services.
Worse, sometimes due to a server becoming unavailable (due to updates/patches/failovers), SSMS is unable to load the service statuses anymore for any new server connections made to object explorer, resulting in the loss of ability to view/change service statuses.
In this case, there is no way to recover (Refresh of Central Management Servers does nothing), except to close SSMS and open it again, and then wait again for all the statuses to load.
I have lived with this since first installing SQL, and regardless of the Windows Updates and SQL patches applied, the problem has never gone away. This also happens if I load SSMS in Windows Server 2012. Its starting to become a huge issue now
that I have to patch several servers each month.
I have already checked WMI permissions, GPO, firewall, etc. as per all the suggestion on the internet, including this post
http://www.sqlservercentral.com/Forums/Topic825246-146-1.aspx. None of these suggestions have made a difference, as my real problem is one of connectivity and performance, and
not security, which most of these suggestions apply to. Of note, all servers are in the same domain, firewall is disabled across the board, correct permissions for local administrators exist for remote registry settings, WMI, GPO, etc, and all service
accounts and windows accounts that are used are local admins and sysadmins.
My work-around has been to delete the Central Management Server and any local server group registered servers, close and re-launch SSMS, and then connect to a server I'm interested in via Object Explorer. Otherwise, close and re-launch will take forever.
My other alternative is to RDP into the remote server and manage services via SQL Configuration Manager locally.
If anyone has any ideas on how to fix this, or make it go faster, I'd really appreciate it.
DianeHi Satish,
Thanks for taking the time to reply. Yes, I actually am already using work-arounds (i.e. methods other than SSMS) to accomplish my tasks. My issue is that this is supposed to be working and provide a nice GUI so that you can easily visualize
any issues, and address them directly, without having to hodge-podge access via scripts or 3rd-Party tools.
Since no one else has any comments, I guess there are no plans to make remote server administration work with SSMS properly then, and that kludge methods are the only ones being advocated.
Diane -
SQL 2012 enterprise service pack 2 fails to install
Hi,
I have installed SQL 2012 sp2 x64 onto the main service manager 2012 database, but it fails on the datawarehouse SQL server. Both are going from SP1 to SP2. Servers are running windows server 2012 sp1 x64.
On the datawarehouse server it gets so far and then just displays a message of completed, with all the other fields blank.
The text file for the Summary of the installation has been copied below:
Overall summary:
Final result: The patch installer has failed to update the following instance: MSSQLSERVER. To determine the reason for failure, review the log files.
Exit code (Decimal): -2068709375
Start time: 2015-01-09 13:55:32
End time: 2015-01-09 14:04:09
Requested action: Patch
Instance MSSQLSERVER overall summary:
Final result: The patch installer has failed to update the shared features. To determine the reason for failure, review the log files.
Exit code (Decimal): -2068709375
Exit facility code: 1202
Exit error code: 1
Exit message: The NT service 'MSSQLServerOLAPService' could not be stopped.
Start time: 2015-01-09 14:00:18
End time: 2015-01-09 14:04:01
Requested action: Patch
Exception help link:
http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.5058.0&EvtType=0xAC454CB1%400xF762992B%401202%401&EvtType=0xAC454CB1%400xF762992B%401202%401
Machine Properties:
Machine name: SCSDWM01
Machine processor count: 4
OS version: Future Windows Version
OS service pack:
OS region: United Kingdom
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 MSSQLSERVER MSSQL11.MSSQLSERVER Database Engine Services
1033 Enterprise Edition 11.1.3153.0 No Yes
SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER Full-Text and Semantic Extractions for Search 1033
Enterprise Edition 11.1.3000.0 No Yes
SQL Server 2012 MSSQLSERVER MSAS11.MSSQLSERVER Analysis Services
1033 Enterprise Edition 11.1.3130.0 No Yes
SQL Server 2012 MSSQLSERVER MSRS11.MSSQLSERVER Reporting Services - Native
1033 Enterprise Edition 11.1.3153.0 No Yes
SQL Server 2012
Management Tools - Basic 1033 Enterprise Edition 11.1.3153.0
No Yes
SQL Server 2012
Management Tools - Complete 1033 Enterprise Edition 11.1.3130.0
No Yes
SQL Server 2012
SQL Server Data Tools - Business Intelligence for Visual Studio 2012 1033
11.1.3402.0 No Yes
SQL Server 2012
Integration Services 1033 Enterprise Edition
11.1.3153.0 No Yes
Package properties:
Description: Microsoft SQL Server 2012
ProductName: SQL Server 2012
Type: RTM
Version: 11
SPLevel: 2
KBArticle: KB2958429
KBArticleHyperlink:
http://support.microsoft.com/?kbid=2958429
PatchType: SP
AssociatedHotfixBuild: 0
Platform: x64
PatchLevel: 11.2.5058.0
ProductVersion: 11.0.2100.60
GDRReservedRange: 11.0.5300.0:11.0.5499.0
PackageName: SQLServer2012-KB2958429-x64.exe
Installation location: c:\ce370c3d01e3ec4095540d8578cc7e\x64\setup\
Updated product edition:
Instance Edition
MSSQLSERVER Enterprise
User Input Settings:
ACTION: Patch
ALLINSTANCES: false
CLUSTERPASSIVE: false
CONFIGURATIONFILE:
ENU: false
HELP: false
IACCEPTSQLSERVERLICENSETERMS: true
INDICATEPROGRESS: false
INSTANCEID: <empty>
INSTANCENAME: <empty>
QUIET: false
QUIETSIMPLE: false
SQMREPORTING: false
UIMODE: Normal
X86: false
Rules with failures:
Global rules:
There are no scenario-specific rules.
Rules report file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20150109_135509\SystemConfigurationCheck_Report.htm
Any ideas on why this has happened and how to fix the error?
Thanks.
JazHello,
Open the errorlog file on the following path C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Log. There
you will find a more descriptive error.
I received that error before. The workaround I used is contained on the following article:
http://www.sqlcoffee.com/Troubleshooting112.htm
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com -
Hi,
We have a core sql database server, which have 256 GB physical memory ,and give maximum physical memory to sql server 240000 MB, sql server service startup account has locked memory privilege.
We found that the free memory is 12094108 KB,but the Page Life Expectancy counter is low,about 300.
Does anybody give some advice why sql server don't (or can't) use free memory, and how to find which parts inside sql server took up these free memory?
Many thanks.
SQL Server Version:
Microsoft SQL Server 2012 - 11.0.5532.0 (X64)
Jul 14 2014 15:00:27
Copyright (c) Microsoft Corporation
Enterprise Edition: Core-based Licensing (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
And this is a clustered sql instance and as a primary node of ag.
Attachments are some dmv results.logdate processinfo
text
2014/9/12 3:10 AM Server
Microsoft SQL Server 2012 - 11.0.5532.0 (X64)
Jul 14 2014 15:00:27
Copyright (c) Microsoft Corporation
Enterprise Edition: Core-based Licensing (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
2014/9/12 3:10 AM Server
(c) Microsoft Corporation.
2014/9/12 3:10 AM Server
All rights reserved.
2014/9/12 3:10 AM Server
Server process ID is 9692.
2014/9/12 3:10 AM Server
"System Manufacturer: 'HP', System Model: 'ProLiant DL980 G7'."
2014/9/12 3:10 AM Server
Authentication mode is MIXED.
2014/9/12 3:10 AM Server
Logging SQL Server messages in file 'X:\Sqldata\MSSQL10_50.SQLInstance\MSSQL\Log\ERRORLOG'.
2014/9/12 3:10 AM Server
The service account is 'XX\SQLAccount'. This is an informational message; no user action is required.
2014/9/12 3:10 AM Server
Registry startup parameters:
-d X:\Sqldata\MSSQL10_50.SQLInstance\MSSQL\DATA\master.mdf
-e X:\Sqldata\MSSQL10_50.SQLInstance\MSSQL\Log\ERRORLOG
-l X:\Sqldata\MSSQL10_50.SQLInstance\MSSQL\DATA\mastlog.ldf
2014/9/12 3:10 AM Server
Command Line Startup Parameters:" -s ""SQLInstance"""
2014/9/12 3:10 AM Server
"SQL Server detected 8 sockets with 8 cores per socket and 16 logical processors per socket, 128 total logical processors; using 128 logical processors based on SQL Server licensing. This is an informational message; no user action is required."
2014/9/12 3:10 AM Server
SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2014/9/12 3:10 AM Server
Detected 262133 MB of RAM. This is an informational message; no user action is required.
2014/9/12 3:10 AM Server
Using locked pages in the memory manager.
2014/9/12 3:10 AM Server
Large Page Allocated: 32MB
2014/9/12 3:10 AM Server
Large Page Allocated: 32MB
2014/9/12 3:10 AM Server
Large Page Allocated: 32MB
2014/9/12 3:10 AM Server
Large Page Allocated: 32MB
2014/9/12 3:10 AM Server
Large Page Allocated: 32MB
2014/9/12 3:10 AM Server
Large Page Allocated: 32MB
2014/9/12 3:10 AM Server
Large Page Allocated: 32MB
2014/9/12 3:10 AM Server
Large Page Allocated: 32MB
2014/9/12 3:10 AM Server
This instance of SQL Server last reported using a process ID of 13236 at 2014/9/12 3:09:42 (local) 2014/9/11 19:09:42 (UTC). This is an informational message only; no user action is required.
2014/9/12 3:10 AM Server
Node configuration: node 0: CPU mask: 0x000000000000ffff:0 Active CPU mask: 0x000000000000ffff: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/9/12 3:10 AM Server
Node configuration: node 1: CPU mask: 0x00000000ffff0000:0 Active CPU mask: 0x00000000ffff0000: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/9/12 3:10 AM Server
Node configuration: node 2: CPU mask: 0x000000000000ffff:1 Active CPU mask: 0x000000000000ffff:1. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2014/9/12 3:10 AM Server
Node configuration: node 3: CPU mask: 0x00000000ffff0000:1 Active CPU mask: 0x00000000ffff0000:1. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2014/9/12 3:10 AM Server
Node configuration: node 4: CPU mask: 0x0000ffff00000000:0 Active CPU mask: 0x0000ffff00000000: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/9/12 3:10 AM Server
Node configuration: node 5: CPU mask: 0xffff000000000000:0 Active CPU mask: 0xffff000000000000: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/9/12 3:10 AM Server
Node configuration: node 6: CPU mask: 0x0000ffff00000000:1 Active CPU mask: 0x0000ffff00000000:1. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2014/9/12 3:10 AM Server
Node configuration: node 7: CPU mask: 0xffff000000000000:1 Active CPU mask: 0xffff000000000000:1. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2014/9/12 3:10 AM 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/9/12 3:10 AM Server
Lock partitioning is enabled. This is an informational message only. No user action is required.
2014/9/12 3:10 AM Server
Software Usage Metrics is disabled.
2014/9/12 3:10 AM spid21s
Starting up database 'master'.
2014/9/12 3:10 AM Server
CLR version v4.0.30319 loaded.
2014/9/12 3:10 AM spid21s
Resource governor reconfiguration succeeded.
2014/9/12 3:10 AM spid21s
SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2014/9/12 3:10 AM spid21s
SQL Server Audit has started the audits. This is an informational message. No user action is required.
2014/9/12 3:10 AM spid21s
"SQL Trace ID 1 was started by login ""sa""."
2014/9/12 3:10 AM Server
Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2014/9/12 3:10 AM spid21s
Server name is 'CLSSQLInstance\SQLInstance'. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid21s
The NETBIOS name of the local node that is running the server is 'SVRXXXXHP980'. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid27s
A self-generated certificate was successfully loaded for encryption.
2014/9/12 3:10 AM spid27s
Server is listening on [X.X.X.X <ipv4> 1433].
2014/9/12 3:10 AM spid27s
Server is listening on [ X.X.X.X <ipv4> 1433].
2014/9/12 3:10 AM spid27s
Started listening on virtual network name 'ClsSQLInstance'. No user action is required.
2014/9/12 3:10 AM spid28s
A new instance of the full-text filter daemon host process has been successfully started.
2014/9/12 3:10 AM spid27s
Started listening on virtual network name 'ClsSQlInstance'. No user action is required.
2014/9/12 3:10 AM spid27s
Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQLInstance].
2014/9/12 3:10 AM spid27s
Server named pipe provider is ready to accept connection on [ \\.\pipe\$$\ClsSQlInstance\MSSQL$SQLInstance\sql\query ].
2014/9/12 3:10 AM spid21s
Database mirroring has been enabled on this instance of SQL Server.
2014/9/12 3:10 AM spid32s
AlwaysOn: The availability replica manager is starting. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid23s
Starting up database 'mssqlsystemresource'.
2014/9/12 3:10 AM spid33s
Starting up database 'msdb'.
2014/9/12 3:10 AM spid36s
Starting up database 'XXDB'.
2014/9/12 3:10 AM spid41s
Starting up database 'CXXDB'.
2014/9/12 3:10 AM spid38s
Starting up database 'XXDB'.
2014/9/12 3:10 AM spid42s
Starting up database 'XXbDB'.
2014/9/12 3:10 AM spid37s
Starting up database 'XXDB'.
2014/9/12 3:10 AM spid32s
AlwaysOn Availability Groups: Waiting for local Windows Server Failover Clustering service to start. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid39s
Starting up database 'XXDB'.
2014/9/12 3:10 AM spid32s
AlwaysOn Availability Groups: Local Windows Server Failover Clustering service started. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid32s
AlwaysOn Availability Groups: Waiting for local Windows Server Failover Clustering node to start. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid32s
AlwaysOn Availability Groups: Local Windows Server Failover Clustering node started. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid32s
AlwaysOn Availability Groups: Waiting for local Windows Server Failover Clustering node to come online. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid32s
AlwaysOn Availability Groups: Local Windows Server Failover Clustering node is online. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid32s
AlwaysOn: The availability replica manager is waiting for the instance of SQL Server to allow client connections. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid23s
The resource database build version is 11.00.5532. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid41s
"Error: 35262, Severity: 17, State: 1."
2014/9/12 3:10 AM spid41s
Skipping the default startup of database 'XXDB' because the database belongs to an availability group (Group ID: 65538). The database will be started by the availability group. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid36s
"Error: 35262, Severity: 17, State: 1."
2014/9/12 3:10 AM spid36s
Skipping the default startup of database 'XXDB' because the database belongs to an availability group (Group ID: 65538). The database will be started by the availability group. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid37s
"Error: 35262, Severity: 17, State: 1."
2014/9/12 3:10 AM spid37s
Skipping the default startup of database 'XXDB' because the database belongs to an availability group (Group ID: 65538). The database will be started by the availability group. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid42s
"Error: 35262, Severity: 17, State: 1."
2014/9/12 3:10 AM spid42s
Skipping the default startup of database 'XXDB' because the database belongs to an availability group (Group ID: 65538). The database will be started by the availability group. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid39s
"Error: 35262, Severity: 17, State: 1."
2014/9/12 3:10 AM spid39s
Skipping the default startup of database 'XXDB' because the database belongs to an availability group (Group ID: 65538). The database will be started by the availability group. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid38s
"Error: 35262, Severity: 17, State: 1."
2014/9/12 3:10 AM spid38s
Skipping the default startup of database 'XXDB' because the database belongs to an availability group (Group ID: 65538). The database will be started by the availability group. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid23s
Starting up database 'model'.
2014/9/12 3:10 AM Server
Started listening on virtual network name 'ClsSQlInstance'. No user action is required.
2014/9/12 3:10 AM Server
Dedicated admin connection support was established for listening remotely on port 58313.
2014/9/12 3:10 AM spid27s
SQL Server is now ready for client connections. This is an informational message; no user action is required.
2014/9/12 3:10 AM 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.
2014/9/12 3:10 AM spid32s
AlwaysOn: The local replica of availability group 'AGGroup' is starting. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid32s
"The state of the local availability replica in availability group 'AGGroup' has changed from 'NOT_AVAILABLE' to 'RESOLVING_NORMAL'. The replica state changed because of either a startup, a failover, a communication issue, or a cluster error. For
more information, see the availability group dashboard, SQL Server error log, Windows Server Failover Cluster management console or Windows Server Failover Cluster log. "
2014/9/12 3:10 AM Server
The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ XXXX] for the SQL Server service.
2014/9/12 3:10 AM Server
The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ xxxx ] for the SQL Server service.
2014/9/12 3:10 AM spid23s
Clearing tempdb database.
2014/9/12 3:10 AM spid23s
Starting up database 'tempdb'.
2014/9/12 3:10 AM spid53
AlwaysOn: The local replica of availability group 'AGGroup' is preparing to transition to the primary role in response to a request from the Windows Server Failover Clustering (WSFC) cluster. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid53
"The state of the local availability replica in availability group 'AGGroup' has changed from 'RESOLVING_NORMAL' to 'PRIMARY_PENDING'. The replica state changed because of either a startup, a failover, a communication issue, or a cluster error.
For more information, see the availability group dashboard, SQL Server error log, Windows Server Failover Cluster management console or Windows Server Failover Cluster log. "
2014/9/12 3:10 AM Server
"The state of the local availability replica in availability group 'AGGroup' has changed from 'PRIMARY_PENDING' to 'PRIMARY_NORMAL'. The replica state changed because of either a startup, a failover, a communication issue, or a cluster error. For
more information, see the availability group dashboard, SQL Server error log, Windows Server Failover Cluster management console or Windows Server Failover Cluster log. "
2014/9/12 3:10 AM spid42s
Starting up database 'XXDB'.
2014/9/12 3:10 AM spid39s
Starting up database 'XXDB'.
2014/9/12 3:10 AM spid32s
Starting up database 'XXDB'.
2014/9/12 3:10 AM spid36s
Starting up database 'XXDB'.
2014/9/12 3:10 AM spid41s
Starting up database 'XXDB'.
2014/9/12 3:10 AM spid37s
Starting up database 'XXDB'.
2014/9/12 3:10 AM spid32s
383 transactions rolled forward in database 'XXDB' (10:0). This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid48s
0 transactions rolled back in database 'XXDB' (10:0). This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid39s
CHECKDB for database 'XXDB' finished without errors on 2011-07-27 00:25:13.070 (local time). This is an informational message only; no user action is required.
2014/9/12 3:10 AM spid49s
Server is listening on [ X.X.X.X <ipv4> 5022].
2014/9/12 3:10 AM spid49s
Server is listening on [X.X.X.X <ipv4> 5022].
2014/9/12 3:10 AM spid49s
Started listening on virtual network name 'ClsSQlInstance'. No user action is required.
2014/9/12 3:10 AM spid49s
The Database Mirroring endpoint is now listening for connections.
2014/9/12 3:10 AM spid49s
Service Broker manager has started.
2014/9/12 3:10 AM spid21s
Launched startup procedure 'sp_MSrepl_startup'.
2014/9/12 3:10 AM spid36s
CHECKDB for database 'XXDB' finished without errors on 2011-07-27 00:25:50.283 (local time). This is an informational message only; no user action is required.
2014/9/12 3:10 AM spid42s
A connection for availability group 'AGGroup' from availability replica 'CLSSQLInstance\SQLInstance' with id [58DE3503-18BB-4C53-BD0A-705BE070EA81] to 'SVRXXXXHP580' with id [C5253E8A-298A-45D8-9568-1184EC4CC3A4] has been successfully established.
This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid41s
A connection for availability group 'AGGroup' from availability replica 'CLSSQLInstance\SQLInstance' with id [58DE3503-18BB-4C53-BD0A-705BE070EA81] to 'SVRXXXXHP580' with id [76DBB6D1-8A06-44DC-9357-6ACCC9AE00B7] has been successfully established.
This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid37s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {76dbb6d1-8a06-44dc-9357-6accc9ae00b7}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid37s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {76dbb6d1-8a06-44dc-9357-6accc9ae00b7}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid39s
A connection for availability group 'AGGroup' from availability replica 'CLSSQLInstance\SQLInstance' with id [58DE3503-18BB-4C53-BD0A-705BE070EA81] to 'SVRXXXXHP580' with id [AB354017-E987-4B96-853E-6C292C9011BD] has been successfully established.
This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid190
Failed to verify Authenticode signature on DLL 'D:\Program Files\Microsoft SQL Server\MSSQL11.SQLInstance\MSSQL\Binn\msxmlsql.dll'.
2014/9/12 3:10 AM spid39s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {c5253e8a-298a-45d8-9568-1184ec4cc3a4}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid42s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {c5253e8a-298a-45d8-9568-1184ec4cc3a4}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid37s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {c5253e8a-298a-45d8-9568-1184ec4cc3a4}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid39s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {c5253e8a-298a-45d8-9568-1184ec4cc3a4}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid37s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {c5253e8a-298a-45d8-9568-1184ec4cc3a4}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid39s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {c5253e8a-298a-45d8-9568-1184ec4cc3a4}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid47s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {c5253e8a-298a-45d8-9568-1184ec4cc3a4}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid42s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {c5253e8a-298a-45d8-9568-1184ec4cc3a4}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid42s
A connection for availability group 'AGGroup' from availability replica 'CLSSQLInstance\SQLInstance' with id [58DE3503-18BB-4C53-BD0A-705BE070EA81] to 'SVRXXXXHP580' with id [6752FE19-1AEC-4DB6-AC63-2F8A6A2E67C8] has been successfully established.
This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid42s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {ab354017-e987-4b96-853e-6c292c9011bd}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid47s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {ab354017-e987-4b96-853e-6c292c9011bd}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid42s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {c5253e8a-298a-45d8-9568-1184ec4cc3a4}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid47s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {c5253e8a-298a-45d8-9568-1184ec4cc3a4}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid245s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {6752fe19-1aec-4db6-ac63-2f8a6a2e67c8}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid245s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {6752fe19-1aec-4db6-ac63-2f8a6a2e67c8}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid245s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {ab354017-e987-4b96-853e-6c292c9011bd}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid245s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {ab354017-e987-4b96-853e-6c292c9011bd}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid248s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {ab354017-e987-4b96-853e-6c292c9011bd}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid247s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {ab354017-e987-4b96-853e-6c292c9011bd}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid248s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {ab354017-e987-4b96-853e-6c292c9011bd}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid247s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {ab354017-e987-4b96-853e-6c292c9011bd}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid248s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {c5253e8a-298a-45d8-9568-1184ec4cc3a4}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid248s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {c5253e8a-298a-45d8-9568-1184ec4cc3a4}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid258s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {ab354017-e987-4b96-853e-6c292c9011bd}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid258s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {ab354017-e987-4b96-853e-6c292c9011bd}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid257s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {6752fe19-1aec-4db6-ac63-2f8a6a2e67c8}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid257s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {76dbb6d1-8a06-44dc-9357-6accc9ae00b7}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid258s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {6752fe19-1aec-4db6-ac63-2f8a6a2e67c8}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid258s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {76dbb6d1-8a06-44dc-9357-6accc9ae00b7}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid275s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {6752fe19-1aec-4db6-ac63-2f8a6a2e67c8}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid258s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {6752fe19-1aec-4db6-ac63-2f8a6a2e67c8}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid304s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {76dbb6d1-8a06-44dc-9357-6accc9ae00b7}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid303s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {76dbb6d1-8a06-44dc-9357-6accc9ae00b7}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid258s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {c5253e8a-298a-45d8-9568-1184ec4cc3a4}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid303s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {6752fe19-1aec-4db6-ac63-2f8a6a2e67c8}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid304s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {6752fe19-1aec-4db6-ac63-2f8a6a2e67c8}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid303s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {ab354017-e987-4b96-853e-6c292c9011bd}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid275s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {ab354017-e987-4b96-853e-6c292c9011bd}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid347s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {76dbb6d1-8a06-44dc-9357-6accc9ae00b7}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid304s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {76dbb6d1-8a06-44dc-9357-6accc9ae00b7}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid362s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {c5253e8a-298a-45d8-9568-1184ec4cc3a4}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid362s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {76dbb6d1-8a06-44dc-9357-6accc9ae00b7}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid362s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {76dbb6d1-8a06-44dc-9357-6accc9ae00b7}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid347s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {c5253e8a-298a-45d8-9568-1184ec4cc3a4}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid364s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {6752fe19-1aec-4db6-ac63-2f8a6a2e67c8}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid304s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {6752fe19-1aec-4db6-ac63-2f8a6a2e67c8}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid427
Attempting to load library 'xpsqlbot.dll' into memory. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid427
Using 'xpsqlbot.dll' version '2011.110.2100' to execute extended stored procedure 'xp_qv'. This is an informational message only; no user action is required.
2014/9/12 3:10 AM spid361s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {c5253e8a-298a-45d8-9568-1184ec4cc3a4}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid361s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {c5253e8a-298a-45d8-9568-1184ec4cc3a4}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid347s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {6752fe19-1aec-4db6-ac63-2f8a6a2e67c8}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid361s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {6752fe19-1aec-4db6-ac63-2f8a6a2e67c8}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid53
Configuration option 'Agent XPs' changed from 0 to 1. Run the RECONFIGURE statement to install.
2014/9/12 3:10 AM spid565
Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid565
Using 'xpstar.dll' version '2011.110.5058' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
2014/9/12 3:10 AM spid565
Attempting to load library 'xplog70.dll' into memory. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid565
Using 'xplog70.dll' version '2011.110.5058' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.
2014/9/12 3:10 AM spid361s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {c5253e8a-298a-45d8-9568-1184ec4cc3a4}. This is an informational message only. No user action is required.
2014/9/12 3:10 AM spid605
"SQL Trace ID 2 was started by login ""XX\SQLAccount""."
2014/9/12 3:11 AM spid701
"SQL Trace ID 3 was started by login ""XX\SQLAccount""."
2014/9/12 3:11 AM spid701
SQL Trace stopped. Trace ID = '3'. Login Name = 'XX\SQLAccount'.
2014/9/12 3:11 AM spid360s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {76dbb6d1-8a06-44dc-9357-6accc9ae00b7}. This is an informational message only. No user action is required.
2014/9/12 3:11 AM spid360s
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {76dbb6d1-8a06-44dc-9357-6accc9ae00b7}. This is an informational message only. No user action is required.
Maybe you are looking for
-
One of four co-founders, Parker Harris has been a quietly powerful force in the success of Salesforce.com, which has grown to nearly $7 billion and earned a top spot in the CRM market since launching in 1999. Harris leads all product development, dat
-
Since no one from Adobe is actually going to address this problem and it's a problem that has significant impacts on my work, I'll ask again. I work on an iMac and use Adobe Acrobat via Creative Cloud. Acrobat crashes on me multiple times a day. Lite
-
Hyperlink from summary field in crosstab??
I want to enable a hyperlink on a summary field in a crosstab so that clicking on it will produce a subreport of the detailed items that are included in the count displayed in the summary field. Keeping my username in mind ;-> I have tried everything
-
Would like to have Automator carry out a timed task
Does anyone know how to create an Automator workflow that carries out a command after a designated time period? For example, I would like to have Automator quit Mail after one hour of inactivity. It seems all Automator tasks need to be initiated manu
-
I have a problem that I have been unable to resolve. I was experimenting with the crossfade feature in iTunes. Now, whenever I play songs purchased and downloaded from the iTunes Store, it crossfades between each track. It does this eventhough the cr