This may be a newbie question but here it goes. I have SQL Server 2000 running on a windows server 2003 machine. When i have my database local, on MSDE everything is fine. But when i switch my code to move to the server, (after i've attached the database within the server) it tells me that server either does not exist or login failed. Now here is my connection statement
OleDbConnection m_conn;
string connectionString = "Provider=SQLOLEDB;Data Source=SERVER1;Initial Catalog=workups;Integrated Security=SSPI";
m_conn = new OleDbConnection(connectionString);
Now like i said when i change the Data Source from (local) to SERVER1 it gives me this error, however on the server all the data is fine, and i can view it locally on the server. Anyone know what's wrong or if it's a coding issue?
Thanks
Dan
What's the error message?|||Error message in my event log, i log the actual exception here it is
System.Data.OleDb.OleDbException: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
at System.Data.OleDb.OleDbConnection.ProcessResults(Int32 hr)
at System.Data.OleDb.OleDbConnection.InitializeProvider()
at System.Data.OleDb.OleDbConnection.Open()
at DotThisSoftware.SqlClient.DatabaseFactory.Open() in C:\Documents and Settings\drux\My Documents\Visual Studio Projects\DotThisSoftware.SqlClient\DatabaseFactory.cs:line 88
THanks
Dan
|||I see, have you verified, since you're using Integrated Security, that the current user running the application can logon to the remote server?|||Ok, i can't log into the server through visual studio, would you know how to fix this or know of a kb article that would help me.
Dan
|||Well, I need for information about the SQL Server: is it 2000, 2005, Express and is it listening on typical port 1433 and can you ping the server from the client using the host name?|||More info:
stated earlier " I have SQL Server 2000 running on a windows server 2003 machine."
I can ping the server, and yes it's running on 1433 standard port. I still have no connectivity from my workstations for the sql server. Thanks for your help.
|||It sounds like a security issue then. You may want to try connecting to the server via the client via a tool such as Query Analyzer to determine if your credentials are sufficient to login.
Also, may I ask why you're not using the native ADO.NET SqlClient provider instead?
|||Please check the following things:
1) what's the protocol enabled on your server? and your client machine? You must have at least on matching protocols on both sides.
2) any firewall on the server? Try disable firewall and do test to isolate the problem. Port 1433 and file sharing should be on the firewall's exception list.
check this blog for more info: http://blogs.msdn.com/sql_protocols
|||
OK here's the problem...
I found out from my lovely network administrator earlier that in fact the service packs weren't installed as she thought. Once these service packs were installed we had access. Don't you just love it when something isn't done that supposed to be.
Thank you though for your help.
Dan
No comments:
Post a Comment