Disable 'sa' login on SQL 2008 ?

Hello, what are the downsides/risks in disabling 'sa' login within SQL 2008 ? Like potential issues on system backend processes, reboots, patching, etc...? Noticed it can be disabled and still continue to own & run SQL Agent jobs I believe
which sounds like a good thing.
Thanks in advanced.

Well. The permission for changing both is the same.
But "locking a user out" is just not what one would expect to be on purpose.
So I would highly recommend using the appropriate techniques to avoid confusion and errors coming from them. Always go for the most stable method.
Here I just happen to have published a short blog post on disabled/denied Logins, which somehow is related to your question:
DISABLE and DENY LOGIN, DENY USER & Effect on Impersonation and Permissions
Andreas Wolter (Blog |
Twitter)
MCM - Microsoft Certified Master SQL Server 2008
MCSM - Microsoft Certified Solutions Master Data Platform, SQL Server 2012
www.andreas-wolter.com |
www.SarpedonQualityLab.com

Similar Messages

MS SQL 2008 R2 Named instance: Login failed. Microsoft SQL server, Error: 18452) - Tryig to access using the FQDN assigned for the backup network card.

Hi,
I have a windows 2008 R2 Enterprise servers with standalone MS-SQL 2008 R2 named instance. The server is having two networks, once production and the second for backup. The server FQDN is resolving to the production IP. The backup NIC
DNS dynamic update is disabled and an "A" record is registered with the dns. While trying to connect to the instance using the management studio:
Successfuly able to connect using the instance name, the production hostname, production IP and backup IP.
but while trying to connect to the insance using the backup hostname getting the below error:
"Login failed. The login is an untrusted domain and cannot be used with windows authentication. (Microsoft SQL server, Error: 18452) "
This is required for the backup tool to get connected using the backup FQDN of the server.
Should I need to create a host name alias, request you to kindly assist me with the best recommedation to fix this.
http://blogs.msdn.com/b/dbrowne/archive/2012/05/21/how-to-add-a-hostname-alias-for-a-sql-server-instance.aspx

Hi,
It might be a kerberos issue. Check that there are valid SPN's registered using the setspn utility - http://technet.microsoft.com/en-us/library/cc731241.aspx
Thanks, Andrew
My blog...

Install Active Directory Domain Controller on Windows server 2008 enterprise, dont login on Sql Server 2008 R2

I install Active Directory Domain Controller on Windows server 2008 enterprise and dont login on Sql Server 2008 R2. Before install ADDC, I have logon SQL Server 2008r2 Success, After when i install ADDC is don't logon on SQL Server 2008r2 -->not success.
I have uninstalled ADDC but i still can't login on SQL server 2008r2.
please help me. it is very very disaster!
I think is loss account SQL server 2008r2!

Hello,
I stronly recommend you post the detail error message to us while you try to connect to SQL Server instance, it's useful for us to do further investigation.
Microsoft recommends that you do not install SQL Server 2008 R2 on a domain controller, there are some limitations:
You cannot run SQL Server services on a domain controller under a local service account or a network service account.
After SQL Server is installed on a computer, you cannot change the computer from a domain member to a domain controller. You must uninstall SQL Server before you change the host computer to a domain controller.
After SQL Server is installed on a computer, you cannot change the computer from a domain controller to a domain member. You must uninstall SQL Server before you change the host computer to a domain member.
SQL Server failover cluster instances are not supported where cluster nodes are domain controllers.
SQL Server Setup cannot create security groups or provision SQL Server service accounts on a read-only domain controller. In this scenario, Setup will fail.
On Windows Server 2003, SQL Server services can run under a domain account or a local system account.
So, I would suggest you try to open up Windows Services list and changed the account for SQL Server service.
Regards,
Elvis Long
TechNet Community Support

Installation fails W.Server 2008, Sql 2008 R2

