Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Development (2000)
 Receiving Error: Login failed for user 'ro'

Author  Topic 

gemcc
Starting Member

5 Posts

Posted - 2007-10-12 : 17:07:00
Hello,

I recently replaced the server at my client site. It has 4 different SQL databases. Three of them seem to be working correctly, however, when we try to access the fourth one, we receive an error "Login failed for user 'ro'". When I click on the details, I get the following:

System.Data.SqlClient.SqlException: Login failed for user 'ro'.
at System.Data.SqlClient.ConnectionPool.GetConnection(Boolean& isInTransaction)
at System.Data.SqlClient.SqlConnectionPoolManager.GetPooledConnection(SqlConnectionString options, Boolean& isInTransaction)
at System.Data.SqlClient.SqlConnection.Open()
at System.Data.Common.DbDataAdapter.QuietOpen(IDbConnection connection, ConnectionState& originalState)
at System.Data.Common.DbDataAdapter.FillFromCommand(Object data, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet)
at Mercury_Assistant.frmSearch.btnOK_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/microsoft.net/framework/v1.1.4322/mscorlib.dll
----------------------------------------
Mercury Assistant
Assembly Version: 1.1.2074.38411
Win32 Version: 1.1.2074.38411
CodeBase: file:///C:/Program%20Files/Community%20Choice%20Federal%20Credit%20Union/Mercury%20Assistant/Mercury%20Assistant.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system.windows.forms/1.0.5000.0__b77a5c561934e089/system.windows.forms.dll
----------------------------------------
System
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
----------------------------------------
System.Drawing
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system.drawing/1.0.5000.0__b03f5f7f11d50a3a/system.drawing.dll
----------------------------------------
Accessibility
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/accessibility/1.0.5000.0__b03f5f7f11d50a3a/accessibility.dll
----------------------------------------
System.Data
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system.data/1.0.5000.0__b77a5c561934e089/system.data.dll
----------------------------------------
System.Xml
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system.xml/1.0.5000.0__b77a5c561934e089/system.xml.dll
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 7.0.5000.0
Win32 Version: 7.10.3052.4
CodeBase: file:///c:/windows/assembly/gac/microsoft.visualbasic/7.0.5000.0__b03f5f7f11d50a3a/microsoft.visualbasic.dll
----------------------------------------
System.EnterpriseServices
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system.enterpriseservices/1.0.5000.0__b03f5f7f11d50a3a/system.enterpriseservices.dll
----------------------------------------

************** JIT Debugging **************
To enable just in time (JIT) debugging, the config file for this
application or machine (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>


Thank you for your help in advance.

rmiao
Master Smack Fu Yak Hacker

7266 Posts

Posted - 2007-10-13 : 00:20:01
Did you use same connection string with different db name?
Go to Top of Page

gemcc
Starting Member

5 Posts

Posted - 2007-10-13 : 18:20:21
I did not change the db name. It was 2221ma on both the old and new servers. And I am sorry, I do not know where the connection string is (fairly new to SQL). Thanks again.
Go to Top of Page

rmiao
Master Smack Fu Yak Hacker

7266 Posts

Posted - 2007-10-13 : 21:32:42
How did you access server then?
Go to Top of Page

gemcc
Starting Member

5 Posts

Posted - 2007-10-14 : 16:11:55
I am not sure what you are asking. I copied the db over to the new server. We have an applcation on a workstation that accesses the db.
Go to Top of Page

rmiao
Master Smack Fu Yak Hacker

7266 Posts

Posted - 2007-10-14 : 16:36:34
Ok, how does the app connect to sql server? Via odbc dsn or oledb connection string? If you don't know that, how can you troubleshoot the problem? So you may need to work with you app developer for this issue.
Go to Top of Page

gemcc
Starting Member

5 Posts

Posted - 2007-10-14 : 17:11:52
Well, that's part if not the whole problem. The developer will not return phone calls. He was a former employee. So you are suggesting I am not able to fix this without his interaction?
Go to Top of Page

Kristen
Test

22859 Posts

Posted - 2007-10-14 : 18:05:28
Sounds like when the database was moved to the new server the Server Logins it users were either not copied across, or were not re-synchronised with the database.

If you still have the original server you should be able to transfer them.

Kristen
Go to Top of Page

gemcc
Starting Member

5 Posts

Posted - 2007-10-14 : 19:18:47
But where are the logins? In SQL, in AD? I see the ro account in the db itself.
Go to Top of Page

Kristen
Test

22859 Posts

Posted - 2007-10-14 : 19:26:03
The Server has logins.

and then each Database grants one or more of those logins access to the database.

So if the logins do not exist ON THE SERVER than a) the link between Loging and Server cannot be made, and b) attempting to login as, say, "ro" will fail.

(Yes the logins could be AD or some Windows Authentication, but I would guess not from the error message)

Kristen
Go to Top of Page

rmiao
Master Smack Fu Yak Hacker

7266 Posts

Posted - 2007-10-14 : 20:45:55
Should you modify connection string to point app to new sql server? Even after copying sql logins over.
Go to Top of Page
   

- Advertisement -