SQL Server Security Logins vs. Databases Security Users

Why isn't all security needs done just in logins? When migrating databases, the Logins are not brought over when restoring a backup. It does not make sense. Could it not be done all just in the Security > Logins area or why not? That COULD be designed to track users and rights on various databases rather than a thing owned by each database....
Thanks for your time.
Gib

Understand
the below points first
Login are being used to access the server (Server level)
Database users are being used to access the database.(Database level)
Why
isn't all security needs done just in logins?
Just Imagine the below things:
I want give the permission to user to take backup for specific databases in this case we will give databasedb_backupoperator
role. Is this possible with server role to take backup for specific databases
I want give the permission to user to run the BULK INSERT statement on databases in this case we
will give bulkadmin server role. Is this possible with database role to run the BULK INSERT statement on databases
Thanks-Vanchan
Please click the Mark as Answer button if a post solves your problem!

Similar Messages

Renaming Sql Server 2008 r2 enterprise edition security roles

Hello All,
We got a requirement to rename existing SQL SERVER 2008 R2 ENTERPRISE EDITION security roles.
We are unaware of the impact on the existing users with these roles.
Can anybody advise us if we rename the role name manually,
We have to restart the sql server services to reflect the role name change to the users with these
roles?
Thanks In Advance

Hello All,
We got a requirement to rename existing SQL SERVER 2008 R2 ENTERPRISE EDITION security roles.
We are unaware of the impact on the existing users with these roles.
Can anybody advise us if we rename the role name manually,
We have to restart the sql server services to reflect the role name change to the users with these
roles?
Thanks In Advance
What security roles are you talking about?
built-in server- or database-roles? - those cannot be renamed.
User-defined roles can be renamed at any point in time without any problems unless you write code that specifically accesses them by name yourself.
Andreas Wolter (Blog |
Twitter)
MCSM: Microsoft Certified Solutions Master Data Platform, MCM, MVP
www.SarpedonQualityLab.com |
www.SQL-Server-Master-Class.com

Create a SQL Server authentication login

I am trying to create an SQL Server authentication login. using the documentation given http://azure.microsoft.com/en-gb/documentation/articles/sql-database-get-started/#QueryDBSysData
with the below sql statement
CREATE LOGIN login1 WITH password='Password1';
but gives an error
Msg 5001, Level 16, State 1, Line 1
User must be in the master database.
how do i get around this problem?

Hi roma_victa,
Please make sure that you issue the command in the master database of your logical server, otherwise it will fail.
Thanks,
Jan

SQL Server to Oracle Converted Model missing users

I am doing a migration from SQL Server to Oracle with about 100 users. The captured model seems to be correct and all of the users are there. But, when creating the Oracle Converted Model, not all of the users are being converted. On the first attempt, the Converted Model had only 21 users, and on the next attempt, the Converted Model only had 16 users. Does anyone know what could be causing this?