Hi,
I need help ASAP please !!
Im trying to install BPC 75 SP03 MS version, in Windows Server 2008, SQL 2008 R2 but I cant manage to get the installation done, an error is shown up and I cant go further even though I applied 2 different workarounds.
Please suggest something
Error:
15/09/2011 12:57:55 p.m. OlapVersion : : OLAP_VERSION_2005
15/09/2011 12:57:55 p.m. GetTimeMembers : End
15/09/2011 12:57:56 p.m. Validate base member of Time dimension. : Succeed
15/09/2011 12:57:56 p.m. Get information of ApShel from SQL. : Succeed
15/09/2011 12:57:56 p.m. Check Insight : Insight disabled.
15/09/2011 12:58:00 p.m. Connect to Olap server(BPCDEMO) :
15/09/2011 12:58:01 p.m. Step 2 : -- Create Olap DB.
15/09/2011 12:58:01 p.m. Step 3 : -- Create DataSource.
15/09/2011 12:58:02 p.m. Step 3 : -- Create DataSource View.
15/09/2011 12:58:02 p.m. Step 4 : -- Create Dimensions.
15/09/2011 12:58:11 p.m. -- C_ACCT : Fail
15/09/2011 12:58:11 p.m. CreateNewOlapDB : True - Message:OLE DB error: OLE DB or ODBC error.
Errors in the high-level relational engine. A connection could not be made to the data source with the DataSourceID of 'AppDef', Name of 'AppDef'.
Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'ApShell', Name of 'C_ACCT' was being processed.
Server: The operation has been cancelled.
15/09/2011 12:58:11 p.m. Create ApShell : ========== END ==========
Workaround 1.
Open up SQL Management Studio
2. Go to Security > Logins > NT AUTHORITYLOCAL SERVICE
3. Right click > Properties
4. In the User Mapping section tick ApShell
5. In the bottom section of the screen, tick db_datareader
Workaround 2.
Install SQLSERVER2008_ASAMO10, SQLServer2005_ADOMD_x64 and SQLServer2008_ADOMD10_x64
Please help
Velázquez

