Hello! I was trying to install sql server 2012 on windows 2012 server standard, but at the end of the install process I get 3 errors and I haven't been unable to complete the installation. This is the main error:
Microsoft.VC80.CRT,version="8.0.50727.42", type="win32", processorArchitecture="x86", publicKeyToken="1fc8b3b9a1e18e3b".
Please refer to Help and Support for more information.
Error code: 1935
Help would be appreciatedI've been pondering a particular configuration and am wondering if anyone else has some input on it.
If you have your Data, Logs, System and TempDB all in VMDK's and those VMDK's are formatted to 64K and then reside on Clustered Storage that is formatted as 4K, which is then running through a SAN controller that is reading and writing in 2MB chunks, is there value in formatting the SQL drives as 64K? Also, would it be better to format the Clustered Storage as 64K? Is this a situation in which formatting the SQL drives as 64K is becoming a moot point?
Hi, I've been asked to create a new SQL server and restore an old server's DBs to the new server.
I'd like to generate a list of the DB names using powershell to distribute to their creators, in case some of these DBs are no longer needed.
Can anyone point me in the right direction? Should be a common request I'd think.
Thanks,
Scott
Hi,
I have a WIN200R2 Core server on Hyper-V and I'd like to install SQL Server 2012 on it. I use the following command:
Setup.exe /qs /Action=install /Features=SQLEngine,IS,Conn /InstanceName=MSSQLServer /SQLSYSADMINACCOUNTS="Contoso\kim_akers" /IAcceptSQLServerLicenseTerms
(This is from book https://www.microsoft.com/learning/en-us/book.aspx?id=16016 )
I receive the following error message:
'Object reference not set to an instance of an object.Hello good day,
i tryed to install a program called maxiXplorer. but every time during the installation the following error comes up: cannot open database requested by the login. the login failed.
the list in the error is the very long with lost of text i cannot upload a picture at this moment :-( you have to verify my account?
i have had contact with my service guys who give my this programm and he could not help my from where he was sitting. (600km away)
can i upload a picture some way to this text?
Summary.txt file is copied below.
I'm attempting to install SQL Server 2012 using a remote unattended installation via PowerShell. The below result, exit code and the text I've highlighted near the bottom and recopied directly below this sentence appear to be the primary information.
The requested operation cannot be completed.
The computer must be trusted for delegation and the current user account must be configured to allow delegation.
Additional Info:
The installation using the configurationfile works great locally (no errors).
Upon installing via PowerShell remotely, the installation continues for approx 2minutes, process starts, then dies out.
Summary.txt File Output of Failed Installation
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2068774911
Exit facility code: 1201
Exit error code: 1
Exit message: There was an error generating the XML document.
Start time: 2015-05-29 15:18:50
End time: 2015-05-29 15:20:12
Requested action: Install
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=0xE0C083E6%400xB2215DAC&EvtType=0xE0C083E6%400xB2215DAC
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 Adv_SSMS: 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 Browser: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Machine Properties:
Machine name: MBSQLCLX002
Machine processor count: 32
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 Configured
Package properties:
Description: Microsoft SQL Server 2012
ProductName: SQL Server 2012
Type: RTM
Version: 11
Installation location: C:\_installs\2012-dev-x64\x64\setup\
Installation edition: Developer
Slipstream: True
SP Level 2
Product Update Status:
User selected not to include product updates.
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: false
AGTSVCACCOUNT: mhs\svcsqlagent
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Disabled
CLTCTLRNAME: <empty>
CLTRESULTDIR: <empty>
CLTSTARTUPTYPE: 0
CLTSVCACCOUNT: <empty>
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: <empty>
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE: c:\_installs\2012-dev-x64\configurationfile.ini
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
CTLRUSERS: <empty>
ENABLERANU: false
ENU: true
ERRORREPORTING: false
FEATURES: SQLENGINE, SSMS, ADV_SSMS
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTSQLSERVERLICENSETERMS: true
INDICATEPROGRESS: false
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server
INSTALLSQLDATADIR: D:\
INSTANCEDIR: C:\Program Files\Microsoft SQL Server
INSTANCEID: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT AUTHORITY\Network Service
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: true
QUIETSIMPLE: false
ROLE:
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: DefaultSharePointMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: F:\MSSQL11.MSSQLSERVER\MSSQL\Backup
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: mhs\svcsqlserver
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: MHS\IS Database Security Group, MHS\SQLServices, MHS\IS Database Interns
SQLTEMPDBDIR: D:\MSSQL11.MSSQLSERVER\MSSQL\DATA
SQLTEMPDBLOGDIR: E:\MSSQL11.MSSQLSERVER\MSSQL\Log
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: E:\MSSQL11.MSSQLSERVER\MSSQL\Log
SQMREPORTING: false
TCPENABLED: 0
UIMODE: Normal
UpdateEnabled: false
UpdateSource: Slipstream
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20150529_151759\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: 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: 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: 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\20150529_151759\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.ChainerInfrastructureException
Message:
There was an error generating the XML document.
HResult : 0x84b10001
FacilityCode : 1201 (4b1)
ErrorCode : 1 (0001)
Data:
DisableWatson = true
Stack:
at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.SerializeObject(String rootPath, Object objectToSerialize, Boolean saveToCache)
at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.FlushCache(Boolean removeAllCachedObj)
at Microsoft.SqlServer.Configuration.SetupExtension.DatastoreCacheFeatureConfigEventHandler.InConfigurationActionExecutionEventHandler(Object sender, FeatureConfigScenarioEventArgs eventArgs)
at Microsoft.SqlServer.Chainer.Infrastructure.NotificationHandler.Invoke(Object notification, Object[] objectArray)
at Microsoft.SqlServer.Configuration.ConfigExtension.ConfigFeatureActionListener.InConfigurationActionExecutionEventHandler(ActionKey key, TextWriter loggingStream)
at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionMetadata.NotifyInExecution(ActionKey actionRunning, TextWriter loggingStream)
at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue()
at Microsoft.SqlServer.Chainer.TimingConfigAction.Execute(String actionId, TextWriter errorStream)
at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun, ServiceContainer context)
Inner exception type: System.InvalidOperationException
Message:
There was an error generating the XML document.
HResult : 0x80131509
Stack:
at System.Xml.Serialization.XmlSerializer.Serialize(XmlWriter xmlWriter, Object o, XmlSerializerNamespaces namespaces, String encodingStyle, String id)
at System.Xml.Serialization.XmlSerializer.Serialize(TextWriter textWriter, Object o)
at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.SerializeObject(String rootPath, Object objectToSerialize, Boolean saveToCache)
Inner exception type: System.Security.Cryptography.CryptographicException
Message:
The requested operation cannot be completed. The computer must be trusted for delegation and the current user account must be configured to allow delegation.
HResult : 0x80090345
Stack:
at System.Security.Cryptography.ProtectedData.Protect(Byte[] userData, Byte[] optionalEntropy, DataProtectionScope scope)
at Microsoft.SqlServer.Common.SqlSecureString.WriteXml(XmlWriter writer)
at System.Xml.Serialization.XmlSerializationWriter.WriteSerializable(IXmlSerializable serializable, String name, String ns, Boolean isNullable, Boolean wrapped)
at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationWriterAgentConfigurationPublic.Write6_AgentConfigurationPublic(String n, String ns, AgentConfigurationPublic
o, Boolean isNullable, Boolean needType)
at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationWriterAgentConfigurationPublic.Write7_AgentConfigurationPublic(Object o)
Hi All,
I am trying to install SQL Server 2014 express edition on my Windows 7 64 Bit system, but unfortunately, everything I have tried so far has resulted in the same error.
Error: 1723 There is a problem with this Windows Installer package. A DLL required for this installation to complete could not be run. Contact your support personnel or package vendor.
I have tried all the possible solutions that I found online. So please refrain from posting a link to another blog or forum because chances are that I have already tried that.
Things that I have tried:
I am aware that there are multiple threads with the same issue, but none have been able to resolve this for me.
It is really urgent for me to resolve this and install the package over the weekend. Any help would be really appreciated.
Note: I am unable to add the links to the log files as of now, but would do so ASAP.
Hi All
I have a question about Service Packs and Cumulative Updates for SQL 2008 R2.
Do you need to apply them in the order that they are released? Or can you just apply the latest Service Pack and Cumulative Update?
Regards
Hi,
I downlaoded SQL Server Express 2014 and double click to install it. The file decompress box appears. When it finished, it closed and then no other dialog / instructions appears.
I checked the SQL log file at TEMP folder and found that it attempted to remove .Net security code group node and then close the setup with code 0x00000000
Seems I cannot upload the whole log file here thus I copied some below:
06/01/2015 16:26:54.881 ======================================================================Hi Team,
I have been looking whether my SQL Server 2005 (Enterprise Edition) - SP4 instance is licensed version or not on windows server 2003 standard edition. This instance was installed few year back, is there any way to find out the whether my SQL Server software
is licenced or not.
Thanks,
Dathuraj
Dathuraj
I am attempting to do a silent install of SQL Server 2008r2 EXPRESS that includes SQL Server Management Studio. I am failing to get Management Studio as part of the install. My command is:
C:\Users\Root\Desktop\SQLServer2008r2\SQLEXPRWT_x64_ENU.exe /QS /INSTANCENAME=MSSQLSERVER /ACTION=Install /FEATURES=SQL,BC,Conn,ADV_SSMS /SAPWD=Password1! /SECURITYMODE=SQL /TCPENABLED=1 /ADDCURRENTUSERASSQLADMIN /SQLSVCSTARTUPTYPE=Automatic /SQLSVCACCOUNT="NT AUTHORITY\SYSTEM" /AGTSVCACCOUNT="NT AUTHORITY\SYSTEM" /IACCEPTSQLSERVERLICENSETERMS
This is based on docs here:
https://technet.microsoft.com/en-us/library/ms144259%28v=sql.105%29.aspx?f=255&MSPPError=-2147217396#Feature
which show that the /FEATURES= parameter should include ADV_SSMS to get SQL Server Management Studio.
I will post contents of various install logs in separate messages below. Any ideas why the Management Studio is not getting installed?
Hello team,
We were installing SQL Server 2014 as a part of setting up our SharePoint 2013 environment.
In the "installation section" the setup failed giving the following error:
Cannot use file 'E:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Data\ReportServer.mdf', because it is on a volume with sector size 2097152. SQL Server supports a maximum sector size of 4096 bytes. Move the file to a volume with a compatible sector size.
We checked the details of the E: partition as follows by running command "Fsutil fsinfo ntfsinfo e:" --
Bytes Per Sector : 512
Bytes Per Physical Sector : 4096
Bytes Per Cluster : 4096
Now we are not sure if the formatting has gone wrong or any other thing. For reference, the error log is as follows:
2015-06-02 07:07:39.71 Server Microsoft SQL Server 2014 - 12.0.2000.8 (X64) Feb 20 2014 20:04:26 Copyright (c) Microsoft Corporation Enterprise Edition: Core-based Licensing (64-bit) on Windows NT 6.3 <X64> (Build 9600: ) 2015-06-02 07:07:39.71 Server UTC adjustment: -4:00 2015-06-02 07:07:39.71 Server (c) Microsoft Corporation. 2015-06-02 07:07:39.71 Server All rights reserved. 2015-06-02 07:07:39.71 Server Server process ID is 3100. 2015-06-02 07:07:39.71 Server System Manufacturer: 'IBM', System Model: 'System x3550 M3 -[7944AC1]-'. 2015-06-02 07:07:39.71 Server Authentication mode is MIXED. 2015-06-02 07:07:39.71 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG'. 2015-06-02 07:07:39.72 Server The service account is 'domain\sql_services'. This is an informational message; no user action is required. 2015-06-02 07:07:39.72 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 2015-06-02 07:07:39.72 Server Command Line Startup Parameters: -s "MSSQLSERVER" -m "SqlSetup" -Q -q "SQL_Latin1_General_CP1_CI_AS" -T 4022 -T 4010 -T 3659 -T 3610 -T 8015 2015-06-02 07:07:39.98 Server SQL Server detected 2 sockets with 4 cores per socket and 8 logical processors per socket, 16 total logical processors; using 16 logical processors based on SQL Server licensing. This is an informational message; no user action is required. 2015-06-02 07:07:39.98 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required. 2015-06-02 07:07:39.98 Server Detected 16372 MB of RAM. This is an informational message; no user action is required. 2015-06-02 07:07:39.98 Server Using conventional memory in the memory manager. 2015-06-02 07:07:40.26 Server Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033) 2015-06-02 07:07:40.30 Server Perfmon counters for resource governor pools and groups failed to initialize and are disabled. 2015-06-02 07:07:40.32 Server Query Store settings initialized with enabled = 1, 2015-06-02 07:07:40.32 Server The maximum number of dedicated administrator connections for this instance is '1' 2015-06-02 07:07:40.33 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. 2015-06-02 07:07:40.35 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. 2015-06-02 07:07:40.35 Server Lock partitioning is enabled. This is an informational message only. No user action is required. 2015-06-02 07:07:40.38 Server Database Mirroring Transport is disabled in the endpoint configuration. 2015-06-02 07:07:40.38 spid8s Warning ****************** 2015-06-02 07:07:40.39 spid8s SQL Server started in single-user mode. This an informational message only. No user action is required. 2015-06-02 07:07:40.39 spid8s Starting up database 'master'. 2015-06-02 07:07:40.47 Server CLR version v4.0.30319 loaded. 2015-06-02 07:07:40.49 Server Software Usage Metrics is disabled. 2015-06-02 07:07:40.70 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\. 2015-06-02 07:07:40.81 spid8s SQL Server Audit is starting the audits. This is an informational message. No user action is required. 2015-06-02 07:07:40.81 spid8s SQL Server Audit has started the audits. This is an informational message. No user action is required. 2015-06-02 07:07:40.88 spid8s SQL Trace ID 1 was started by login "sa". 2015-06-02 07:07:40.90 spid8s Server name is 'INTRAUATDB2013'. This is an informational message only. No user action is required. 2015-06-02 07:07:40.91 spid17s Password policy update was successful. 2015-06-02 07:07:40.96 spid17s A self-generated certificate was successfully loaded for encryption. 2015-06-02 07:07:40.96 spid17s Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ]. 2015-06-02 07:07:40.96 spid17s Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag 7806. This is an informational message only. No user action is required. 2015-06-02 07:07:40.96 spid17s SQL Server is now ready for client connections. This is an informational message; no user action is required. 2015-06-02 07:07:40.96 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. 2015-06-02 07:07:40.98 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/IntraUATDB2013.***.****.com ] for the SQL Server service. Windows return code: 0x2098, state: 15. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered. 2015-06-02 07:07:40.98 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/IntraUATDB2013.***.****.com:1433 ] for the SQL Server service. Windows return code: 0x2098, state: 15. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered. 2015-06-02 07:07:42.48 spid18s A new instance of the full-text filter daemon host process has been successfully started. 2015-06-02 07:07:42.66 spid8s Starting up database 'msdb'. 2015-06-02 07:07:42.67 spid11s Starting up database 'mssqlsystemresource'. 2015-06-02 07:07:42.69 spid11s The resource database build version is 12.00.2000. This is an informational message only. No user action is required. 2015-06-02 07:07:42.83 spid11s Starting up database 'model'. 2015-06-02 07:07:43.09 spid11s Clearing tempdb database. 2015-06-02 07:07:43.60 spid11s Starting up database 'tempdb'. 2015-06-02 07:07:43.71 spid8s Recovery is complete. This is an informational message only. No user action is required. 2015-06-02 07:07:43.81 spid51 Changed database context to 'master'. 2015-06-02 07:07:43.81 spid51 Changed language setting to us_english. 2015-06-02 07:07:44.03 spid51 Setting database option RECOVERY to FULL for database 'model'. 2015-06-02 07:07:44.09 spid51 Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install. 2015-06-02 07:07:44.12 spid51 Configuration option 'default language' changed from 0 to 0. Run the RECONFIGURE statement to install. 2015-06-02 07:07:44.13 spid51 Configuration option 'default full-text language' changed from 1033 to 1033. Run the RECONFIGURE statement to install. 2015-06-02 07:07:44.14 spid51 Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install. 2015-06-02 07:07:44.26 spid51 Setting database option NEW_BROKER to ON for database 'tempdb'. 2015-06-02 07:07:44.30 spid51 Setting database option NEW_BROKER to ON for database 'msdb'. 2015-06-02 07:07:44.43 spid51 The file "tempdev" has been modified in the system catalog. The new path will be used the next time the database is started. 2015-06-02 07:07:44.44 spid51 The file "templog" has been modified in the system catalog. The new path will be used the next time the database is started. 2015-06-02 07:07:44.59 spid51 Changed database context to 'master'. 2015-06-02 07:07:44.59 spid51 Changed language setting to us_english. 2015-06-02 07:07:44.86 spid51 Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install. 2015-06-02 07:07:44.88 spid51 Configuration option 'Agent XPs' changed from 0 to 1. Run the RECONFIGURE statement to install. 2015-06-02 07:07:44.90 spid51 Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required. 2015-06-02 07:07:44.94 spid51 Using 'xpstar.dll' version '2014.120.2000' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required. 2015-06-02 07:07:44.96 spid51 Configuration option 'Agent XPs' changed from 1 to 0. Run the RECONFIGURE statement to install. 2015-06-02 07:07:44.97 spid51 Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install. 2015-06-02 07:07:46.11 spid51 Changed database context to 'master'. 2015-06-02 07:07:46.11 spid51 Changed language setting to us_english. 2015-06-02 07:07:46.27 spid51 Error: 5179, Severity: 16, State: 1. 2015-06-02 07:07:46.27 spid51 Cannot use file 'F:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Data\ReportServer_log.ldf', because it is on a volume with sector size 2097152. SQL Server supports a maximum sector size of 4096 bytes. Move the file to a volume with a compatible sector size. 2015-06-02 07:07:46.27 spid51 Error: 5179, Severity: 16, State: 1. 2015-06-02 07:07:46.27 spid51 Cannot use file 'E:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Data\ReportServer.mdf', because it is on a volume with sector size 2097152. SQL Server supports a maximum sector size of 4096 bytes. Move the file to a volume with a compatible sector size. 2015-06-02 07:07:46.27 spid51 Error: 5179, Severity: 16, State: 1. 2015-06-02 07:07:46.27 spid51 Cannot use file 'F:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Data\ReportServer_log.ldf', because it is on a volume with sector size 2097152. SQL Server supports a maximum sector size of 4096 bytes. Move the file to a volume with a compatible sector size. 2015-06-02 07:07:46.27 spid51 Error: 5179, Severity: 16, State: 1. 2015-06-02 07:07:46.27 spid51 Cannot use file 'E:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Data\ReportServer.mdf', because it is on a volume with sector size 2097152. SQL Server supports a maximum sector size of 4096 bytes. Move the file to a volume with a compatible sector size. 2015-06-02 07:07:46.27 spid51 Error: 1802, Severity: 16, State: 4. 2015-06-02 07:07:46.27 spid51 CREATE DATABASE failed. Some file names listed could not be created. Check related errors. 2015-06-02 07:42:06.49 spid51 Error: 5179, Severity: 16, State: 1. 2015-06-02 07:42:06.49 spid51 Cannot use file 'F:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Data\ReportServer_log.ldf', because it is on a volume with sector size 2097152. SQL Server supports a maximum sector size of 4096 bytes. Move the file to a volume with a compatible sector size. 2015-06-02 07:42:06.49 spid51 Error: 5179, Severity: 16, State: 1. 2015-06-02 07:42:06.49 spid51 Cannot use file 'E:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Data\ReportServer.mdf', because it is on a volume with sector size 2097152. SQL Server supports a maximum sector size of 4096 bytes. Move the file to a volume with a compatible sector size. 2015-06-02 07:42:06.49 spid51 Error: 5179, Severity: 16, State: 1. 2015-06-02 07:42:06.49 spid51 Cannot use file 'F:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Data\ReportServer_log.ldf', because it is on a volume with sector size 2097152. SQL Server supports a maximum sector size of 4096 bytes. Move the file to a volume with a compatible sector size. 2015-06-02 07:42:06.49 spid51 Error: 5179, Severity: 16, State: 1. 2015-06-02 07:42:06.49 spid51 Cannot use file 'E:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Data\ReportServer.mdf', because it is on a volume with sector size 2097152. SQL Server supports a maximum sector size of 4096 bytes. Move the file to a volume with a compatible sector size. 2015-06-02 07:42:06.49 spid51 Error: 1802, Severity: 16, State: 4. 2015-06-02 07:42:06.49 spid51 CREATE DATABASE failed. Some file names listed could not be created. Check related errors. 2015-06-02 07:48:37.45 Logon Error: 18461, Severity: 14, State: 1. 2015-06-02 07:48:37.45 Logon Login failed for user 'domain\sql_admin'. Reason: Server is in single user mode. Only one administrator can connect at this time. [CLIENT: <local machine>] 2015-06-02 07:49:43.17 Logon Error: 18461, Severity: 14, State: 1. 2015-06-02 07:49:43.17 Logon Login failed for user 'domain\sql_services'. Reason: Server is in single user mode. Only one administrator can connect at this time. [CLIENT: <local machine>] 2015-06-02 07:49:43.19 Logon Error: 18461, Severity: 14, State: 1. 2015-06-02 07:49:43.19 Logon Login failed for user 'domain\sql_services'. Reason: Server is in single user mode. Only one administrator can connect at this time. [CLIENT: <local machine>] 2015-06-02 08:01:23.49 Logon Error: 18461, Severity: 14, State: 1. 2015-06-02 08:01:23.49 Logon Login failed for user 'sa'. Reason: Server is in single user mode. Only one administrator can connect at this time. [CLIENT: <local machine>]
Regards, Nayan
Hello Guys,
We have two nodes and of course some clustered disks {data, logs, etc..}
We will migrate to new Storage >> please correct me if i'm wrong but the simplest way is to
1. Stop the SQL Services and start the storage migration
2. Add the new Storage to the Clustered SQL Instance (from the failover manager)
3. Remove the old storage from the SQL Instance (from the failover manager)
4. Assign the old driver letters to the new storage
5. start the SQL Services ..
----------------------------------------------------------------
Friend of mine told me this is wrong. and i should after "step 2" i need to de-attach all SQL Databases and after step 4.. i should reattach them all again to make sure.
I don't understand why ! i will be using the same driver letters and no need to re attach them again !
Thanks in advance :)
Hi,
I am using windows 8 and I have only one user in laptop. While installing SQL 2014, I am getting an error (Missing System Administrator). Under SQL Server Agent and SQL Server Database I have select the system user and gave the password but still I am getting the error.
Can anyone please help me how to resolve this.
Thanks in advance.
NRC
Hi,
I know there's an option in the SSMS to remove the hook at the option
"Prevent Saving changes that require table re-creation".
But how can I set the option silent. I mean for instance at the setup or by a secret T-SQL command or setting a value in a hidden file? I don't want the user to open the options dialog.
Help would be appreciated. Thanks
EDIT:
Hi, thanks to all answers.
I found a way to solve this after I stumbled over the word "registry" in some community.
Then I logged the registry by a tool and alas there was it. So the thing is to set
the registry entry by our own setup after installing the SSMS.
when i m trying to install SQl Server 2008 R2 the following errors are occurred
cannot find service{0}.
Parameter name:MSSQLServerADHelper100
I am using SQL Server 2008 R2. I'd like to set up a reporting server with SSRS but I cannot find out how to install it. Please help.
Thanks
Dear Expert,
This is my first question to this forum and poor in english.
I had made certain application with Back end MS SQL 2008 Express.
Few of My client needs to run the same application in their portable Drive (Ext. HDD).They have intention to work on on application in window PC or Laptop.
I came to know about MS sql local DB 2012 which has no installation issue and start its services as and when require.
But I m not finding the way how to run / deploy my application along with MS SQL local DB.
Please help.