Oracle Database XE does not allow more than one instance per server.
To define a primary key correct syntax is:
Create table summary(
Field NOT NULL PRIMARY KEY,
Or:
PRIMARY KEY constraint tabla_PK (field)
To generate the value of the primary key you must create a sequence before or after creating the table:
Create Sequence summary_seq
Start with 1
Increment by 1
Nocycle;
You can use the sequence in INSERT INTO or through a trigger:
With Insert Into:
Insert into Summary
Values (summary_seq.nextval, valkor1, value2 ,...);
With a trigger:
Create or replace Trigger BI_summary
Before Insert on SUMMARY
For each row
Begin
Select summary_seq.nextval into campoPK
From dual;
End;

SQL Server Agent Job And Database Mail - Error formatting query, probably invalid paramters

We have a stored procedure that we are trying to call with a SQL Server Agent Job. The stored procedure calls Database Mail. This is SQL 2008. The execute task is simply:
USE [Production]
GO
EXEC [dbo].[JOB_EMAIL_SCHEDULED_REPORTS]
GO
When the job runs, it is erroring out immediately, with the error:
Execute as user: NT AUTHORITY\NETWORK SERVICE. Error formatting query, probably invalid paramters [SQLSTATE 42000] (Error 22050). The step failed.
When we go into SQL Server Manager and just execute the SQL query, it works though. Something within the SQL Server Agent job, and Database Mail is causing problems. Any ideas? Thanks.

Justin,
If you use SSMS then the procedure is executed under a different user when compared to running using a SQL Server Agent Job.
Isolate the problem by running a SQL Server agent job that sends a mail. Also check if the NT Authority\Network Service account is
in good standing. Look at the below thread with a similar problem that had an expired account.
http://social.msdn.microsoft.com/Forums/en/sqltools/thread/bac7ecee-a156-4313-b532-ba15813a0700
http://SankarReddy.com/

Alert: SQL Server Service Broker or Database Mirroring Transport stopped

Hi Team,
I got this error message even no one DB configured as mirroring ???
Alert: SQL Server Service Broker or Database Mirroring Transport stopped Priority: 0 Severity: 2 Resolution state: New
Alert description: The Database Mirroring protocol transport has stopped listening for connections.

Can you check the rule. By default the configurations are disabled state that is the reason you are getting the alert.
If it's not configured properly then you might need to override it
--Prashanth

Article - LabVIEW-Based Utility to Package & Deploy MS SQL Server 2005 Express Edition Databases

Anthony Lukindo, the newest ExpressionFlow blog LabVIEW community author, has just published the first part of his two-part blog article
LabVIEW-Based Utility to Package & Deploy MS SQL Server 2005 Express Edition Databases - Part 1
Please check it out!
Tomi Maila

Anthony Lukindo, the newest ExpressionFlow blog LabVIEW community author, has just published the first part of his two-part blog article
LabVIEW-Based Utility to Package & Deploy MS SQL Server 2005 Express Edition Databases - Part 2
Please check it out!
Tomi Maila

Querying SQL server table from Oracle database 11g

Hi all
We are using oracle database 11g R2 on REL 5 and i have an SQL server database used by one of our application.
In my Oracle database, i want to query one table in my SQL server database and to link it in a table in Oracle database to compare data.
Is there a way like database link or something else to do this need>
Please send a link or pots here step by step the way on how to accomplish my query.
Thank you.

Yes, you can set up your SQL Server as an external database link, using Oracle Heterogeneous Services with SQL Server as an ODBC connection (easier to do if your Oracle server is a Windows server, a little more tricky if your Oracle server is *nix based)
Here's the documentation... for 11gR2
http://www.oracle.com/pls/db112/search?remark=quick_search&word=heterogeneous+services

Can DPM 2012 R2 backup SQL Server 2012 AlwaysOn enabled databases

Is it possible to use DPM 2012 R2 for backing up
SQL Server 2012 AlwaysOn enabled databases ?
Because if Alwayson configured for any Database , particular database is not available to select for backup.

Hi,
Yes, starting with DPM 2012 SP1 SQL AlwaysOn enabled databases can be protected as long as they are not part of sharepoint farm. DPM shows the Availability Groups under Cluster Group.
You must explicitly add the system account NTAuthority\System or NT AUTHORITY\DPMRA to the Sysadmin group on SQL Server.
Protecting SQL Server Data
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

SQL Server Upgrade Advisor 2014 - Database Compatibility Level checking

I have the following scenario... I have a database server running SQL Server 2008 R2 (10.50.4260). On that server I restored a database from SQL Server 2005. Looking at the compatibility level through the properties of the database (using SSMS) and
by querying against sys.databases, I can see the database has the compatibility level of 90, which is what I expected.
In looking to bring this database over to a SQL Server 2014 database server, I have run the SQL Server Upgrade Advisor 2014 tool as well as the SQL Server Upgrade Advisor 2012 tool. With the 2014 tool, my expectation would be that it would warn me
that the compatibility level will be upgraded to 10 (or something), however, I received no such warning. I ran the 2012 version of the tool as well, expecting that I might get a deprecation warning (or something), no such luck. I have run the 2014
tool from my computer and from another one, same results.
Does the upgrade advisor not check for the compatibility level? Or does my configuration maybe have something to do with it (having it on a 2008 R2 server)? From looking at screenshots of when other people have ran the tool, I was under the impression
it checked this. See the link below for an example...
http://blogs.msdn.com/b/mspfe/archive/2012/12/06/sql-server-upgrade-advisor-considerations-when-upgrading-from-sql-2000-to-sql-2012.aspx
Thoughts anyone?

Lydia,
I agree with regards to the 2012 version. However, in SQL Server 2014, upgrading a database with a compatibility level of 90 sets
the database to compatibility level 100. See link below...
https://technet.microsoft.com/en-us/library/bb510680.aspx
Shouldn't the 2014 version of the advisor tool issue the same warning seen in the screenshot of the msdn blog post we both mentioned? As in... "After upgrade, compatibility levels <list of levels>, will be set to 100".
Hi JJordheim,
According to my test, SQL Server 2014 Upgrade Advisor also only raise warning when database compatibility level is less than 90 in the “SQL Server Parameters” page.
From your description, when database compatibility level is set to 90, SQL Server 2014 Upgrade Advisor should also raise warning, right? If so , this is a design issue of SQL Server 2014 Upgrade Advisor, personally, I recommend you
submit a feedback to the Microsoft Connect at this link
https://connect.microsoft.com/SQLServer/Feedback . Your feedback enables Microsoft to offer the best software and deliver superior services.
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support

Sql Server 2012 Login Failed for user "NT Authority\System"

I have installed SQL Server on a new server. I have been getting the following error on each of the database in it.
Login failed for user 'NT AUTHORITY\SYSTEM'. Reason: Failed to open the explicitly specified database 'ABC'. [CLIENT: xxx.xxx.xxx.xxx]
Here is some information on the instance:
1) Default instance
2) SQL Server, Sql Server Agent, Sql Server Reporting services are running / log on using a domain service account.
3) Sql Server Browser is disabled.
4) SQL Server VSS Writer is running / log on as Local Service.
5) NT AUTHORITY\SYSTEM does exists in Login with just public server roles.
I ran a trace on login failed and I get:
ApplicationName: Microsoft Windows Script Host
and it runs every 15 minutes.
Help please?

