Can't install SQL server 2017 or 2019 on a new windows 11 - sql-server-2017

Could anyone provide some assistance? We can't install SQL Server 2017 or 2019 on a brandnew Windows 11 pc. We have removed all SQL applications, rebooted and tried again. We had the IT of the customer remove and reinstall Windows after a formatting of the hard disc and tried again after, always the same errors.
System specs are: AMD Ryzen 5 5500U 2.10GHz with 8GB RAM
We get error 0x851A001A in event viewer application log, but "fsutil fsinfo sectorinfo c:" shows the size is 4096.
In SQL Server setup we get the error: "Wait on database engine recovery handle failed check the sql server error log for potential causes"
And in the Log of 2019 for instance we get this:
2022-10-05 14:03:48.75 Server Microsoft SQL Server 2019 (RTM-CU18) (KB5017593) - 15.0.4261.1 (X64)
Sep 12 2022 15:07:06
Copyright (C) 2019 Microsoft Corporation
Express Edition (64-bit) on Windows 10 Pro 10.0 (Build 22621: ) (Hypervisor)
2022-10-05 14:03:48.75 Server UTC adjustment: 2:00
2022-10-05 14:03:48.75 Server (c) Microsoft Corporation.
2022-10-05 14:03:48.75 Server All rights reserved.
2022-10-05 14:03:48.75 Server Server process ID is 7464.
2022-10-05 14:03:48.75 Server System Manufacturer: 'LENOVO', System Model: '20YG00B6MB'.
2022-10-05 14:03:48.75 Server Authentication mode is MIXED.
2022-10-05 14:03:48.75 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL15.OXYGEN2\MSSQL\Log\ERRORLOG'.
2022-10-05 14:03:48.75 Server The service account is 'NT Service\MSSQL$OXYGEN2'. This is an informational message; no user action is required.
2022-10-05 14:03:48.75 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL15.OXYGEN2\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL15.OXYGEN2\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL15.OXYGEN2\MSSQL\DATA\mastlog.ldf
2022-10-05 14:03:48.75 Server Command Line Startup Parameters:
-s "OXYGEN2"
-m "SqlSetup"
-T 4022
-T 4010
-T 1905
-T 3701
-T 8015
2022-10-05 14:03:48.76 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.
2022-10-05 14:03:48.76 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2022-10-05 14:03:48.76 Server Detected 6986 MB of RAM. This is an informational message; no user action is required.
2022-10-05 14:03:48.76 Server Using conventional memory in the memory manager.
2022-10-05 14:03:48.76 Server Page exclusion bitmap is enabled.
2022-10-05 14:03:48.84 Server Buffer Pool: Allocating 524288 bytes for 378182 hashPages.
2022-10-05 14:03:48.84 Server Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
2022-10-05 14:03:48.87 Server Buffer pool extension is already disabled. No action is necessary.
2022-10-05 14:03:48.90 Server Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
2022-10-05 14:03:48.93 Server Query Store settings initialized with enabled = 1,
2022-10-05 14:03:48.93 Server The maximum number of dedicated administrator connections for this instance is '1'
2022-10-05 14:03:48.93 Server This instance of SQL Server last reported using a process ID of 328 at 5/10/2022 14:03:46 (local) 5/10/2022 12:03:46 (UTC). This is an informational message only; no user action is required.
2022-10-05 14:03:48.94 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.
2022-10-05 14:03:48.94 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.
2022-10-05 14:03:48.95 Server In-Memory OLTP initialized on lowend machine.
2022-10-05 14:03:48.96 Server [INFO] Created Extended Events session 'hkenginexesession'
2022-10-05 14:03:48.96 Server Database Instant File Initialization: disabled. For security and performance considerations see the topic 'Database Instant File Initialization' in SQL Server Books Online. This is an informational message only. No user action is required.
2022-10-05 14:03:48.97 Server Total Log Writer threads: 2. This is an informational message; no user action is required.
2022-10-05 14:03:48.97 Server Database Mirroring Transport is disabled in the endpoint configuration.
2022-10-05 14:03:48.97 Server clwb is selected for pmem flush operation.
2022-10-05 14:03:48.97 Server Software Usage Metrics is disabled.
2022-10-05 14:03:48.97 spid10s Warning ******************
2022-10-05 14:03:48.97 spid10s SQL Server started in single-user mode. This an informational message only. No user action is required.
2022-10-05 14:03:48.97 spid10s Starting up database 'master'.
2022-10-05 14:03:48.99 spid10s There have been 256 misaligned log IOs which required falling back to synchronous IO. The current IO is on file C:\Program Files\Microsoft SQL Server\MSSQL15.OXYGEN2\MSSQL\DATA\master.mdf.
2022-10-05 14:03:49.05 Server CLR version v4.0.30319 loaded.
2022-10-05 14:03:49.13 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.