Hi there,
Support for SQL Server 2008 R2 only became available in BPC MS 7.5 SP04
See [Note 1512045 - Planning and Consolidation 75M SP04 Central Note|https://service.sap.com/sap/support/notes/1512045]
Can you access and process the cubes/dims in SSAS?
Thanks,
John

Cannot see new SQL 2008 R2 Express instance on Small Business Server 2011!

Hi,
As it is stated on the subject line, I'm having a problem after I did a new install of SQL 2008 R2 Express and put a new instance on SBS 2011.
I'm developing a new program using SQL 2008 in C# and VB.Net. I have SQL 2008 R2 Express installed on my computer called "MSQL8R2EDATA" on my PC. Now I need to deploy it on SBS 2011 so I can do some testing on other workstations.
I'm currently running Windows 7, 64 bit, and it's named STEVE-PC. The SBS 2011 is named SERVER1, and it's 64 bit as well.
After installation on SERVER1 (SBS 2011), I then fired up SQL Server Configuration Manager and enabled Named Pipes, TCP/IP, and VIA.
After I've completed the SQL Configuration on SERVER1, I went back on my PC (STEVE-PC) and I tried to use Management Studio to connect to the new instance MSQL8R2EDATA on SBS 2011, only problem is, I only see the computer name, not the new instance
I've installed.
Back on SBS 2011 (SERVER1), I've verified that all the protocols are enabled, and the SQL Server Browser is automatically loaded and currently running, as well the MSQL8R2EDATA instance is automatically loaded and running, yet I still cannot see
it from my PC (STEVE-PC). I even switched from dynamic ports to a static port of 64719 (that was what the MSQL8R2EDATA was listening on that port when it was dynamic), and then added new rules to the Windows Firewall for program of the SQLSERVR.EXE, and
for UDP and TCP for port 64719 to "Allow All Connections" for Domain, Private, and Public; yet I still cannot connect SERVER1\MSQL8R2EDATA. I even disabled the firewall and then trying to connect once again to SBS 2001 and it still fails.
In case you're wondering, I left it on port 64719 since there are other active SQL Servers on SBS 2011 (SharePoint, SBSMonitoring, and ACT7).
Interestingly, when I run Management Studio on SBS 2011, I can see STEVE-PC\MSQL8R2EDATA and I'm able to log in and connect to it.
So what's going on here?!? Why am I able to connect to STEVE-PC which is Windows 7 64 from SBS 2011 (SERVER1), but I cannot connect from my computer to that instance on SBS 2011??
I really could use some big time help on this.
EDIT: Sorry for the confusion, but on the Windows Firewall (WF.msc), I did add new rules for incoming connections on:
Program incoming connections to SQLSERVR.EXE
TCP Port 64719
UDP Port 64719
EDIT: To further assist, I have Management Studio installed on the SBS 2011, and I can locally log in and connect to the MSQL8R2DATA on SERVER1 with success. I even tried tcp:SERVER1\MSQL8R2DATA and again it is successful log-in and connection.
Thanks in advance!
Steve

Hi,
Thanks for the response, but I have a question:
Installing SQL Express or SQL Server is not recommended on SBS
2011 because it is a DC, however technically it will work.
I'm a newbie when it comes to SBS 2011 and I'm taking a crash course on the subject. Can you explain to me what you mean by "DC"? Also, why
isn't recommended to install a new instance on SBS 2011?
As I also stated, I've added "New Rules" to the Windows Firewall to allow incoming connections on port 64719 for both TCP and UDP, and I also allowed incoming connections for SQLSERVR.EXE but no joy to connect to the SERVER1\MSQL8R2EDATA.
And yes, I can log-in and connect locally on SERVER1 using Management Studio with success. I even used tcp:SERVER1\MSQL8R2EDATA with the same success. It's my workstation STEVE-PC that fails. If that fails, then the rest of the workstations are going to fail.
Are you suggesting that I put the SQL Server 2008 Express on another workstation and just allow to to be
accessed that way?

Security issue in SQL Server replication in SQL 2008 Express edition

Hi,
I am trying to do merge replication through web sync in SQL server 2008 express edition. i tried the merge replication using RMO with C# code but no luck. i am getting the security related error.
my Publisher and distribution are on SQL server 2008 R2 Standard edition. machine name "Printserver",
I created subscription on SQL server 2008 express edition.
I hosted the web service for merge syncronization on another machine named "ANUJVMWIN7".
I installed SSL cerificate on all the machine (server, hosted server and subscriber machine.)
here is the error description.
The upload message to be sent to Publisher ‘PRINTSERVER’ is being generated
The merge process is using Exchange ID ’0B23EBE2-D502-4D92-A9A1-88B8F738CFFC’ for this web synchronization session.
A security error occurred
A security error occurred
The Merge Agent could not connect to the URL ‘https://ANUJVMWIN7.prospecta.in/WebSyncTest/replisapi.dll’ during Web synchronization. Please verify that the URL, Internet login credentials and proxy server settings are correct and that the Web server is reachable.
The same process i tested with the SQL server 2008 standard edition and all the things are working fine. i could able to merge the databases but no luck with SQL 2008 express edition.
Please help.
Thanks
Anuj Sharma
Thanks Anuj Sharma Software Engineer

Hi Brandon,
I am not using self signed certificate. I installed SSL certificate provided by RapidSSL CA. This certificate is installed on my publisher machine ("Printserver"),
web hosting machine ("ANUJVMWIN7") and my subscriber machine as well.
Here are the certificate details which i installed on each machine.
Thanks
Anuj Sharma
Thanks Anuj Sharma Software Engineer

Problems install SCCM 2012 with remote sql 2008 r2 sp2

I am having issues installing sccm 2012 on a remote sql 2008 r2 sp2 server on a seperate instance.
I get the error "The network path was not found"
if i point it at the primary instance it will let me continue but i cannot install sccm into that instance.
I have turned off dynamic ports and set a static port but I do not see where i can enter that in the installer.
I cannot seem to verify is the ssb port is working correctly or not.
my account is local admin on both servers and a sql sysadm.
There is no firewall between servers.
Any suggestions?
Regards
Don

SPN is setup to AUTO register and is working. remote sql is not a cluster. Windows firewall on both servers is disabled. Sql browser is enabled and started. we have a group for system center that contains site servers and this group
is in the local admin of both servers and sysadm inside of sql server.
Why we are consolidating all or our lesser sql servers into a larger one.
Snipt of the log.
12/12/2012 2:57:37 PM: ConfigMgrSetupWizard Error: 1 : Exception message: [The network path was not found.
], Exception details: [System.IO.IOException: The network path was not found.
Server stack trace:
at Microsoft.Win32.RegistryKey.Win32ErrorStatic(Int32 errorCode, String str)
at Microsoft.Win32.RegistryKey.OpenRemoteBaseKey(RegistryHive hKey, String machineName)
at Microsoft.SystemCenter.ConfigMgr.Setup.DatabaseUtility.GetSqlConnection(String databaseName, String serverName, Boolean encrypt)
at Microsoft.SystemCenter.ConfigMgr.Setup.DatabaseUtility.CheckSqlConnection(String serverName, String instanceName)
at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(Message reqMsg, Boolean bProxyCase)
at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(Object NotUsed, MessageData& msgData)
at Microsoft.SystemCenter.ConfigMgr.Setup.CheckSqlAsync.EndInvoke(IAsyncResult result)
at Microsoft.SystemCenter.ConfigMgr.Setup.DatabasePage.ValidatePage()
at Microsoft.SystemCenter.ConfigMgr.SetupFramework.WizardForm.ActivatePage(String pageId, Boolean goingNext)
at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
at System.Windows.Controls.Button.OnClick()
at System.Windows.Controls.Primitives.ButtonBase.OnMouseLeftButtonUp(MouseButtonEventArgs e)
at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
at System.Windows.UIElement.ReRaiseEventAs(DependencyObject sender, RoutedEventArgs args, RoutedEvent newEvent)
at System.Windows.UIElement.OnMouseUpThunk(Object sender, MouseButtonEventArgs e)
at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
at System.Windows.UIElement.RaiseEvent(RoutedEventArgs args, Boolean trusted)
at System.Windows.Input.InputManager.ProcessStagingArea()
at System.Windows.Input.InputManager.ProcessInput(InputEventArgs input)
at System.Windows.Input.InputProviderSite.ReportInput(InputReport inputReport)
at System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr hwnd, InputMode mode, Int32 timestamp, RawMouseActions actions, Int32 x, Int32 y, Int32 wheel)
at System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at System.Windows.Interop.HwndSource.InputFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Boolean isSingleParameter)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Boolean isSingleParameter, Delegate catchHandler)].
12/12/2012 3:01:42 PM: ConfigMgrSetupWizard Information: 1 : Creating SQL connection to database ADMIN\master on server YSQL030.srf.local.
12/12/2012 3:01:42 PM: ConfigMgrSetupWizard Error: 1 : Exception message: [The network path was not found.
], Exception details: [System.IO.IOException: The network path was not found.

Sharepoint 2010 SQl 2008 r2 Reporting Services Integrated with Claims

i have a 4 server sharepoint 2010 farm all servers are windows 2008 r2 x64
two severs are sharepoint app/wfe servers
one server is SQL sharepoint content db server sql 2008 r2 enterprise
one server is SQL Claims Provider DB and reporting services on SQL 2008 r2
the site is behind a forefront tmg proxy firewall for both internal and external users and both locations are producing the same results.
the web application i am having an issue with consists of a primary web app claims enabled web app that only has NTLM enabled, with an extended extranet webapp that supports claims and NTLM.
there is surrently a site collection that has been configured for reporting services when i log into the site as a SQL Claims user i am able to run the reportbuilder as a content type using the New Report builder report content type from a library on
this site. Reportbuilder launches and i am once gain prompted to login i login with the same credentials i used to log into the site and reportbuilder opens up and then i am able to open datasourceas and reports.
When i log in to the same site collection as a domain user i am able to log in to the site and launch reportbuilder. When reportbuilder opens up i am prompted to log in, i insert my domain\username and password and nothing happens the login prompt appears again
blank on the back end it throws the following exceptions
1. Password check on 'username' generated exception: 'System.ServiceModel.FaultException`1[Microsoft.IdentityModel.Tokens.FailedAuthenticationException]: The security token username and password could not be validated. (Fault Detail is equal to Microsoft.IdentityModel.Tokens.FailedAuthenticationException:
The security token username and password could not be validated.).'.
2.An exception occurred when trying to issue security token: The security token username and password could not be validated.
any thoughts on where i should begin troubleshooting this.

I think i am getting close i am now seeing a new error it seems that the sp farm account is unable my domain account when launching reportbuilder.
vent code: 4006
Event message: Membership credential verification failed.
Event time: 4/6/2014 10:59:05 AM
Event time (UTC): 4/6/2014 2:59:05 PM
Event ID: 7640af98dab846829f78e7d74a4e1e8a
Event sequence: 9
Event occurrence: 8
Event detail code: 0
Application information:
    Application domain: /LM/W3SVC/2/ROOT/SecurityTokenServiceApplication-1-130412687342754349
    Trust level: Full
    Application Virtual Path: /SecurityTokenServiceApplication
    Application Path: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\WebServices\SecurityToken\
    Machine name: (SP WFE MACHINE NAME)
Process information:
    Process ID: 8044
    Process name: w3wp.exe
    Account name: (SP FARM ACCOUNT)
Request information:
    Request URL:
    Request path:
    User host address:
    User:
    Is authenticated: False
    Authentication Type:
    Thread account name: (SP FARM ACCOUNT)
Name to authenticate: (doamin account launching reportbuilder)
Custom event details:

Sql 2008 express not listening on port 1433

I installed sql 2008 express on 2008R2 but it is not listening on port 1433.
I check configuration for tcp and enabled that already. also started sql browser service.
any idea?

I installed sql 2008 express on 2008R2 but it is not listening on port 1433.
I check configuration for tcp and enabled that already. also started sql browser service.
any idea?
by default SQL Server Express does not enable Remote Connections.
Could you check the following:
1) check that the SQL Express is running (SQL Server Configuration Tool)
2) log onto the box containing the SQL Server and try to connect with SSMS to the SQL Express instance. Try tcp/ip and/or shared memory to connect.
if you can successfully login check that the SQL Server does allow Remote Connections
3) Firewall does not block incoming connections
4) does the DNS server name resolve to the correct ip address of the SQL Server ?

Downgrade SQL 2008 R2 Enterprise Cluster to SQL 2008 R2 Standard Cluster

Hi
While I found several information about Downgrading an 2008 R2 Enterprise to 2008 R2 Standard edition (even here in this forum) I didn't found much information doing this when it's a clustered SQL Server. Is there anything I've to be aware of? My solution
I've in mind is:
1.) Stop SQL Service
2.) Move all database (users and system) to another location
3.) Uninstall existing Enterprise nodes/instances of both servers
4.) Install the SQL 2008 R2 Standard on both nodes. Use same folders for databases as in the original installation. Use also all other configs as the original one (instance/cluster name, network ressource name,...)
5.) Stop SQL Service
6.) Remove original user and system databases back to their original folder. Replace system databases of new installation with the original ones.
Should this work or not?