Hi,
The error was thrown when the SCOM components connected to the backend SCOM databases.
You can specify a domain account, grant it the sysadmin role and the error should be gone.
Also, see the replies in your previous thread:
http://social.technet.microsoft.com/Forums/en-US/23f6b6cb-ec41-4117-8613-26d24c948827/login-failed-for-user-username-reason-failed-to-open-the-explicitly-specified-database
Thanks.
Tracy Cai
TechNet Community Support

SQL Server Log: Login failed for user ''

We've found in SQL Server Log many records:
Date
3/22/2013 11:13:03 AM
Log
Windows NT (Application)
Source
MSSQLSERVER
Category
Logon
Event
3221243928
Computer
SBO05
Message
Login failed for user ''. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: <local machine>]
The server autentification is set to "SQL Server and Windows Autentification mode". But when we open SAP, before entering login/password, we see this message in log. But we still could work in SAP.
How could we solve this?
Kind regards,
Anna Shevchenko

Hi Joseph,
It doesn't help. The same things i've already done.
But when I change Mixed Autentification to Windows, i see another error:
Date
3/22/2013 11:04:26 AM
Log
SQL Server (Current - 3/22/2013 12:33:00 PM)
Source
Logon
Message
Login failed for user 'sa'. Reason: Failed to open the explicitly specified database. [CLIENT: 192.168.0.145]
Do you know why?
Kind regards,
Anna Shevchenko

SQL Server 2012 installation and to default user database files to a particular path

Hi, I am working on SQL Server 2012 installation on one of our test boxes and I would like to configure the sql server install binaries and all the system databases but for tempdb to be in my C and tempdb on a different drive and once all this is set up,
whenever a developer creates a new database without specifying the path for the mdf & ldf files. They should be defaulted to a path like "D:/Data file" & "D:/Log file" for instance instead of being created on the C drive.
Thanks in advance.........
Ione