For systems running Windows 11, some storage devices and new device drivers will display a disk sector size larger than the supported 4 KB sector size.
When this occurs, SQL Server cannot start because of an unsupported file system. SQL Server currently supports sector storage sizes of 512 bytes and 4 KB.
You can fix the problem by running the command:
fsutil fsinfo sectorinfo <volume pathname>
Example:
fsutil fsinfo sectorinfo E:
Look for the value PhysicalBytesPerSectorForAtomicity, returned in bytes. A value of 4096 indicates a sector storage size of 4 KB.
If you are still having problems running SQL server, then you can follow the instructions on this page.

Related

BitLocker metadata for the encrypted drive is not valid (0x80310010)

I'm moving an external drive to a new computer.
The drive is protected with Bitlocker, but I can unlock it and view the contents.
However, when I try to configure auto-unlock I see:
C:\>manage-bde -autounlock -enable d:
BitLocker Drive Encryption: Configuration Tool version 10.0.17763
Copyright (C) 2013 Microsoft Corporation. All rights reserved.
ERROR: An error occurred (code 0x80310010):
The BitLocker metadata for the encrypted drive is not valid. You can attempt to repair the drive to restore access.
Is there a way to rebuild the metadata?
Clearly the metadata is valid enough to unlock the volume, so I'm wondering if the error message is even correct.
Further investigation revealed that the error message was incorrect.
The cause of the problem was that the disk was marked as readonly.
After using diskpart to clear the readonly flag, then locking and unlocking the volume, manage-bde -autounlock -enable d: worked correctly.
C:\>diskpart
Microsoft DiskPart version 10.0.17763.1554
Copyright (C) Microsoft Corporation.
On computer: HYPER-V
DISKPART> list volume
Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
Volume 0 C NTFS Partition 465 GB Healthy Boot
Volume 1 Recovery NTFS Partition 499 MB Healthy Hidden
Volume 2 FAT32 Partition 100 MB Healthy System
Volume 3 D DATA ReFS Partition 7449 GB Healthy
DISKPART> select volume 3
Volume 3 is the selected volume.
DISKPART> attributes disk
Current Read-only State : Yes
Read-only : Yes
Boot Disk : No
Pagefile Disk : No
Hibernation File Disk : No
Crashdump Disk : No
Clustered Disk : No
DISKPART> attributes disk clear readonly
Disk attributes cleared successfully.
DISKPART> exit
C:\>manage-bde -lock d:
BitLocker Drive Encryption: Configuration Tool version 10.0.17763
Copyright (C) 2013 Microsoft Corporation. All rights reserved.
Volume D: is now locked
C:\>manage-bde -unlock d: -pw
BitLocker Drive Encryption: Configuration Tool version 10.0.17763
Copyright (C) 2013 Microsoft Corporation. All rights reserved.
Enter the password to unlock this volume:
The password successfully unlocked volume D:.
C:\>manage-bde -autounlock -enable d:
BitLocker Drive Encryption: Configuration Tool version 10.0.17763
Copyright (C) 2013 Microsoft Corporation. All rights reserved.
Key Protectors Added:
External Key:
ID: {3CEFC24B-BBBF-4818-A128-9FA0E87E872D}
External Key File Name:
3CEFC24B-BBBF-4818-A128-9FA0E87E872D.BEK
Automatic unlock enabled.

How to connect properly symfony 3.3.x doctrine2 and sql server 2005