Hi,
I guess you already know it and you are follwoing correct process.But what plans you have for enterprise features which were used in Ent edition and will not be present in standard edition.did you made any alternatives for it.
Did you checked your application code or built in jobs(which used enterprise features) if so good to go then.
For features suported by various edition look at below link
http://msdn.microsoft.com/en-us/library/cc645993(v=sql.105).aspx
For downgrading this link will be helpful
http://www.mssqltips.com/sqlservertip/3079/downgrade-from-sql-server-enterprise-edition-to-standard-edition/
Please make sure you migrate login and jobs either with script method or use below link
http://support.microsoft.com/kb/918992/en-gb
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

SQL 2008 R2 Management Tools Install Fails - The specified account already exists

Hello,
The installation SQL 2008 R2 Management Tools on a Windows 7 workstation fails with the error, The specified account already exists.
Below is the Summary Log.
Thanks.
Paul
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):           -2068052700
Exit facility code:            1212
Exit error code:               1316
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-20 09:02:16
End time:                      2014-10-20 09:05:57
Requested action:              Install
Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141020_085102\sqlncli_Cpu64_1.log
Exception help link:
http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.1600.1
Machine Properties:
Machine name:                  WS287
Machine processor count:       4
OS version:                    Windows 7
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:
\\SRVDIA18\MSSQL2008R2Install\x64\setup\
Installation edition:          STANDARD
User Input Settings:
ACTION:                        Install
ADDCURRENTUSERASSQLADMIN:      False
AGTSVCACCOUNT:                 <empty>
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:         Disabled
CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141020_085102\ConfigurationFile.ini
CUSOURCE:
ENABLERANU:                    False
ENU:                           True
ERRORREPORTING:                False
FARMACCOUNT:                   <empty>
FARMADMINPORT:                 0
FARMPASSWORD:                  *****
FEATURES:                      SSMS,ADV_SSMS
FILESTREAMLEVEL:               0
FILESTREAMSHARENAME:           <empty>
FTSVCACCOUNT:                  <empty>
FTSVCPASSWORD:                 *****
HELP:                          False
IACCEPTSQLSERVERLICENSETERMS: False
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:                    <empty>
INSTANCENAME:                  <empty>
ISSVCACCOUNT:                  NT AUTHORITY\NetworkService
ISSVCPASSWORD:                 *****
ISSVCSTARTUPTYPE:              Automatic
NPENABLED:                     0
PASSPHRASE:                    *****
PCUSOURCE:
PID:                           *****
QUIET:                         False
QUIETSIMPLE:                   False
ROLE:                          <empty>
RSINSTALLMODE:                 FilesOnlyMode
RSSVCACCOUNT:                  <empty>
RSSVCPASSWORD:                 *****
RSSVCSTARTUPTYPE:              Automatic
SAPWD:                         *****
SECURITYMODE:                  <empty>
SQLBACKUPDIR:                  <empty>
SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT:                 <empty>
SQLSVCPASSWORD:                *****
SQLSVCSTARTUPTYPE:             Automatic
SQLSYSADMINACCOUNTS:           <empty>
SQLTEMPDBDIR:                  <empty>
SQLTEMPDBLOGDIR:               <empty>
SQLUSERDBDIR:                  <empty>
SQLUSERDBLOGDIR:               <empty>
SQMREPORTING:                  False
TCPENABLED:                    0
UIMODE:                        Normal
X86:                           False
Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141020_085102\ConfigurationFile.ini
Detailed results:
Feature:                       Management Tools - Complete
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Management Tools - Basic
Status:                        Failed: see logs for details
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\20141020_085102\SystemConfigurationCheck_Report.htm
The specified account already exists

