SQL Server Express is being a real pain
I've been messing with this SQL Server Express installation
since Friday and still can't get this application and database to
work together correctly. The program is written in ColdFusion, but
the errors seem to be permissions related to me but I just can't
figure it out.
I've created a user within SQL Server Management Express
program and all goes well. I then assign it as database owner for
the particular database I'm using. I've created the datasource from
within the ColdFusion administrator and it says the connection is
being made.
When trying to access the script, I get the error below.
In the SQL Management system I have tried everything that I
know to do - from adding this particular account as a user for the
"tUsers" table and giving it "Select" permissions to re-creating
the account and making it owner of the entire database. I tried
adding the schema to the front and surrounding the table name in
brackets [ ].
The database was restored from a backup on another server.
Would that cause problems at all? I just tried deleting the
database, creating it again, then restoring it from the file and
setting the owner as this user during the import process. I'm still
not having any luck though.
I've searched Google and almost every result is a forums post
from people having this same problem who have fixed it by giving
the account permission to access the database and/or table. For
some reason that isn't working for me - or I'm an idiot and missing
something.
Does anyone have any ideas?
At first, no, I couldn't perform any queries at all against
the database.
I fixed the problem by editing the "server" in the CF admin
for this datasource and making it:
localhost/SQLEXPRESS
CF Admin says it doesn't verify, but if I attach the username
and password to each CFQUERY statement they work!
Very strange problem. I'm not sure if this is a 'feature' or
a known bug, but I don't see any reason why that connection doesn't
verify. Especially since if it would've I could have saved myself
countless hours of work.
Oh well - thanks everyone for your suggestions and
help!
Similar Messages
-
SQL Server Express 2014 on Win8.1: Could not find the Database Engine startup handle
Hello,
I tried to follow all the similarly titled posts in this forum, yet no solution seems to work, so I hope I can find some up-to-date suggestion here (most of the older posts refer to versions from 2008 to 2012...).
I have installed Visual Studio 2013 (with the latest Update 2 RC) on a freshly installed development workstation with Win 8.1 with all its updates. Now I'd want to install SQL Server 2014 Express, but the setup keeps failing with the dreaded "Could
not find the Database Engine startup handle" error (the log follows below).
What I tried:
1) download again and repair. Same error.
2) completely uninstall by launching setup.exe /Action=uninstall (success), then rebooting the OS, then installing again. Same error. I did this twice, the second time I also manually removed any directory left out in C:\Program Files etc.
When I launch the setup, I select all the components for installation in the package SQLEXPRADV_x64_ENU.exe (1.12 GB, last downloaded today -Apr 3, 2014-), and accept all the defaults including the proposed services accounts. There is no preexisting
SQL Server instance, as expected.
The setup takes its time, and finally fails with the error quoted above. I really do not want to reformat my HD and fully reconfigure my workstation, which took about 3 days... Could anyone suggest a solution to have SQL Server 2014 setup so I can start
developing instead of wasting time in administering the system?
Thanks to all! The log follows.
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2061893607
Start time: 2014-04-03 18:30:58
End time: 2014-04-03 19:04:41
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for RS: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for SQLEngine: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for FullText: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for Replication: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Machine Properties:
Machine name: DIOMEDES
Machine processor count: 4
OS version: Windows 8
OS service pack:
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered Configured
Package properties:
Description: Microsoft SQL Server 2014
ProductName: SQL Server 2014
Type: RTM
Version: 12
SPLevel: 0
Installation location: C:\Users\Daniele\Downloads\SQLEXPRADV_x64_ENU\x64\setup\
Installation edition: Express
Product Update Status:
None discovered.
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: true
AGTSVCACCOUNT: NT AUTHORITY\NETWORK SERVICE
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Disabled
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:
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
CTLRUSERS: <empty>
ENABLERANU: true
ENU: true
ERRORREPORTING: false
FEATURES: SQLENGINE, REPLICATION, FULLTEXT, RS, CONN, BC, SDK, BOL, SSMS, ADV_SSMS, LOCALDB
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT Service\MSSQLFDLauncher$SQLEXPRESS
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTSQLSERVERLICENSETERMS: true
INDICATEPROGRESS: false
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: SQLEXPRESS
INSTANCENAME: SQLEXPRESS
ISSVCACCOUNT: NT AUTHORITY\Network Service
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: AllFeatures_WithDefaults
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: DefaultSharePointMode
RSSVCACCOUNT: NT Service\ReportServer$SQLEXPRESS
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: <empty>
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: Latin1_General_CI_AS
SQLSVCACCOUNT: NT Service\MSSQL$SQLEXPRESS
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: DIOMEDES\Daniele
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: false
TCPENABLED: 0
UIMODE: AutoAdvance
UpdateEnabled: true
UpdateSource: MU
USEMICROSOFTUPDATE: false
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140403_183057\ConfigurationFile.ini
Detailed results:
Feature: Management Tools - Complete
Status: Passed
Feature: Client Tools Connectivity
Status: Passed
Feature: Client Tools SDK
Status: Passed
Feature: Client Tools Backwards Compatibility
Status: Passed
Feature: Management Tools - Basic
Status: Passed
Feature: Reporting Services - Native
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A0019
Error description: Could not find the Database Engine startup handle.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A0019
Error description: Could not find the Database Engine startup handle.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
Feature: Full-Text and Semantic Extractions for Search
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A0019
Error description: Could not find the Database Engine startup handle.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
Feature: SQL Server Replication
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A0019
Error description: Could not find the Database Engine startup handle.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
Feature: SQL Browser
Status: Passed
Feature: Documentation Components
Status: Passed
Feature: SQL Writer
Status: Passed
Feature: LocalDB
Status: Passed
Feature: Setup Support Files
Status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140403_183057\SystemConfigurationCheck_Report.htmThank you, it worked! I suppose that it was really your nr.3 which made the difference. I changed NT Service\MSSQL$SQLEXPRESS to NT AUTHORITY\System for the Data service. I'll then change it again as suggested (any suggestion about a "standard"
account to be used here?), even if this is a development workstation using SQL Server Express only as a local database for debugging, so security is not really a big concern.
Thanks for the feedback.Ya I know No3 was real step but just added more info so as to rule out any other possibility.
No not as such, you wont believe,quite few pf my clients I have worked for keep it with local system and they have not complained yet ,they are afraid to change account as few of them faced issue SQL Server not coming online due to logon failure( after changing
startup account to some domain a and that was happening due to some AD policy.But if you have nay plans to move Critical database in production which would be act as Database to some Internet facing application please follow my suggestion
of running SQL Server with Least privileged domain account.
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers -
SQL Server Express intermittent installation issue
Have been seeing this error for several months trying to duplicate and troubleshoot. SQL Server 2008 R2 SP2 Express being installed on Windows 7 (x86 or x64) Professional, various processors, various execution environments (VM and non-VM). Yesterday duplicated
on x86 Win7 Pro VM clean install (installed Win7 Pro, loaded all updates except .NET 4.5, and installed my application). App installer copies .NET 4, Visual Studio 2010 C++ run-time, and then SQL Server 2008 R2 SP2. Below is portion of detail.txt from
setup failure log:
2014-07-12 18:22:17 Slp: ----------------------------------------------------------------------
2014-07-12 18:22:17 Slp: Running Action: SqlEngineDBStartConfigAction_install_configrc_Cpu32
2014-07-12 18:22:17 Slp: Action Data:
2014-07-12 18:22:17 Slp: Feature = SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu32
2014-07-12 18:22:17 Slp: Scenario = install
2014-07-12 18:22:17 Slp: Timing = ConfigRC
2014-07-12 18:22:17 Slp: ConfigObjectType = Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineDBStartConfig
2014-07-12 18:22:17 Slp: FeatureName = SQL_Engine_Core_Inst
2014-07-12 18:22:17 Slp: FeatureCpuType = Cpu32
2014-07-12 18:22:17 Slp: FeaturePackageId = sql_engine_core_inst
2014-07-12 18:22:17 Slp: SlipstreamInstall = 1
2014-07-12 18:22:17 SQLEngine: --SqlEngineDBStartConfig: Install: SqlEngineDBStartConfig Configuration
2014-07-12 18:22:17 SQLEngine: : Action Scenario: Install, Feature Scenario: Install, Resolved Scenario Install
2014-07-12 18:22:17 Slp: Sco: Attempting to get network service account name
2014-07-12 18:22:17 Slp: Sco: Attempting to get NT account from sid S-1-5-20
2014-07-12 18:22:17 Slp: Sco: Attempting to get account from sid S-1-5-20
2014-07-12 18:22:17 Slp: Sco: Attempting to get network service account name
2014-07-12 18:22:17 Slp: Sco: Attempting to get NT account from sid S-1-5-20
2014-07-12 18:22:17 Slp: Sco: Attempting to get account from sid S-1-5-20
2014-07-12 18:22:17 Slp: Sco: Attempting to get account sid for user account NT AUTHORITY\NETWORK SERVICE
2014-07-12 18:22:17 Slp: Sco: Attempting to get sid for user account NT AUTHORITY\NETWORK SERVICE
2014-07-12 18:22:17 Slp: Sco: GetSidForAccount normalized accountName NT AUTHORITY\NETWORK SERVICE parameter to NT AUTHORITY\NETWORK SERVICE
2014-07-12 18:22:17 SQLEngine: --RegistryProperties: container.ActiveNode =
2014-07-12 18:22:17 SQLEngine: --RegistryProperties: container.IsActiveNodeUpgraded = False
2014-07-12 18:22:17 SQLEngine: --RegistryProperties: container.Version =
2014-07-12 18:22:17 SQLEngine: --RegistryProperties: container.IsDefaultInstance = False
2014-07-12 18:22:17 SQLEngine: --RegistryProperties: container.InstanceId = MSSQL10_50.SQLEXPRESS
2014-07-12 18:22:17 SQLEngine: --RegistryProperties: container.ReferenceInstanceId = MSSQL10_50.SQLEXPRESS
2014-07-12 18:22:17 SQLEngine: --RegistryProperties: container.InstanceName = SQLEXPRESS
2014-07-12 18:22:17 SQLEngine: --RegistryProperties: container.SqlServerServiceName = MSSQL$SQLEXPRESS
2014-07-12 18:22:17 SQLEngine: --ProductProperties: Retrieving product properties from local node.
2014-07-12 18:22:17 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
2014-07-12 18:22:17 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\Setup
2014-07-12 18:22:17 Slp: Sco: Attempting to get registry value ProductCode
2014-07-12 18:22:17 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
2014-07-12 18:22:17 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\Setup
2014-07-12 18:22:17 Slp: Sco: Attempting to get registry value Language
2014-07-12 18:22:17 SQLEngine: --GroupProperties: Loading group properties from local machine.
2014-07-12 18:22:17 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
2014-07-12 18:22:17 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\Setup
2014-07-12 18:22:17 Slp: Sco: Attempting to get registry value SQLGroup
2014-07-12 18:22:17 Slp: Sco: Attempting to get account from sid S-1-5-21-3076291671-3154185214-3698330068-1005
2014-07-12 18:22:17 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
2014-07-12 18:22:17 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\Setup
2014-07-12 18:22:17 Slp: Sco: Attempting to get registry value SQLPath
2014-07-12 18:22:17 SQLEngine: --EffectiveProperties: Dumping Effective Properties for new instance.
2014-07-12 18:22:17 SQLEngine: --EffectiveProperties: InstanceId = MSSQL10_50.SQLEXPRESS
2014-07-12 18:22:17 SQLEngine: --EffectiveProperties: InstanceName = SQLEXPRESS
2014-07-12 18:22:17 SQLEngine: --EffectiveProperties: IsDefaultInstance = False
2014-07-12 18:22:17 SQLEngine: --EffectiveProperties: SqlServerServiceName = MSSQL$SQLEXPRESS
2014-07-12 18:22:17 SQLEngine: --EffectiveProperties: IsExpressSku = True
2014-07-12 18:22:17 SQLEngine: --EffectiveProperties: IsWorkgroupSku = False
2014-07-12 18:22:17 SQLEngine: --InstallProperties: Dumping Install Properties
2014-07-12 18:22:17 SQLEngine: --InstallProperties: EnableRanu = True
2014-07-12 18:22:17 SQLEngine: --InstallProperties: SecurityMode =
2014-07-12 18:22:17 SQLEngine: --InstallProperties: LoginMode = 1
2014-07-12 18:22:17 SQLEngine: --InstallProperties: SqlCollation = SQL_Latin1_General_CP1_CI_AS
2014-07-12 18:22:17 SQLEngine: --InstallProperties: SqlAdminAcounts =
2014-07-12 18:22:17 SQLEngine: --InstallProperties: SqlServiceStartupType = Automatic
2014-07-12 18:22:17 SQLEngine: --InstallProperties: SqlAccount = NT AUTHORITY\NETWORK SERVICE
2014-07-12 18:22:17 SQLEngine: --InstallProperties: SqlDomainGroup =
2014-07-12 18:22:17 SQLEngine: --InstallProperties: AddCurrentUserAsSQLAdmin = True
2014-07-12 18:22:17 SQLEngine: --RegistryProperties: Dumping Registry Properties
2014-07-12 18:22:17 SQLEngine: --RegistryProperties: SqlServiceRelativeRegPath = System\CurrentControlSet\Services\MSSQL$SQLEXPRESS
2014-07-12 18:22:17 SQLEngine: --RegistryProperties: CompleteInstanceRegPathByName = SOFTWARE\Microsoft\Microsoft SQL Server\SQLEXPRESS
2014-07-12 18:22:17 SQLEngine: --RegistryProperties: CompleteInstanceRegPathById = SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS
2014-07-12 18:22:17 SQLEngine: --RegistryProperties: ReferenceInstanceRegPathById = SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS
2014-07-12 18:22:17 SQLEngine: --RegistryProperties: MSSQLServerInstanceRegPath = SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQLServer
2014-07-12 18:22:17 SQLEngine: --RegistryProperties: ReferenceMSSQLServerInstanceRegPath = SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQLServer
2014-07-12 18:22:17 SQLEngine: --RegistryProperties: SetupInstanceRegPath = SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\Setup
2014-07-12 18:22:17 SQLEngine: --RegistryProperties: ReferenceSetupInstanceRegPath = SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\Setup
2014-07-12 18:22:17 SQLEngine: --ProductProperties: Dumping Product Properties
2014-07-12 18:22:17 SQLEngine: --ProductProperties: ProductCode = b5153233-9aee-4cd4-9d2c-4faac870dbe2
2014-07-12 18:22:17 SQLEngine: --ProductProperties: LCID = 1033
2014-07-12 18:22:17 SQLEngine: --GroupProperties: Dumping Group Properties
2014-07-12 18:22:17 SQLEngine: --GroupProperties: SqlEngineGroupSid = S-1-5-21-3076291671-3154185214-3698330068-1005
2014-07-12 18:22:17 SQLEngine: --GroupProperties: SqlEngineGroupNameFromSid = WIN-EAD5VG4PBDE\SQLServerMSSQLUser$WIN-EAD5VG4PBDE$SQLEXPRESS
2014-07-12 18:22:17 SQLEngine: --GroupProperties: SqlEngineGroupNameFromSidNoDomain = SQLServerMSSQLUser$WIN-EAD5VG4PBDE$SQLEXPRESS
2014-07-12 18:22:17 SQLEngine: --PublicBasedDirectoryProperties: Dumping Directory Propreties
2014-07-12 18:22:17 SQLEngine: --PublicBasedDirectoryProperties: DataRootDirectory = c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL
2014-07-12 18:22:17 SQLEngine: --PublicBasedDirectoryProperties: SystemDataDirectory = c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA
2014-07-12 18:22:17 SQLEngine: --PublicBasedDirectoryProperties: InstallSqlInstanceDir = c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL
2014-07-12 18:22:17 SQLEngine: --PublicBasedDirectoryProperties: DefaultDataDirectory = c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA
2014-07-12 18:22:17 SQLEngine: --PublicBasedDirectoryProperties: DefaultLogDirectory = c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA
2014-07-12 18:22:17 SQLEngine: --PublicBasedDirectoryProperties: BackupDirectory = c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Backup
2014-07-12 18:22:17 SQLEngine: --PublicBasedDirectoryProperties: TempDbDirectory = c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA
2014-07-12 18:22:17 SQLEngine: --PublicBasedDirectoryProperties: TempDbLogDirectory = c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA
2014-07-12 18:22:17 SQLEngine: --PublicBasedDirectoryProperties: ErrorLogDirectory = c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Log
2014-07-12 18:22:17 SQLEngine: --PublicBasedDirectoryProperties: TemplateDataDirectory = c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Template Data
2014-07-12 18:22:17 SQLEngine: --PublicBasedDirectoryProperties: SqlInstanceBinnDir = c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Binn
2014-07-12 18:22:17 SQLEngine: --PublicBasedDirectoryProperties: SqlInstanceTemplatesDir = c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Binn\Templates
2014-07-12 18:22:17 SQLEngine: --PublicBasedDirectoryProperties: MasterDbPath =
2014-07-12 18:22:17 SQLEngine: --PublicBasedDirectoryProperties: MasterLogPath =
2014-07-12 18:22:17 SQLEngine: --SqlEngineDBStartConfig: ConfigRC : SqlEngineDBStartConfig Configuration
2014-07-12 18:22:18 Slp: Sco: Attempting to set directory full path
2014-07-12 18:22:18 Slp: Sco: Attempting to normalize directory path c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA
2014-07-12 18:22:18 Slp: Sco: Attempting to set directory full path
2014-07-12 18:22:18 Slp: Sco: Attempting to normalize directory path c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA
2014-07-12 18:22:18 Slp: Sco: Attempting to set directory full path
2014-07-12 18:22:18 Slp: Sco: Attempting to normalize directory path c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA
2014-07-12 18:22:18 SQLEngine: --SqlServerStartup: SQLEngine: Slipstream case: Enable traceflag -T902
2014-07-12 18:22:18 SQLEngine: : Checking Engine checkpoint 'StartEngineService'
2014-07-12 18:22:18 SQLEngine: --SqlServerServiceSCM: Starting SQL via SCM (-mSqlSetup -f -Q -qSQL_Latin1_General_CP1_CI_AS -T4022 -T4010 -T3659 -T3610 -T902 -dc:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Template Data\master.mdf -lc:\Program
Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Template Data\mastlog.ldf)...
2014-07-12 18:22:18 Slp: Sco: Attempting to start service MSSQL$SQLEXPRESS
2014-07-12 18:22:20 Slp: Sco: Service MSSQL$SQLEXPRESS started
2014-07-12 18:22:20 Slp: Sco: Attempting to get service process id for service MSSQL$SQLEXPRESS
2014-07-12 18:22:20 Slp: Invoking QueryServiceStatusEx Win32 API
2014-07-12 18:22:20 Slp: Sco: Returning service process id 3480
2014-07-12 18:22:20 SQLEngine: : Checking Engine checkpoint 'GetSqlServerProcessHandle'
2014-07-12 18:22:22 SQLEngine: --SqlServerServiceSCM: Waiting for nt event 'Global\sqlserverRecComplete$SQLEXPRESS' to be created
2014-07-12 18:22:24 SQLEngine: --SqlServerServiceSCM: Waiting for nt event 'Global\sqlserverRecComplete$SQLEXPRESS' or sql process handle to be signaled
2014-07-12 18:22:24 SQLEngine: : Checking Engine checkpoint 'WaitSqlServerStartEvents'
2014-07-12 18:22:59 Slp: Sco: Attempting to initialize script
2014-07-12 18:23:01 Slp: Sco: Attempting to initialize default connection string
2014-07-12 18:23:03 Slp: Sco: Attempting to set script connection protocol to NotSpecified
2014-07-12 18:23:03 Slp: Sco: Attempting to set script connection protocol to NamedPipes
2014-07-12 18:23:03 SQLEngine: --SqlDatabaseServiceConfig: Connection String: Data Source=\\.\pipe\SQLLocal\SQLEXPRESS;Initial Catalog=master;Integrated Security=True;Pooling=False;Network Library=dbnmpntw;Application Name=SqlSetup
2014-07-12 18:23:03 SQLEngine: : Checking Engine checkpoint 'ServiceConfigConnect'
2014-07-12 18:23:03 SQLEngine: --SqlDatabaseServiceConfig: Connecting to SQL....
2014-07-12 18:23:03 Slp: Sco: Attempting to connect script
2014-07-12 18:23:04 Slp: Connection string: Data Source=\\.\pipe\SQLLocal\SQLEXPRESS;Initial Catalog=master;Integrated Security=True;Pooling=False;Network Library=dbnmpntw;Application Name=SqlSetup
2014-07-12 18:24:16 Slp: Sco: Connection error code from SqlException is : -2
2014-07-12 18:24:30 Slp: Watson Bucket 1
Original Parameter Values
2014-07-12 18:24:30 Slp: Parameter 0 : SQL Server 2008
R2@RTM@
2014-07-12 18:24:30 Slp: Parameter 2 : System.Data.SqlClient.SqlInternalConnection.OnError
2014-07-12 18:24:30 Slp: Parameter 3 :
Microsoft.SqlServer.Configuration.Sco.ScoException@1211@1
2014-07-12 18:24:30 Slp: Parameter 4 :
System.Data.SqlClient.SqlException@-2146232060
2014-07-12 18:24:30 Slp: Parameter 5 : SqlEngineDBStartConfigAction_install_configrc
2014-07-12 18:24:30 Slp:
Final Parameter Values
2014-07-12 18:24:30 Slp: Parameter 0 : SQL Server 2008
R2@RTM@
2014-07-12 18:24:30 Slp: Parameter 2 : 0x1BBF2F31
2014-07-12 18:24:30 Slp: Parameter 3 : 0x0A2FBD17@1211@1
2014-07-12 18:24:30 Slp: Parameter 4 : 0x3906094D
2014-07-12 18:24:30 Slp: Parameter 5 : SqlEngineDBStartConfigAction_install_configrc
2014-07-12 18:24:36 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140712_180319\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
2014-07-12 18:24:36 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140712_180319\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
2014-07-12 18:24:36 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140712_180319\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
2014-07-12 18:25:26 Slp: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
2014-07-12 18:25:32 Slp: Watson bucket for exception based failure has been created
2014-07-12 18:25:32 SQLEngine: Copying 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Log\ERRORLOG' to 'C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140712_180319\SQLServer_ERRORLOG_2014-07-12T18.25.32.txt' ...
2014-07-12 18:25:32 Slp: Sco: Attempting to set file full path to 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Log\ERRORLOG'
2014-07-12 18:25:32 Slp: Sco: Attempting to normalize directory path 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Log\ERRORLOG'
2014-07-12 18:25:32 Slp: Sco: Attempting to check if file 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Log\ERRORLOG' exists
2014-07-12 18:25:32 Slp: Sco: Attempting to copy file 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Log\ERRORLOG' to file 'C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140712_180319\SQLServer_ERRORLOG_2014-07-12T18.25.32.txt'
2014-07-12 18:25:32 Slp: Sco: Attempting to check if file 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Log\ERRORLOG' exists
2014-07-12 18:25:32 Slp: Sco: Attempting to normalize directory path 'C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140712_180319\SQLServer_ERRORLOG_2014-07-12T18.25.32.txt'
2014-07-12 18:25:32 Slp: Sco: Attempting to set file full path to 'C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140712_180319\SQLServer_ERRORLOG_2014-07-12T18.25.32.txt'
2014-07-12 18:25:32 Slp: Sco: Attempting to normalize directory path 'C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140712_180319\SQLServer_ERRORLOG_2014-07-12T18.25.32.txt'
2014-07-12 18:25:32 Slp: Sco: Attempting to check if directory path 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Log\ERRORLOG' is equal to path 'C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140712_180319\SQLServer_ERRORLOG_2014-07-12T18.25.32.txt'
2014-07-12 18:25:32 Slp: Sco: Attempting to check if directory path 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Log\ERRORLOG' is equal to path 'C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140712_180319\SQLServer_ERRORLOG_2014-07-12T18.25.32.txt'
2014-07-12 18:25:32 Slp: Sco: Attempting to normalize directory path 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Log\ERRORLOG'
2014-07-12 18:25:32 Slp: Sco: Attempting to normalize directory path 'C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140712_180319\SQLServer_ERRORLOG_2014-07-12T18.25.32.txt'
2014-07-12 18:25:32 Slp: Sco: Attempting to get security descriptor for file 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Log\ERRORLOG'
2014-07-12 18:25:32 Slp: Sco: Attempting to check if file 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Log\ERRORLOG' exists
2014-07-12 18:25:32 Slp: Sco: Returning security descriptor O:NSG:NSD:AI(A;ID;FA;;;NS)(A;ID;FA;;;SY)(A;ID;FA;;;BA)(A;ID;FA;;;S-1-5-21-3076291671-3154185214-3698330068-1005)(A;ID;0x1201ff;;;S-1-5-21-3076291671-3154185214-3698330068-1006)
2014-07-12 18:25:32 Slp: Sco: Attempting to dispose script
Please note that this is NOT a question about fixing this one installation. This is an SQL Server Express install as part of my application install and MUST WORK FIRST TIME, EVERY TIME. Please direct me.
Paul T.Here are the parameters used with the SQL Server Express installer EXE (both x86 and x64):
/q /hideconsole /action=Install /features=SQL /instancename=SQLEXPRESS /enableranu=1 /sqlsvcaccount="NT Authority\Network Service" /AddCurrentUserAsSqlAdmin /skiprules=RebootRequiredCheck /IAcceptSQLServerLicenseTerms
I presume that TCP/IP is not enabled by default for Express installs. I THINK that named pipe should be enabled.
Summary.txt is copied below:
Overall summary:
Final result: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then
rerun SQL Server Setup.
Exit code (Decimal): -2068119551
Exit facility code: 1211
Exit error code: 1
Exit message: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then
rerun SQL Server Setup.
Start time: 2014-07-12 18:06:14
End time: 2014-07-12 18:25:44
Requested action: Install
Log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140712_180319\Detail.txt
Exception help link: http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.50.4000.0%26EvtType%3d0x1BBF2F31%400x3906094D
Machine Properties:
Machine name: WIN-EAD5VG4PBDE
Machine processor count: 1
OS version: Windows 7
OS service pack: Service Pack 1
OS region: United States
OS language: English (United States)
OS architecture: x86
Process architecture: 32 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID
Feature Language
Edition Version Clustered
Package properties:
Description: SQL Server Database Services 2008 R2
ProductName: SQL Server 2008 R2
Type: RTM
Version: 10
Installation location: c:\b610200f3dc88995d16c2effd8b6ac\x86\setup\
Installation edition: EXPRESS
Slipstream: True
SP Level 2
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: True
AGTSVCACCOUNT: NT AUTHORITY\NETWORK SERVICE
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Disabled
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASDOMAINGROUP: <empty>
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: *****
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Disabled
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140712_180319\ConfigurationFile.ini
CUSOURCE:
ENABLERANU: True
ENU: True
ERRORREPORTING: False
FARMACCOUNT: <empty>
FARMADMINPORT: 0
FARMPASSWORD: *****
FEATURES: SQLENGINE,REPLICATION
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: *****
HELP: False
INDICATEPROGRESS: False
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: SQLEXPRESS
INSTANCENAME: SQLEXPRESS
ISSVCACCOUNT: NT AUTHORITY\NetworkService
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
NPENABLED: 0
PASSPHRASE: *****
PCUSOURCE: c:\b610200f3dc88995d16c2effd8b6ac\PCUSOURCE
PID: *****
QUIET: True
QUIETSIMPLE: False
ROLE: AllFeatures_WithDefaults
RSINSTALLMODE: FilesOnlyMode
RSSVCACCOUNT: NT AUTHORITY\NETWORK SERVICE
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT Authority\Network Service
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: <empty>
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: False
TCPENABLED: 0
UIMODE: AutoAdvance
X86: False
Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140712_180319\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code:
0x0A2FBD17@1211@1
Configuration error description: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140712_180319\Detail.txt
Feature: SQL Server Replication
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code:
0x0A2FBD17@1211@1
Configuration error description: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140712_180319\Detail.txt
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140712_180319\SystemConfigurationCheck_Report.htmd
The entire contents of the installation log can be found in ZIP format here:
https://onedrive.live.com/redir?resid=8E983C44B610198D!3984&authkey=!AFbuZaCG3Lm38Pw&ithint=folder%2c.zip
Paul T. -
SQL Server Express Performance Limitations With OGC Methods on Geometry Instances
I will front load my question. Specifically, I am wondering if any of the feature restrictions with SQL Server Express cause performance limitations/reductions with OGC methods on geometry instances, e.g., STIntersects? I have spent time reading
various documents about the different editions of SQL Server, including the Features Supported by the Editions of SQL Server 2014, but nothing is jumping out at me. The
limited information on spatial features in the aforementioned document implies spatial is the same across all editions. I am hoping this is wrong.
The situation.... I have roughly 200,000 tax parcels within 175 taxing districts. As part of a consistency check between what is stored in tax records for taxing district and what is identified spatially, I set up a basic point-in-polygon query
to identify the taxing district spatially and then count the number of parcels within in taxing district. Surprisingly, the query took 66 minutes to run. As I pointed out, this is being run on a test machine with SQL Server Express.
Some specifics.... I wrote the query a few different ways and compared the execution plans, and the optimizer always choose the same plan, which is good I guess since it means it is doing its job. The execution plans show a 'Clustered Index Seek
(Spatial)' being used and only costing 1%. Coming in at 75% cost is a Filter, which appears to be connected to the STIntersects predicate. I brute forced alternate execution plans using HINTS, but they only turned out worse, which I guess is also
good since it means the optimizer did choose a good plan. I experimented some with changing the spatial index parameters, but the impact of the options I tried was never that much. I ended up going with "Geometry Auto Grid" with 16 cells
per object.
So, why do I think 66 minutes is excessive? The reason is that I loaded the same data sets into PostgreSQL/PostGIS, used a default spatial index, and the same query ran in 5 minutes. Same machine, same data, SQL Server Express is 13x slower than
PostgreSQL. That is why I think 66 minutes is excessive.
Our organization is mostly an Oracle and SQL Server shop. Since more of my background and experience are with MS databases, I prefer to work with SQL Server. I really do want to understand what is happening here. Is there something I can
do different to get more performance out of SQL Server? Does spatial run slower on Express versus Standard or Enterprise? Given I did so little tuning in PostgreSQL, I still can't understand the results I am seeing.
I may or may not be able to strip the data down enough to be able to send it to someone.Tessalating the polygons (tax districts) is the answer!
Since my use of SQL Server Express was brought up as possibly contributing to the slow runtime, the first thing I did was download an evaluation version of Enterprise Edition. The runtime on Enterprise Edition dropped from 66 minutes to 57.5 minutes.
A reduction of 13% isn't anything to scoff at, but total runtime was still 11x longer than in PostgreSQL. Although Enterprise Edition had 4 cores available to it, it never really spun up more than 1 when executing the query, so it doesn't seem
to have been parallelizing the query much, if at all.
You asked about polygon complexity. Overall, a majority are fairly simple but there are some complex ones with one really complex polygon. Using the complexity index discussed in the reference thread, the tax districts had an average complexity
of 4.6 and a median of 2.7. One polygon had a complexity index of 120, which was skewing the average, as well as increasing the runtime I suspect. Below is a complexity index breakdown:
Index
NUM_TAX_DIST
1
6
<2
49
<3
44
<4
23
<5
11
<6
9
<7
9
<8
4
<9
1
<10
4
>=10
14
Before trying tessellation, I tweaked the spatial indexes in several different ways, but the runtimes never changed by more than a minute or two. I reset the spatial indexes to "geometry auto grid @ 32" and tried out your tessellation functions
using the default of 5000 vertices. Total runtime 2.3 minutes, a 96% reduction and twice as fast as PostgresSQL! Now that is more what I was expecting before i started.
I tried using different thresholds, 3,000 and 10,000 vertices but the runtimes were slightly slower, 3.5 and 3.3 minutes respectively. A threshold of 5000 definitely seems to be a sweet spot for the dataset I am using. As the thread you referenced
discussed, SQL Server spatial functions like STIntersect appear to be sensitive to the number of vertices of polygons.
After reading your comment, it reminded me of some discussions with Esri staff about ArcGIS doing the same thing in certain circumstances, but I didn't go as far as thinking to apply it here. So, thanks for the suggestion and code from another post.
Once I realized the SRID was hard coded to 0 in tvf_QuarterPolygon, I was able to update the code to set it to the same as the input shape, and then everything came together nicely. -
Issues using BitLocker in Windows 8 Emedded with 2012 SQL Server Express
I was told that this forum may be able to help me with my issues (see original thread here:
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/8c81fde1-e91b-46eb-8d2f-b79426805ddd/using-sql-server-2012-express-with-bitocker?forum=sqlexpress).
Background:
To summarize, I have an OS that is partitioned into two volumes: C and D.
C drive contains the running software, SQL Server install, and the OS.
D drive is the encrypted partition via BitLocker. The SQL Server files are stored here (logs, backup, and mdf).
Problem:
The software cannot connect to the database stored on the encrypted D volume when BitLocker is turned on. The user account that I use to enable BitLocker is the same SQL Server Service account and has is also part of the Local Admin Group. As soon as I disable
BitLocker, the software works fine and the database connection succeeds. I am currently using the SQL System Admin account to login (SA) and BitLocker is being used with a TPM.
The error I am experiencing when connecting through the software is 'login
failed for user sa'.
Thank you for the suggestions/help.Hi HMLunger,
Did you install the SQL Server instance successfully? If not, please help to post the summary and detail logs for analysis. By default, the logs can be found in: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log.
However, if you fail to start SQL Server Express service after successfully installing SQL Server,
you might have to change the paths of the files by running the following scripts from the command prompt. For more details, please review this similar
thread.
NET START MSSQL$SQLEXPRESS /f /T3608
SQLCMD -S .\SQLEXPRESS
ALTER DATABASE model MODIFY FILE (NAME = logical_name , FILENAME = 'new_path\os_file_name');
ALTER DATABASE model MODIFY FILE (NAME = logical_name , FILENAME = 'new_path\os_file_name');
go
exit;
ALTER DATABASE msdb MODIFY FILE (NAME = logical_name , FILENAME = 'new_path\os_file_name');
ALTER DATABASE msdb MODIFY FILE (NAME = logical_name , FILENAME = 'new_path\os_file_name');
NET STOP MSSQL$SQLEXPRESS
In addition, you can follow the steps in this KB article to uninstall SQL Server.
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support -
We have purchased a new computer that has Win 8.1 Pro. We are migrating an application from a Win 7 Pro machine we are currently successfully using (the vendor migrates it for us) and they have said that the application will require the installation of SQL
Server 2008 Express (which we do have on our Win 7 machine).
In looking at the requirements for SQL Server 2008 Express (on the download page for it), it does not mention it being compatible with Win 8.1
In addition, Installation Instructions says that it requires:
Microsoft .Net Framework 3.5 SP1
Windows Installer 4.5.
Windows PowerShell 1.0
I see that 3.5 is already listed as a program feature of Win8.1 and I've enabled it. Do I need to install SP1? I downloaded it, and launched it, and nothing happened.
I also looked at the Windows Installer 4.5 download page, and it's not clear if that is compatible with 8.1. Do I need to download and install it?
Power Shell 2.0 is already installed. I assume that will be backwards compatible with PowerShell 1.0; is that correct?
I saw another question about SQL Server Express Compatibility with Win 8.1 (http://social.technet.microsoft.com/Forums/windows/en-US/038ec00e-4fc1-41ba-9fdc-21c022aad67e/action?threadDisplayName=sql-server-express-compatibility-with-windows-81) and the response
said that SQL Server Express 2012 will work, but the link contained in the answer led to a page for SQL Server Express 2014.
My vendor has told me that SQL SERver Express 2012 will be backwards compatible with their product. But they said that I would first have to install 2008 first. Is that correct for Win 8.1?
So, the ultimate questions are:
1. What is the link for Sql Server 2012 Express for Win 8.1?
2. Will the SQL Server 2012 Express download require prior install of the 2008 version
3. What other component requirements are required for SQL Server 2012 Express, and how can I determine if they have already been installed. (This is a brand new computer with a clean Win8.1 Install).
4. Finally, can we use the 2014 version of SQL Server Express for Win 8.1? If so, questions 1, 2 and 3 apply, too.
Thanks for your help on this!! HIGH ANXIETY.Hello,
The following article provides which updates are required to make SQL Server versions compatible with Windows 8 or 8.1:
http://support.microsoft.com/kb/2681562/en-us
1. You can use the product updates feature on SQL Server 2012 to make it compatible with Window 8.1. Apply SP1 as described on the following
article:
http://www.sqlcoffee.com/SQLServer2012_0008.htm
2. No.
3. Download and install .NET Framework 4.0 and enable .NET Framework 3.5. For more information:
http://www.sqlcoffee.com/SQLServer2012_0017.htm
4. Yes, you can use SQL Server 2014 with Windows 8.1. Please refer to the Support article provided above.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com -
Our builds kick off and run integration tests. They are configured to hit a SQL Server Express server.
If the builds have been quiet for a while, the first test to connect fails after stalling for 20 minutes.
Subsequent tests are fine.
Reversing test order does the same thing, with a different test.
We noticed in the SQL Server express log the server saying it is waking up after being idle.
Microsoft SQL Server Express with Microsoft SQL Server JDBC Drivers 4.0.2206.
Connection times out after 20 minutes.Occurs with the first connection made after the SQL Server Express server wakes up from going to sleep.Connections after the first are just fine, until SQL Server Express sleeps.SSL enabled. Timeout duration for the connection failure is unaffected by setting timeout options for the connection. Work around:
cron-like job that runs every minute that makes a simple query on the server keeps the server from going to sleep.
Has anyone else run into this?Hello,
SQL Server Express will go to sleep if idle, this behavior is not configurable.
When SQL Express transitions from idle to active some of the memory that was released needs to be reclaimed; this results is a slight lag during "startup time" when you're first connecting to SQL Express.
The other sort of sleep occurs when a database with AUTO_CLOSE unloading itself after a period of inactivity. This can be resolved by setting AUTO_CLOSE to false.
You can refer to the following blog about more details about this:
http://blogs.msdn.com/b/sqlexpress/archive/2008/02/22/sql-express-behaviors-idle-time-resources-usage-auto-close-and-user-instances.aspx
You can try to upgrade the SQL Server Express to a non-free version to get rid of this.
Regards,
Fanny Liu
Fanny Liu
TechNet Community Support -
HELP - SQL Server Express Install Problems
The SQL Server Express completed without error. However, when I tried to connect to the SQLEXPRESS instance I received one of those wonderful MS errors, "Specified file not found". WHAT FILE? (After all these years MS still can't figure out how
to give an error msg. that provides some hint of what's wrong.) Going on, I started the install console and selected the REPAIR option. (It didn't ask what the problem was, it just ran.) It did ask what instance needed repair. I told
it SQLSERVER. It proceeded to repairing it. My first hint that their repair function worked as well as their error handling was when I got the: That share name has already been used (or something like that) error (notice, MS didn't tell me what
share name, or what aspect of the db they were talking about). After pressing OK, the REPAIR function proceeded to run to completion. When I reviewed the REPAIR report I found that three db processes all had the same SHARE NAME ALREADY USED error.
Actually, I thought that it was no big deal. If this was a real REPAIR, it shouldn't matter that the name was already used because everything else should be the same. (I know I'm nigh eve about the
Intricacies of SQL server.) After repairing my installation, I brought up the SQL Server Management Console again. This time, it did not display SQLEXPRESS in the Connect field. I selected the drop down list arrow to see if it was
listed and the list was blank so I entered SQLEXPRESS in the connect field and clicked on the CONNECT button. I got a NETWORK PATH NOT FOUND error. So, before I really mess things up, I thought I should ask if anyone knows what I should do
next. (As an aside, I've pressed the MS Error Message HELP button numerous times abut various errors I've received over the years. Not only are MS error messages useless, their Help Page has never ONCE been able to provide any information
about the encountered error. MS should spend some time and develop some truly helpful error messages as "File not found" and unknown error code 837289 are absolutely useless and especially since their HELP PAGE is never able to provide any
information either. I do wonder how I can get Unknown Error codes from people who wrote the code that raises the error. Don't they document anything?)I did read the requirements and made sure I met them all. The install package I used was: SQLEXPRADV_x64_ENU.exe. You're correct. I'm not familiar with SQL Server.
I downloaded SQL Server Express and Visual Studio Express to learn and explore because I wanted to learn about the new technology.
After leaving my message, I did some more studying and playing with the system. I managed to figure out that I had to turn on the data base service before I could connect with it. I'm sorry, I don't understand how Microsoft could install a data
base system without turning on its services. Why would I want to install something and NOT use it? The default should be ON and the setup manager should provide a choice to set it to OFF on the configuration page.
My experience is rather dated. I had to retire due to a disability in 2005. I couldn't control my arms and hands. The doctor recently tried a medication again that I had had a severe negative reaction to. He first administered steroids
and started me on a small dose and titrated it up as I was able to handle it. Now I have some days where I have pretty good control — I can print a little but can't write well and other days where I can't print, write, or feed myself.
I have performed many functions. I have been an analyst, a programmer, a data base designer, and a college professor at three different colleges. I've done extensive work in process automation and have even automated the management functions
for a data base system that was used to schedule every aspect of all the aircraft, ranges, and weapons development processes on Eglin AFB. I also wrote major pieces of the code used by the system and trouble shot and corrected functions written by other
programmers. The system supported over 300 users a day on two bases. Unfortunately it was developed in Fortran on a VAX and with VB6 and MS Access using VBA, Queries, Tables and Forms on networked PCs.
I plan to do a lot of reading. I'll also be looking at the Microsoft sites for a sample DB and lessons to go with it. I am a little frustrated with how information is organized on the web. The other night I needed to find some information
about something from Microsoft. It took me almost two hours to ask my question in such a way that MS was able to provide what I wanted. I kept asking essentially the same thing, but I had to use the exact phrase MS used on the page. I know
MS is big and they support multiple generations of each product. They have an almost impossible task. I just have to find the various product entry pages.
Thanks for offering your help. -
I have a data cluster that I am working to write to either Access 2007 thru 2010 and/or SQL Server Express 2008 thru 2012 all on a Windows 7 64 bit OS. Some of the elements are long strings that I put delimited data for the raw trace data. The fields can be 10's of KB long. With Access I cannot stuff any string >255char into the memo field. With SQL Server Express 2008R2 - 2012 I found that if the strings are >32767 they again fail to fill the memo fields. The Access write or reads work fine otherwise, just not the listed offending fields in the cases mentioned. Anyone else having the issue or a solution?
If the long string field has repetitive data, you might be able to compress it using GZIP to reduce it's size below the 32K limitation you mentioned.
GZIP compress/uncompress of string using .NET
Now is the right time to use %^<%Y-%m-%dT%H:%M:%S%3uZ>T
If you don't hate time zones, you're not a real programmer.
"You are what you don't automate"
Inplaceness is synonymous with insidiousness -
VS 2013 Community and SQL Server Express 2005
Not sure if I'm in the right forum, but I'll give it a shot. I have a laptop with Vista and SQL Server Express 2005. I created a db on it and put a lot of time into it. But now the laptop is dieing. I am wanting to use the db with VS 2013
Community.
I plan to upload the db files to OneDrive from the Vista laptop and then download them to my new laptop that has VS on it. Will it work? Is it practical? Should I go with SQL Express 2008 or higher?
I'm just learning VS and not sure what to do. Any help will be appreciated. Thanks.
BillThanks for pvdg42’s help.
Hi Bill,
It seems that you have resolved certain issues, you know that one thread for one issue, so for the new issue, it would be better if you could post them in new threads.
>>The ProgramFiles folder has a folder Microsoft Visual Studio 12.0. The ProgramFiles(x86) has a VS 11.0 ands VS 12.0 folder. I did not know this when I downloaded 2013CE.
It would be related to your windows version 32 bit or 64 bit, for example, the 64 bit version windwos 8.1 in my side, it would setup in this path default:
C:\Program Files (x86)\Microsoft Visual Studio 12.0
In addition, my understanding the latest issue “The tables not show in object explorer window” would be related to the database upgraded from the old SQL Server version to the high version. So it would be not the VS IDE issue.
Of course, if you add a new table in this database, how about the result?
If you connect to the previous database in this high version, how about the result if you add a table?
I think if it would works well when you add a new table in other database of high version in VS2013, it means that it is not the VS IDE issue, the real issue would be related to your previous database.
My suggestion is that you could post this issue to the SQL Server forum since it is related to the database migration.
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/home?category=sqlserver
Sincerely,
Jack
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey. -
How to access Sql Server Express installed on Virtual PC from Host?
I have SQL Server Express 2008 R2 installed on Virtual PC. and on my Host machine i have SQL Server 2008 R2 ( Enterprise Version) installed.
Since Management studio that comes with SQL express does not support SQL profiler, i want to access SQL Server Express from the Host machine’s management studio which has SQL profiler.
But I could access it using VM’s ip address & instance nameHi lax,
Follow below steps in your Virtual Machine:
1. Allow remote connections to this server
The first thing you want to check is if Remote Connections are enabled on your SQL Server database. In SQL Server 2008 you do this by opening SQL Server 2008 Management Studio, connect to the server in question, right click the server and open the Server Properties.
Navigate to Connections and ensure that Allow remote connections to this server is checked.
2. Protocols for MSSQLServer
The next good thing to check is the SQL Server Network Configuration. Open the SQL Server Configuration Manager, unfold the node SQL Server Network Configuration and select Protocols for MSSQLServer (or whatever the name of your SQL Server instance is). Make
sure that TCP/IP is enabled.
3. The Firewall
If there is still no communication happening between your computer and the remote SQL Server you most likely need to configure your firewall settings.
A good first step is to figure out which port is being used by TCP/IP (and which you need to open in your firewall). You can do this by right clicking TCP/IP and selecting Properties. Click on the tab IP Addresses .
That was easy enough and all there is left to do is to allow inbound TCP/IP traffic on Port 1433 in your firewall. In Windows 7 this works something like this. Open the Control Panel and navigate to Windows Firewall. Click on Advanced Settings on the left hand
side and you should see the Windows Firewall with Advanced Security. Select the Inboud Rules on the left hand side and click on New Rule on the right hand side. This opens the New Inbound Rule Wizard which you can use to allow inbound traffic on Port 1433
for TCP/IP.
For more information, please refer to
http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx.
In host machine:
After you have done steps above, you could use the SQL Server Management Studio in the host machine to connect the SQL Server Express R2 in Virtual PC. If you installed a default instance in Virtual PC, you could use VirtualComputerName to login the SQL
Server database engine. If you installed a named instance in Virtual PC, you could use VirtualComputerName\InstanceName to login the SQL Server database engine.
Thanks,
Maggie
Please remember to mark the replies as answers if they help and unmark them if they provide no help. This can be beneficial to other community members reading the thread. -
Problems on installation SQL Server Express
I have problems installation of SQL server express.
Here is the error message:
TITLE: SQL Server Setup failure.
SQL Server Setup has encountered the following error:
'.', hexadecimal value 0x00, is an invalid character. Line 1, position 52351.
Error code 0x84B10001.Have a look at this link.
http://stackoverflow.com/questions/21643363/error-0x84b10001-when-installing-sql-server-2012-on-a-machine-with-vs2013
==
Well, turns out that this cryptic error is due to an older
instance of SQL Server Desktop Engine (MSDE) being present.
After uninstalling MSDE, the SQL Server 2012 setup worked without errors.
==
Satheesh
My Blog | How to ask questions in technical forum -
License for multi-core CPU on SQL Server Express
I would like to know is it Legal to use SQL Server Express 2008 R2 / 2012
on a machine using 6 cores CPU(e.g.Xeon E5-2440).
Thank you.SQL Express 2012 will USE a maximum of 4 cores, but there's nothing preventing you running on a server with more cores than that, it simply won't use those additional 2 cores.
For the limitations of the different versions of SQL Server 2012 see
http://msdn.microsoft.com/en-us/library/cc645993(v=SQL.110).aspx#CrossBoxScale
I can't remember the exact situation with 2008 R2 unfortunately. From
http://msdn.microsoft.com/en-us/library/cc645993(v=sql.105).aspx#Scalability you'll see it's listed simply as being limited to 1 CPU with no mention of cores, so it MIGHT be the case that it will use all of that one physical CPU, but can't remember if that's
definitely the case or not. -
Having issues with getting SQL Server Express to start services and run.
Good afternoon everyone,
I have been working on a 2012 R2 server getting ready to move databases to new hardware. I had SQL Server Express 2008 R2 running on this server with no issues. I was handed another software package that ran SQL Express 2012 and had to for compatibility
reasons. I have had multiple versions run on Server 2012 before with no issues. This time, not so lucky. When the installer from the updated package put on SQL Express 2012 it completed with errors ( error log posted at the end of post) and
would not allow me to run software. I then tried the db that I had installed on 2008 R2 and it also gave the same error as the 2012 version. IN basic terms the required services attempted to start and shut back down again. I have received
Error 1068 about database handles and error %%945. I know this db has plenty of space and the permissions were added for the Admin account to access both db's. I then uninstalled both versions and tried again, with the same errors listed when
I tried to start the services. I am thinking that a clean install would fix the issue however I am not certain what files/folders/reg entries need to be deleted or modified. I have researched all the errors I can find, however I am very
new with SQL anything so I know I am missing something. I also do not have an "E:" drive on this server (not sure why it is going there). Input would be very welcome as I am not certain where to go from here.
Thanks,
Matt
Error Log follows, server and domain names have been blacked out with ****.
2015-04-15 11:57:55.16 Server Microsoft SQL Server 2012 (SP1) - 11.0.3128.0 (X64)
Dec 28 2012 20:23:12
Copyright (c) Microsoft Corporation
Express Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: ) (Hypervisor)
2015-04-15 11:57:55.16 Server (c) Microsoft Corporation.
2015-04-15 11:57:55.16 Server All rights reserved.
2015-04-15 11:57:55.16 Server Server process ID is 4104.
2015-04-15 11:57:55.16 Server System Manufacturer: 'HP', System Model: 'ProLiant ML350p Gen8'.
2015-04-15 11:57:55.16 Server Authentication mode is WINDOWS-ONLY.
2015-04-15 11:57:55.16 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\Log\ERRORLOG'.
2015-04-15 11:57:55.17 Server The service account is 'NT AUTHORITY\LOCAL SERVICE'. This is an informational message; no user action is required.
2015-04-15 11:57:55.17 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\DATA\mastlog.ldf
2015-04-15 11:57:55.17 Server Command Line Startup Parameters:
-s "SQLEXPRESS"
2015-04-15 11:57:55.48 Server SQL Server detected 1 sockets with 6 cores per socket and 12 logical processors per socket, 12 total logical processors; using 8 logical processors based on SQL Server licensing. This is an informational message;
no user action is required.
2015-04-15 11:57:55.48 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2015-04-15 11:57:55.48 Server Detected 8157 MB of RAM. This is an informational message; no user action is required.
2015-04-15 11:57:55.48 Server Using conventional memory in the memory manager.
2015-04-15 11:57:55.68 Server This instance of SQL Server last reported using a process ID of 7840 at 4/15/2015 11:57:47 AM (local) 4/15/2015 3:57:47 PM (UTC). This is an informational message only; no user action is required.
2015-04-15 11:57:55.68 Server Node configuration: node 0: CPU mask: 0x00000000000000ff:0 Active CPU mask: 0x00000000000000ff:0. This message provides a description of the NUMA configuration for this computer. This is an informational message
only. No user action is required.
2015-04-15 11:57:55.69 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-04-15 11:57:55.72 Server Software Usage Metrics is disabled.
2015-04-15 11:57:55.73 spid5s Starting up database 'master'.
2015-04-15 11:57:55.79 spid5s 20 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required.
2015-04-15 11:57:55.79 spid5s 0 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required.
2015-04-15 11:57:55.80 Server CLR version v4.0.30319 loaded.
2015-04-15 11:57:55.86 spid5s Service Master Key could not be decrypted using one of its encryptions. See sys.key_encryptions for details.
2015-04-15 11:57:55.89 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2015-04-15 11:57:55.91 spid5s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2015-04-15 11:57:55.91 spid5s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2015-04-15 11:57:55.94 spid5s SQL Trace ID 1 was started by login "sa".
2015-04-15 11:57:55.94 spid5s Server name is '********\SQLEXPRESS'. This is an informational message only. No user action is required.
2015-04-15 11:57:55.96 spid5s Failed to verify Authenticode signature on DLL 'C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\Binn\ftimport.dll'.
2015-04-15 11:57:55.96 spid5s Starting up database 'msdb'.
2015-04-15 11:57:55.96 spid9s Starting up database 'mssqlsystemresource'.
2015-04-15 11:57:55.96 spid5s Error: 17204, Severity: 16, State: 1.
2015-04-15 11:57:55.96 spid5s FCB::Open failed: Could not open file e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\MSDBData.mdf for file number 1. OS error: 3(The system cannot find the path specified.).
2015-04-15 11:57:55.96 spid5s Error: 5120, Severity: 16, State: 101.
2015-04-15 11:57:55.96 spid5s Unable to open the physical file "e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\MSDBData.mdf". Operating system error 3: "3(The system cannot find the path specified.)".
2015-04-15 11:57:55.96 spid5s Error: 17207, Severity: 16, State: 1.
2015-04-15 11:57:55.96 spid5s FileMgr::StartLogFiles: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\MSDBLog.ldf'.
Diagnose and correct the operating system error, and retry the operation.
2015-04-15 11:57:55.96 spid5s File activation failure. The physical file name "e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\MSDBLog.ldf" may be incorrect.
2015-04-15 11:57:55.99 spid9s The resource database build version is 11.00.3000. This is an informational message only. No user action is required.
2015-04-15 11:57:56.02 spid12s A self-generated certificate was successfully loaded for encryption.
2015-04-15 11:57:56.03 spid12s Server is listening on [ 'any' <ipv6> 53345].
2015-04-15 11:57:56.03 spid12s Server is listening on [ 'any' <ipv4> 53345].
2015-04-15 11:57:56.03 spid12s Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQLEXPRESS ].
2015-04-15 11:57:56.03 spid12s Server named pipe provider is ready to accept connection on [ \\.\pipe\MSSQL$SQLEXPRESS\sql\query ].
2015-04-15 11:57:56.04 spid12s Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag 7806.
This is an informational message only. No user action is required.
2015-04-15 11:57:56.04 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-04-15 11:57:56.04 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/********.****.local:SQLEXPRESS ] for the SQL Server service. Windows return code: 0xffffffff, state: 53.
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-04-15 11:57:56.04 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/********.****.local:53345 ] for the SQL Server service. Windows return code: 0xffffffff, state: 53. 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-04-15 11:57:56.09 spid9s Starting up database 'model'.
2015-04-15 11:57:56.10 spid9s Error: 17204, Severity: 16, State: 1.
2015-04-15 11:57:56.10 spid9s FCB::Open failed: Could not open file e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\model.mdf for file number 1. OS error: 3(The system cannot find the path specified.).
2015-04-15 11:57:56.10 spid9s Error: 5120, Severity: 16, State: 101.
2015-04-15 11:57:56.10 spid9s Unable to open the physical file "e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\model.mdf". Operating system error 3: "3(The system cannot find the path specified.)".
2015-04-15 11:57:56.10 spid9s Error: 17207, Severity: 16, State: 1.
2015-04-15 11:57:56.10 spid9s FileMgr::StartLogFiles: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\modellog.ldf'.
Diagnose and correct the operating system error, and retry the operation.
2015-04-15 11:57:56.10 spid9s File activation failure. The physical file name "e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\modellog.ldf" may be incorrect.
2015-04-15 11:57:56.10 spid9s Error: 945, Severity: 14, State: 2.
2015-04-15 11:57:56.10 spid9s Database 'model' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details.
2015-04-15 11:57:56.10 spid9s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
Hi HMLunger,
Did you install the SQL Server instance successfully? If not, please help to post the summary and detail logs for analysis. By default, the logs can be found in: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log.
However, if you fail to start SQL Server Express service after successfully installing SQL Server,
you might have to change the paths of the files by running the following scripts from the command prompt. For more details, please review this similar
thread.
NET START MSSQL$SQLEXPRESS /f /T3608
SQLCMD -S .\SQLEXPRESS
ALTER DATABASE model MODIFY FILE (NAME = logical_name , FILENAME = 'new_path\os_file_name');
ALTER DATABASE model MODIFY FILE (NAME = logical_name , FILENAME = 'new_path\os_file_name');
go
exit;
ALTER DATABASE msdb MODIFY FILE (NAME = logical_name , FILENAME = 'new_path\os_file_name');
ALTER DATABASE msdb MODIFY FILE (NAME = logical_name , FILENAME = 'new_path\os_file_name');
NET STOP MSSQL$SQLEXPRESS
In addition, you can follow the steps in this KB article to uninstall SQL Server.
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support -
Adding SQL Server Express to Visual Studio 2013 Pro on Windows 10 Preview
I have installed VS 2013 Pro on Windows 10. I need to delevop unsing SQL Server Express. Do I download the full SQL Server 2012 Express Advanced (with full text search), or do I need only part of it? I was going to download the SQLEXPRADV_X64_ENU.exe.
Is this a good way to go?
Do I also need to download any other .net frameworks?
kciNDevHello,
Please read the following resources:
http://msdn.microsoft.com/en-us/library/ms233763.aspx
http://stackoverflow.com/questions/20333518/how-to-create-a-database-in-ms-visual-studio-2013
http://msdn.microsoft.com/en-us/vstudio/bb643825.aspx
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com
Maybe you are looking for
-
Keep getting error message when attempting to buy a song (Error 5002)
This error message seems to pop up with just this one song (says there is an issue with the iTunes store and that it is an unknown error) and it has not changed this status for a month now. I have the latest iTunes and there were no problems in updat
-
Hi , When i am creating an acquisition in the fixed asset module,the acquisition is added successfully but no journal entry is created. What am i doing wrong? Thanks Nisha
-
Problem with JMenuItem, method isArmed()
Hi everybody, I want hide my menu when I "open" it and click in another part of the application. it did not work when I made the verification using the method isArmed() in JMenuItem. I added a mouseListener in my JPanel, that is located below my JMen
-
OBIEE 11.1.1.5.0 export to excel with filters?
Hi all, Is it possible in OBIEE 11.1.1.5 to export the analysis with the current filters? Thanks in advance, Alexander.
-
Photoshop CS3 Extended crashes when using Black and White or photomerge
Photoshop crashes when I go to adjustment > Black and White also crashes on Photomerge. Running 10.4.11 have uninstalled and reinstalled 2 times. Runs fine on old HD only different program is Office 2008. Have 3 gigs of ram and 500 gig HD . G5 1.6 GH