I am working with symfony 3.3.10, php5.6.31 and I tried several times to connect doctrine to SQL Server 2005 database. I already installed the driver to use sqlsrv and pdo_sqlsrv. Here are my config files:
php.ini
extension=php_sqlsrv_56_ts.dll
extension=php_pdo_sqlsrv_56_ts.dll
symfony config.yml
driver: pdo_sqlsrv
host: server_addr
port: 1433
dbname: dbname
user: db_user
password: db_p#ssw0rd
That is my config, now when I try to do something with doctrine it raises the following errors:
Using pdo_sqlsrv as driver
[Doctrine\DBAL\Driver\PDOException]
SQLSTATE[08001]: [Microsoft][ODBC Driver 11 for SQL Server]ODBC Driver 11 f
or SQL Server does not support connections to SQL Server 2000 or earlier ve
rsions.
[PDOException]
SQLSTATE[08001]: [Microsoft][ODBC Driver 11 for SQL Server]ODBC Driver 11 f
or SQL Server does not support connections to SQL Server 2000 or earlier ve
rsions.
Using sqlsrv as driver
[Doctrine\DBAL\Driver\SQLSrv\SQLSrvException]
SQLSTATE [IMSSP, -33]: Invalid value type for option Database was specified
. String type was expected.
my phpinfo() has no problems and is detectig both php_sqlsrv and php_pdo_sqlsrv
Registered PHP Streams php, file, glob, data, http, ftp, zip, compress.zlib, compress.bzip2, https, ftps, sqlsrv, phar
PDO drivers
mysql, odbc, pgsql, sqlite, sqlsrv
Thanks in advance and sorry for bad English.
My SQL Server version output is:
Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86) Feb 9 2007 22:47:07 Copyright (c) 1988-2005 Microsoft Corporation Enterprise Edition on Windows NT 6.0 (Build 6002: Service Pack 2)
I have found this post which makes a reference to this link. Now I am using the lastest version (5.1.1). After check the extension is working I just configure multiples entity managers and I can connect to the database and execute/fetch queries.
php.ini
extension=php_pdo_sqlsrv_ts.dll
extension=php_sqlsrv_ts.dll

IBM WebSphere Portal V8.5 wcm library syndication