Hi,
You can of course set default location of database through management Studio please refer below link. Once you change default location even if you do not specify location it would take default one.
http://sqlandme.com/2013/03/18/sql-server-changing-default-database-location-for-server/
I would advise you not to keep files on C drive let it be dedicated system drive also its quite possible that SQL server service account would not have privilege on C drive so after you move tempdb SQL server would not come online as tempdb files cannot
be created . Tempdb is always recreated after SQL Server starts so you just need to change location once using Alter database command
See example mentioned in below link for how to do that
http://msdn.microsoft.com/en-us/library/ms345408%28SQL.90%29.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 Articles

Sql server will not start - Database 'model' cannot be opened. It is in the middle of a restore.

Sql server service will not start after server reboot:
2009-08-13 14:15:43.94 spid7s      SQL Trace ID 1 was started by login "sa".
2009-08-13 14:15:43.97 spid7s      Starting up database 'mssqlsystemresource'.
2009-08-13 14:15:43.97 spid7s      The resource database build version is 10.00.1600. This is an informational message only. No user action is required.
2009-08-13 14:15:44.30 Server      A self-generated certificate was successfully loaded for encryption.
2009-08-13 14:15:44.30 spid7s      Server name is 'WIN-37R9WFWAJIB\MSDB1'. This is an informational message only. No user action is required.
2009-08-13 14:15:44.32 spid10s     Starting up database 'model'.
2009-08-13 14:15:44.32 Server      Server is listening on [ 'any' <ipv6> 49167].
2009-08-13 14:15:44.33 Server      Server is listening on [ 'any' <ipv4> 49167].
2009-08-13 14:15:44.33 Server      Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSDB1 ].
2009-08-13 14:15:44.33 Server      Server named pipe provider is ready to accept connection on [ \\.\pipe\sql\query ].
2009-08-13 14:15:44.35 spid10s     The database 'model' is marked RESTORING and is in a state that does not allow recovery to be run.
2009-08-13 14:15:44.38 Server      Server is listening on [ ::1 <ipv6> 49168].
2009-08-13 14:15:44.38 Server      Server is listening on [ 127.0.0.1 <ipv4> 49168].
2009-08-13 14:15:44.38 Server      Dedicated admin connection support was established for listening locally on port 49168.
2009-08-13 14:15:44.39 spid10s     Error: 927, Severity: 14, State: 2.
2009-08-13 14:15:44.39 spid10s     Database 'model' cannot be opened. It is in the middle of a restore.
2009-08-13 14:15:44.49 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.
2009-08-13 14:15:44.50 spid10s     SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informa
there is plenty of room on the server, so i dont think its a disk space issue. i am able to start the service as such:
C:\Users\Administrator>net start MSSQL$MSDB1 /c /m /T3608
The SQL Server (MSDB1) service is starting.
The SQL Server (MSDB1) service was started successfully
sqlcmd -e
1> select name, status from sysdatabases;
2> go
select name, status from sysdatabases;
name
                                                 status
master
                                                       65544
tempdb
                                                       65544
model
                                                       65568
msdb
                                                  1073807368
SS_DBA_Dashboard
                                                  1073807368
(5 rows affected)
model is in RESTORING state and I dont know how to fix it. I am running simple backups, so I have a somewhat recent backup of model.bak but when I attempt to restore it I get an error:
1> restore database model
2> go
restore database model
Msg 3112, Level 16, State 1, Server WIN-37R9WFWAJIB\MSDB1, Line 1
Cannot restore any database other than master when the server is in single user
mode.
Msg 3013, Level 16, State 1, Server WIN-37R9WFWAJIB\MSDB1, Line 1
RESTORE DATABASE is terminating abnormally.
other forums suggest manually updating the status column but i dont know if my syntax is wrong or it just cant be done in sql server 2008:
1> begin transaction
2> update sysdatabases set status=16 where name='model'
3> ;
4> go
begin transaction
update sysdatabases set status=16 where name='model'
Msg 4406, Level 16, State 1, Server WIN-37R9WFWAJIB\MSDB1, Line 2
Update or insert of view or function 'sysdatabases' failed because it contains a
derived or constant field.
1>
yet another forum suggested taking a cleanly shut down model.mdf and model.ldf from another sql server 2008 instance and placing those in the data directory while moving the 'restoring' ones to a backup location. this didnt work either. any help is appreciated im new to sql server and this is very frustrating! thanks in advance!

