Hi,
I have a server (WIN 2000 server), is connected with many clients mostly having Win 2000 Professional OS. My application is developed in VB 6.0 and we have MS SQL Server 2000 DB in our server. All the clients with win 2000 professional have no problem with connecting and accessing my SQL Database. But few of my WIN XP clients don€™t connect to database thru my application. It gives error as follows.
Runtime error
Login Failed for user €˜(null)€™ . Reason: Not associated with a trusted SQL Connection.
I've installed the SQL Server Native Client, and I included the optional SDK components. Only the x86 versions of opends60.lib and sqlncli.lib get installed, not the x64 (or amd64) versions. Any idea where I can get ahold of these?
Hi, I am trying to edit some data from a SQL2000-datasource in ASP.NET 2.0 and have a problem with a column that has bit-data and is used for selection. SQL2005 works fine when declaring <SelectParameters> <asp:Parameter DefaultValue="TRUE" Name="APL" Type="boolean" /> </SelectParameters>When running this code with SQL2000, there are no error-msgs, but after editing a record the "APL"-column looses its value of 1 and is set to 0. Looks like an issue with type-conversion, we've hit incompatibilities between SQL200 and 2005 with bit/boolean several times before. So, how is this done correctly with SQL2000? (I've tried setting the Type to "int16" -> err. Also setting Defval="1" gave an err) ThanksMichael
hello can anybody help me in this issue:-i got two sets of connection string modules, let us say (1) working (2) not working, and here is the code for the two sets:-set (1) which is working fine:- private void OpenData(){System.Data.DataTable dt = new System.Data.DataTable(); // The connection string was not originally hardcoded but for some reason it was staying around when passed // in through the constructor. It was always blank. System.Data.SqlClient.SqlConnection cn = new System.Data.SqlClient.SqlConnection(@"data source=localhost;initial catalog=truckorder;Integrated Security=SSPI;"); //System.Data.SqlClient.SqlConnection cn = new System.Data.SqlClient.SqlConnection(_cnString); cn.Open(); new System.Data.SqlClient.SqlDataAdapter("SELECT * FROM dealers WHERE DealerWeb like '%" + _url + "%'", cn).Fill(dt); if(dt.Rows.Count > 0) {_dealerid = Int32.Parse(dt.Rows[0]["dealerid"].ToString());_dealername = dt.Rows[0]["dealerName"].ToString();_dealerparent = Int32.Parse(dt.Rows[0]["dealerParent"].ToString());_usedMessage = dt.Rows[0]["usedMessage"].ToString();_rentalMessage = dt.Rows[0]["rentalMessage"].ToString();} cn.Close();}----------------------------------------------------------------------------------------------------------------------------------------------------------------------set (2) not working fine:-private void OpenData() { System.Data.DataTable dt = new System.Data.DataTable();System.Data.SqlClient.SqlConnection conn = new System.Data.SqlClient.SqlConnection ();conn.ConnectionString = "integrated security=SSPI;data source=FR011PC;persist security info=False;initial catalog=TruckOrder";
try{conn.Open();new System.Data.SqlClient.SqlDataAdapter("SELECT * FROM dealers WHERE DealerWeb like 'yalevictoria.com.au'", conn).Fill(dt); if(dt.Rows.Count > 0){_dealerid = Int32.Parse(dt.Rows[0]["dealerid"].ToString());_dealername = dt.Rows[0]["dealerName"].ToString();_dealerparent = Int32.Parse(dt.Rows[0]["dealerParent"].ToString());_usedMessage = dt.Rows[0]["usedMessage"].ToString();_rentalMessage = dt.Rows[0]["rentalMessage"].ToString(); _dealerWeb = dt.Rows[0]["dealerWeb"].ToString();}} finally {conn.Close();}THE DIFFERENCE IN BOTH THE SETS IS :- The Connection String (if you look at carefully) the one which is working has localhost and the one which is not working is having FR011PC (this code is working fine on FR011PC machine name and SqlServer Name) BUTwhen i transfer FR011PC code to the localhost machine, I mean i changed to datasource from FR011PC to localhost and run its giving me SQL SERVER DOESN'T EXIST OR ACCESS DENIED.Can any body help me on this issue has this is urgent for me please...................
I have the following situation: A webserver in a DMZ which connects to a DbServer in a Domain.
but when I try to make a ODBC connection on the webserver I get the well-known "Server does not exist or access denied" error.
I tried using IP address as well as FQDN. I turned off the firewall in the router (I'm able to access shares and what not from the webserver so the firewall is really turned off).
I think however i have narrowed down the problem to the TCP/IP connection of the SQL Server. Normally when you try from a command prompt "telnet dbserver 1433" you get a connection. But when I try this to the specific DbServer I get an "unable to connect" error. Even when I try it on the dbserver itself (so telnet localhost 1433). This should work always?
In the network configuration of the sql server the Named Piped as well as the TCP/IP protocols are enabled. TCP/IP is offcourse configured on port 1433.
I want to give a client access to a SQL Server 7 database sitting on a different NT domain without setting up a trust relationship between the two domains. Has anyone tried doing this?
The reason I want to put an ip address on connection string i just want to create connection strings as people do in their work. When the app tried access the connection string it gives the error in the attachment.
Because I haven't used this user/password for a long time I'm pretty sure the user name and password is correct but i have the following questions
1. Assume the user and password is incorrect, is there way to reset this? 2. what other configuration that i need to do in order to make teh C# app access this Database?
If I give the user access dbo on 1 of the database, when he logon using SQL Server Management Studio for running query etc, can he only see his database instead of other as well system database?
Is there any best practise in term of setting the SQL client for 2005?
I can't get the OLAP Manager to install on my client PC running Windows95. It does install on the server running NT4.0. I want to remotely administer the OLAP, just like I do with the Enterprise Manager on the client. Anyone have any suggestions? Do you have to have NT on the client?
Primary platform is XP as client side and 2003 as server.
When I press F5 in order to see my report from IE appears this error:
An error has occurred during report processing. (rsProcessingAborted) Cannot create a connection to data source 'SQL1.BDADMIN'. (rsErrorOpeningConnection) For more information about this error navigate to the report server on the local server machine, or enable remote errors
However, preview button works properly and data are showed. Let me know where am I failing.
I am a VB6 programmer and I'm really new to SQL Express, I have always used ACCESS because it was so easy to deploy. I've now written a VB6 program which uses SQL Express and I want to know how to deploy it. Basically my PC will host the SQL database as it has SQL Express loaded onto it. I now want to install my EXE onto other Client's PC and have them read/write to the database on my machine.
Besides the EXE program, what software do I need to load onto the Client's PC so they can access my SQLExpress database...? (eg: Net Framework, SQLExpress, etc).
Also, if my machine is called ABC123, in my connectionstring do I just put in
ABC123sqlexpress as the datasource..?. Will this be enough for the other PCs to connect to mine ?
I've installed SQL 2005 Express, enabled local and Remote connections but my client app cannot connect to the SQL server. I'm getting access denied or SQL does not exists. Any idea's on how to resolve this issue?
I have a quick question regarding domains and workgroups.
Currently I am working on an issue in the office of a small business. Right now there are 3 client computers that connect to a dell server running windows std. server 2003. The server has sql running on it that takes care of the invoicing system. Two out of the three work stations are able to use the database fine, but there is one that is unable to connect to the database. The only different that I could find is that the two workstations that DO work are currently set to use a workgroup, whereas the one workstation that does NOT work is set to use a domain...... I tried switching that computer to workgroup, but then I was unable to login as the normal user that I had always logged in as before.....
What can I do to solve this dilemma?
Any help would be greatly appreciated!
I apologize if this is the wrong forum for this, and if it is, if someone would point me to the correct one I would appreciate it.
We recently migrated from SQL Server 7 to SQL Server 2005. Now there's a curious thing with some legacy applications. I have pasted some code below. Don't judge me, because like I said, it's legacy.
You can see, that I have two connection strings. One is commented and accessing via SQL Native Client. The other one is doing this through the old SQL Server driver. Funnily enough, when I use the new Native Client driver, the exception "Run-time error '-2147467259 (80004005)' [Microsoft][SQL Native Client]Invalid attribute value" is thrown in the rsPorder2.Update line. With the old driver, this works just alright.
Is this a bug? Is there a way, to make the code run, because we don't want to search the whole application for other occurances, if not necessary.
Any insights would be greatly appreciated.
Best regards, DD
Dim ilinx As New ADODB.Connection Dim rsPorder As New ADODB.Recordset Dim rsPorder2 As New ADODB.Recordset Dim cmdLinx As New ADODB.Command Dim strConn As String
I have a SQL 7 Enterprise Edition production server. I have installed SQL 2000 personal edition on a client station. I wish to use the 2000 tools to view,modify and create objects on the SQL 7 production server. These include stored procs,tables,dts packages etc.
What are the potential pitfalls of this. I am using this strategy to introduce myself to the SQL 2000 enviroment, and perhaps utilise some of its benefits.
using System; using System.Collections.Generic; using System.Text; using System.Data; using System.Data.OleDb; using System.Collections;
namespace TimeTracking.DB { public class sql { OleDbConnection conn;
// //the constructor for this class, set the connectionstring // public sql() { DBConnectionstring ConnectToDB = new DBConnectionstring(); conn = ConnectToDB.MyConnection(); }
// // // public void UpdateEntry(int ID, string Week, string Year, string Date, string Project, string Action, string Time, string Comment) { int m_ID = ID; int m_Week = (Convert.ToInt32(Week)); int m_Year = (Convert.ToInt32(Year)); string m_Date = Date; string m_Project = Project; int m_ProjectID = new int(); string m_Action = Action; int m_ActionID = new int(); Single m_Time = (Convert.ToSingle(Time)); string m_Comment = Comment;
// //get the project ID from the database and store it in m_ProjectID // OleDbCommand SelectProjectID = new OleDbCommand("SELECT tblProject.ProjectID FROM tblProject" + " WHERE (((tblProject.Project) LIKE @Project))", conn);
// //get the action ID from the database and store it in m_ActionID // OleDbCommand SelectActionID = new OleDbCommand("SELECT tblAction.ActionID FROM tblAction" + " WHERE (((tblAction.Action) LIKE @Action))", conn);
finally { //close the connection if (conn != null) { conn.Close(); } } } } }
Code Snippet
The update statement is not working in my application, no error in C# and no error in ms-access. When I paste the update query into the ms-access query tool and replace the parameter values (@....) with real values, is will update the record.
I am accessing a SQL2005 Express SP1 Server via TCP/IP (all machines fully up to date with windows update). For ease of configuration the Server IP is mapped to an Alias in Native Client Configuration Manager. On the Client Force Protocol Encryption is set to Yes and Trust Server Certificate is set to No. The clients are accessing the DB via SQL 2005 Management studio express and Ms Access 2003 (an access adp front end to the sql database).
As a test i turned off force encryption on the server. A Network trace shows no encryption! Turning on force encryption on the server corrects this.
As a further test I configured the server with a certificate the client doesn't trust. No error is generated by the un-trusted certificate! The only way to generate the certificate error is to enable encryption in the connection properties of each application. Why isn't the Native Client Configuration Manager utility enforcing this???
This brings me on to a second (off-topic problem). In my access adp file, if I enable €œuse encryption for data€? advanced option under the database connection dialog all works as expected (encryption + certificate verification). However, I am programmatically updating the connection in VBA
Application.CurrentProject.OpenConnection "Provider=SQLOLEDB.1;Data Source=AliasName;Use Encryption for Data=True;..."
If I do this no encryption is enabled!!! Access seems to just ignore the encryption statement.
Has anybody got any ideas as to why either of these issues are occurring or if there are any workarounds?
According to MS Knowledge Base Article 269824, "[SQL Server 2000 ClientTools] ... must be installed ... on any computer on which someone may makedesign changes in an Access project to a SQL Server 2000 database".This is the situation I'm facing. Can I download these Client Tools andinstall them for free, or are they only available on the SQL Server 2000Installation CD?Thanks for any help!
I have SQL Server2005 client in my system,I am able to connect SQL Server 2000,but I am unable to create DTS packages.2005 client not at all showing Local packages icon to create package.
any body experianced with this Please guide me ragarding.
Hi guys,I'm not sure if I'm just bad at googling but I can't seem to find a way to set an ASP.NET 2.0 web application to connect to SQL Server 2005 using the current client's user credentials. My web application is using Integrated Windows Authentication so its Page.User.Identity is set to a DOMAINusername value... I want to pass that to my connectionstring or have my connections pick up the identity automatically and use that Identity when accessing the db server.Oh and another thing, my IIS Application Pool is using a specific Identity itself, so I don't know if that might affect the above.Hope someone could help.
When you connect to SQL Server using SQLConnection, how to set client machine name(or IP address) so that you can monitor the process on Server side using Enterprise Manager?
I'm trying to remember how to install the SQL 2000 client tools onto a SQL 2005 server. There are a couple of bizarre steps that will allow this to happen, but I can't for the life of me remember what comes after the unicycle down the stairs with the umbrella stand of machetes.
Can anybody remember the magic, or do I resort to using VPC to kludge the install until I can find my clay tablets again?
I'm having difficulties when connecting to our SQL server 2000 from my SQL Server Mgmt Studio 2005. I can't create tables and columns due to permission errors. But from 2000 (on a different machine) it works fine. *Sometimes* even when I log in with my AD account it won't let me in and complains that user 'null' is not authorized to log in...
Anyway, I've installed both SP1 and SP2 and the problem still persists.
Any help is appreciated.
P.S> I tinstalled SQL 2000 on my machine but that didn't help either; I guess the 2005's configurations are being read by 2000.
I have recently installed SQL 2005 client tools with SQL Server Management Studio and accessing databases on a SQL 2000 server. The response I am getting is extremely slow. Should I go back to SQL 2000 client or are there methods by which I can improve the performance.
I have a 500-MB full installation CD for SQL Server 2000. All I needis to install "Client Connectivity" component (about 272K) on a bunchof workstations for users across the nation.How do I reduce the installation file size, by eliminating most of theunwanted files?Thanks.
I am trying to create several Excel sheets using SQL 2000 views like so:
Select * INTO [Excel 8.0;Database="C:spreadSheetsaNew.xls"] FROM [aView].
When I try and execute this in my app I get the following - Specified owner name 'Excel 8.0;Database=c:spreadSheetsaNew.xls' either does not exist or you do not have permission to use it.
If I use the above Select statement with an OLEDB connection it works.
I am using Imports System.Data.SqlClient, instantiating a new SQlConnection object, opening the connection, etc..
Hi, A quick Q for all the Sql Server 2000 beta testers out there. Does anyone know of any problems associated with using SS2000 Enterprise Manager with a SS7 backend running SP2? In particular, I'm keen to try out the Tsql debugger features, if they'll work with SS7.
Many thanks in advance, Jon Reade, Sql Server 7 DBA NEC Technologies (UK) Ltd Telford, Shropshire.
I recently had configured my Web Server based on Windows 2003 Server and IIS 5x. I'd also installed SQL Server 2005 into this. Now I want toc onfigure this SQL Server, so that my client can access their database through a DNS name. I request you all for your kind support in this regard. Thanks in advance.
I recently have configured my Web Server based on Windows 2003 Server and IIS 5x. I'd also installed SQL Server 2005 into this. Now I want toc onfigure this SQL Server, so that my client can access their database through a DNS name. I request you all for your kind support in this regard. Thanks in advance.