I have a WebSphere Portal Version 8.5 Cluster on AIX 7.1 with multiple Virtual Portals, working with managed pages and each Virtual Portal has it's own libraries and one shared library for all VPs using syndication of that library to each VP.
i successfully created the syndication pair between the syndicator (WAS base portal) and the subscriber (Virtual Portal) and tested connection between them and all is good (make sense since VP are local on the same server). however when trying to syndicate the library content it stays on Queued status and in the SystemOut.log i see the following error log:
[4/25/17 9:33:53:201 IDT] 00004163 PackageConsum E Unexpected exception thrown while updating subscription: [IceId: Current State: ], exception: com.ibm.workplace.wcm.services.WCMServiceRuntimeException: code: 400
com.ibm.workplace.wcm.services.WCMServiceRuntimeException: code: 400
at com.aptrix.syndication.business.subscriber.CatalogRetrieverTask.getSourceCatalog(CatalogRetrieverTask.java:330)
at com.aptrix.syndication.business.subscriber.CatalogRetrieverTask.process(CatalogRetrieverTask.java:144)
at com.aptrix.syndication.business.subscriber.PackageConsumerTask.processPackage(PackageConsumerTask.java:513)
at com.aptrix.syndication.business.subscriber.PackageConsumerTask.processUpdate(PackageConsumerTask.java:267)
at com.aptrix.syndication.business.subscriber.PackageConsumerTask$1.run(PackageConsumerTask.java:183)
at com.ibm.wps.ac.impl.UnrestrictedAccessImpl.run(UnrestrictedAccessImpl.java:84)
at com.ibm.wps.command.ac.ExecuteUnrestrictedCommand.execute(ExecuteUnrestrictedCommand.java:90)
at com.aptrix.syndication.business.subscriber.PackageConsumerTask.doManagedWork(PackageConsumerTask.java:195)
at com.aptrix.syndication.business.ManagedTask.runWork(ManagedTask.java:62)
at com.ibm.workplace.wcm.services.workmanager.AbstractWcmWork.runImpl(AbstractWcmWork.java:162)
at com.ibm.workplace.wcm.services.workmanager.AbstractWcmSystemWork.access$001(AbstractWcmSystemWork.java:40)
at com.ibm.workplace.wcm.services.workmanager.AbstractWcmSystemWork$1.run(AbstractWcmSystemWork.java:92)
at com.ibm.wps.ac.impl.UnrestrictedAccessImpl.run(UnrestrictedAccessImpl.java:84)
at com.ibm.wps.command.ac.ExecuteUnrestrictedCommand.execute(ExecuteUnrestrictedCommand.java:90)
at com.ibm.workplace.wcm.services.repository.PACServiceImpl.runAsPrivileged(PACServiceImpl.java:1878)
at com.ibm.workplace.wcm.services.workmanager.AbstractWcmSystemWork.runImpl(AbstractWcmSystemWork.java:87)
at com.ibm.workplace.wcm.services.workmanager.AbstractWcmWork.run(AbstractWcmWork.java:146)
at com.ibm.wps.services.workmanager.impl.WasWorkWrapper.run(WasWorkWrapper.java:44)
at com.ibm.ws.asynchbeans.J2EEContext$RunProxy.run(J2EEContext.java:271)
at java.security.AccessController.doPrivileged(AccessController.java:274)
at com.ibm.ws.asynchbeans.J2EEContext.run(J2EEContext.java:797)
at com.ibm.ws.asynchbeans.WorkWithExecutionContextImpl.go(WorkWithExecutionContextImpl.java:222)
at com.ibm.ws.asynchbeans.ABWorkItemImpl.run(ABWorkItemImpl.java:206)
at java.lang.Thread.run(Thread.java:804)
[4/25/17 9:33:53:222 IDT] 00004163 SyndicationEx W Unsuccessful request to send summary: 400
com.aptrix.deployment.wizard.SyndicatorCommunicationException: Unsuccessful request to send summary: 400
at com.ibm.workplace.wcm.api.syndication.SyndicationExtensionsServiceImpl.sendSummaryToSyndicator(SyndicationExtensionsServiceImpl.java:293)
at com.ibm.workplace.wcm.api.syndication.SyndicationExtensionsServiceImpl.processSubscriberCompleting(SyndicationExtensionsServiceImpl.java:246)
at com.aptrix.syndication.business.subscriber.SubscriberTaskManager.processFailedUpdate(SubscriberTaskManager.java:405)
at com.aptrix.syndication.business.subscriber.PackageConsumerTask.processUpdate(PackageConsumerTask.java:400)
at com.aptrix.syndication.business.subscriber.PackageConsumerTask$1.run(PackageConsumerTask.java:183)
at com.ibm.wps.ac.impl.UnrestrictedAccessImpl.run(UnrestrictedAccessImpl.java:84)
at com.ibm.wps.command.ac.ExecuteUnrestrictedCommand.execute(ExecuteUnrestrictedCommand.java:90)
at com.aptrix.syndication.business.subscriber.PackageConsumerTask.doManagedWork(PackageConsumerTask.java:195)
at com.aptrix.syndication.business.ManagedTask.runWork(ManagedTask.java:62)
at com.ibm.workplace.wcm.services.workmanager.AbstractWcmWork.runImpl(AbstractWcmWork.java:162)
at com.ibm.workplace.wcm.services.workmanager.AbstractWcmSystemWork.access$001(AbstractWcmSystemWork.java:40)
at com.ibm.workplace.wcm.services.workmanager.AbstractWcmSystemWork$1.run(AbstractWcmSystemWork.java:92)
at com.ibm.wps.ac.impl.UnrestrictedAccessImpl.run(UnrestrictedAccessImpl.java:84)
at com.ibm.wps.command.ac.ExecuteUnrestrictedCommand.execute(ExecuteUnrestrictedCommand.java:90)
at com.ibm.workplace.wcm.services.repository.PACServiceImpl.runAsPrivileged(PACServiceImpl.java:1878)
at com.ibm.workplace.wcm.services.workmanager.AbstractWcmSystemWork.runImpl(AbstractWcmSystemWork.java:87)
at com.ibm.workplace.wcm.services.workmanager.AbstractWcmWork.run(AbstractWcmWork.java:146)
at com.ibm.wps.services.workmanager.impl.WasWorkWrapper.run(WasWorkWrapper.java:44)
at com.ibm.ws.asynchbeans.J2EEContext$RunProxy.run(J2EEContext.java:271)
at java.security.AccessController.doPrivileged(AccessController.java:274)
at com.ibm.ws.asynchbeans.J2EEContext.run(J2EEContext.java:797)
at com.ibm.ws.asynchbeans.WorkWithExecutionContextImpl.go(WorkWithExecutionContextImpl.java:222)
at com.ibm.ws.asynchbeans.ABWorkItemImpl.run(ABWorkItemImpl.java:206)
at java.lang.Thread.run(Thread.java:804)
[4/25/17 9:33:53:227 IDT] 00004163 syndication I Syndication Summary - Subscriber
Syndicator: IntShared_Syn, URL=http://'Was_Server':10039/wps/wcm/connect?MOD=Synd
Subscriber: IntShared_Sub, URL=http://'Was_Server':10039/wps/wcm/connect/'VP_URL_Context'?MOD=Subs
Status: FAILED
Failure Detail: Update failed on subscriber
Unexpected exception thrown while updating subscription: [IceId: Current State: ], exception: com.ibm.workplace.wcm.services.WCMServiceRuntimeException: code: 400
Update Type: REBUILD
Start Date: Tue Apr 25 09:33:53 IDT 2017
Finished Date: Tue Apr 25 09:33:53 IDT 2017
Duration:
Total: 0
Total Failed: 0
[4/25/17 9:33:54:613 IDT] 00000136 syndication I Syndication Summary - Syndicator
Syndicator: IntShared_Syn, URL=http://'Was_Server':10039/wps/wcm/connect?MOD=Synd
Subscriber: IntShared_Sub, URL=http://'VP_HostName':10039/wps/wcm/connect?MOD=Subs
Status: FAILED
Failure Detail: Terminated without confirmation
Returned non-confirmed response: Not confirmed. Unable to contact subscriber. Check the subscriber to ensure it is active and error free. Also review your network connections and your syndication configuration to ensure the subscriber details are correct.
Update Type: REBUILD
Start Date: Tue Apr 25 09:33:53 IDT 2017
Finished Date: Tue Apr 25 09:33:54 IDT 2017
Duration: 1 second
Total: 0
Total Failed: 0
WCM Syndication requires HTTP Basis Authentication to be configured and working.
then I needed to make sure that Trust Association is enabled in WAS Console under Security -> Global Security -> Web and SIP security -> Trust association.
confirmed that the box that says Enable trust association is checked.
also ensured the Interceptor com.ibm.portal.auth.tai.HTTPBasicAuthTAI is created and the configuration were correct.
the cause of the error was that in the fields of urlBlackList and urlWhiteList there was use of the variable ${WpsContextRootPath} which i found out that it is not set anywhere so i change it to /wps instead and now the fields are as follow:
urlBlackList = /wps/myportal*
urlWhiteList = /wps/mycontenthandler*
after Restarting the server and retry syndication - it works!.
also you may follow the direction in this link:
https://developer.ibm.com/answers/questions/206675/why-do-i-see-occasionally-see-a-popup-box-with-a-t.html
but setting these parameters disabled the servlet of vieweing all items in the libraries...
You can try using the ip address instead of the hostname. or Try adding the VP context to the syndicator/subscriber URLs.