I have the same issue on SQL Server 2008R2, after a server reboot, but none of the NET START commands or command line attempts are successful to start the Service.
NET START command results in "Access Denied" "System Error 5" and the Command line attempts result in
Server      Error: 17058, Severity: 16, State: 1.
Server      initerrlog: Could not open error log file ''.
Any help?
SQL Error log file:
2011-03-29 16:50:49.40 Server      (c) Microsoft Corporation.
2011-03-29 16:50:49.40 Server      All rights reserved.
2011-03-29 16:50:49.40 Server      Server process ID is 7292.
2011-03-29 16:50:49.40 Server      System Manufacturer: 'Dell Inc.', System Model: 'PowerEdge T710'.
2011-03-29 16:50:49.40 Server      Authentication mode is MIXED.
2011-03-29 16:50:49.40 Server      Logging SQL Server messages in file 'E:\MSSQL\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2011-03-29 16:50:49.40 Server      This instance of SQL Server last reported using a process ID of 7448 at 3/29/2011 4:30:06 PM (local) 3/29/2011 8:30:06 PM (UTC). This is an informational message only; no user action is required.
2011-03-29 16:50:49.40 Server      Registry startup parameters:
-d E:\MSSQL\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\master.mdf
-e E:\MSSQL\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG
-l E:\MSSQL\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
-T 4616
2011-03-29 16:50:49.42 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2011-03-29 16:50:49.42 Server      Detected 24 CPUs. This is an informational message; no user action is required.
2011-03-29 16:50:49.84 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.
2011-03-29 16:50:49.84 Server      Lock partitioning is enabled. This is an informational message only. No user action is required.
2011-03-29 16:50:49.86 Server      Node configuration: node 0: CPU mask: 0x0000000000fff000:0 Active CPU mask: 0x0000000000fff000:0. This message provides a description of the NUMA configuration for this computer. This is an informational
message only. No user action is required.
2011-03-29 16:50:49.86 Server      Node configuration: node 1: CPU mask: 0x0000000000000fff:0 Active CPU mask: 0x0000000000000fff:0. This message provides a description of the NUMA configuration for this computer. This is an informational
message only. No user action is required.
2011-03-29 16:50:49.89 spid9s      Starting up database 'master'.
2011-03-29 16:50:49.95 spid9s      CHECKDB for database 'master' finished without errors on 2011-03-18 08:46:34.257 (local time). This is an informational message only; no user action is required.
2011-03-29 16:50:49.95 spid9s      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2011-03-29 16:50:49.97 spid9s      SQL Trace ID 1 was started by login "sa".
2011-03-29 16:50:49.97 spid9s      Starting up database 'mssqlsystemresource'.
2011-03-29 16:50:49.99 spid9s      The resource database build version is 10.50.1600. This is an informational message only. No user action is required.
2011-03-29 16:50:50.20 spid13s     Starting up database 'model'.
2011-03-29 16:50:50.20 spid9s      Server name is 'XXXX'. This is an informational message only. No user action is required.
2011-03-29 16:50:50.21 Server      The certificate [Cert Hash(sha1) "C41DC20703F049763778AC2842C3C8A3A2C6EED4"] was successfully loaded for encryption.
2011-03-29 16:50:50.21 Server      Server is listening on [ 'any' <ipv6> 1433].
2011-03-29 16:50:50.21 Server      Server is listening on [ 'any' <ipv4> 1433].
2011-03-29 16:50:50.21 Server      Server local connection provider is ready to accept connection on [
\\.\pipe\SQLLocal\MSSQLSERVER ].
2011-03-29 16:50:50.21 Server      Server named pipe provider is ready to accept connection on [
\\.\pipe\sql\query ].
2011-03-29 16:50:50.21 Server      Server is listening on [ ::1 <ipv6> 1434].
2011-03-29 16:50:50.21 spid13s     The database 'model' is marked RESTORING and is in a state that does not allow recovery to be run.
2011-03-29 16:50:50.21 Server      Server is listening on [ 127.0.0.1 <ipv4> 1434].
2011-03-29 16:50:50.21 spid13s     Error: 927, Severity: 14, State: 2.
2011-03-29 16:50:50.21 spid13s     Database 'model' cannot be opened. It is in the middle of a restore.
2011-03-29 16:50:50.21 Server      Dedicated admin connection support was established for listening locally on port 1434.
2011-03-29 16:50:50.22 spid13s     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.
2011-03-29 16:50:50.22 spid13s     SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.