There is definitely more amusing endeavours in this world, than trying to understand why an SQL Server install failed. The log files are verbose - but somehow the real information about what went wrong seems to be hiding. Never have proverb about not being
able to see the forest for all the trees felt more appropriate.
Nevertheless, this is where things go sour:
MSI (s) (F4:EC) [09:04:15:744]: Resolving source.
MSI (s) (F4:EC) [09:04:15:744]: Resolving source to launched-from source.
MSI (s) (F4:EC) [09:04:15:744]: Setting launched-from source as last-used.
MSI (s) (F4:EC) [09:04:15:744]: PROPERTY CHANGE: Adding SourceDir property. Its value is '\\server\MSSQL2008R2Install\1033_ENU_LP\x64\setup\x64\'.
MSI (s) (F4:EC) [09:04:15:744]: PROPERTY CHANGE: Adding SOURCEDIR property. Its value is '\\server\MSSQL2008R2Install\1033_ENU_LP\x64\setup\x64\'.
MSI (s) (F4:EC) [09:04:15:744]: PROPERTY CHANGE: Adding SourcedirProduct property. Its value is '{2180B33F-3225-423E-BBC1-7798CFD3CD1F}'.
MSI (s) (F4:EC) [09:04:15:744]: SOURCEDIR ==> \\server\MSSQL2008R2Install\1033_ENU_LP\x64\setup\x64\
MSI (s) (F4:EC) [09:04:15:744]: SOURCEDIR product ==> {2180B33F-3225-423E-BBC1-7798CFD3CD1F}
MSI (s) (F4:EC) [09:04:15:744]: SECREPAIR: CryptAcquireContext succeeded
MSI (s) (F4:EC) [09:04:15:744]: Determining source type
MSI (s) (F4:EC) [09:04:15:744]: Note: 1: 2203 2: \\server\MSSQL2008R2Install\1033_ENU_LP\x64\setup\x64\SQL ODBC Native Client 10 - 64bit.msi 3: -2147287038
MSI (s) (F4:EC) [09:04:15:744]: Note: 1: 1316 2: \\server\MSSQL2008R2Install\1033_ENU_LP\x64\setup\x64\SQL ODBC Native Client 10 - 64bit.msi
MSI (s) (F4:EC) [09:04:15:744]: SECREPAIR: Error determining package source type
MSI (s) (F4:EC) [09:04:15:744]: SECUREREPAIR: SecureRepair Failed. Error code: 524F91D34B8
MSI (s) (F4:EC) [09:04:40:775]: Product: Microsoft SQL Server 2008 R2 Native Client -- Error 1316. The specified account already exists.
What account? I supposed you have already asked yourself that and just shaken your head.
But there is another error code 2203, NET HELPMSG 2203 says "The password parameter is invalid." And I note that the source is apparently on a share.
So where is my guess: the MSI installer - which runs as a service, somehow does not have permissions to read the installation from the share. Or is trying to log on to the share with your username/password? No, I don't know, I am just speculating widely.
But my advice would be to copy the installation directory from the share to a local disk.
Maybe that CryptAcquireContext is significant as well - I don't know.
Oh, wait, here is something just before the section above in the log:
MSI (s) (F4:EC) [09:04:15:729]: Note: 1: 2205 2: 3: Environment
MSI (s) (F4:EC) [09:04:15:729]: Note: 1: 2228 2: 3: Environment 4: SELECT `Name`,`Value` FROM `Environment`,`Component` WHERE `Component_`=`Component` AND (`Component`.`Action` = 1 OR `Component`.`Action` = 2)
Action start 9:04:15: WriteEnvironmentStrings.
2205 is "The logon processor did not add the message alias." I see that in a successful log that I have, so that is probably benign. But 2228 seems to be
"There are too many names in the user accounts database."
Exactly what that means, I have no clue, but it could be a Windows problem.
Erland Sommarskog, SQL Server MVP, [email protected]

SQL 2008 R2 SSRS Security Problems

Hello,
We have SSRS running on SQL 2008 R2, using a Windows 2008 R2 Standard Server. When we setup Systems users and also roles such as Browser all that goes through. The issue is, the security does not take effect on the system.
For example <domainuser>\<domainuser> can login to the site and traverse ANY folders, even ones that have folder security set, not inheritening permissions. I've came to realize it seems the Windows Group "Users" applies to who can
get into the server. If we do not have domain users or specific logins in the Windows group you just keep getting a popup for login going to the main SSRS home.
I do not the behavior concerning windows group by design but at any rate adding all domain users we then perceive the folder and site settings apply to folders and report access on the Report manager. It does not simply work. Any users can get into
the admin folder (Which has only 3-4 people with access) and run anything. It is as if the SSRS permissions simply do not work. I've tried using a server account and also Network Service (Which it is set to now).
Has anyone ran into this issue and have any ideas how to resolve it? I understand the BROWSER role has access to "View Folders" but I see no granular other than folder and item permissions being set to not allow specific folders to be accessed.
I appreciate your time,
KT

Hi KT,
Per my understanding that you have set the security in the report server but the some of the user still get some extra permission, right?
Generally, Reporting Services uses role-based security to grant user access to a report server, and there are two types of roles:
Item-level roles and System-level roles.
By default, Reporting Services has assigned both System Administrator roles (System-level) and the Content Manager role (Item-level) to the BUILTIN\Administrators group. So, the user that is in the local administrators group will
perform the role as ”Content Manager” without extra settings, you can check if the users who have extra permissions was in this group，if the domain user in this group, please try to remove it and add it in the Local Users and Groups other
then Administrators group :
You have menioned that the user shouldn't have permission to the Admin folder but now they have access.
Please check the security of the admin folder to make sure the users were not in the list of the groups and users as below:
If the issue still exists, please check all the folder one by one to make sure this is not any inheried problem and re-set the security.
Similar thread for your reference:
How to remove the DELETE item from the Running report context
list box
If you still have any question, please feel free to ask.
Regards
Vicky Liu
Vicky Liu
TechNet Community Support

