Installation issues with SQL Server and SPS on a member server.

Digital certificates
Identity & Access Management
Security tokens
Single sign-on
I have a small windows 2003 domain.My domain controller runs Exchange server 2003 too.Wanting to set up a practice server for SPS2003, I introduced another Windows 2003 member server. I installed windows server 2003 and IIS 6 fine. When I got to the authentications stage during the installation of SQL server, I shose to use the domain admin account for this.Unfortunately I got an error stating "the account could not be verified for the SQL server service". This was wierd because i had logged in as domain admin and the server was already a member of the domain. I chose to install SQL by using "local system" account and finished the installation. When I started to install SPS2003, I ran into the same problem of the domain account not being recognsed. I have tried to rebuild the server from scratch but the issue remains. It's almost as if there is some security setting on the DC that is preventing service account authentication. I desperately need help to resolve this issue. Thanks in advance.

Answer Wiki

Thanks. We'll let you know when a new response is added.

You REALLY DO NOT want Exchange running on your domain controller.

Discuss This Question: 4  Replies

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • Howard2nd
    A - Concur with Kerm - move Exchange off DC. B - That probably has nothing to do with your stated problem. 1st never install applications to operate as the domain administrator, ALWAYS use the system account or a specially created account you can limit permissions on. C - When you installed SQL Server 2003 and the SP3a patch, you did set a password on the 'SA' account? And you set SQL Server for dual authentication 'Windows' AND 'SQL'? D - SharePointServices (sps2003) has a service pack (SP1) which is in the latest download. When you istall SPS and want to use an existing SQL server instance, you HAVE to use the command line options, and know the system account and password, AND the SA account and password. E - What worked for me is a clean install of Server 2003 as member server NOT DC. Setup IIS. Verify that a regular machine can see the website. Install the SPS package and accept the MSDE defaults. Allow the drivers in IIS admin. and test that a regular machine can see the webpage for SPS. NOTE: By default you have to login to the website and unless you have added the test user with view/read permissions to the SPS site you get the 'Not authorized to view' error. F - It is a great tool and can be very useful. BUT it is NOT easy, getting the permissions set for the various user levels and NTFS and IIS requires good palnning and better notes. GOOD LUCK!
    30 pointsBadges:
  • Dipampatel
    I appreciate the advise guys. Let me give some background. We are a very small consulting shop.Due to budgetary reasons, we setup a single server for Exchange and also to be a DC.It has worked fine for a couple of years. Recently I decided to setup a server to setup SPS portal. I purchased the book " Microsoft SharePoint 2003 Unleashed". I followed the instructions for installation.The order being, Windows 2003->IIS6->SQL 2000->SPS 2003. The server setup fine and everything worked. Unfortunately the original Dc crashed and the OS had to be reinstalled. so I had to rebuild the DC. I then had to make the SPS server a member of the new domain.At this point SPS refused to play.After spending a lot of time troubleshooting, I decided to rebuild the box as it was a test box anyway. This is where I am now. I am building a fresh windows 2003 box,installing IIS, and then trying to install SQL.But now,I cannot install SQL under a domain account. Could it be some security issue on the DC?Thats he only thing I can think of.
    0 pointsBadges:
  • GregNottage
    If cost is an issue, maybe you could look at something like MS Virtual Server as a way of running multiple virtual machines on one physical server. This way you would get the separation that is recommended, yet you wouldn't need a whole new box. Thanks, Greg.
    0 pointsBadges:
  • Squidly
    Very likely the Domain Administrator does not have permissions to login as a service (this is not given by default). I would actually recommend NOT using your Domain Administrator as a service account though (hackers love this). I'd highly recommend setting up a service account with the appropriate permissions and then using that account to login as a service. There are a couple of ways in which you can give an account permissions to login as a service - through local or domain/domain controller security Group Policies. The most simplistic way to make this happen is to go to that box, open the SERVICES window, go to the service in questions and change the authentication permissions to the local/domain account you wish to use. As soon as you hit apply, if that account did not previously have permissions to login as a service, then you will get a notification that the account has now been given that permission on that box. Note: SQL may have two different services running - SQLSERVER and MSSQL Service. Only change the SQLSERVER service authentication. Do not change the MSSQL service. Hope this helps. -Dean F.
    0 pointsBadges:

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.


Share this item with your network: