Accessing SQL Server Express on Win 8 Single language pack machine
Hi
I have written a small windows app which is installed on multiple windows laptops in our house among our family members.
The app requires a data base which is an SQL express 2012 Edition. We need to install this on our new DELL PC with Win 8 SIngle language Pack OS.
My Query is I am not able to access the Database from our laptops. Looking for a solution.
V.Gopalkrishnan
Hi,
First,please use Ping command to check the network connectivity.
For the WIndows 8 PC,please check the follow service to ensure this service is start.
SQL Server (MSSQLSERVER)
Also,temporarily disable firewall and other security software to check if that helps
If the issue still persists,please contact the app support or
SQL SERVER forum for help.
Regards,
Kelvin Xu
TechNet Community Support
Similar Messages
-
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. -
Is this the right way to implement a database using SQL Server Express?
Purchase a single central server (if you don’t have one already) and house it in the Wild Wood Apartments headquarters located in San Francisco, California
Purchase and install Windows Server 2012 Datacenter onto this single central server.
Along with the Windows Server 2012 Datacenter, you will have to purchase a license called Client Access License or commonly referred to as CAL
Install SQL Server Express onto this single central server as well
You will then need to install remote desktop access to each computer in the 20 building complexes Wild Wood Apartments owns. This allows each complex manager to access SQL Server Express on their computer and input information into the database.
Is there anything that I would have to add on or include, am I missing something, or is something incorrect?
Thank youThis allows each complex manager to access SQL Server Express on their computer and input information into the database.
Yes, but application software must be developed or purchased.
Your design would work for a small scale database and application. More likely you need a pay SS product such as Standard Edition.
Kalman Toth Database & OLAP Architect
SQL Server 2014 Database Design
New Book / Kindle: Beginner Database Design & SQL Programming Using Microsoft SQL Server 2014 -
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 -
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. -
Import MS Access 2010 (*.accdb) to SQL Server Express 2014
Hi,
I have a SQL Server Express 2014 installed in my laptop and when I trying to import MS Access 2010 (.accdb) database using .net framework ODBC it still looking for a driver. Please help. Thanks!!Hi,
You can use SQL Server Migration Assistant (SSMA) to migrate Access databases to SQL Server.
Migrating Access Databases to SQL Server/SQL Azure (AccessToSQL)
http://technet.microsoft.com/en-us/library/hh313051.aspx
Also, refer to the below thread:
Issues in Importing Access Database into SQL Server 2014 Express
http://social.technet.microsoft.com/Forums/en-US/3a40eda6-b609-4855-96e5-f5765acf5059/issues-in-importing-access-database-into-sql-server-2014-express
Hope it helps
Tracy Cai
TechNet Community Support -
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 -
What's SQL Server express got over Access?
I have recently found out that there is a free version of SQL
server called SQL Server Express, and I wondered if anybody here
uses the express version.
What has it got that beats Access? What benefit can I get
from using it over Access? Does it have any benefits over MySQL?
Also, does it have a user interface or is it command line
based?
Any help and advice would be greatly appreciated.
Thanks.
Matmatthew stuart wrote:
> I have recently found out that there is a free version
of SQL server called SQL
> Server Express, and I wondered if anybody here uses the
express version. What
> has it got that beats Access? What benefit can I get
from using it over Access?
> Does it have any benefits over MySQL? Also, does it have
a user interface or
> is it command line based? Any help and advice would be
greatly appreciated.
> Thanks. Mat
>
The main difference is that it's a server, unlike Access
which is file
that the webserver connects to. It comes with Management
Studio software
that allows you to connect to the sql server.
If you own your own or rent a Windows webserver then you can
happily
install SQL express, but if you don't, your host will have to
offer it
to you as an add on, just like they have to offer MySQL as
part of your
hosting package.
Access is really a desktop application that can work on a
website, but
its not a "proper" sql server like MS SQL or Oracle or any
other other
big boys out there.
You don't need to know SQL to use it, but if you opt to learn
SQL, even
just the basics, then it will all make sense and will be
beneficial to you.
Steve -
Cannot install SQL Server Express - Access is denied messagwe
When trying to run the downloaded SQL Server Express EXE, I get an error message "Access is denied". Can anyone advise me how to proceed?
Are you running from special folder i.e desktop ?
Can you try to de-compress first then launch setup
to de-compress express package run from the commandline
<package.exe> /x:"<decompression path>"
FAQ
Regards,
Ahmed Ibrahim
SQL Server Setup Team
My Blog
This posting is provided "AS IS" with no warranties, and confers no rights. Please remember to click
"Mark as Answer" and "Vote as Helpful"
on posts that help you.
This can be beneficial to other community members reading the thread. -
How many sql server express instances i can install maximum in single system
Hello Team,
I want to install multiple sql express instances in single machine. My question is that how many instances of sql server express editions i can install in single machine ?
Thanks,
Udaya Kumar
udaya kumarFor practical reasons as much as you like you probably would not exceed in any case 10 instances because after that resource crunch would start but any how you can read Max specification for SQL Server
More accurate answer is "50 instances on a stand-alone server for all SQL Server editions."
https://msdn.microsoft.com/en-us/library/ms143432.aspx
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP -
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 -
I have tried installing SQL Server 2008 multiple times on my machine, and I always receive this error about 3/4 of the way through: '' is not a valid login or you do not have permission.
I have tried installing both SQL Server Express 2008 with Tools and SQL Server Express 2008 with Advanced Services, and they both fail the same way. I am trying to do a new stand-alone installation.
I'm running Windows XP Home Edition SP3.
Looking into the error, some forums say I have to install it from THE Administrator account, and not an account with administrator permissions; it also cannot be in Safe Mode, because then the Windows Installer won't work. Unfortunately, I haven't been able to login to the Administrator account. I can go to the home login screen, do ctrl+alt+del twice, and attempt to login to the Administrator account, but I receive this error: Unable to Log You on because of an Account Restriction.
Other forums say that in the Server Configuration section, all you have to do is provide the username and a strong password from an administrative account on the computer, and it doesn't have to be THE Administrator. Well, I did that, but for some reason it doesn't recognize my username and password, it says something like "The credentials you provided for the SQL Server Agent are invalid". BUT THOSE ARE THE CORRECT CREDENTIALS FOR MY ADMINISTRATIVE USER! So I'm forced to use one of the accounts without a password, like NT AUTHORITY\SYSTEM. That's the only way I can get past this step.
Also, just FYI, on the next step, which is Database Engine Configuration, I am using Mixed Mode for the Security Mode. I AGAIN provide a password, and then add my current user (who IS an administrator on my machine!) to the SQL Server Administrators box.
But yet, it fails every single time.
This is pathetic and ridiculous. I must have tried to install this thing 15 times, that is not an exaggeration. I'm posting this on several other forums as well, maybe an MVP or Bill Gates himself can help me.
I have one of the log files from a failed installation. If someone would like to see it, I will post it.Papy Normand wrote:
Hello,
Please, could you have a look on the excellent answer of Mike Wachal you will find here :
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=4160294&SiteID=1
Don't hesitate to post again for more help or explanations
Have a nice day
PS : if you are talking about the Sql Server Agent Service, it is disabled for Sql Server Express. It is enabled only for the Workgroup/Standard/Dev and Entreprise Editions
Sorry, but I've tried the suggestion in that link, and it hasn't helped me.
For anyone wonder, the link is talking about the problem in Server Configuration where I enter my Windows user account and password (which is in the Administrative group), but it says the credentials are invalid. The link suggests that you need to either enter your Windows account (which I did, and it wouldn't let me go to the next step), or to use one of the built in accounts (which I also tried, but it gave me the " '' is not a valid login" error during the installation).
Any other ideas?
I haven't had any answers from any other forums either, so I'll just post my log file in case anyone wants to look at this:
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): -2068643839
Exit facility code: 1203
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: 2008-11-17 11:13:47
End time: 2008-11-17 12:17:25
Requested action: Install
Log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081117_110917\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.0.1600.22%26EvtType%3d0xBE029E38%400x12C2466D
Machine Properties:
Machine name: STEVEN
Machine processor count: 2
OS version: Windows XP
OS service pack: Service Pack 3
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
SQLProductFamilyCode: {628F8F38-600E-493D-9946-F4178F20A8A9}
ProductName: SQL2008
Type: RTM
Version: 10
SPLevel: 0
Installation location: D:\x86\setup\
Installation edition: DEVELOPER
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: False
AGTSVCACCOUNT: NT AUTHORITY\SYSTEM
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Config
ASDATADIR: C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Data
ASDOMAINGROUP: <empty>
ASLOGDIR: C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Log
ASPROVIDERMSOLAP: 1
ASSVCACCOUNT: NT AUTHORITY\SYSTEM
ASSVCPASSWORD: *****
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: STEVEN\Steven
ASTEMPDIR: C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Temp
BROWSERSVCSTARTUPTYPE: Disabled
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081117_110917\ConfigurationFile.ini
ENABLERANU: False
ERRORREPORTING: False
FEATURES: SQLENGINE,REPLICATION,FULLTEXT,AS,RS,BIDS,CONN,IS,BC,SDK,BOL,SSMS,ADV_SSMS,SNAC_SDK,OCS
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT AUTHORITY\LOCAL SERVICE
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: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT AUTHORITY\SYSTEM
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
MEDIASOURCE: D:\
NPENABLED: 0
PID: *****
QUIET: False
QUIETSIMPLE: False
RSINSTALLMODE: DefaultNativeMode
RSSVCACCOUNT: NT AUTHORITY\SYSTEM
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT AUTHORITY\SYSTEM
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: STEVEN\Steven
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: False
TCPENABLED: 0
X86: False
Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081117_110917\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: 0x12C2466D
Configuration error description: '' is not a valid login or you do not have permission.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081117_110917\Detail.txt
Feature: SQL Client Connectivity SDK
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: SQL Server Replication
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0x12C2466D
Configuration error description: '' is not a valid login or you do not have permission.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081117_110917\Detail.txt
Feature: Full-Text Search
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0x12C2466D
Configuration error description: '' is not a valid login or you do not have permission.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081117_110917\Detail.txt
Feature: Analysis Services
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Reporting Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0x12C2466D
Configuration error description: '' is not a valid login or you do not have permission.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081117_110917\Detail.txt
Feature: Integration Services
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Client Tools Connectivity
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Complete
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Basic
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Client Tools SDK
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Client Tools Backwards Compatibility
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Business Intelligence Development Studio
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: SQL Server Books Online
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Microsoft Sync Framework
Status: Passed
MSI status: Passed
Configuration status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081117_110917\SystemConfigurationCheck_Report.htm -
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 2008 R2 and Windows 8.1 (Standard)
I recently re-engineered the backend of a legacy Access 2003 application because we knew that going forward we were going to loose the replication capability in Access. This is a small, departmental app, so the new SQL Server Express 2008 R2 backend is
hosted on a robust Windows 7 system. I tested the implementation with both Windows XP and Windows 7 clients running the updated Access 2003 frontend and everything worked great.
We are now in the midst of a company-wide upgrade to Windows 8.1 and I'm having issues. The legacy frontend works fine with Access 2013 (full version) when run locally on the Win7 machine, but I can't get any of the new Win 8.1 clients to connect to the
SQL database using the Access 2013 Runtime module. I CAN create ODBC connections to SQL Server from the clients and they test successfully, so I think I have a valid SQL connection to the Win 7 box.
To recap: old clients were WinXP Pro with Office 2003 Pro, new clients are Win 8.1 (non-Pro) with Access 2013 Runtime module.
Any ideas?Hi ,
Glad to hear that you have found the solution. Thank you for coming back and let us know the result:)
Best Regards,
Tracy
Tracy Cai
TechNet Community Support
Maybe you are looking for
-
Changing a Boundary in SCCM 2007
I have a live SCCM 2007 environment, and I need to change the existing boundaries so as to accommodate a SCCM 2012 environment that we are introducing (and will eventually migrate to). The SCCM 2007 boundaries are all 'IP address range'. So my questi
-
Hi all, I have 2 screens 1000 & 2000 in module pool. In PAI of 1000, i am using CAll screen 2000. As we know in case of <b>call screen</b> we can come back to the previous screen. Now when i write leave screen in PAI of 2000. Control is not going to
-
SMIL ignores 'switch' in 'seq' tags
I've built a player based off sprint 10 (0.93) that uses the SMILPlugin and Dynamic Streaming. The player was working great with single items, either flv or a set of MBR streams, once I started sequencing them I ran into some issues. It appears the S
-
Hi, Im wanting to be able to make a JPopupMenu appear when i right click on a JTable, but ive found that when i right click over actual rows, it doesnt register the right click but when i right click over blank space in the table it works fine this i
-
Error while downloading ios 5.1.1
i am trying to download ios 5.1.1(on air) as my ipad is giving some trouble like hanging in between n other problems, it goes on downloading but when it goes to updates it shows < error occured while upodating 5.1.1> any solution for this issue pleas