Re: Login problem

From: Jens Süßmeyer (Jens_at_Remove_this_For_Contacting.sqlserver2005.de)
Date: 04/28/05 

Date: Thu, 28 Apr 2005 07:32:10 +0200

Sounds like you have switched the LoginMode for this Server or the password
of the user you are connecting with.

Try connecting to the server with the SQL login, if that won´t work use
integrated authentication and check wheter the loginmode is WIndows or Mixed
Mode. If its mixed mode, you gotta reset your password because it doesn´t
fit to that you you have. If you already tried that, there can be a
difference between the accounts that you imported. A user is created on the
server side on granted access to something on the db on the database level.
If you got a back restore on the backup server, these accounts won´t fit
togehter, so oyu gotta delete the user on the db level and recreate him with
the appopiate security Script.

If you don´t know how, just raise a hand (or write a mail) and i´ll help
you.

HTH, Jens Suessmeyer. 

---
http://www.sqlserver2005.de
---
"Ragnar Midtskogen" <ragnar_ng@newsgroups.com> schrieb im Newsbeitrag 
news:O5d0%23g3SFHA.2096@TK2MSFTNGP14.phx.gbl...
> Hello,
>
> I have two servers where the SQL Server DB provides the data for a Web 
> site.
> One server is the live Web server, the other one will serve as a backup.
>
> I use an ODBC connection to conect to SQL Server, and there are a number 
> of asp pages that connect the SQL Server using SQL Server authentication.
>
> Recently I restored the website DB on the backup server with a full backup 
> file from the live server and now the asp pages can not connect any more.
> When I try to configure the ODBC connection I also get a message that 
> connection failed.
> If I switch to Windows authentication in the ODBC manager I can connect 
> and the DB tests out successfully.
>
> I tried editing the password but when I try to save it I get the message 
> that the userid already exists.
> I also tried deleting the userid and adding it back in, but I get the same 
> message, that userid already exists.
>
> I have just transferred another backup from the live server and it 
> includes a backup of the master, model and msdb DB's. I am hoping that 
> restoring all from this backup will correct the problem, but I am not an 
> experienced DBA, so I am not sure
>
> Any suggestions as to how I could fix this problem would be appreciated, 
> our live server is acting up so we may need to switch.
>
> Ragnar
>

Relevant Pages

  • Re: MSKB 891957, VSS Update for Windows Server 2003
    ... I left the connection sit idle and checked back in an hour. ... server and browsed around for a few minutes. ... it would seem that there is still some issue with the V6 RDP ... I left the server with user Backup logged in when I left the ...
    (microsoft.public.windows.server.general)
  • Re: MSKB 891957, VSS Update for Windows Server 2003
    ... Well, it turns out the RDP connection dropping issue won't go away, ... level to the server in the office may have an affect on the issue. ... I just remembered I also re-installed RDP Client V6 last night as ... I left the server with user Backup logged in when I left the ...
    (microsoft.public.windows.server.general)
  • Re: accessing data mining model via web/PDA
    ... Is your OPENROWSET clause connecting to a SQL Server 2000 database? ... Is your SQL Server instance running on the same machine as your Analysis ... i need some> help for the connection string, let say to access the> mining model in the AS. ...
    (microsoft.public.sqlserver.datamining)
  • Re: VB Express SQL Express Remote Connection
    ... Yes I can connect using the SQL Server Management Studio Express Tool. ... I changed my connection to exactly what you specified and it connected. ... I can connect and create databases on the Remote Server ...
    (microsoft.public.dotnet.languages.vb)
  • Re: How to Direct connect with ActiveSync
    ... That won't work because you have a connection string that can't be correct. ... You're saying that the database is, but it's not; ... Server 2000, Visual Studio 2008. ... Again sorry if this should be in another form but you say that SQL Server ...
    (microsoft.public.sqlserver.ce)