Connection Failed SQL State: 'HYT00' SQL Server Error: 0 [Microsoft] [ODBC SQL Server Driver] Login Timeout expired

I backed up my database   on old Notebook    SQLSTRINGCONNECT worked all day for any database in SQL SERVR I created
have brand new computer Notebook
installed SQL SERVER 2008 THE EXACT SAME WAY
I RESTORED THE DATABASE
However, I cannot connect to it via Visual FoxPro 9.0 with   SQLSTRINGCONNECT
or even Windows 7    ODBC Data Source ADministrator

Hi,
We need more information as Olaf asked, but my first guess is that you have permissions problem since the users are not the same users in different machines (local users, or SQL Server users),
even if they have the same name :-)
[Personal Site] [Blog] [Facebook]

SQl Server Installation failing for Database Engine and Its Services

Hi,
I was trying to install SQL SERVER 2008 R2 on VM having 500 GB hard disk and 16 GB RAM.
OS is Windows Server 2008
But it fails for Database Engine.
Installation Details are as 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-10-13 18:41:01
End time: 2014-10-13 19:26:32
Requested action: Install
Log with failure: C:Program FilesMicrosoft SQL Server100Setup BootstrapLog20141013_183354Detail.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.1600.1%26EvtType%3d0x476BF04A%400xBB814387
Machine Properties:
Machine name: KVS-IN-WFAN092
Machine processor count: 4
OS version: Windows Server 2008 R2
OS service pack: Service Pack 1
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered
Package properties:
Description: SQL Server Database Services 2008 R2
ProductName: SQL Server 2008 R2
Type: RTM
Version: 10
SPLevel: 0
Installation location: di-softwareSoftwaresSQLSQL_2008_R2_Enterprisex64setup
Installation edition: ENTERPRISE
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: False
AGTSVCACCOUNT: NT AUTHORITYNETWORK SERVICE
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
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: Automatic
CONFIGURATIONFILE: C:Program FilesMicrosoft SQL Server100Setup BootstrapLog20141013_183354ConfigurationFile.ini
CUSOURCE:
ENABLERANU: False
ENU: True
ERRORREPORTING: False
FARMACCOUNT: <empty>
FARMADMINPORT: 0
FARMPASSWORD: *****
FEATURES: SQLENGINE,REPLICATION,FULLTEXT,SSMS,ADV_SSMS
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT AUTHORITYLOCAL SERVICE
FTSVCPASSWORD: *****
HELP: False
IACCEPTSQLSERVERLICENSETERMS: False
INDICATEPROGRESS: False
INSTALLSHAREDDIR: C:Program FilesMicrosoft SQL Server
INSTALLSHAREDWOWDIR: C:Program Files (x86)Microsoft SQL Server
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:Program FilesMicrosoft SQL Server
INSTANCEID: SQLServer
INSTANCENAME: SQLSERVER
ISSVCACCOUNT: NT AUTHORITYNetworkService
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
NPENABLED: 0
PASSPHRASE: *****
PCUSOURCE:
PID: *****
QUIET: False
QUIETSIMPLE: False
ROLE: <empty>
RSINSTALLMODE: FilesOnlyMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT AUTHORITYNETWORK SERVICE
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: KRONOSENGsuperuser
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: False
TCPENABLED: 1
UIMODE: Normal
X86: False
Configuration file: C:Program FilesMicrosoft SQL Server100Setup BootstrapLog20141013_183354ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: SQL Server Replication
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Full-Text Search
Status: Failed: see logs for details
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
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:Program FilesMicrosoft SQL Server100Setup BootstrapLog20141013_183354SystemConfigurationCheck_Report.htm
And Error in log file are maily as below.
2014-10-13 19:26:27 Slp: Completed Action: SqlBrowserConfigAction_install_Startup_Cpu32, returned True
2014-10-13 19:26:27 Slp: Action "ConfigEvent_SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64_Install_Startup_postmsi" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64_Install_Startup_postmsi The condition tests feature: SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There are 11
dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Action "SqlBrowserConfigEngAction_install_Startup_Cpu64" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: SqlBrowserConfigEngAction_install_Startup_Cpu64 The condition tests feature: SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There are 11 dependant features. The feature is tested
for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Action "SqlEngineConfigAction_install_startup_Cpu64" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: SqlEngineConfigAction_install_startup_Cpu64 The condition tests feature: SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There are 11 dependant features. The feature is tested
for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Action "ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Install_Startup_postmsi" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Install_Startup_postmsi The condition tests feature: MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64. There are 2 dependant
features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Action "AgentInstall_AgentInstallStartup_Cpu64" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: AgentInstall_AgentInstallStartup_Cpu64 The condition tests feature: MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64. There are 2 dependant features. The feature is tested for results:
ValidateResult, Result." did not pass as it returned false and true was expected.
2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Action "ConfigEvent_SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64_Install_Startup_postmsi" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64_Install_Startup_postmsi The condition tests feature: SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64. There
are 3 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Action "ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_Install_Startup_postmsi" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_Install_Startup_postmsi The condition tests feature: SQL_FullText_Adv_sql_fulltext_Cpu64. There are 3 dependant features. The feature
is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Action "FulltextConfigAction_install_startup_Cpu64" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: FulltextConfigAction_install_startup_Cpu64 The condition tests feature: SQL_FullText_Adv_sql_fulltext_Cpu64. There are 3 dependant features. The feature is tested for results:
ValidateResult, Result." did not pass as it returned false and true was expected.
2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Action "ConfigEvent_SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64_Install_StartupFinalize_postmsi" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64_Install_StartupFinalize_postmsi The condition tests feature: SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There
are 11 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Action "ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Install_StartupFinalize_postmsi" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Install_StartupFinalize_postmsi The condition tests feature: MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64. There are
2 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Action "ConfigEvent_SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64_Install_StartupFinalize_postmsi" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64_Install_StartupFinalize_postmsi The condition tests feature: SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64.
There are 3 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Action "ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_Install_StartupFinalize_postmsi" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_Install_StartupFinalize_postmsi The condition tests feature: SQL_FullText_Adv_sql_fulltext_Cpu64. There are 3 dependant features.
The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Completed Action: PostMsiTimingConfigAction, returned True
2014-10-13 19:26:27 Slp: Completed Action: ExecuteStandardTimingsWorkflow, returned True
2014-10-13 19:26:27 Slp: ----------------------------------------------------------------------
2014-10-13 19:26:27 Slp: Running Action: ExecuteExtendedTimingsWorkflow
Thanks,
Mahesh

I have uploaded detail.txt at below url.
http://m.uploadedit.com/b041/1413264342685.txt
Hi Mahesh,
According to log file, I find the message ‘The setup100.exe.config file was not found, therefore the DTSWizard and SQLWatson app config files were not replaced’. It seems that the SQL Server setup file is not complete. Please check that if the SQL Server
setup file is corrupted, if it is corrupted, please download it again and reinstall SQL Server 2008 R2.
However, if there’s no problem with the setup file, please check that if there is third-party software such as anti-virus software on your computer blocking the process of SQL Server installation. In addition, make sure that you choose ‘Run as administrator’
to launch the setup and configure SQL Server service accounts appropriately with administrator permission during the installation.
For more details about this error, please review the following similar thread.
http://answers.flyppdevportal.com/categories/sqlserver/sqlsetupandupgrade.aspx?ID=ad794a97-09ae-4aae-9d68-0b06f9af3e16
Thanks,
Lydia Zhang

SQL Server Security Logins vs. Databases Security Users

Similar Messages

Maybe you are looking for