.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Register
 
Win Surprise Gifts!!!
Congratulations!!!


Top 5 Contributors of the Month
Easy Web
Imran Ghani
Post New Web Links

Connect VB6 app to SQL server 2005

Posted By:      Posted Date: September 20, 2010    Points: 0   Category :Sql Server
 

Hi,

I have a VB6 app that has to connect to SQL server 2005 located on another machine.
Now I use a connection string like this

"Provider=SQLOLEDB.1;Persist Security Info=False;Initial Catalog=test1;Network=DBMSSOCN;Server=100.100.100.100;Integrated Security=SSPI"
and it works from my laptop.

The question is, when I move the VB6 app to another machine, what do I need installed there for the same connection string to work?
What stays behind "Provider=SQLOLEDB.1" ?
Is it a single .dll that I only have to put on the other machine and regsvr32 , or it's something more complex?

Thanks




View Complete Post


More Related Resource Links

Can't connect to SQL 2005 Enterprise using Management Studio with Server Name (only (local) works

  
This is a test system, everything running locally & no domains. Win 2003 Ent. Server & SQL Server 2005 Enterprise. I can't log into SQL Server Management Studio using the server name & using either Windows Authentication or SQL login. If I change the name of the server in the drop-down list to "(local)", I connect just fine (both Windows & SQL security modes). Shared Memory, Named Pipes & TCP/IP enabled in both server & client. Remote connections allowed. I have IP adresses (both 127.0.0.1 & external IP) in my hosts file pointing to the server name. Does SQL require a DNS server? This wouldn't be a problem except for the fact that I can't install SQL 2005 SP3 due to authentication failure since there's no way to enter (local) as the server name. SQL tools (management studio, SP install) seem to see the SQL server running but won't authenticate the user through any means other than setting server name to (local). This is driving me crazy!!!

Unable to connect to SQL Server 2005 remotly, all client protocols are blank

  
I have an installation of SQL 2005 and had issues connecting remotly. Looking at the client protocolols, they are all blank. I can see that TCPIP, Named Pipes, VIA, etc. are 'enabled', but where the words 'TCPIP', 'Names Pipes', etc. should be, it's just blank. I tried to install SQL 2008R hoping the Client Protocols would be corrected during the installaion, but they were not. I'm assuming the issue with the Client Protocols not showing up is a symptom of the problem. Does anyone have any ideas? Thanks!

Connect SQL Server 2005 to Ms Access on another computer

  
I'm trying to create a "Linked Server" on my SQL Server 2005.  This linked server is a reference to an Access File on a remote computer.  I've set up all the permissions and shared resources.  I've created an ODBC DSN to connect to the database.  If i open the DSN in excel, i can retrieve data.  If I open a linked server connected to the DB I get the following error when i try to run a query against it.   ------------------ OLE DB provider "MSDASQL" for linked server "LS_Specialty" returned message "[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed". OLE DB provider "MSDASQL" for linked server "LS_Specialty" returned message "[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed". OLE DB provider "MSDASQL" for linked server "LS_Specialty" returned message "[Microsoft][ODBC Microsoft Access Driver] The Microsoft Jet database engine cannot open the file '(unknown)'.  It is already opened exclusively by another user, or you need permission to view its data.". Msg 7303, Level 16, State 1, Line 1 Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "LS_Specialty". ---------------------   Why does this DSN work in Excel and Access, but not in SQL

SOS: Cannot connect to SQL Server 2005 locally by Windows Authentication DOMAIN \ myname. But networ

  
Cannot connect to SQL Server 2005 locally by Windows Authentication DOMAIN \ myname. But network connection is successful.   But SQL Server Logins contain   BUILTIN \ Administrators, and                                                    BUILTIN \  Administrators contain DOMAIN \ Domain Admins, and                                                    DOMAIN \ Domain Admins contain DOMAIN \ myname.   Creating SQL Server Login with DOMAIN \ myname entail successful local connection.   Removing SQL Server Login with DOMAIN \ myname and creating SQL Server Login with DOMAIN \ Domain Admins do NOT entail successful connection. Cannot connect! System:   Windows Server 2008. Error 18456

Cannot connect to SQL Server 2005 locally by Windows Authentication, but network connection is succe

  
Cannot connect to SQL Server 2005 locally by Windows Authentication DOMAIN \ myname. But network connection is successful.   But SQL Server Logins contain   BUILTIN \ Administrators, and                                                    BUILTIN \  Administrators contain DOMAIN \ Domain Admins, and                                                    DOMAIN \ Domain Admins contain DOMAIN \ myname.   Creating SQL Server Login with DOMAIN \ myname entail successful local connection.   Removing SQL Server Login with DOMAIN \ myname and creating SQL Server Login with DOMAIN \ Domain Admins do NOT entail successful connection. Cannot connect!                                     &

Recommend the best JDBC driver and version to connect to SQL server 2005 sp2

  

SQL version details:Microsoft SQL Server 2005 - 9.00.3050.00 (Intel X86) Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2) on a clustered server.

Are there any issues using:

JDBC driver: Microsoft SQL Server JDBC Driver 3.0.
JBOSS: JBoss 4.2.3 with JDK 6 ?


how to connect my hosting database from my pc using sql server management studio 2005

  

Hi..

I have one asp.net hosting account with some service provider.. 

They have given me some xxx.xxxxxx.com to access sql server from my desktop... 

I enter xxx.xxxxx.com in server name and username and password but it will not connect.. 

so please let me know what are the steps i have to do to access my hosting database...

they have given sql server 2008 im using in local sql server 2005 management studio so let me know how to connect

thanks in advance


Access 2007 upsizing wizard can't connect to SQL Server 2005 Express

  
Hi,

When trying to use the Access 2007 upsizing wizard to move a database to SQL Server 2005 Express, I get the following error message:

Connection failed:
SQLState: '01000'
SQL Server Error: 2
[Microsoft][ODBC SQ Server Driver][Share
Memory][ConnectionOpen(Connect()).
Connection failed:
SQLState:'08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][Shared Memory]SQL Server
does not exist or access denied.

I get the same message regardless of whether I configure SQL Server to run as a local system or service.

I am the only user on my Vista 32 PC and am therefore the administrator. As far as I can tell I have sufficient authority since I can start and stop SQL Server.

As a newbie to all this, I can't find any step by step instructions as to how a local copy of SQL Server should be configured to work with the upsizing wizard. In fact I can't even find any Access 2007 help walk-throughs on this upsizing wizard, let alone troubleshooting its error messages.

Any help would be appreciated, as well as links to step by step instructions (which I can't find in the MSDN Library materials).

Thanks!
Richard
PS Does MS understand how inadequate and inefficient its built-in documentation really is? Maybe that's what keeps MS Press in business!

windows 7 can't connect to SQL Server 2005

  

This is quite the odd problem, or at least that's how it seems.   I have a brand new installation of Windows 7 x64 as my dev machine.  I am having issues with connecting to instances of SQL2005 SP2.   We'll call them LOCAL_NETWORK_SQL and VPN_SQL, and they are both named instances.

From my Win7 machine, I can connect to LOCAL_NETWORK_SQL using Management Studio.  I can NOT connect to it using any SqlConnection through .NET.  This fails with..

"A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified"

I can NOT connect to VPN_SQL using either Management Studio OR a .NET SqlConnection; it fails with the same error (above) in both cases

I CAN connect to LOCAL_NETWORK_SQL using OSQL

I CAN connect to other SQL server instances ( SQL2005 SP3) that are on the same VPN network/domain as VPN_SQL using either Management Studio OR .NET SqlConnection.

I CAN connect to a named instance that is hosted locally on my dev machine (SQL2008 Express)

This seems a little bit like the issue described here http://social.msdn.

Cannot connect to Sql server 2005 database engine

  
Hello everybody!

I am having problems to connect to Sql Server Database Engine. I have recently(yesterday) installed Sql Server 2005 Developer Edition. The installation was totally successfull. Yesterday I was able to connect to Sql Server Database engine via SSMS but today it gives me an error:

A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.) (Microsoft SQL Server, Error: 233)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=233&LinkId=20476

It is strange because only one day before It worked fine.

Thanks a lot



When connect to local sql server 2005 to online sql server 2008

  

OLE DB provider "SQLNCLI" for linked server "xx.xxx.xxx.xxx" returned message "The partner transaction manager has disabled its support for remote/network transactions.".
Msg 7391, Level 16, State 2, Procedure reminder, Line 5
The operation could not be performed because OLE DB provider "SQLNCLI" for linked server "xx.xxx.xxx.xxx" was unable to begin a distributed transaction.

OLE DB provider "SQLNCLI" for linked server "xx.xxx.xxx.xxx" returned message "The partner transaction manager has disabled its support for remote/network transactions.".

Msg 7391, Level 16, State 2, Procedure reminder, Line 5

The operation could not be performed because OLE DB provider "SQLNCLI" for linked server "xx.xxx.xxx.xxx" was unable to begin a distributed

[SQL-DMO] You must use SQL Server 2005 management tools to connect to this server

  

The application I'm using is throwing an error when trying to connect so SQL Server 2005.

 

If I go to Administrative Tools, Computer Management, Services and Applications, Microsoft SQL Servers, 2005 Server, I get this message:

 

A connection could not be established to [server name].

Reason: [SQL-DMO] You must use SQL Server 2005 management tools to connect to this server.

Please verify SQL Server is running and check your SQL Server registration properties and try again.

 

I have SQL 2000 and SQL 2005 installed on my pc.  I'm not having any problems with 2000.


Cannot connect Visual Studio 2008 to Sql Server 2005

  

I have Windows 7 and installed Visual Studio 2008 Pro and also installed SQL server developer addiotion that comes with VS. After creating a test database in SQL maangement studio and adding the standard asp.net membership provider tables with the aspnet_regsql tool, I created a web project and added a connection string to the web.config file to connect to the database.

No matter what, I cannot connect to the database.

I can create a connection through the server explorer in visual studio and when I drag a sqldatasource onto my page and configure it I can connect to the database etc. But no web.config connection.

This worked on my XP pro machine but not Windows 7.

Has anybody had this problem and what am I doing wrong.

thanks


Unable to connect to SQL Server 2005 on Windows 7 64-bit

  

On client site, I am working on a PC running Window 7 64-bit. Prior to me using it, Visual Studio 2010 was installed. As a default installation was done, SQL Express 2008 was installed. I have since installed SQL 2005 Developer Edition. The installation proceeded without error, however I am unable to connect from SQL Server Management Studio. When attempting to connect, the local server connection list is empty.

I have checked that SQL Database services are running.

Any suggestions as how to resolve this problem.


Connect SQL Server 2005 SSMS to SQL Server 2008

  

is it ok to connect to sql server2008 server form sql server 2005 management studio. If yes, can you please let me know what should i do ?


cannot connect to SQL Server 2005 Express

  

Hello

I am in the process of migrating a website running ASP with SQL Server 2000 to SQL Server 2005 Express.

I have installed the data, and fixed the problems with orphaned users (I think).

I can access the data using SQL Server Management Studio Express

However I cannot establish a connection from any of the ASP or ASP.NET applications. At first I thought it was just the connection string (using SQLOLEDB) but then I tried to set up a data source using ODBC with either the SQL Server or SQL Native Client driver. I have tried this on a remote machine (it is set up to allow remote connections), and also on the local server. The "Create a New Data Source" returns with the error "Specified SQL Server Not Found"

I am using (IPAddress)/SQLEXPRESS as the server name (I have also tried localhost and 127.0.0.1 when trying to connect locally.

When using the "Create New Data Source" locally I have tried connecting as one of the database users, and as sa, and using the local network account (which is used to run SQL Server Management Studio Express.

I have disabled the firewall.

I have checked that TCP/IP is enabled using SQL Server Configuration Manager

Port 1433 is open.

Could anyone assist me in this ?

Thank you in advance

RL


SQL Server 2005 Try and Catch Exception Handling

  
I'm pretty excited to see that there is some real error handling for T-SQL code in SQL Server 2005. It's pretty painful to have your wonderfully architected .NET solution tainted by less-than-VBScript error handling for stored procedures in the database. The big difference being the addition of TRY..CATCH blocks. Let's take a look:
Categories: 
ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend