Error During Installation Of Server 2005 When Typing Domain Account
Sep 23, 2010
I am installing SQL Server 2005 on a server (Windows Server Enterprise Edition 2003 SP2) that is not domain controller and on the screen "Service Account" I checked the box "Customize for each service account" and typed a domain account (it has permission to "logon as a service"), its password and domain, and when I click the "Next" button, I am getting the error below:"SQL Server Setup could not validate the service accounts. Either the service accounts have not been provided for all of the services being installed, or the specified username or password is incorrect. For each service, specify a valid username, password, and domain, or specify a built-in system account. "
I have a SQL Server 2005 Express edition instance set up on one server, and IIS on another server.
The SQL Server process account is a domain user account, which I have added to the local groups that SQL Server created during installation (I originally used a local user account instead of domain account; however, the problem occurs with both).
SQL Server runs fine, and if I set my IIS application pool identity to a domain admin, my web app can access the database and retrieve the data necessary.
However, I have a domain user account that I want to use to run the app pool and retrieve the data. The domain user account is added to the IIS_WPG group on the web server. On the database server, I have created a login for the account, as well as added it to the db_datareader role of the database that is used for the site.
However, the user is not able to connect to the SQL Server. I get the "Login failed for user <user account>" error in ASP.NET. I also tried connecting with SQL Server Management Studio, and I get the same error. I checked and the user has connect permission to the database server.
With admin accounts, there are no problems logging in, etc.
Any pointers are appreciated,
Thanks,
SA.
Edit: I was able to find out that the State is 11 for the error. According to http://blogs.msdn.com/sql_protocols/archive/2006/02/21/536201.aspx, this indicates "Valid login but server access failure." I am not sure how to resolve this.
During install of SQL Server 2005, we can of course use a domain account or the built-in system account for running the services. I lean toward domain for obvious reaons but would like to know a +/- to each option and why I'd choose one over the other and what consequences or limitations one may encounter if I choose one over the other.
I recenly installed SP1 on 2 servers. For some strange reason I am unable to run the SQL service or the SQL Agent service using the normal SQL service domain account. It has always worked and is currently running on the other server without a problem.
Hi there,BOL notes that in order for replication agents to run properly, theSQLServerAgent must run as a domain account which has privledges to loginto the other machines involved in replication (under "SecurityConsiderations" and elsewhere). This makes sense; however, I waswondering if there were any repercussions to using duplicate localaccounts to establish replication where a domain was not available.Anotherwords, create a local windows account "johndoe" on both machines(with the same password), grant that account access to SQL Server onboth machines, and then have SQL Server Agent run as "johndoe" on bothmachines. I do not feel this is an ideal solution but I havecircumstances under which I may not have a domain available; mypreliminary tests seem to work.Also, are there any similar considerations regarding the MSSQLSERVERservice, or can I always leave that as local system?Dave
I am running a SQL 2008r2 install while logged onto the server with a local admin account, not a domain account. I am specifying a domain account to run the SQL service. The install fails saying the service account credentials are invalid but I am 99.9% sure they are right.My theory - the local admin account running Setup cannot validate the service account creds against AD. Is it a requirement to run Setup while logged on with a domain account?
I have a situation that I have discovered in our QA database that I need to resolve. When I looked at the Activity Monitor for our server, I discovered that a process is running under a domain user account for one of our .Net applications. The problem is that that domain user account has not been created as a SQL login account on the server. I am trying to figure out how someone can log in to the database server with a domain user account that has not been added to SQL Server as a login account.
Does anyone have any insight on this? I don't like the idea of someone being able to create domain account that can access the database without me granting them specific access.
Hi, i tried to install MS SQL server 2000 in my XP system but during the setup service account installation, i tried to use a domain user account but it cannot validate my user name and password. I used my windows administrator logon account and password. Please help..thank you.
Bootstrapsetup.exe === MSI (c) (88:78) [10:24:26:828]: Resetting cached policy values MSI (c) (88:78) [10:24:26:828]: Machine policy value 'Debug' is 0 MSI (c) (88:78) [10:24:26:828]: ******* RunEngine: ******* Product: F:ServersSetupSqlRun_SQL.msi ******* Action: ******* CommandLine: ********** MSI (c) (88:78) [10:24:26:828]: Client-side and UI is none or basic: Running entire install on the server. MSI (c) (88:78) [10:24:26:828]: Grabbed execution mutex. MSI (c) (88:78) [10:24:26:828]: Cloaking enabled. MSI (c) (88:78) [10:24:26:828]: Attempting to enable all disabled priveleges before calling Install on Server MSI (c) (88:78) [10:24:26:828]: Incrementing counter to disable shutdown. Counter after increment: 0 MSI (s) (7C:94) [10:24:26:843]: Grabbed execution mutex. MSI (s) (7C:54) [10:24:26:843]: Resetting cached policy values MSI (s) (7C:54) [10:24:26:843]: Machine policy value 'Debug' is 0 MSI (s) (7C:54) [10:24:26:843]: ******* RunEngine: ******* Product: F:ServersSetupSqlRun_SQL.msi ******* Action: ******* CommandLine: ********** MSI (s) (7C:54) [10:24:26:843]: Note: 1: 2203 2: F:ServersSetupSqlRun_SQL.msi 3: -2147287010 MSI (s) (7C:54) [10:24:26:843]: MainEngineThread is returning 1620 MSI (c) (88:78) [10:24:26:843]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1 MSI (c) (88:78) [10:24:26:843]: MainEngineThread is returning 1620 === Verbose logging stopped: 3/27/2008 10:24:26 ===
SUMMARY.txt (C:Program FilesMicrosoft SQL Server90Setup BootstrapLOG) has follwing contents...
Microsoft SQL Server 2005 9.00.1399.06 ============================== OS Version : Microsoft Windows XP Professional Service Pack 2 (Build 2600) Time : Thu Mar 27 09:57:45 2008
Machine : ADITYA Product : Microsoft SQL Server Setup Support Files (English) Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_SQLSupport_1.log -------------------------------------------------------------------------------- Machine : ADITYA Product : Microsoft Office 2003 Web Components Product Version : 11.0.6558.0 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_OWC11_1.log -------------------------------------------------------------------------------- Machine : ADITYA Product : Microsoft SQL Server 2005 Backward compatibility Product Version : 8.05.1054 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_BackwardsCompat_1.log -------------------------------------------------------------------------------- Machine : ADITYA Product : MSXML 6.0 Parser Product Version : 6.00.3883.8 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_MSXML6_1.log -------------------------------------------------------------------------------- Machine : ADITYA Product : Microsoft SQL Server Setup Support Files (English) Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_SQLSupport_2.log -------------------------------------------------------------------------------- Machine : ADITYA Product : Microsoft SQL Server Native Client Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_SQLNCLI_1.log -------------------------------------------------------------------------------- Machine : ADITYA Product : Microsoft Office 2003 Web Components Product Version : 11.0.6558.0 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_OWC11_2.log -------------------------------------------------------------------------------- Machine : ADITYA Product : Microsoft SQL Server 2005 Backward compatibility Product Version : 8.05.1054 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_BackwardsCompat_2.log -------------------------------------------------------------------------------- Machine : ADITYA Product : MSXML 6.0 Parser Product Version : 6.00.3883.8 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_MSXML6_2.log -------------------------------------------------------------------------------- Machine : ADITYA Product : Microsoft SQL Server Setup Support Files (English) Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_SQLSupport_3.log -------------------------------------------------------------------------------- Machine : ADITYA Product : Microsoft SQL Server Native Client Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_SQLNCLI_2.log -------------------------------------------------------------------------------- Machine : ADITYA Product : Microsoft Office 2003 Web Components Product Version : 11.0.6558.0 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_OWC11_3.log -------------------------------------------------------------------------------- Machine : ADITYA Product : Microsoft SQL Server 2005 Backward compatibility Product Version : 8.05.1054 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_BackwardsCompat_3.log -------------------------------------------------------------------------------- Machine : ADITYA Product : MSXML 6.0 Parser Product Version : 6.00.3883.8 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_MSXML6_3.log -------------------------------------------------------------------------------- Machine : ADITYA Product : Microsoft SQL Server Setup Support Files (English) Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_SQLSupport_4.log -------------------------------------------------------------------------------- Machine : ADITYA Product : Microsoft Office 2003 Web Components Product Version : 11.0.6558.0 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_OWC11_4.log -------------------------------------------------------------------------------- Machine : ADITYA Product : Microsoft SQL Server 2005 Backward compatibility Product Version : 8.05.1054 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_BackwardsCompat_4.log -------------------------------------------------------------------------------- Machine : ADITYA Product : Microsoft SQL Server Setup Support Files (English) Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_SQLSupport_5.log -------------------------------------------------------------------------------- Machine : ADITYA Product : Microsoft SQL Server Native Client Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_SQLNCLI_3.log -------------------------------------------------------------------------------- Machine : ADITYA Product : Microsoft Office 2003 Web Components Product Version : 11.0.6558.0 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_OWC11_5.log -------------------------------------------------------------------------------- Machine : ADITYA Product : Microsoft SQL Server VSS Writer Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_SqlWriter_1.log -------------------------------------------------------------------------------- Machine : ADITYA Product : Microsoft SQL Server 2005 Backward compatibility Product Version : 8.05.1054 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_BackwardsCompat_5.log -------------------------------------------------------------------------------- Machine : ADITYA Product : MSXML 6.0 Parser Product Version : 6.00.3883.8 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_MSXML6_4.log -------------------------------------------------------------------------------- Machine : ADITYA Product : Microsoft SQL Server Setup Support Files (English) Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_SQLSupport_6.log -------------------------------------------------------------------------------- Machine : ADITYA Product : Microsoft SQL Server Native Client Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_SQLNCLI_4.log -------------------------------------------------------------------------------- Machine : ADITYA Product : Microsoft Visual Studio 2005 Premier Partner Edition - ENU Product Version : 8.0.50727.42 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_PPESku_1.log -------------------------------------------------------------------------------- Machine : ADITYA Product : Microsoft Office 2003 Web Components Product Version : 11.0.6558.0 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_OWC11_6.log -------------------------------------------------------------------------------- Machine : ADITYA Product : Microsoft SQL Server 2005 Books Online (English) Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_BOL_1.log -------------------------------------------------------------------------------- Machine : ADITYA Product : Microsoft SQL Server 2005 Backward compatibility Product Version : 8.05.1054 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_BackwardsCompat_6.log -------------------------------------------------------------------------------- Machine : ADITYA Product : MSXML 6.0 Parser Product Version : 6.00.3883.8 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_MSXML6_5.log -------------------------------------------------------------------------------- Machine : ADITYA Product : Microsoft SQL Server 2005 Integration Services Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_DTS.log -------------------------------------------------------------------------------- Machine : ADITYA Product : SQLXML4 Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_SQLXML4_1.log -------------------------------------------------------------------------------- Machine : ADITYA Product : SQLXML4 Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_SQLXML4_2.log -------------------------------------------------------------------------------- Machine : ADITYA Product : Microsoft SQL Server 2005 Analysis Services Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_AS.log -------------------------------------------------------------------------------- Machine : ADITYA Product : Microsoft SQL Server 2005 Notification Services Product Version : 9.00.1399.06 Install : Failed Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ADITYA_NS.log Error Number : 1602 --------------------------------------------------------------------------------
SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%Microsoft SQL Server90Setup BootstrapLOGSummary.txt.
I am trying to install the SQL Server 2005 SP2 but before the installation begins, the installation fails and it displays the following error "Hotfix.exe is not a valid Win32 application". I downloaded both the X64 version and the IA64 version. It didn't work in both cases.
I downloaded SQL Server Express 2005 SP2 from Microsoft site. I tried to install it but I get this error message: An Installation package for the product Microsoft SQL Server Native Client cannot be found. Try the installation again using a valid copy of the isntallation package 'sqlncli.msi'
What does this mean...can someone tell me where I can get a working copy of the SQL Server Express. I am installing it on tha WindowsXP laptop
I'm trying to install the Eval copy of SQL Server 2005 on a Win2k Server computer. The error message that
"The drop location is missing file(s) that allow setup to determine how a multi instance product should be installed. Setup cannot continue, please repair the drop and try again."
I am having an installation error for SQL Server Express SP2 installation: 2259. I have no idea how to fix it. The error log is given below. Please help.
Thank you
Microsoft SQL Server 2005 9.00.3042.00 ============================== OS Version : Professional (Build 6000) Time : Wed Jun 13 11:50:09 2007
Microsoft SQL Server 2005 9.00.3042.00 ============================== OS Version : Professional (Build 6000) Time : Wed Jun 13 11:50:09 2007
Computer-2 : Microsoft Internet Information Services (IIS) is either not installed or is disabled. IIS is required by some SQL Server features. Without IIS, some SQL Server features will not be available for installation. To install all SQL Server features, install IIS from Add or Remove Programs in Control Panel or enable the IIS service through the Control Panel if it is already installed, and then run SQL Server Setup again. For a list of features that depend on IIS, see Features Supported by Editions of SQL Server in Books Online. Machine : Computer-2 Product : Microsoft SQL Server Setup Support Files (English) Product Version : 9.00.3042.00 Install : Successful Log File : c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0007_Computer-2_SQLSupport_1.log -------------------------------------------------------------------------------- Machine : Computer-2 Product : Microsoft SQL Server Native Client Product Version : 9.00.3042.00 Install : Successful Log File : c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0007_Computer-2_SQLNCLI_1.log -------------------------------------------------------------------------------- Machine : Computer-2 Product : Microsoft SQL Server VSS Writer Product Version : 9.00.3042.00 Install : Successful Log File : c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0007_Computer-2_SqlWriter_1.log -------------------------------------------------------------------------------- Machine : Computer-2 Product : SQL Server Database Services Error : The installer has encountered an unexpected error. The error code is 2259. Database: Table(s) Update failed -------------------------------------------------------------------------------- Machine : Computer-2 Product : Microsoft SQL Server 2005 Product Version : 9.2.3042.00 Install : Failed Log File : c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0007_Computer-2_SQL.log Last Action : ValidateUpgrade Error String : The installer has encountered an unexpected error. The error code is 2259. Database: Table(s) Update failed Error Number : 2259 --------------------------------------------------------------------------------
i got this error msg when installing 2005 SQL Server components only on my system:
SQL Server Setup cannot continue because an earlier version of Office Web Components is installed on this computer. Uninstall Office Web Components, and then run installation again.
i could not find any info on this error. any ideas?
Doing webforms in ASP.NET and i have a connection string in the webconfig that connects to a locally created SQL Server user account.
This is fine however when i try to connect to a domain account created by the IT administrator for me, it wont work.
The User name and password he supplied are correct as i logged into my PC (Win 2000) using it to test it. However when i try to connect to this remote network domain account by changing my connection string it fails... anyone any ideas, or am i missing a subtlety of ASP.NET and SQL connectionstrings?
Heres the connection string that works... ConnectionString = value="Server=MY-SERVER;Network Library=DBMSSOCN;Initial Catalog=MYDATABASE2;User ID=MrLocalUser;Password=password;"
Heres the connection string that fails... ConnectionString = value="Server=MY-SERVER;Network Library=DBMSSOCN;Initial Catalog=MYDATABASE2;User ID=DOMAINMrDomainUser;Password=password;"
I doing some testing with security and ran into the following problem.I want to log into the SQL server (from Query Analyzer) using mydomain account. To allow this, I went into Logins section inEnterprise Manager and added my user account as a Windows User.If I set Analyzer to use Windows authentication I am to log in with noproblems. But if it is set to SQL Server authentication and I type inmy username (in the format domainusername or username@domain) andpassword I get a login error.Is there a way to login in to SQL using domain account without usingwindows authentication?Thanks,Jason
New to SQL Server. Plan to install SQL Server 2005 standard edition on Windows 2k3. After searched a lot of places, still don't understand what exactly "domain user account" is. Could someone explain it to me? 1. Is this a OS account where SQL Server is running? 2. Or, is this an account under domain controller on other machine? Is this an account on DNS srver? How do I create it? 3. Or, is this an account in SQL Server?
Where is this account located? How do I manage it?
I am seeing a couple of domain/username accounts trying to access SQL 2k5 SP2 and get the error above. The concern I have is these accounts shouldn't be trying to access SQL at all and do not exist is SQL hence the error The question I have is how can I track down what is trying to use this account and connect to sql? Thanks in advance.
John
SQL Server Log:
Message Login failed for user 'DOMAIN ampbell'. [CLIENT: <named pipe>]
I have two servers that are setup to use their local system account. They are in the same workgroup, but aren't on a domain. Is there a way to setup replication without a domain? If so, how?
I'd like to install SQL SERVER 2005 Express Edition ,I begin to install it from DVD but during the installation it dosn't ask me about any instance and after installation there isn't SQLExpress service and I can't use sql server .(there are not MSSQL and Binn directory in sql server 2005) but when I install visual studio 2005 and after that I install sql server 2005 it ask me for name of instance and with this way every thing is ok and I use sql server completely.
I 'd like to know the complete installation of sql server 2005 is depend on installation of visual studio 2005 befor it ?if not how can I introduce any instance after installation of sel server 2005 .
Hi all, I have seen in documents that I can install SS2K on a machine without network domain connection using a domain account.It said that domain accounts are prefered according to some reasons and it is not limited to machines on a domain so you should do it on a single PC. I tried this during installation and entered many different things but no chance: <OS_account> <machine_name>/<OS_account> ... Would you please telling me what should I enter as service starter account if I want to use domain users? -Thanks in advance
Hi, I want to use a domain user account not belonging to local admin or domain admin groups in SQL 2000/2005 Enterprise edition. This is what I've done so far.. On the machine that is the Domain Controller: - installed SQL 2005 as a domain admin
- created a domain user account using Active Directory Users and Computers. This user is only
"Member of" domain users; not any Administrators group.
- added this user to SQL Server Management Studio->Logins and in Server Roles assigned
sysadmin role. Question 1: Do I need to give any additional permissions to this user to work with SQL? Question 2: How can I test this user for basic SQL operations like database creation? Can I use Osql? Question 3: Can I use this user account to login to my domain controller using remote desktop? I tried adding this user to remote users, but in vain.
I am trying to configure Reporting Services to allow a domain group access to reports. I am able to configure the domain and group (mydomaingrpname) in both Report Manager and BIDS. I'm sure I entered the correct name because I purposely misspelled it and received an error. I think this tells me it is finding the group correctly.
However, when my test user goes to Report Manager, there are no folders displayed. I checked and he is in the domain group I am using. If I explicitly add him (mydomainandy) to the folders, he can see them and execute the reports.
After searching the forums and other websites, I have checked IIS is using Windows Integrated Security and not anonymous access.
I apologize for the newbie question but I'm looking for the correct answer. We have 4 production SQL servers at this time. When we had originally set them up the "sa" account belonged to the domain administrators group. Since we have a SQL admin team and a domain admin team we would like to remove this privilege. Is this something we can and should do? Our SQL servers use mixed mode authentication and some databases are configured for Windows authentication. I would appreciate any input from the community.
I've done some searching, but have found no definite answer yet. Our SQL 2005 servers are members of Active Directory Services. We want to run SQL services using an ADS account.
I see 7 SQL services in the SQL Server Configuration Manager: Integration Services, FullText Search, SQL Server, Analysis Services, Reporting Services, Browser, and Agent.
Question: Is it a bad move to run them all using the same domain account? I mean, wouldn't this give, say the Browser service, more privileges than it needs by allowing its account access to the same resources as, for example, the Agent service? What I'm concerned about is a vulnerability in one service compromising another service.
I would like to be able to use one domain account for all 7 services on two SQL servers, but I have a feeling this is a poor choice.
What is the best method for running SQL services using a domain account?
Hi am i am facing problem adding a domain group to the reporting services. while setting the security of a report, i am getting the rsUnknownUserName error while adding a domain group. the group is valid and it does exists. i tried creating a windows group on the machine running reporting services and tried adding the domain group and it accepted. but the reporting services is not accepting. can somebody tell me whats the problem with this. i am able to add other domain group belonging to the same domain and the SSRS accepts but not this particular domain group which is like any other domain group.
- first machine holds MOSS 2007 - second machine SQL 2005 SP2+MOSS Web Front
MOSS config. database is on Sql server. I'm trying to configure Reporting Services on SQL server in Sharepoint Integration Mode. As per Microsoft tutorials I've set up domain accounts for Sql services. When I use Reporting Services Configuration to configure Web Service Identity to use an App. Pool that runs under a domain account i get this error: "ReportServicesConfigUI.WMIProvider.WMIProviderException: An unknown error has occurred in the WMI Provider. Error Code 800708AC at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.SetWebServiceIdentity(String applicationPool)"
Database Setup and Windows Service Identity work fine using domain account. I've searched many forums, Microsoft "How To" to no avail.
I downloaded the SQL server 2005 trival version (180 days trival peroid) from the MS website. But i got a error saying that I have don't have enough space to extract the package on my C: drive when I do the installation. Actually I have 13g space on my c drive, so I may be miss something? I looked up the internet and found a solution using SET TEMP=C:TEMP and SET TMP=C:TEMP, but it doesn't work for me.
Does anyone have a better idear? I had a SQL 2005 express edition installed on my laptop before, but I have remove it, maybe I did not remove it completely and cause this problem?
We deploy an application that uses SQL Server Express 2005. One of our test engineers tried to use our setup on Windows XP SP 3. But the SQL server installer gave an error - unable to update msxml6r.dll. Is this a bug of the SQL Server installer or do we need to make use of a more recent version of msxml6?
