Intalling a server product on a member server in a Windows 2003 Do

microsoft.public.windows.server.general

22 Mar 2005 3:29 PM

I am posting this again, with the hope of geting some advise or help.

I am in the process of building a server with SPS2003. Below is the process
I followed.

1. Install windows 2003.

2.Install IIS.

3.Apply all patches.

4. Make server member of Windows 2003 AD domain.

5. Install MS SQL server 2003.
I could not get the domain account to work during installation. I kept on
getting the message "the account can not be found for the SQL Server
service." I got around this by installing SQL to run under the local system
account. Then after installation, changed the service accounts to the domain
accounts.

The final step was to install SPS 2003. When I get to the stage of "Provide
a valid Microsoft Windows account", I enter the SPSADMIN domain account I
created for this purpose.This account is a member of the Power users group on
the server I am installing on. However, I get the message ""Sharepoint Portal
Server could not verify the Windows NT account you entered".

As both applications had issues, I am thinking that this may be a security
issue. what is the process of authenticaion an application uses during
installation? Is there a way to trace where the authentication fails? I can
login onto the server with a domain admin account and have made sure DNS is
setup correctly.

Thanks in advance.

22 Mar 2005 5:59 PM

TheThaiTech

First. Microsoft didn't make SQL server 2003 and they never will. Because SQL
Server 2005 is coming soon.

There are a lot to say about SQL server.
1. You need to apply SQL Server SP2 or higher when you install it on Windows
Server 2003.
2. SQL Server comes with 2 authentication modes which they are Windows
Authentication and Mixed Mode Authentication. You need to choose whichever
suit your application. Some applications do not run under Windows
Authentication.

I think you should read these.
http://www.microsoft.com/technet/prodtechnol/sql/2000/default.mspx

Show quoteHide quote

"DP" wrote:

> I am posting this again, with the hope of geting some advise or help.
>
> I am in the process of building a server with SPS2003. Below is the process
> I followed.
>
> 1. Install windows 2003.
>
> 2.Install IIS.
>
> 3.Apply all patches.
>
> 4. Make server member of Windows 2003 AD domain.
>
> 5. Install MS SQL server 2003.
> I could not get the domain account to work during installation. I kept on
> getting the message "the account can not be found for the SQL Server
> service." I got around this by installing SQL to run under the local system
> account. Then after installation, changed the service accounts to the domain
> accounts.
>
> The final step was to install SPS 2003. When I get to the stage of "Provide
> a valid Microsoft Windows account", I enter the SPSADMIN domain account I
> created for this purpose.This account is a member of the Power users group on
> the server I am installing on. However, I get the message ""Sharepoint Portal
> Server could not verify the Windows NT account you entered".
>
> As both applications had issues, I am thinking that this may be a security
> issue. what is the process of authenticaion an application uses during
> installation? Is there a way to trace where the authentication fails? I can
> login onto the server with a domain admin account and have made sure DNS is
> setup correctly.
>
> Thanks in advance.

Are all your drivers up to date? click for free checkup

22 Mar 2005 8:41 PM

Thanks you very much for pointing out my obvious typo about the SQL server
version. I am aware that you need to apply SP2 for Win2k3.But thats kinda
difficult when one cannot install SQL server to start with.I am also aware of
the two modes of authentication.But don't you agree that a server that is a
member of a domain should be able to use windows authentication?This is a
plain vanilla win2k3 server. nothing else installed on it.

Show quoteHide quote

"TheThaiTech" wrote:

> First. Microsoft didn't make SQL server 2003 and they never will. Because SQL
> Server 2005 is coming soon.
>
> There are a lot to say about SQL server.
> 1. You need to apply SQL Server SP2 or higher when you install it on Windows
> Server 2003.
> 2. SQL Server comes with 2 authentication modes which they are Windows
> Authentication and Mixed Mode Authentication. You need to choose whichever
> suit your application. Some applications do not run under Windows
> Authentication.
>
> I think you should read these.
> http://www.microsoft.com/technet/prodtechnol/sql/2000/default.mspx
>
> "DP" wrote:
>
> > I am posting this again, with the hope of geting some advise or help.
> >
> > I am in the process of building a server with SPS2003. Below is the process
> > I followed.
> >
> > 1. Install windows 2003.
> >
> > 2.Install IIS.
> >
> > 3.Apply all patches.
> >
> > 4. Make server member of Windows 2003 AD domain.
> >
> > 5. Install MS SQL server 2003.
> > I could not get the domain account to work during installation. I kept on
> > getting the message "the account can not be found for the SQL Server
> > service." I got around this by installing SQL to run under the local system
> > account. Then after installation, changed the service accounts to the domain
> > accounts.
> >
> > The final step was to install SPS 2003. When I get to the stage of "Provide
> > a valid Microsoft Windows account", I enter the SPSADMIN domain account I
> > created for this purpose.This account is a member of the Power users group on
> > the server I am installing on. However, I get the message ""Sharepoint Portal
> > Server could not verify the Windows NT account you entered".
> >
> > As both applications had issues, I am thinking that this may be a security
> > issue. what is the process of authenticaion an application uses during
> > installation? Is there a way to trace where the authentication fails? I can
> > login onto the server with a domain admin account and have made sure DNS is
> > setup correctly.
> >
> > Thanks in advance.