Report Retrieval Times in BPCv7 SP3 using SQL 2008

General Information: We are a two server environment, one WEB and one SQL, using SQL 2008. We are using BPC v7 SP3. In our devlopment environment, we have selected a handful of reports to use as a benchmark against our production version of Outlooksoft version 4.
Problem: The benchmark reports are taking longer to retrieve in BPC v7 then they are in Outlooksoft version 4 SP9. We have stripped out the dimension formulas, unchecked the INAPP for each dimension property, reset the compatability level in SQL, and removed all data from the facttables in BPC version 7. The initial pull of the report seems to take almost 3 times as long in BPC v7 than in Outlooksoft version 4. Subsequent pulls, changing the date, take less than 15 seconds for the same report.
We are at a stand still trying to figure out why we are experiencing such lengthy retrieval times in the initial pull of a report in BPC version 7.
Additional Info: In our development environment of BPC v7, we currently have only 4 users set up to test. Our Outlooksoft version 4 has a total of 186 users. I don't know the maximium concurrent users we may have at one time.
Question: We are wondering if any other users are experiencing the same issue when they try and retrieve data from a report in BPC version 7? Please share your insight to this problem.

Hi Irene,
It is a big diference of design between 4.x and 7.x.
Into 4.x when you pull data into a report actually you are using PTS from client and you already have the connection and everything from client direct to OLAP server.
In 7.x all the request are going first to application server and the application server is the one taking the data from OLAP and after that data is sent to client.
So first time when you are doing refresh of report into application server it is necessary to create instances for all COM+ components necessary connection etc...and in that case the reports is taking longer.
When you are doing other refresh with the same reports or with other the time for refresh is much faster because already the COM+ instances were created and in this case the reports should be faster than v 4.x
So I suggest to try the follow test.
after login with BPC client just open first a small reports which you know is not taking too long.
After that open your big report. It should retrieve data faster than 4.x or almost the same time.
Also make sure you have all the settings done from Tunning Guide for BPC 5.x ( these settings can be applied also for 7.X)
to be sure that your 7.0 environment is working properly. This tunning guide can be found into bpx/sdn HTG section.
I hope this will help.
Regards
Sorin Radulescu

SQL 2008 R2 Install problems

Good day all.
About a month ago I cloned a virtual server "2008 R2 Ent" as our new SQL server. Upon installation of the "Microsoft SQL 2008 Ent
R2" using "run as administrator. I receive the following install error:
The following error has occurred:
Updating permission setting for folder 'E:\Program Files\Microsoft SQL Server\100\DTS\' failed. The folder permission setting were supposed to be set to 'D:(A;OICI;FA;;;BA)(A;OICI;FA;;;SY)(A;OICI;FA;;;CO)(A;OICI;0x1200a9;;;BU)'.
Click 'Retry' to retry the failed action, or click 'Cancel' to cancel this action and continue setup.
For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.1600.1&EvtType=0x88792597%25400xD69AB41D
I have performed the following troubleshooting steps:
-Researched all forums with related issues. Attempted all findings.
-Attempted limited install.
-Attempted install to new directory.
-Downloaded another copy of SQL image.
-Tried install from CMD line.
-Cloned another server and attempted a fresh install.
Any thoughts would be greatly appreciated.
Tony Schnellbach

Chunsong, Below is the content from th summary.txt file. Thanks
Overall summary:
  Final result: Pending
  Exit code (Decimal): 0
  Exit message: Pending
  Start time: 2011-03-22 10:06:12
  End time: 2011-03-22 10:11:04
  Requested action: Install
Machine Properties:
  Machine name: ITS-COLO-SQL2
  Machine processor count: 1
  OS version: Windows Server 2008 R2
  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
Package properties:
  Description: SQL Server Database Services 2008 R2
  ProductName: SQL Server 2008 R2
  Type: RTM
  Version: 10
  SPLevel: 0
  Installation location: E:\Installs\SQLFULL_ENU-- first\x64\setup\
  Installation edition: ENTERPRISE
