Re: Problem connecting to SQL2000...

From: Tommie Severinsson (anonymous_at_discussions.microsoft.com)
Date: 02/11/04 

Date: Tue, 10 Feb 2004 22:32:36 -0800

Thats what I meant, sorry...

Yesterday we did a test, we selected a
different sql server for the configuration database, and
it worked like a charm.

Yesterday, they also told me that they been having some
problems with their current sql installation. So we did an
all nighter and re-installed sql2000 per default. The only
change they wanted was to change the default port from
1433 to another port. Could this have something to do with
it?? Today we see the same error as before *sigh*

I also ran profiler yesterday because I wanted to see if
anything happens at all. Nothing on the "real" sql
machine, but on the one we tested, we could follow the
whole procedure.

between a rock and a hard place on this one... ;)

>-----Ursprungligt meddelande-----
>No, when you installed SPS (the windows installer), you
had to select
>Install without database engine (that way you could
connect to remote SQL).
>Before windows installer finishes, you need to enter an
account and *that*
>account is the database access account.
>
>If this didn't happen, you may need to do the
installation again to set the
>database access account.
>
>--
>James Edelen
>Microsoft MVP - SharePoint Portal Server
>Microsoft MVP - Windows XP Media Center
>Microsoft Associate Expert
>Expert Zone -
http://www.microsoft.com/windowsxp/expertzone
>"Tommie Severinsson"
<anonymous@discussions.microsoft.com> wrote in message
>news:d00b01c3efa5$fc9659e0$a101280a@phx.gbl...
>> What do you mean by that?? It seems that we cant even
get
>> to the end... ;)
>>
>> When you do the "create configuration database" bit you
>> set an account to handle this, this account we put into
>> the database creators and the security group on the sql
>> server?? right??
>>
>> Forgot to tell you, SPS2003 is on a Win2003 Standard
>> Edition and SQL2000 is on a Win2000 server, both with
the
>> latest service packs.
>>
>> >-----Ursprungligt meddelande-----
>> >Also, make sure you are setting the permissions on the
>> correct account. The
>> >account you are using to configure the server is *not*
>> the Database access
>> >account where you need to set permissions. The DB
Access
>> account (the one
>> >that matters) is the one you set at the end of SPS
>> installation.
>> >
>> >--
>> >James Edelen
>> >Microsoft MVP - SharePoint Portal Server
>> >Microsoft MVP - Windows XP Media Center
>> >Microsoft Associate Expert
>> >Expert Zone -
>> http://www.microsoft.com/windowsxp/expertzone
>> >"Tommie Severinsson" <info@opit.se> wrote in message
>> >news:d06901c3eeee$2afc97d0$a401280a@phx.gbl...
>> >> When installing SPS2003 and we come to the "Specify
>> >> Configuration Database Settings for server_name", we
>> >> select "create configuration database" and we enter
the
>> >> sql servername and we use the default db name, we
get an
>> >> error after pressing ok.
>> >>
>> >> Error accessing database. Verify that the database
>> server
>> >> name and the instance name (if present) are correct.
>> Also,
>> >> ensure the configuration database administration
account
>> >> has sufficient permissions on the server or instance
and
>> >> the service corresponding to your SQL Server
instance is
>> >> running.
>> >>
>> >> Now, we have added the account to the power user
group
>> on
>> >> the SPS machine, added the account to the database
>> >> creators group and security admin group on the sql
>> server.
>> >>
>> >> If we try to specify the instance name after
>> >> sql_servername we get an other error:
>> >>
>> >> Invalid SQL Server Name
>> >>
>> >> We are totally lost now, has anyone else had this
>> problem
>> >> and solved it???
>> >
>> >
>> >.
>> >
>
>
>.
>

Relevant Pages

  • Re: ASP.NET, Win2k, SQL 2k on an intranet (w/Kerberos?)
    ... In your place I would go trough database and have mirrored accounts in SQL ... you can create views on SQL server to filter out ... Grant ASPNET account logon rights to SQL server and limit ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: ADP/SQL Server 2000 Security Problem
    ... The server is running Windows 2003. ... I'll also test using a SQL Server account and see what happens. ... it worked in MSDE 2000. ... I have not created any new accounts for the production database. ...
    (microsoft.public.access.adp.sqlserver)
  • Re: Help with WSS 3.0 Server Farm Config - Backend SQL 2005
    ... I had to use only "sharepoint" to get the ... What interest me though is that the database get created but fails after ... Virtual Server with DBSVR ... an account local to the WEBSVR) to create and access the SQL server, ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: Restored Server but SharePoint refusing admin access
    ... > SID/BID or remove the user from the database and add it again. ... >, In SQL Configuration Manager go to SQL> Server ... > you had) you cannot access the database from that account. ... > newly added administrator account (for me, since I added a new admin ...
    (microsoft.public.windows.server.sbs)
  • Re: Keep getting this error when trying to use Web Parts in VS2005 Beta 2. Why?
    ... > setup another database. ... >> operation or the server is not responding. ... This is necessary because the web server account will ... >> This is necessary because the web server account will attempt to ...
    (microsoft.public.dotnet.framework.aspnet)