Unable to connect to the Administration Server weblogic 12.2.1

I have a WebLogic domain whit an Admin server and one Managed Server. I installed the certificate for ssl connection beetwen Admin and Managed, but when I restart the Managed I have this error:
<May 2, 2016 6:39:24 PM CEST> <Info> <Management> <BEA-141307> <Unable to connect to the Administration Server. Waiting 5 second(s) to retry (attempt number 3 of 3).>
<May 2, 2016 6:39:29 PM CEST> <Info> <Management> <BEA-141298> <Could not register with the Administration Server: java.rmi.RemoteException: [Deployer:149150]An IOException occurred while reading the input.; nested exception is:
javax.net.ssl.SSLHandshakeException: General SSLEngine problem>
I changed this option:
admin console Servers -> server name -> Configuration SSL tab -> Advanced -> Change Hostname Verification dropdown to None
Version 12.2.1
Do you have any solutions?
Thanks
Fabrizio
There's probably some problem with the SSL certificate. I would recommend to double check that and also rerun with -Dssl.debug added to the Weblogic command line to get more information. Then check both the admin and managed server log files, as it might have enough information to answer. If not, please and add more information here.

SQL server service fails to start

I have been trying to start the sql server from last 12 hours but not quite sure what is happening. I got the error 1814 which is 'not sufficient space for tempdb' but I have 60GB of data in C: drive. Also, it is trying to open tables from E: drive which is my DVD drive which is not supposed to happen.
Here by adding the logs. Please let me know whats wrong.
2012-12-26 12:24:06.34 Server Microsoft SQL Server 2008 (SP1) - 10.0.2531.0 (Intel X86)
Mar 29 2009 10:27:29
Copyright (c) 1988-2008 Microsoft Corporation
Express Edition on Windows NT 6.1 <X86> (Build 7601: Service Pack 1)
2012-12-26 12:24:06.34 Server (c) 2005 Microsoft Corporation.
2012-12-26 12:24:06.34 Server All rights reserved.
2012-12-26 12:24:06.34 Server Server process ID is 3456.
2012-12-26 12:24:06.34 Server System Manufacturer: 'WIPRO', System Model: 'WNB7PBM4930R-0007'.
2012-12-26 12:24:06.34 Server Authentication mode is WINDOWS-ONLY.
2012-12-26 12:24:06.34 Server Logging SQL Server messages in file 'c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\Log\ERRORLOG'.
2012-12-26 12:24:06.34 Server This instance of SQL Server last reported using a process ID of 5716 at 12/26/2012 12:15:10 PM (local) 12/26/2012 6:45:10 AM (UTC). This is an informational message only; no user action is required.
2012-12-26 12:24:06.34 Server Registry startup parameters:
-d c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\DATA\master.mdf
-e c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\Log\ERRORLOG
-l c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\DATA\mastlog.ldf
2012-12-26 12:24:06.36 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2012-12-26 12:24:06.36 Server Detected 2 CPUs. This is an informational message; no user action is required.
2012-12-26 12:24:06.41 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.
2012-12-26 12:24:06.48 Server Node configuration: node 0: CPU mask: 0x00000003 Active CPU mask: 0x00000003. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2012-12-26 12:24:06.50 spid6s Starting up database 'master'.
2012-12-26 12:24:06.62 spid6s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'SQLEXPRESS'.
2012-12-26 12:24:06.65 spid6s SQL Trace ID 1 was started by login "sa".
2012-12-26 12:24:06.65 spid6s Starting up database 'mssqlsystemresource'.
2012-12-26 12:24:06.66 spid6s The resource database build version is 10.00.2531. This is an informational message only. No user action is required.
2012-12-26 12:24:06.91 spid6s Server name is 'L--COMPUTER\SQLEXPRESS'. This is an informational message only. No user action is required.
2012-12-26 12:24:06.91 spid10s Starting up database 'model'.
2012-12-26 12:24:06.91 spid6s Informational: No full-text supported languages found.
2012-12-26 12:24:06.91 spid6s Starting up database 'msdb'.
2012-12-26 12:24:07.19 spid10s Error: 17204, Severity: 16, State: 1.
2012-12-26 12:24:07.19 spid10s FCB::Open failed: Could not open file e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\model.mdf for file number 1. OS error: 21(The device is not ready.).
2012-12-26 12:24:07.19 spid10s Error: 5120, Severity: 16, State: 101.
2012-12-26 12:24:07.19 spid10s Unable to open the physical file "e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\model.mdf". Operating system error 21: "21(The device is not ready.)".
2012-12-26 12:24:07.20 spid6s Error: 17204, Severity: 16, State: 1.
2012-12-26 12:24:07.20 spid6s FCB::Open failed: Could not open file e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\MSDBData.mdf for file number 1. OS error: 21(The device is not ready.).
2012-12-26 12:24:07.20 spid6s Error: 5120, Severity: 16, State: 101.
2012-12-26 12:24:07.20 spid6s Unable to open the physical file "e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\MSDBData.mdf". Operating system error 21: "21(The device is not ready.)".
2012-12-26 12:24:07.20 Server A self-generated certificate was successfully loaded for encryption.
2012-12-26 12:24:07.20 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQLEXPRESS ].
2012-12-26 12:24:07.20 Server Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$SQLEXPRESS\sql\query ].
2012-12-26 12:24:07.20 Server 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.
2012-12-26 12:24:07.22 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
2012-12-26 12:24:07.22 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2012-12-26 12:24:07.45 spid10s Error: 17207, Severity: 16, State: 1.
2012-12-26 12:24:07.45 spid10s FileMgr::StartLogFiles: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\modellog.ldf'. Diagnose and correct the operating system error, and retry the operation.
2012-12-26 12:24:07.45 spid10s File activation failure. The physical file name "e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\modellog.ldf" may be incorrect.
2012-12-26 12:24:07.45 spid10s Error: 945, Severity: 14, State: 2.
2012-12-26 12:24:07.45 spid10s Database 'model' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details.
2012-12-26 12:24:07.45 spid10s Could not create tempdb. You may not have enough disk space available. Free additional disk space by deleting other files on the tempdb drive and then restart SQL Server. Check for additional errors in the event log that may indicate why the tempdb files could not be initialized.
2012-12-26 12:24:07.45 spid10s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
2012-12-26 12:24:07.45 spid6s Error: 17207, Severity: 16, State: 1.
2012-12-26 12:24:07.45 spid6s FileMgr::StartLogFiles: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\MSDBLog.ldf'. Diagnose and correct the operating system error, and retry the operation.
2012-12-26 12:24:07.48 spid6s File activation failure. The physical file name "e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\MSDBLog.ldf" may be incorrect.
Look at these links:
http://social.msdn.microsoft.com/Forums/en-US/sqldatabaseengine/thread/922fe202-a2a8-47e4-8f77-402ef14944f8/
http://blogs.msdn.com/b/sanchan/archive/2006/06/04/617585.aspx
1) Make sure you UNCHECK "Compress contents to save disk space" for the file tempdb.mdf
2) Make sure you are NOT saving tempdb in a compressed folder
ALSO:
What's this error:
e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\model.mdf
Maybe you want to just take "model" offline?
I had the same problem with SQL Express. MS SQL installers are very buggy. Several times I've gotten into situations where I just had to reinstall the OS. For this particular issue, the solution is here: https://social.technet.microsoft.com/wiki/contents/articles/31786.sql-server-not-starting-after-fresh-installation.aspx.
The essential bits are:
Start the service from the command line using the following command
NET START MSSQLSERVER /f /T3608
Run the command-line query processor:
SQLCMD –S .\
or
SQLCMD –S .\INSTANCENAME
Check the paths of the databases:
SELECT name, physical_name, state_desc FROM sys.master_files ORDER BY database_id;
go
Fix the database paths:
ALTER DATABASE model MODIFY FILE ( NAME = modeldev, FILENAME = 'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\model.mdf');
ALTER DATABASE model MODIFY FILE ( NAME = modellog, FILENAME = 'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\modellog.ldf');
ALTER DATABASE msdb MODIFY FILE ( NAME = MSDBData, FILENAME = 'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\MSDBData.mdf');
ALTER DATABASE msdb MODIFY FILE ( NAME = MSDBLog, FILENAME = 'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\MSDBLog.ldf');
ALTER DATABASE tempdb MODIFY FILE ( NAME = tempdev, FILENAME = 'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\temp.mdf');
ALTER DATABASE tempdb MODIFY FILE ( NAME = templog, FILENAME = 'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\temp.ldf');
go
Exit and restart the service:
exit
NET STOP MSSQLSERVER
NET START MSSQLSERVER
Works for me in SQL Server 2008. Actually tempdb moved to a location which became inaccessible upon system restart.