User Input Settings:
  ACTION: Install
  ADDCURRENTUSERASSQLADMIN: True
  AGTSVCACCOUNT: SrvAcctSQL
  AGTSVCPASSWORD: *****
  AGTSVCSTARTUPTYPE: Manual
  ASBACKUPDIR: E:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Backup
  ASCOLLATION: Latin1_General_CI_AS
  ASCONFIGDIR: E:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Config
  ASDATADIR: E:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Data
  ASDOMAINGROUP: <empty>
  ASLOGDIR: E:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Log
  ASPROVIDERMSOLAP: 1
  ASSVCACCOUNT: SrvAcctSQL
  ASSVCPASSWORD: *****
  ASSVCSTARTUPTYPE: Automatic
  ASSYSADMINACCOUNTS: INFINITYBUSINES\SchnellbachAJ,INFINITYBUSINES\MerrittJM
  ASTEMPDIR: E:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Temp
  BROWSERSVCSTARTUPTYPE: Disabled
  CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110322_100253\ConfigurationFile.ini
  CUSOURCE:
  ENABLERANU: False
  ENU: True
  ERRORREPORTING: True
  FARMACCOUNT: <empty>
  FARMADMINPORT: 0
  FARMPASSWORD: *****
  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
  IACCEPTSQLSERVERLICENSETERMS: False
  INDICATEPROGRESS: False
  INSTALLSHAREDDIR: E:\Program Files\Microsoft SQL Server\
  INSTALLSHAREDWOWDIR: E:\Program Files (x86)\Microsoft SQL Server\
  INSTALLSQLDATADIR: <empty>
  INSTANCEDIR: E:\Program Files\Microsoft SQL Server\
  INSTANCEID: MSSQLSERVER
  INSTANCENAME: MSSQLSERVER
  ISSVCACCOUNT: NT AUTHORITY\NetworkService
  ISSVCPASSWORD: *****
  ISSVCSTARTUPTYPE: Automatic
  NPENABLED: 0
  PASSPHRASE: *****
  PCUSOURCE:
  PID: *****
  QUIET: False
  QUIETSIMPLE: False
  ROLE: AllFeatures_WithDefaults
  RSINSTALLMODE: DefaultNativeMode
  RSSVCACCOUNT: NT AUTHORITY\NETWORK SERVICE
  RSSVCPASSWORD: *****
  RSSVCSTARTUPTYPE: Automatic
  SAPWD: *****
  SECURITYMODE: SQL
  SQLBACKUPDIR: <empty>
  SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
  SQLSVCACCOUNT: NT AUTHORITY\NETWORK SERVICE
  SQLSVCPASSWORD: *****
  SQLSVCSTARTUPTYPE: Automatic
  SQLSYSADMINACCOUNTS: INFINITYBUSINES\SchnellbachAJ,INFINITYBUSINES\MerrittJM
  SQLTEMPDBDIR: <empty>
  SQLTEMPDBLOGDIR: <empty>
  SQLUSERDBDIR: <empty>
  SQLUSERDBLOGDIR: <empty>
  SQMREPORTING: True
  TCPENABLED: 1
  UIMODE: Normal
  X86: False
  Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110322_100253\ConfigurationFile.ini
Detailed results:
  Feature: Database Engine Services
  Status: Failed: see logs for details
  MSI status: Passed
  Configuration status: Passed
  Feature: SQL Client Connectivity SDK
  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: Analysis Services
  Status: Failed: see logs for details
  MSI status: Passed
  Configuration status: Passed
  Feature: Reporting Services
  Status: Failed: see logs for details
  MSI status: Passed
  Configuration status: Passed
  Feature: Integration Services
  Status: Failed: see logs for details
  MSI status: Passed
  Configuration status: Passed
  Feature: Client Tools Connectivity
  Status: Failed: see logs for details
  MSI status: Passed
  Configuration status: Passed
  Feature: Management Tools - Complete
  Status: Failed: see logs for details
  MSI status: Passed
  Configuration status: Passed
  Feature: Management Tools - Basic
  Status: Failed: see logs for details
  MSI status: Passed
  Configuration status: Passed
  Feature: Client Tools SDK
  Status: Failed: see logs for details
  MSI status: Passed
  Configuration status: Passed
  Feature: Client Tools Backwards Compatibility
  Status: Failed: see logs for details
  MSI status: Passed
  Configuration status: Passed
  Feature: Business Intelligence Development Studio
  Status: Failed: see logs for details
  MSI status: Passed
  Configuration status: Passed
  Feature: SQL Server Books Online
  Status: Failed: see logs for details
  MSI status: Passed
  Configuration status: Passed
  Feature: Microsoft Sync Framework
  Status: Failed: see logs for details
  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\20110322_100253\SystemConfigurationCheck_Report.htm
Tony Schnellbach

Migrating SQL 2008 DB to SQL 2012 for SharePoint Farm

Our SharePoint 2013 Farm runs on ISCSI Disk on Windows 20008 R2 Standard SP1 Platform with SQL 2008 R2 Standard SP2.
Now we are planning to move this ISCSI Disk to another SQL 2012 Standard Platform and then upgrade the SQL 2008 Databse to SQL 2012. Can some one please let me know what challenges we might face during this implementation.

http://technet.microsoft.com/en-us/library/cc512723(v=office.14).aspx
It depends if you want to move all, or just some, of your databases to the new server. If you need to move all of them that link describes the process but in short;
Backup and restore all databases to the new server
Configure the server roles and logins for the SharePoint accounts on SQL
Create (or modify) your SQL alias to point to the new server

Disable 'sa' login on SQL 2008 ?

Similar Messages

Maybe you are looking for