The recomindation to not install SQL express on a Domain Controller. Is there a specific technical reason or is it just the general don't use the DC has a Terminal server / sql server / application server line of thought?
The reason I ask is we have been using SQL 2000 on a W2k3 server configured as a DC as well as for Terminal Services. (yes I am aware of the security risks) but in a small network with 5 or less ft clients and 30 thin, I can't justify a seperate DC and App server.
I want to install SQL Express 2K5 on a lightly used second Windows 2003 SP1 DC. I know about the warning not to do this type of install. However, the group is small and their budget does not allow for another server just for one application. With that being said, the error message I keep getting is "can't create local groups......" (I know that you do not have local groups with AD). So, is there a work around to this issue or can someone point me in the right direction as how to install on a domain controller? Thanks in advance for your time!!!
Novice wants to learn why it is not recommended to install sql 2005 express on to a 2003 domain controller. I have installed sql 2005 express on a 2003 domain controller and when I tried to run management studio it failed to run. there seems to be no problem with the engine, oh I also installed books online I wonder... can there be an issue with the books online and management studio I remember there were problems in the beta era. Now I am wondering if it's a good idea at all I feel like I have been left at train station with all my luggage, I have all this equipment... work stations, a server, printers and no resolution to my problem. most of all I want to learn why I shouldn't install sql on a domain controller... can someone please explain in detail.
Arnie I have sql express, 2003 R2 as a domain controller, a laptop I use as a remote connection to the server. What I want to accomplish is to connect to a website using the server as a branch headquarters type of connections. I was told to look into using sharepoint services. I noticed my server has this service. Can't I use sql in this type of senario. I want to be able to have content uploaded to the web site by verious employees then have that content scanned and cleaned if needed and made available for my server. And from there I would have what I need to continue my publishing the content.
I have a problem with OLAP running on a Server that is domain controller, the problems is that after the Server was promoted to Domain controller, all users are allowed to see all databases and cubes, I did the same test on another server and found same problem after upgrading to domain controller.
I already tried demoting the server as domain controller to member server, but did not work.
I have 2 questions, the first one is more of a DC/AD issue, but I don't think there is a forum for that. But that question leads directly into my other question which involves SQL Server. I hope someone can give me some feedback.
We have a small network of about 12 users, and we are running SBS 2003 as our DC and Exchange server. We are going to start doing a lot of heavy lifting with data so we got another box to run Server 2003 Standard and SQL Server 2005 Standard. But now it's been suggested that we also install a second DC on the new SQL box. I am opposed because a DC should be on it's own box, and the SQL Server will need all of the available resources. I don't really think we need a second domain controller anyway, considering we have such a small office and good backups.
So my questions are: does anyone have an opinion as to whether or not we really need a second domain controller in our 12 person Small Business Server environment. I'm thinking there wouldn't be a whole lot of benefit. We certainly don't need it to share the load, and a SBS dc cannot give up it's FSMO roles so i don't see how a second dc would be able to properly serve as a failover should the first one go down.
My second question is: what kind of impact on the SQL Server would there be by installing a DC? I know it's not Microsoft recommended to have them on the same box.
Hello everyone, I have searched the forum regarding this topic and have found numerous good threads about installing SQL Express on a DC. My question is, I am assuming that if installing SQL Express on a Domain Controller is not recommended, that installing the MSDE 2000 on a Domain Controller is not recommended either?
I have a customer that was using Sql 2005 Express on a W2k3 server. They then decided to turn the server in to a second domain controller. When they did this Sql Express stopped working, I'm guess because the account the service was running as nolonger existed (Network Service account). Because of this they demoted it back to just a member server, but still the sql express service wouldn't start.
When I look at their server now I have noticed that the Sql2005$ accounts Sql express created during installation are all missing.
What I want to do now is set the Sql express setvice to use a domain account (using the SqlServer configuration manager), but I'm concerned that because the sql2005$ groups are missing things won't run as expected.
Should I be worried about these accounts?
What would happen when it becomes a domain controller anyway, won't these local account disappear and hence my new sqlexpress service account wouldn't have permission to the sql server data folders??
I saw a lot of webcast about security in Sql Server and many of those talk about that is not recomendable install Sql Server on Windows Server Domain Controller. Actually, I don't know Why not? Someone can explain me, please?
If my SQL Server authentication is windows integrated authentication, whenever my application makes a connection to SQL server does it contact the windows active directory domain controller to authenticate the windows user account? How does windows integrated authentication work in the background?
I have SQL 2005 installed in a virtual (ESX) environment with a separate DC. Every minute or so an event shows up in the Application Event Log that says:
Type: Failure Audit
User: dgtestdc1$
Computer: sql1
Source: MSSQLSERVER
Category: (4)
Event ID: 18456
Description:
Login failed for user 'dgtestdc1$'. [Client: <ip address>]
SQL Server 2005 SP2, installed as a default instance at the domain controller. SSIS connection failed with the message Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum) The RPC server is unavailable. No firewalls, client and server in the same subnet, ping is ok. I suspect the issue is similar to described here: http://support.microsoft.com/kb/940232 I've given the user all the rights to DCOM MsDTSServer, but I cannot include him to the local "Distributed COM users" group because the domain controller doesn't have local group at all. I have included the user into the "domain admins" group, after that user got a connection. But this is not good, you know what I mean. Does any other solution exists, without reinstallation SQL Server to another server or giving the administrator's rights to the user? Thank you.
I am currently runinng Sql Server 2000 on a Windows 2003 domain controller. I cannot access my local sql server using windows authentication. All i receive is a cannot generate SSPI context error. I understand this is probably related to a security policy issue on the domain controller. Also Sqlserveragent service will not remain running and shutdowns immediately after it is started. This also produces an SSPI context error in the error log. If anyone can help with my configuartion of windows server 2003 such that sql server will recognize a valid sysadmin role for my domain admin account it would be greatly appreciated.
I've just got RS Enterprise Edition. Installed it in a Test Server, ok. Installed it in a DEV server, having some errors.
My DEV server is an "ALL in 1" server, which is also a Domian Controller. While Test Server is not a DC.
The installation was succesful but when I open RS Manager thru the web, it gives me a ASP.NET error:
Access to the path "D:Program FilesMicrosoft SQL ServerMSSQLReporting ServicesReportManagerin" is denied. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.UnauthorizedAccessException: Access to the path "D:Program FilesMicrosoft SQL ServerMSSQLReporting ServicesReportManagerin" is denied.
ASP.NET is not authorized to access the requested resource. Consider granting access rights to the resource to the ASP.NET request identity. ASP.NET has a base process identity (typically {MACHINE}ASPNET on IIS 5 or Network Service on IIS 6) that is used if the application is not impersonating. If the application is impersonating via <identity impersonate="true"/>, the identity will be the anonymous user (typically IUSR_MACHINENAME) or the authenticated request user.
To grant ASP.NET write access to a file, right-click the file in Explorer, choose "Properties" and select the Security tab. Click "Add" to add the appropriate user or group. Highlight the ASP.NET account, and check the boxes for the desired access.
I tried doing everything I can possible think of from the error message advice, including adding rights to ASPNET user from ISS to that particular folder...no success.
What I'm suspecting is I can't install RS in a DC box. But I can't find this info anyway in the web.
Anyone can point me to the correct direction or any advice?
I have observed that a temporary loss of a domain controller can causeproblems creating new ado connections between a client machine runningado and a separate sql server machine that are members of the domain.I understand why this happens when creating connections with windowsauthentication. What is a mystery is that it also sometimes effectsnew connections that use "sql authentication". Below is a descriptionof my test scenario.a. Setup 3 machines.i. one domain controller machine. windows 2000 based. I have triedboth a regular domain setup and a domain setup in compatibility mode.ii. one sql server machine that is a member of the domain. windows2000.iii. one client machine running an ado test program that communicateswith the sql server machine. I have tried both 2000 and xp.b. Start your test ado program and create a connection.c. Fire a query.d. It should work.e. Unplug the network cord on the domain controller.f. Create a new connection and fire a new connection about a minute orso after.g. It should work. Apparently the client caches account informationfrom the domain controller for a certain amount of time. The timeseems to be shorter by default in xp than 2000.h. Wait 20 minutes or more.i. Create another new connection. You will notice a timeout error.If your using windows authentication the timeout will happen 100% ofthe time. That is to be expected. If your using sql authenticationthe timeout seems to happen about 50% of the time. I can't explain itother than some strange Microsoft bug. I speculate that it may besome bug with the way ado caches connections. Perhaps a previouslysetup windows authentication connection gets reused by a request for asql authentication connection. However I haven't been able to proveit.Any insight you can offer would be appreciated. I also have a testprogram you can use to reproduce this behavior if you are interested.Thanks,Frank
how to configure sql express 2008 R2 on windows server 2008 R2 domain controller?? and one more thing, what log on should I use for sql express service in sql server configuration manager on domain controller??
I would like to install SQL server 2005 cluster on Windows 2003 cluster. Is domain controller (AD and DNS) necessary for the SQL server 2005 cluster? If yes, may I install it on one of the SQL server 2005 cluster nodes? Thanks in advance
I am attempting to set up an always on cluster on VMware for testing. setting up everything through the Failover cluster is fine, the trouble comes when I try to set up the AlwaysOn availability group. Whenever I attempt to specify a network location I receive the following error: Operating System Error 1265(The system cannot contact a domain controller to service the authentication request..).
I looked up this error and most sites point towards a Windows 8 homegroup issue. Since this is a on a domain, I don't think it is relevant. I also added the service accounts from server A to Server B and visa versa. I even added the computer objects to its opposite partner..I have attempted to use "Join Only" and do a manual copy.
I am receiving the following error when attempting to access reporting services... to sum things up real nice and tidy-
I get three login prompts - then the access denied response. It is almost as if it is unable to authenticate the user... anyway... here's the actual error response, I'd really appreciate any input/insight/resolution.
Server Error in '/Reports' Application.
Access to the path 'C:Program FilesMicrosoft SQL ServerMSSQL.2Reporting ServicesReportManagerin' is denied.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.UnauthorizedAccessException: Access to the path 'C:Program FilesMicrosoft SQL ServerMSSQL.2Reporting ServicesReportManagerin' is denied.
ASP.NET is not authorized to access the requested resource. Consider granting access rights to the resource to the ASP.NET request identity. ASP.NET has a base process identity (typically {MACHINE}ASPNET on IIS 5 or Network Service on IIS 6) that is used if the application is not impersonating. If the application is impersonating via <identity impersonate="true"/>, the identity will be the anonymous user (typically IUSR_MACHINENAME) or the authenticated request user.
To grant ASP.NET access to a file, right-click the file in Explorer, choose "Properties" and select the Security tab. Click "Add" to add the appropriate user or group. Highlight the ASP.NET account, and check the boxes for the desired access.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. Stack Trace:
I have DBA that is convinced that they need domain admin rights to install SQL 2005 into an existing cluster. The domain groups and service accounts for SQL have been created already. Is having domain admin rights required during the install of SQL 2005 in a cluster?
-A "master domain" AD, a "sub domain" AD, a trust relationship between the two (sub trust master) -A sql server 2005 on a win server 2003 in "sub domain" AD -A linked server to "sub domain" AD -A linked server login using a "sub domain" admin acccount -A view to this linked server -A grant on masterDomain/Domain Users to the database -A grant on subDomain/Domain Users to the database -We want all connections done through "Windows Authentication" not "Database Authentication".
Queries on the view work fine using "sub domain" user accounts. Queries on the view fail using "master domain" user accounts (including master domain admin accounts)
"Msg 7399, Level 16, State 1, Line 1
The OLE DB provider "ADsDSOObject" for linked server "ADSI" reported an error. The provider indicates that the user did not have the permission to perform the operation."
All connections are done through "Windows Authentication" not "Database Authentication".
Can we establish cross domain connectivity with "Windows Authentication" ?
Below are details of the implementation:
SELECT TOP (100) PERCENT * FROM OPENQUERY(ADSI, 'SELECT displayname, givenName, sn, cn (etc...) FROM ''LDAP://OU=PEOPLE,DC=subDomain,DC=com'' WHERE objectCategory = ''Person'' AND objectClass = ''user'' ')
In SQL Server Mngt Studio in Server Objects/Linked Servers/Providers/ ADSI properties security tab I have:
"connections will: <be made using this security context> Remote login:'subDomainAdminAccnt' With password: 'subDomainAdminAccntPassword'
Error: Msg 7399, Level 16, State 1, Line 1
The OLE DB provider "ADsDSOObject" for linked server "ADSI" reported an error. The provider indicates that the user did not have the permission to perform the operation.
Msg 7320, Level 16, State 2, Line 1
Cannot execute the query "SELECT displayname, givenName, sn, cn
FROM 'LDAP://OU=PEOPLE,DC=subDomain,DC=com'
WHERE
objectCategory = 'Person'
AND objectClass = 'user'
" against OLE DB provider "ADsDSOObject" for linked server "ADSI".
After using ADMT to migrate the domain user or group into the root domain, when I use enterprise manager to try and change the permissions allocated to that domain user/group, i get the 'Error 15401 NT user or Group not found'.
This is a correct error as the user is now in the root domain, however sql (in sysxlogins) still thinks its in the child domain.
Is there a simpler way, other than collecting the users permissions, deleting the user from SQL then adding back in with the correct domainusername format, then adding the permissions back?
I tried renaming the 'name' in sysxlogins (not recommended) and while that worked, whenever I tried to add the migrated user to another database, the login name was missing and would not resolve.
I believe it is something to do with the SID not matching.
we recently migrated from our in-house domain to the Enterprise domain. Everything went smooth except for the fact that I can no longer accept my dBs using my SA or my domain admin account. There is only 1 account I can get into the management studio with but it has no admin privileges, so I can't make any  password changes or add accounts. I don't have a test environment so kind of hesitant to experiment with our production system.
I heard that is said that MSQ SQL 2000 doesn't work correctly with raid (for example raid 5) I have my application in 2 companies. The first one with not a raid controller (even though the computer has a raid controller) executes a backup when no users are online in more than 8 minuter and the file of the database backup is 3,5 GB. The memory of the computer is 2GB. In the other company when more than 20 users work in the database with a raid controller the backup is occured in 2,6 minutes and the database backup file is more than 6 GB. The memory of this computer is 4 GB. What is your opinion? Is this rumor true? Do you suggest I should apply raid 5 to the first server? Regards, Manolis
I have an installation of Cognos Controller 8.2. The installation of application seems to be all 100%.I can create blank SQL database use the application to upgrade the tables but as soon as I populate the database with data and try to optimise from the application there is an issue. It gives me the error below: Standard error Number 5 Source: Frango dircect.Optimise.DeleteTempFox#controllerProxyClie nt Description: System.Web.Services.Protocols.SoapException server was unable to process request-->System.Security.Security Exception: Permission Denied I have checked permissions on the database and all is fine "fastnet" is added as the DB owner and the SQL instance is 100%, Can anyone please shed some light on this.
I have a guy who wants me to move his databases to an external drive. Hardware is my major weakness and I usually think I am McGyver when I can swap out a RAM board in my home PC. Whenever guys in the office start talking hardware, I go hide in the bathroom.
I know I have read that this is a very bad idea in some book and a few message board threads. This guy is going to use SCSI and it is going to be attached to the same controller as his other disks. I know he should have a battery backup for the drive especially if it employs write caching and that it should be formatted to NTFS and not FAT32.
I googled echnettedBOLedMSDNed this for 2 hours yesterday because I remember reading something about disc controllers and external drives and SQL Server being a recipe for disaster but I could not find anything to back me up.
I was informed (by Microsoft) that for all SQL Servers prior 2008 recommended (or must) stripe size is 64k Does anyone knows full set of settings that must be applied when setting up raid 5 for sql server box
We have a Dell 6450 quad 1.6MHz, 4GB RAM running SQL 2000 on Win 2000server with 2 PERC3/QC cards. Server has 4 internal drives configuredas two raid-1 drives (OS and SQL logs). Server has 7 more drives inexternal drive rack for RAID-5 SQL data. We did not have a UPSavailable for server at installation so I set cache as write-through,even though should not matter since it writes back at restart right?.I am planning on switching back to write-back cache and was wonderinghow do users run this setting and any problms/caveats? How do I tellif the PERC cards are mirrored? Or does one PERC card run 4 internaldrives and other card run raid5? How much performance boost do youget from using write-back? What are the recommended settings for readcache (readahead, adaptive etc)? Can you post some reference websites? Thanks P
I'm trying to run a test from my test environment which is a non-domain Windows 2000 server to access my domain 2003 with SQL2005. I have install 2005 tools to try to access the SQL server.
- I have try following the KB265808 - no success. - Reading alot of blogs and it seems all are pointing to the same problem. "Remote access" but the settign is enabled.Error Message:
TITLE: Connect to Server ------------------------------
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=53&LinkId=20476
Question: Could Windows 2003 security be blocking access? I'm using sa account to access.
Also, sa account does not seems to work for remote access. It is ok when accessing locally.
We are trying to setup a system to system failover cluster using twonodes (x346) which each have a single hba running to seperatecontrollers on the DS400.For full redundnancy, IBM recommends dual path from each node but wedont need that. The current setup has two completly seperate paths. hbaon node 1 to controller A on DS400 and hba on node 2 to controller B.If i take a controller offline, failover works fine to jumo to othercontroller and throw all resources to it's node but if i shutdown anode- the cluster loses all attached storage and DS400 is unaware toswitch ownership to other controller.Is there a way to us mscs without dual path from each node?anotherwords... if either node or controller fails on a single path, wewant the other path to become active.our main goal is to use sql server 2005 clustering on the cluster.everything checks out perfect if i only use one controller on the DS400for both nodes but this brings us back to another single point offailure.I saw that Qlogic has MPIO drivers on thir website for the DS400 but itseems as though they are for 32bit systems and the install errors outwith:C:Driversmpio1.0.8.4 (w32)>install.exe -iPre-Installing the Multi-Path Adapter Filter...SuccessInstalling the Multi-Path Bus Driver...Failure. Error code (0xe0000235)configuration:2 X IBM x346 w/ single QLogic 2340 HBAs running win2k3 64bit EnterpriseDS400 w/ dual controllers
