Connect to SQL Server: install

Showing posts with label install. Show all posts

Tuesday, March 27, 2012

Connecting to SQL Server 2005

Hello!
I was wondering if I need to install something on the client in order to
establish ODBC/OLEDB connection to SQL Server 2005. Currently, I have ADO
2.6 installed. Are there any changes in ODBC/OLEDB drivers for SQL Server
2005?
Thanks,
IgorHi
It is best to use MDAC 2.8, but 2.6 will connect to SQL Server 2005, but you
will not be able to use the new datatypes that SQL Server 2005 has
introduced.
The ODBC/OLEDB drivers no longer ship with SQL Server, as it is now a
function of the Operating System to update them.
The new way to connect to SQL Server 2005 is SQL Native Client (SQLNCLI)
"Provider=SQLNCLI"
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"imarchenko" <igormarchenko@.hotmail.com> wrote in message
news:ulvm%23pcCGHA.2300@.TK2MSFTNGP15.phx.gbl...
> Hello!
> I was wondering if I need to install something on the client in order
> to establish ODBC/OLEDB connection to SQL Server 2005. Currently, I have
> ADO 2.6 installed. Are there any changes in ODBC/OLEDB drivers for SQL
> Server 2005?
> Thanks,
> Igor
>|||"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:%2326c1IiCGHA.3984@.TK2MSFTNGP14.phx.gbl...
> Hi
> It is best to use MDAC 2.8, but 2.6 will connect to SQL Server 2005, but
> you will not be able to use the new datatypes that SQL Server 2005 has
> introduced.
> The ODBC/OLEDB drivers no longer ship with SQL Server, as it is now a
> function of the Operating System to update them.
> The new way to connect to SQL Server 2005 is SQL Native Client (SQLNCLI)
> "Provider=SQLNCLI"
>
This is not quite right. MDAC is part of the operating system, but SQL
Native Client is not.
The SQL Native Client is a seperate install. It is included in the SQL
Server distribution and available here:
http://msdn.microsoft.com/data/sqlnative/default.aspx
There are now 3! OleDb providers for SQL Server. Two in MDAC: MSDASQL
(deprecated) and SQLOLEDB (current). Plus one in the SQL Native Client
(SQLNCLI). SQLNCLI is the best, but you must install it.
SQL Native Client also has a new ODBC driver.
David|||David,
I am able to connect to SQL Server 2005 using SQL Native Client but
I got en error 'Server unavailable or access denied ...' when trying to
connect using Microsoft OLE DB provider for SQL Server. I am trying to
connect by setting up properties of UDL file on the same box where SQL
Server is installed. Did I get it right that I have to install latest
drivers on client computers from the link your provided?
Thanks,
Igor
"David Browne" <davidbaxterbrowne no potted meat@.hotmail.com> wrote in
message news:O$2MO8jCGHA.2664@.TK2MSFTNGP15.phx.gbl...
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:%2326c1IiCGHA.3984@.TK2MSFTNGP14.phx.gbl...
> This is not quite right. MDAC is part of the operating system, but SQL
> Native Client is not.
>
> The SQL Native Client is a seperate install. It is included in the SQL
> Server distribution and available here:
> http://msdn.microsoft.com/data/sqlnative/default.aspx
> There are now 3! OleDb providers for SQL Server. Two in MDAC: MSDASQL
> (deprecated) and SQLOLEDB (current). Plus one in the SQL Native Client
> (SQLNCLI). SQLNCLI is the best, but you must install it.
> SQL Native Client also has a new ODBC driver.
> David
>|||David,
I wa able to connect by enabling remote connections using Surface Area.
Thanks,
Igor
"imarchenko" <igormarchenko@.hotmail.com> wrote in message
news:%23t2FLdxCGHA.724@.TK2MSFTNGP10.phx.gbl...
> David,
> I am able to connect to SQL Server 2005 using SQL Native Client but
> I got en error 'Server unavailable or access denied ...' when trying to
> connect using Microsoft OLE DB provider for SQL Server. I am trying to
> connect by setting up properties of UDL file on the same box where SQL
> Server is installed. Did I get it right that I have to install latest
> drivers on client computers from the link your provided?
> Thanks,
> Igor
>
> "David Browne" <davidbaxterbrowne no potted meat@.hotmail.com> wrote in
> message news:O$2MO8jCGHA.2664@.TK2MSFTNGP15.phx.gbl...
>

Connecting to SQL Server 2005

Hello!
I was wondering if I need to install something on the client in order to
establish ODBC/OLEDB connection to SQL Server 2005. Currently, I have ADO
2.6 installed. Are there any changes in ODBC/OLEDB drivers for SQL Server
2005?
Thanks,
Igor
Hi
It is best to use MDAC 2.8, but 2.6 will connect to SQL Server 2005, but you
will not be able to use the new datatypes that SQL Server 2005 has
introduced.
The ODBC/OLEDB drivers no longer ship with SQL Server, as it is now a
function of the Operating System to update them.
The new way to connect to SQL Server 2005 is SQL Native Client (SQLNCLI)
"Provider=SQLNCLI"
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"imarchenko" <igormarchenko@.hotmail.com> wrote in message
news:ulvm%23pcCGHA.2300@.TK2MSFTNGP15.phx.gbl...
> Hello!
> I was wondering if I need to install something on the client in order
> to establish ODBC/OLEDB connection to SQL Server 2005. Currently, I have
> ADO 2.6 installed. Are there any changes in ODBC/OLEDB drivers for SQL
> Server 2005?
> Thanks,
> Igor
>
|||"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:%2326c1IiCGHA.3984@.TK2MSFTNGP14.phx.gbl...
> Hi
> It is best to use MDAC 2.8, but 2.6 will connect to SQL Server 2005, but
> you will not be able to use the new datatypes that SQL Server 2005 has
> introduced.
> The ODBC/OLEDB drivers no longer ship with SQL Server, as it is now a
> function of the Operating System to update them.
> The new way to connect to SQL Server 2005 is SQL Native Client (SQLNCLI)
> "Provider=SQLNCLI"
>
This is not quite right. MDAC is part of the operating system, but SQL
Native Client is not.
The SQL Native Client is a seperate install. It is included in the SQL
Server distribution and available here:
http://msdn.microsoft.com/data/sqlnative/default.aspx
There are now 3! OleDb providers for SQL Server. Two in MDAC: MSDASQL
(deprecated) and SQLOLEDB (current). Plus one in the SQL Native Client
(SQLNCLI). SQLNCLI is the best, but you must install it.
SQL Native Client also has a new ODBC driver.
David
|||David,
I am able to connect to SQL Server 2005 using SQL Native Client but
I got en error 'Server unavailable or access denied ...' when trying to
connect using Microsoft OLE DB provider for SQL Server. I am trying to
connect by setting up properties of UDL file on the same box where SQL
Server is installed. Did I get it right that I have to install latest
drivers on client computers from the link your provided?
Thanks,
Igor
"David Browne" <davidbaxterbrowne no potted meat@.hotmail.com> wrote in
message news:O$2MO8jCGHA.2664@.TK2MSFTNGP15.phx.gbl...
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:%2326c1IiCGHA.3984@.TK2MSFTNGP14.phx.gbl...
> This is not quite right. MDAC is part of the operating system, but SQL
> Native Client is not.
>
> The SQL Native Client is a seperate install. It is included in the SQL
> Server distribution and available here:
> http://msdn.microsoft.com/data/sqlnative/default.aspx
> There are now 3! OleDb providers for SQL Server. Two in MDAC: MSDASQL
> (deprecated) and SQLOLEDB (current). Plus one in the SQL Native Client
> (SQLNCLI). SQLNCLI is the best, but you must install it.
> SQL Native Client also has a new ODBC driver.
> David
>
|||David,
I wa able to connect by enabling remote connections using Surface Area.
Thanks,
Igor
"imarchenko" <igormarchenko@.hotmail.com> wrote in message
news:%23t2FLdxCGHA.724@.TK2MSFTNGP10.phx.gbl...
> David,
> I am able to connect to SQL Server 2005 using SQL Native Client but
> I got en error 'Server unavailable or access denied ...' when trying to
> connect using Microsoft OLE DB provider for SQL Server. I am trying to
> connect by setting up properties of UDL file on the same box where SQL
> Server is installed. Did I get it right that I have to install latest
> drivers on client computers from the link your provided?
> Thanks,
> Igor
>
> "David Browne" <davidbaxterbrowne no potted meat@.hotmail.com> wrote in
> message news:O$2MO8jCGHA.2664@.TK2MSFTNGP15.phx.gbl...
>

Connecting to SQL Server 2005

Hello!
I was wondering if I need to install something on the client in order to
establish ODBC/OLEDB connection to SQL Server 2005. Currently, I have ADO
2.6 installed. Are there any changes in ODBC/OLEDB drivers for SQL Server
2005?
Thanks,
IgorHi
It is best to use MDAC 2.8, but 2.6 will connect to SQL Server 2005, but you
will not be able to use the new datatypes that SQL Server 2005 has
introduced.
The ODBC/OLEDB drivers no longer ship with SQL Server, as it is now a
function of the Operating System to update them.
The new way to connect to SQL Server 2005 is SQL Native Client (SQLNCLI)
"Provider=SQLNCLI"
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"imarchenko" <igormarchenko@.hotmail.com> wrote in message
news:ulvm%23pcCGHA.2300@.TK2MSFTNGP15.phx.gbl...
> Hello!
> I was wondering if I need to install something on the client in order
> to establish ODBC/OLEDB connection to SQL Server 2005. Currently, I have
> ADO 2.6 installed. Are there any changes in ODBC/OLEDB drivers for SQL
> Server 2005?
> Thanks,
> Igor
>|||"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:%2326c1IiCGHA.3984@.TK2MSFTNGP14.phx.gbl...
> Hi
> It is best to use MDAC 2.8, but 2.6 will connect to SQL Server 2005, but
> you will not be able to use the new datatypes that SQL Server 2005 has
> introduced.
> The ODBC/OLEDB drivers no longer ship with SQL Server, as it is now a
> function of the Operating System to update them.
> The new way to connect to SQL Server 2005 is SQL Native Client (SQLNCLI)
> "Provider=SQLNCLI"
>
This is not quite right. MDAC is part of the operating system, but SQL
Native Client is not.
The SQL Native Client is a seperate install. It is included in the SQL
Server distribution and available here:
http://msdn.microsoft.com/data/sqlnative/default.aspx
There are now 3! OleDb providers for SQL Server. Two in MDAC: MSDASQL
(deprecated) and SQLOLEDB (current). Plus one in the SQL Native Client
(SQLNCLI). SQLNCLI is the best, but you must install it.
SQL Native Client also has a new ODBC driver.
David|||David,
I am able to connect to SQL Server 2005 using SQL Native Client but
I got en error 'Server unavailable or access denied ...' when trying to
connect using Microsoft OLE DB provider for SQL Server. I am trying to
connect by setting up properties of UDL file on the same box where SQL
Server is installed. Did I get it right that I have to install latest
drivers on client computers from the link your provided?
Thanks,
Igor
"David Browne" <davidbaxterbrowne no potted meat@.hotmail.com> wrote in
message news:O$2MO8jCGHA.2664@.TK2MSFTNGP15.phx.gbl...
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:%2326c1IiCGHA.3984@.TK2MSFTNGP14.phx.gbl...
>> Hi
>> It is best to use MDAC 2.8, but 2.6 will connect to SQL Server 2005, but
>> you will not be able to use the new datatypes that SQL Server 2005 has
>> introduced.
>> The ODBC/OLEDB drivers no longer ship with SQL Server, as it is now a
>> function of the Operating System to update them.
>> The new way to connect to SQL Server 2005 is SQL Native Client (SQLNCLI)
>> "Provider=SQLNCLI"
> This is not quite right. MDAC is part of the operating system, but SQL
> Native Client is not.
>
> The SQL Native Client is a seperate install. It is included in the SQL
> Server distribution and available here:
> http://msdn.microsoft.com/data/sqlnative/default.aspx
> There are now 3! OleDb providers for SQL Server. Two in MDAC: MSDASQL
> (deprecated) and SQLOLEDB (current). Plus one in the SQL Native Client
> (SQLNCLI). SQLNCLI is the best, but you must install it.
> SQL Native Client also has a new ODBC driver.
> David
>|||David,
I wa able to connect by enabling remote connections using Surface Area.
Thanks,
Igor
"imarchenko" <igormarchenko@.hotmail.com> wrote in message
news:%23t2FLdxCGHA.724@.TK2MSFTNGP10.phx.gbl...
> David,
> I am able to connect to SQL Server 2005 using SQL Native Client but
> I got en error 'Server unavailable or access denied ...' when trying to
> connect using Microsoft OLE DB provider for SQL Server. I am trying to
> connect by setting up properties of UDL file on the same box where SQL
> Server is installed. Did I get it right that I have to install latest
> drivers on client computers from the link your provided?
> Thanks,
> Igor
>
> "David Browne" <davidbaxterbrowne no potted meat@.hotmail.com> wrote in
> message news:O$2MO8jCGHA.2664@.TK2MSFTNGP15.phx.gbl...
>> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
>> news:%2326c1IiCGHA.3984@.TK2MSFTNGP14.phx.gbl...
>> Hi
>> It is best to use MDAC 2.8, but 2.6 will connect to SQL Server 2005, but
>> you will not be able to use the new datatypes that SQL Server 2005 has
>> introduced.
>> The ODBC/OLEDB drivers no longer ship with SQL Server, as it is now a
>> function of the Operating System to update them.
>> The new way to connect to SQL Server 2005 is SQL Native Client (SQLNCLI)
>> "Provider=SQLNCLI"
>>
>> This is not quite right. MDAC is part of the operating system, but SQL
>> Native Client is not.
>>
>> The SQL Native Client is a seperate install. It is included in the SQL
>> Server distribution and available here:
>> http://msdn.microsoft.com/data/sqlnative/default.aspx
>> There are now 3! OleDb providers for SQL Server. Two in MDAC: MSDASQL
>> (deprecated) and SQLOLEDB (current). Plus one in the SQL Native Client
>> (SQLNCLI). SQLNCLI is the best, but you must install it.
>> SQL Native Client also has a new ODBC driver.
>> David
>

Connecting to SQL Server & XP Service Pack 2

I installed XP Service Pack 2 on my desktop machine which had SQL Server 2000
running on it prior to the install. I have a C# web application that runs
against a local SQL Server database which I cannot get to work now that I
have installed the XP service pack. I have read all of the Microsoft "HOW To"
documents about configuring SQL Server for the Service Pack but I still
cannot get the Web Appliation to communicate with the database. I always get
the "SQL Server does not exist or access denied." error message. I have tried
the following:
1. Added Port 1433 (TCP/IP) to the Firewall Exception List (1433 is the
static port SQL Server is using)
2. Added Port 445 (TCP/IP) to the Firewall Exception List
3. Added the sqlserver.exe file to the Firewall Exception List
The database connection string I am using in the web application is:
server=local;uid=sa;pwd=<password>;database=Resear ch
At this point I am not sure what else to try. I cannot connect to the
database if the Firewall is turned off. Should this be the case? Any
assistance is much appreciated.
Sincerely,
Tom Hessen
Hi Tom,
I had the same problem and decided to look at the other end of the
connection. I was running SQL Server ( Service Pack 2 ). When I upgraded
to SQL Server ( Service Pack 3a ) everything started working again.
"Tom Hessen" <Tom Hessen@.discussions.microsoft.com> wrote in message news:<645A76F5-D701-4411-9720-1C6AC67A7ED5@.microsoft.com>...
> I installed XP Service Pack 2 on my desktop machine which had SQL Server 2000
> running on it prior to the install. I have a C# web application that runs
> against a local SQL Server database which I cannot get to work now that I
> have installed the XP service pack. I have read all of the Microsoft "HOW To"
> documents about configuring SQL Server for the Service Pack but I still
> cannot get the Web Appliation to communicate with the database. I always get
> the "SQL Server does not exist or access denied." error message. I have tried
> the following:
> 1. Added Port 1433 (TCP/IP) to the Firewall Exception List (1433 is the
> static port SQL Server is using)
> 2. Added Port 445 (TCP/IP) to the Firewall Exception List
> 3. Added the sqlserver.exe file to the Firewall Exception List
> The database connection string I am using in the web application is:
> server=local;uid=sa;pwd=<password>;database=Resear ch
> At this point I am not sure what else to try. I cannot connect to the
> database if the Firewall is turned off. Should this be the case? Any
> assistance is much appreciated.
> Sincerely,
> Tom Hessen
|||Hi Tom,
I've had a little trouble posting, but hopefully this will get through.
I also did everything you listed below. It did not work for me
either ( for a java client ).
I then decided to look at the other end of the connection. I was running
SQLServer ( Service Pack 2 ). When I upgraded to SQLServer ( Service Pack
3a ) everything started working again.
Hope this helps,
Mike S.
"Tom Hessen" <Tom Hessen@.discussions.microsoft.com> wrote in message news:<645A76F5-D701-4411-9720-1C6AC67A7ED5@.microsoft.com>...
> I installed XP Service Pack 2 on my desktop machine which had SQL Server 2000
> running on it prior to the install. I have a C# web application that runs
> against a local SQL Server database which I cannot get to work now that I
> have installed the XP service pack. I have read all of the Microsoft "HOW To"
> documents about configuring SQL Server for the Service Pack but I still
> cannot get the Web Appliation to communicate with the database. I always get
> the "SQL Server does not exist or access denied." error message. I have tried
> the following:
> 1. Added Port 1433 (TCP/IP) to the Firewall Exception List (1433 is the
> static port SQL Server is using)
> 2. Added Port 445 (TCP/IP) to the Firewall Exception List
> 3. Added the sqlserver.exe file to the Firewall Exception List
> The database connection string I am using in the web application is:
> server=local;uid=sa;pwd=<password>;database=Resear ch
> At this point I am not sure what else to try. I cannot connect to the
> database if the Firewall is turned off. Should this be the case? Any
> assistance is much appreciated.
> Sincerely,
> Tom Hessen
sql sql

Connecting to SQL Server & XP Service Pack 2

I installed XP Service Pack 2 on my desktop machine which had SQL Server 2000
running on it prior to the install. I have a C# web application that runs
against a local SQL Server database which I cannot get to work now that I
have installed the XP service pack. I have read all of the Microsoft "HOW To"
documents about configuring SQL Server for the Service Pack but I still
cannot get the Web Appliation to communicate with the database. I always get
the "SQL Server does not exist or access denied." error message. I have tried
the following:
1. Added Port 1433 (TCP/IP) to the Firewall Exception List (1433 is the
static port SQL Server is using)
2. Added Port 445 (TCP/IP) to the Firewall Exception List
3. Added the sqlserver.exe file to the Firewall Exception List
The database connection string I am using in the web application is:
server=local;uid=sa;pwd=<password>;database=Research
At this point I am not sure what else to try. I cannot connect to the
database if the Firewall is turned off. Should this be the case? Any
assistance is much appreciated.
Sincerely,
Tom HessenHi Tom,
I had the same problem and decided to look at the other end of the
connection. I was running SQL Server ( Service Pack 2 ). When I upgraded
to SQL Server ( Service Pack 3a ) everything started working again.
"Tom Hessen" <Tom Hessen@.discussions.microsoft.com> wrote in message news:<645A76F5-D701-4411-9720-1C6AC67A7ED5@.microsoft.com>...
> I installed XP Service Pack 2 on my desktop machine which had SQL Server 2000
> running on it prior to the install. I have a C# web application that runs
> against a local SQL Server database which I cannot get to work now that I
> have installed the XP service pack. I have read all of the Microsoft "HOW To"
> documents about configuring SQL Server for the Service Pack but I still
> cannot get the Web Appliation to communicate with the database. I always get
> the "SQL Server does not exist or access denied." error message. I have tried
> the following:
> 1. Added Port 1433 (TCP/IP) to the Firewall Exception List (1433 is the
> static port SQL Server is using)
> 2. Added Port 445 (TCP/IP) to the Firewall Exception List
> 3. Added the sqlserver.exe file to the Firewall Exception List
> The database connection string I am using in the web application is:
> server=local;uid=sa;pwd=<password>;database=Research
> At this point I am not sure what else to try. I cannot connect to the
> database if the Firewall is turned off. Should this be the case? Any
> assistance is much appreciated.
> Sincerely,
> Tom Hessen|||Hi Tom,
I've had a little trouble posting, but hopefully this will get through.
I also did everything you listed below. It did not work for me
either ( for a java client ).
I then decided to look at the other end of the connection. I was running
SQLServer ( Service Pack 2 ). When I upgraded to SQLServer ( Service Pack
3a ) everything started working again.
Hope this helps,
Mike S.
"Tom Hessen" <Tom Hessen@.discussions.microsoft.com> wrote in message news:<645A76F5-D701-4411-9720-1C6AC67A7ED5@.microsoft.com>...
> I installed XP Service Pack 2 on my desktop machine which had SQL Server 2000
> running on it prior to the install. I have a C# web application that runs
> against a local SQL Server database which I cannot get to work now that I
> have installed the XP service pack. I have read all of the Microsoft "HOW To"
> documents about configuring SQL Server for the Service Pack but I still
> cannot get the Web Appliation to communicate with the database. I always get
> the "SQL Server does not exist or access denied." error message. I have tried
> the following:
> 1. Added Port 1433 (TCP/IP) to the Firewall Exception List (1433 is the
> static port SQL Server is using)
> 2. Added Port 445 (TCP/IP) to the Firewall Exception List
> 3. Added the sqlserver.exe file to the Firewall Exception List
> The database connection string I am using in the web application is:
> server=local;uid=sa;pwd=<password>;database=Research
> At this point I am not sure what else to try. I cannot connect to the
> database if the Firewall is turned off. Should this be the case? Any
> assistance is much appreciated.
> Sincerely,
> Tom Hessen

Monday, March 19, 2012

Connecting to MSDE2000RelA

I was able to install MSDE into WXP and migrated my Access
databases through Windows Integrated Authentication Method.
But whenever I tried connecting to MSDE by SQL login it
gives me the following error:
Invalid username and/or password, you are using a windows
login that is not your own, or server does not exist.
Please help.
Tnx,
Jess
hi Jess,
jess.tayag@.dhl.com wrote:
> I was able to install MSDE into WXP and migrated my Access
> databases through Windows Integrated Authentication Method.
> But whenever I tried connecting to MSDE by SQL login it
> gives me the following error:
> Invalid username and/or password, you are using a windows
> login that is not your own, or server does not exist.
>
if the raised error is
"Login failed for user 'UserName'. Reason: Not associated with a trusted SQL
Server connection."
the reason is MSDE is only allowing WindowsNT trusted connections and not
SQL Server authenticated connections, and this can be solved as explained in
http://support.microsoft.com/default...b;en-us;285097 in the part
regarding the Windows registry modification, while the
"SQL Server does not exists or access denied"
message is usually related to other kind of troubles, as indicated in
http://support.microsoft.com/default...06&Product=sql
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

Connecting to MSDE named instance

If we install MSDE 2000 SP3a with out a named instance we can connect to
through OSQL from a different computer on the network.
We used SVRNETCN.EXE to add TCP/IP to the protocol list.
We changed the port from 1059 or something like that to 1433.
We changed "LoginMode" to 2, but we also tried it with 0
But when we try to connect via OSQL
osql -S ROBXP\RR -U sa -P 11111
we get the following error.
[DBNETLIB]SQL Server does not exist or access denied.
[DBNETLIB]ConnectionOpen (Connect()).
the same OSQL command works OK from the local computer.
If we re-install with out a named instance we can connect fine with OSQL
Any ideas?
-Rob
PS. it was installed with the following:
setup SAPWD=11111 DISABLENETWORKPROTOCOLS=0 SECURITYMODE=SQL INSTANCENAME=RR
Check your MDAC version on the client you're trying to connect from. Upgrade
to the latest version and try it again.
MeanOldDBA
derrickleggett@.hotmail.com
http://weblogs.sqlteam.com/derrickl
When life gives you a lemon, fire the DBA.
"rob" wrote:

> If we install MSDE 2000 SP3a with out a named instance we can connect to
> through OSQL from a different computer on the network.
> We used SVRNETCN.EXE to add TCP/IP to the protocol list.
> We changed the port from 1059 or something like that to 1433.
> We changed "LoginMode" to 2, but we also tried it with 0
> But when we try to connect via OSQL
> osql -S ROBXP\RR -U sa -P 11111
> we get the following error.
>
> [DBNETLIB]SQL Server does not exist or access denied.
> [DBNETLIB]ConnectionOpen (Connect()).
> the same OSQL command works OK from the local computer.
>
> If we re-install with out a named instance we can connect fine with OSQL
> Any ideas?
> -Rob
> PS. it was installed with the following:
> setup SAPWD=11111 DISABLENETWORKPROTOCOLS=0 SECURITYMODE=SQL INSTANCENAME=RR
>
>
|||I ran Componet Checker 2.0 and it indidcates I have MDAC 2.8 SP1 which looks
to be the latest version.
"MeanOldDBA" <MeanOldDBA@.discussions.microsoft.com> wrote in message
news:86C87062-5A4C-4962-8FB3-99BA9CA2F375@.microsoft.com...
> Check your MDAC version on the client you're trying to connect from.
> Upgrade
> to the latest version and try it again.
|||hi,
rob wrote:

> We used SVRNETCN.EXE to add TCP/IP to the protocol list.
> We changed the port from 1059 or something like that to 1433.
usually 1433 is for default instances, where other port numbers indicates
named instances...
specifying a fixed port and not using the dynamic assigned port (wiche
requires on the server the UDP 1434 port to be available out of eventual
firewall) you have to specify an alias via Client Network Utility
(cliconfg.exe) on each remote client...
Andrea Montanari
http://www.asql.biz/DbaMgr.shtm
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||THANKS it works.
For anyone else reading this thread in the future.
You give it an alias name (RR for example) and and the servername is the
servername\instance
you can test the connection by using the alias name:
osql -S RR -U sa -Pxxxxx
thanks again.
.....
I have done some more testing. The only thing I am concerned about is:
After my program and MSDE is installed on someones computer, if they want to
access it from a different computer they will need to know how to create
exceptions in the WindowsXP firewall.
They will need to open up UPD 1434 and TCP port XXXX where XXXX is whatever
random port is used during installation of MSDE. I can find that port in
the registry and tell them at install time. But my users are not always
very proficient at using computers, and could have a hard time opening up
ports in the firewall.
If anyone has any suggestions about making this easier I would love to hear
about it.
-Rob
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3qfs6cFe280bU1@.individual.net...
> hi,
> rob wrote:
>
> usually 1433 is for default instances, where other port numbers indicates
> named instances...
> specifying a fixed port and not using the dynamic assigned port (wiche
> requires on the server the UDP 1434 port to be available out of eventual
> firewall) you have to specify an alias via Client Network Utility
> (cliconfg.exe) on each remote client...
> --
> Andrea Montanari
> http://www.asql.biz/DbaMgr.shtm
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||hi Rob,
rob wrote:
> ....
> I have done some more testing. The only thing I am concerned about
> is: After my program and MSDE is installed on someones computer, if
> they want to access it from a different computer they will need to
> know how to create exceptions in the WindowsXP firewall.
> They will need to open up UPD 1434 and TCP port XXXX where XXXX is
> whatever random port is used during installation of MSDE. I can find
> that port in the registry and tell them at install time. But my
> users are not always very proficient at using computers, and could
> have a hard time opening up ports in the firewall.
> If anyone has any suggestions about making this easier I would love
> to hear about it.
>
actually you can provide the script available at
http://support.microsoft.com/kb/839980/en-us to provide an "automatic open
ports" :D
try having a look at it if can helps..
Andrea Montanari
http://www.asql.biz/DbaMgr.shtm
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Wow, that will make it easier. I was dreading having to give instructions to
open the firewall. ; )
I don't want to bother you, but I have one more question.
Your advice did work, and I can connect to the newly installed instance, -
IF I set up an alias.
BUT,
I have one computer that I installed with an instance that I do NOT have to
set up an alias for to connect remotely. I can not see what is different
for this computer. I even printed out the MSSQL registry settings for the
two computers and could not see a difference (besides uptime, etc.)
Even though your suggestion works, it would be much easier if I did not have
to set up an alias on the clients. Do you have any ideas what I did
differently with the one that works with out an alias?
Thanks,
Rob
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3qhp0hFem400U1@.individual.net...
> hi Rob,
> actually you can provide the script available at
> http://support.microsoft.com/kb/839980/en-us to provide an "automatic open
> ports" :D
> try having a look at it if can helps..
> --
> Andrea Montanari
> http://www.asql.biz/DbaMgr.shtm
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||I downloaded your program DBMgr2 and was able to connect to my DB without
using an alias. The difference was (from your help file) to use servername =
ROBXP\RR,1433
explicitly name the port number. This works via osql also.
The difference remains that I have one computer that I do not need to know
what the port number is, or set up an alias.
"rob" <ryost@..no.spam.rentright.com> wrote in message
news:OqGjGPbyFHA.2924@.TK2MSFTNGP15.phx.gbl...
> Wow, that will make it easier. I was dreading having to give instructions
> to open the firewall. ; )
> I don't want to bother you, but I have one more question.
> Your advice did work, and I can connect to the newly installed instance, -
> IF I set up an alias.
> BUT,
> I have one computer that I installed with an instance that I do NOT have
> to set up an alias for to connect remotely. I can not see what is
> different for this computer. I even printed out the MSSQL registry
> settings for the two computers and could not see a difference (besides
> uptime, etc.)
> Even though your suggestion works, it would be much easier if I did not
> have to set up an alias on the clients. Do you have any ideas what I did
> differently with the one that works with out an alias?
> Thanks,
> Rob
> "Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
> news:3qhp0hFem400U1@.individual.net...
>
|||hi Rob,
rob wrote:
> I downloaded your program DBMgr2 and was able to connect to my DB
> without using an alias. The difference was (from your help file) to
> use servername = ROBXP\RR,1433
> explicitly name the port number. This works via osql also.
> The difference remains that I have one computer that I do not need to
> know what the port number is, or set up an alias.
probably it's not a named instance but a default one, that's to say ROBXP
and not ROBXP\RR..
default instances automatically listen on TCP 1433 as this port is the one
Microsoft reserved on IANA for SQL Server...
try having a look at it..
Andrea Montanari
http://www.asql.biz/DbaMgr.shtm
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||I am pretty sure it is a named instance. I connected to it through your
Dbamgr2k by specifing
MICHELLEP\MICHELLE
I did not have to give it port 1433 (which is its port)
I did set this server up several months ago, and do not remember exactly how
I did it.
Also, when I go to add remove programs it is listed as:
Microsoft SQL Server Desktop Engine (MICHELLE)
and I think the instance name is listed in the paren's
From SQLPing:
C:\>sqlping 192.168.0.88
SQL-Pinging 192.168.0.88
Listening...
ServerName:MICHELLEP
InstanceName:MICHELLE
IsClustered:No
Version:8.00.194
tcp:1433
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3qieavFf286oU1@.individual.net...
> probably it's not a named instance but a default one, that's to say ROBXP
> and not ROBXP\RR..
> default instances automatically listen on TCP 1433 as this port is the one
> Microsoft reserved on IANA for SQL Server...
> try having a look at it..
> --
> Andrea Montanari
> http://www.asql.biz/DbaMgr.shtm
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>

Connecting to Local Database after Application Install

I have created an application which uses a SQL Express database. The program runs fine on the the computer where I built the app, however when I install the app on another computer I get an error telling me that under default SQL Express does not allow remote connections. The problem is that I dont want a remote connection I want a local connection, the database file is on the commputer. How can do get my application to look for the database on the local machine.

My connection string is:

Data Source=(local)\SQLEXPRESS;Initial Catalog="C:\DOCUMENTS AND SETTINGS\ADMINISTRATOR\PLDAQ.MDF";Integrated Security=True

I have made sure that the file is in the correct directory.

Any help would be greatly appretiated

hi,

the folder you are referencing is not a "standard" one in the "traditional" sense of SQL Server, and you can get problems if the account running the instance is not able to access that path... and anyway you should reference the intital catalog in the connection string via the "logical" name and not the physical primary data file name, thus
Data Source=(local)\SQLEXPRESS;Initial Catalog=dbLogicalFileName;Integrated Security=True
or use the AttachDBFilename feature of the User Instances mode..

try modifying the connection string to see if you are granted connection to the instance you are dealing with, as the exception you are reporting is quite a generic connection exception..

regards

|||

Andrea

I still have the same problem, I have updated my connection string to this:

Data Source = .\SQLEXPRESS;AttachDBFilename = [DataDirectory]\PLDaq.mdf;Integrated Security = True; UserInstance = False

I have managed to get arround the error by changeing the name of the non-design computer to mach the name of the design computer, this however, as I am sure you will agree, is only temporary as I don't want to have to change the name of every computer that I install this application on, what do I need to do to rectify this situation.

|||

hi,

as you are not using "User Instances", I'd not go for the AttachDBFileName property of the connection string.. I'd attach/create the database once and then I'd go for the "traditional" Database=yourDbName property of the connection string...

I have managed to get arround the error by changeing the name of the non-design computer to mach the name of the design computer

do you mean by that you "named" the destination computer the same as your dev pc? this is obviously not "mandatory"...

what is your |DataDirectory| value?

regards

|||

do you mean by that you "named" the destination computer the same as your dev pc? this is obviously not "mandatory"...

Unfortunatly this is the only way it will not generate the error posted above. Like I said the program is looking for a remote connection but I want a local one. So I tricked it into thinking that it was running on the dev computer by changeing the name. I will agree that this is obviously not convient, but that is why I am posting I just cant figure out how to fix it.

The |DataDirectory| tells the connection to look in the bin\debug folder during dev time, and also to look into the bin\data folder at run time, after installation obviously. So when the program is installed and all data files are stored in the (AppPath)\bin\data directory and that is where the program is supposed to look for the data files (e.g. Database and Log files), however, if the non dev computer has a different name it trys to find the dev computer to connect to the database, a remote connection, It cant do this as it is not connected to any network.

I have tryed the traditional Database = yourDbName and that causes the same problem

Also There may come a time when I want to use User Instances, but for the time being I just want the thing to work.

|||

PEng1 wrote:

Unfortunatly this is the only way it will not generate the error posted above. Like I said the program is looking for a remote connection but I want a local one. So I tricked it into thinking that it was running on the dev computer by changeing the name. I will agree that this is obviously not convient, but that is why I am posting I just cant figure out how to fix it.

the fix is using

Data Source = .\SQLEXPRESS or Data Source = (Local)\SQLEXPRESS property in the connection string...

here you have to specify the instance you have to connect to, and you can provide "." and/or "(Local)" for "local" connections"...

The |DataDirectory| tells the connection to look in the bin\debug folder during dev time, and also to look into the bin\data folder at run time, after installation obviously. So when the program is installed and all data files are stored in the (AppPath)\bin\data directory and that is where the program is supposed to look for the data files (e.g. Database and Log files), however, if the non dev computer has a different name it trys to find the dev computer to connect to the database, a remote connection, It cant do this as it is not connected to any network.

pay attention to your "custom data folder"... consider that the account running the SQLExpress intstance required adeguate NTFS permissions to that folder.. and consider Vista "headaches"/requirements with regard writing in Program Files folder...

regards

|||

Andrea,

I guess that I had the answer for a while and just didn't bother to check if it would work with a different name, or I changed something and just don't remeber what, probably the latter of the two, either way, the problem is resolved and I am greatly indebted for all of your help. Thanks a lot.

This program will be run on Windows 2000 for quite a while but it will eventually have to be moved to Vista or higher, what "headaches" are you refering to, I am not at all familiar with Vista since the company I work for still has some machines that are running 95 and One that is running DOS, yeah thats right I said DOS. I guess however that I should probably read up on the New OS any recomended reading?

|||

hi,

PEng1 wrote:

Andrea,
I guess that I had the answer for a while and just didn't bother to check if it would work with a different name, or I changed something and just don't remeber what, probably the latter of the two, either way, the problem is resolved and I am greatly indebted for all of your help. Thanks a lot.
This program will be run on Windows 2000 for quite a while but it will eventually have to be moved to Vista or higher, what "headaches" are you refering to, I am not at all familiar with Vista since the company I work for still has some machines that are running 95 and One that is running DOS, yeah thats right I said DOS. I guess however that I should probably read up on the New OS any recomended reading?

start reading at http://technet.microsoft.com/en-us/windowsvista/aa905108.aspx, http://technet.microsoft.com/en-us/windowsvista/aa906021.aspx, ....

and look in this forum for Vista troubles with UAC..

regards

Connecting to Local Database after Application Install

My connection string is:

Data Source=(local)\SQLEXPRESS;Initial Catalog="C:\DOCUMENTS AND SETTINGS\ADMINISTRATOR\PLDAQ.MDF";Integrated Security=True

I have made sure that the file is in the correct directory.

Any help would be greatly appretiated

hi,

try modifying the connection string to see if you are granted connection to the instance you are dealing with, as the exception you are reporting is quite a generic connection exception..

regards

|||

Andrea

I still have the same problem, I have updated my connection string to this:

Data Source = .\SQLEXPRESS;AttachDBFilename = [DataDirectory]\PLDaq.mdf;Integrated Security = True; UserInstance = False

|||

hi,

I have managed to get arround the error by changeing the name of the non-design computer to mach the name of the design computer

do you mean by that you "named" the destination computer the same as your dev pc? this is obviously not "mandatory"...

what is your |DataDirectory| value?

regards

|||

do you mean by that you "named" the destination computer the same as your dev pc? this is obviously not "mandatory"...

I have tryed the traditional Database = yourDbName and that causes the same problem

Also There may come a time when I want to use User Instances, but for the time being I just want the thing to work.

|||

PEng1 wrote:

Unfortunatly this is the only way it will not generate the error posted above. Like I said the program is looking for a remote connection but I want a local one. So I tricked it into thinking that it was running on the dev computer by changeing the name. I will agree that this is obviously not convient, but that is why I am posting I just cant figure out how to fix it.

the fix is using

Data Source = .\SQLEXPRESS or Data Source = (Local)\SQLEXPRESS property in the connection string...

here you have to specify the instance you have to connect to, and you can provide "." and/or "(Local)" for "local" connections"...

The |DataDirectory| tells the connection to look in the bin\debug folder during dev time, and also to look into the bin\data folder at run time, after installation obviously. So when the program is installed and all data files are stored in the (AppPath)\bin\data directory and that is where the program is supposed to look for the data files (e.g. Database and Log files), however, if the non dev computer has a different name it trys to find the dev computer to connect to the database, a remote connection, It cant do this as it is not connected to any network.

regards

|||

Andrea,

|||

hi,

PEng1 wrote:

Andrea,
I guess that I had the answer for a while and just didn't bother to check if it would work with a different name, or I changed something and just don't remeber what, probably the latter of the two, either way, the problem is resolved and I am greatly indebted for all of your help. Thanks a lot.
This program will be run on Windows 2000 for quite a while but it will eventually have to be moved to Vista or higher, what "headaches" are you refering to, I am not at all familiar with Vista since the company I work for still has some machines that are running 95 and One that is running DOS, yeah thats right I said DOS. I guess however that I should probably read up on the New OS any recomended reading?

start reading at http://technet.microsoft.com/en-us/windowsvista/aa905108.aspx, http://technet.microsoft.com/en-us/windowsvista/aa906021.aspx, ....

and look in this forum for Vista troubles with UAC..

regards

Connecting to Local Database after Application Install

My connection string is:

Data Source=(local)\SQLEXPRESS;Initial Catalog="C:\DOCUMENTS AND SETTINGS\ADMINISTRATOR\PLDAQ.MDF";Integrated Security=True

I have made sure that the file is in the correct directory.

Any help would be greatly appretiated

hi,

try modifying the connection string to see if you are granted connection to the instance you are dealing with, as the exception you are reporting is quite a generic connection exception..

regards

|||

Andrea

I still have the same problem, I have updated my connection string to this:

Data Source = .\SQLEXPRESS;AttachDBFilename = [DataDirectory]\PLDaq.mdf;Integrated Security = True; UserInstance = False

|||

hi,

I have managed to get arround the error by changeing the name of the non-design computer to mach the name of the design computer

do you mean by that you "named" the destination computer the same as your dev pc? this is obviously not "mandatory"...

what is your |DataDirectory| value?

regards

|||

do you mean by that you "named" the destination computer the same as your dev pc? this is obviously not "mandatory"...

I have tryed the traditional Database = yourDbName and that causes the same problem

Also There may come a time when I want to use User Instances, but for the time being I just want the thing to work.

|||

PEng1 wrote:

Unfortunatly this is the only way it will not generate the error posted above. Like I said the program is looking for a remote connection but I want a local one. So I tricked it into thinking that it was running on the dev computer by changeing the name. I will agree that this is obviously not convient, but that is why I am posting I just cant figure out how to fix it.

the fix is using

Data Source = .\SQLEXPRESS or Data Source = (Local)\SQLEXPRESS property in the connection string...

here you have to specify the instance you have to connect to, and you can provide "." and/or "(Local)" for "local" connections"...

The |DataDirectory| tells the connection to look in the bin\debug folder during dev time, and also to look into the bin\data folder at run time, after installation obviously. So when the program is installed and all data files are stored in the (AppPath)\bin\data directory and that is where the program is supposed to look for the data files (e.g. Database and Log files), however, if the non dev computer has a different name it trys to find the dev computer to connect to the database, a remote connection, It cant do this as it is not connected to any network.

regards

|||

Andrea,

|||

hi,

PEng1 wrote:

Andrea,
I guess that I had the answer for a while and just didn't bother to check if it would work with a different name, or I changed something and just don't remeber what, probably the latter of the two, either way, the problem is resolved and I am greatly indebted for all of your help. Thanks a lot.
This program will be run on Windows 2000 for quite a while but it will eventually have to be moved to Vista or higher, what "headaches" are you refering to, I am not at all familiar with Vista since the company I work for still has some machines that are running 95 and One that is running DOS, yeah thats right I said DOS. I guess however that I should probably read up on the New OS any recomended reading?

start reading at http://technet.microsoft.com/en-us/windowsvista/aa905108.aspx, http://technet.microsoft.com/en-us/windowsvista/aa906021.aspx, ....

and look in this forum for Vista troubles with UAC..

regards

Thursday, March 8, 2012

Connecting to a SQL Server 2005 Instance

I completed a default install that uses the server name: Server1
and completed an instance install on Server1 called Server1test with
the same users, etc.
I can connect remotely to Server1 using SQL Server 2005 Management
Studio, but when I try to connect to Server1\Server1test I get:
An error has occurred while establishing a connection to the server.
When connecting to SQL Server 2005, this failure may be caused by the
fact that under the default settings SQL Server does not allow remote
connections. (Provider: SQL Network Interfaces, error: 26 - Error
Locating Server/Instance Specified) (Microsoft SQL Server)
If I can connect to Server1 using the SA account why is it not allowing
the named instance (i.e., Server1\Server1test) to connect? While at
Server1 I can connect to Server1\Server1test using the SA account.
Thanks for any suggestions.
RBollinger
Let's see your ConnectString.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"robboll" <robboll@.hotmail.com> wrote in message
news:1169744212.563385.41730@.v33g2000cwv.googlegro ups.com...
>I completed a default install that uses the server name: Server1
> and completed an instance install on Server1 called Server1test with
> the same users, etc.
> I can connect remotely to Server1 using SQL Server 2005 Management
> Studio, but when I try to connect to Server1\Server1test I get:
> An error has occurred while establishing a connection to the server.
> When connecting to SQL Server 2005, this failure may be caused by the
> fact that under the default settings SQL Server does not allow remote
> connections. (Provider: SQL Network Interfaces, error: 26 - Error
> Locating Server/Instance Specified) (Microsoft SQL Server)
> If I can connect to Server1 using the SA account why is it not allowing
> the named instance (i.e., Server1\Server1test) to connect? While at
> Server1 I can connect to Server1\Server1test using the SA account.
> Thanks for any suggestions.
> RBollinger
>
|||When I connect to the default instance from a remote client using SQL
Server 2005 Management Studio it is:
Server type: Database Engine
Server name: Server1
Authentication: SQL Server Authentication
Login: sa
Password: mypassword
Result: Works as expected
Whn I connect to the named instance from the same remote client using
SQL Server 2005 Management Studio it is:
Server type: Database Engine
Server name: Server1\server1test
Authentication: SQL Server Authentication
Login: sa
Password: mypassword
Result: Fails
On Jan 25, 12:12 pm, "William $Bill$ Vaughn"
<billvaRemoveT...@.nwlink.com> wrote:[vbcol=seagreen]
> Let's see your ConnectString.
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speakerwww.betav.com/blog/billvawww.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no rights.
> __________________________________
> Visitwww.hitchhikerguides.netto get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ----X---
> "robboll" <robb...@.hotmail.com> wrote in messagenews:1169744212.563385.41730@.v33g2000cwv.go oglegroups.com...
>
>
>
>
|||While these aren't ConnectString strings, they do tell me that you're using
SA to access the servers. This is not a good idea, but it's not why you
aren't getting connected. When you install SQL Server it does not support
SQL Server authentication unless it was specifically requested in the
interactive setup process. Each instance must be so configured. The SQL
Server Surface Area Configuration tools can help adjust these settings.
hth
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"robboll" <robboll@.hotmail.com> wrote in message
news:1169751617.893553.179310@.v33g2000cwv.googlegr oups.com...
When I connect to the default instance from a remote client using SQL
Server 2005 Management Studio it is:
Server type: Database Engine
Server name: Server1
Authentication: SQL Server Authentication
Login: sa
Password: mypassword
Result: Works as expected
Whn I connect to the named instance from the same remote client using
SQL Server 2005 Management Studio it is:
Server type: Database Engine
Server name: Server1\server1test
Authentication: SQL Server Authentication
Login: sa
Password: mypassword
Result: Fails
On Jan 25, 12:12 pm, "William $Bill$ Vaughn"
<billvaRemoveT...@.nwlink.com> wrote:[vbcol=seagreen]
> Let's see your ConnectString.
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speakerwww.betav.com/blog/billvawww.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> __________________________________
> Visitwww.hitchhikerguides.netto get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ----X---
> "robboll" <robb...@.hotmail.com> wrote in
> messagenews:1169744212.563385.41730@.v33g2000cwv.go oglegroups.com...
>
>
>
>

Connecting to a SQL Server 2005 Instance

I completed a default install that uses the server name: Server1
and completed an instance install on Server1 called Server1test with
the same users, etc.
I can connect remotely to Server1 using SQL Server 2005 Management
Studio, but when I try to connect to Server1\Server1test I get:
An error has occurred while establishing a connection to the server.
When connecting to SQL Server 2005, this failure may be caused by the
fact that under the default settings SQL Server does not allow remote
connections. (Provider: SQL Network Interfaces, error: 26 - Error
Locating Server/Instance Specified) (Microsoft SQL Server)
If I can connect to Server1 using the SA account why is it not allowing
the named instance (i.e., Server1\Server1test) to connect? While at
Server1 I can connect to Server1\Server1test using the SA account.
Thanks for any suggestions.
RBollingerLet's see your ConnectString.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"robboll" <robboll@.hotmail.com> wrote in message
news:1169744212.563385.41730@.v33g2000cwv.googlegroups.com...
>I completed a default install that uses the server name: Server1
> and completed an instance install on Server1 called Server1test with
> the same users, etc.
> I can connect remotely to Server1 using SQL Server 2005 Management
> Studio, but when I try to connect to Server1\Server1test I get:
> An error has occurred while establishing a connection to the server.
> When connecting to SQL Server 2005, this failure may be caused by the
> fact that under the default settings SQL Server does not allow remote
> connections. (Provider: SQL Network Interfaces, error: 26 - Error
> Locating Server/Instance Specified) (Microsoft SQL Server)
> If I can connect to Server1 using the SA account why is it not allowing
> the named instance (i.e., Server1\Server1test) to connect? While at
> Server1 I can connect to Server1\Server1test using the SA account.
> Thanks for any suggestions.
> RBollinger
>|||When I connect to the default instance from a remote client using SQL
Server 2005 Management Studio it is:
Server type: Database Engine
Server name: Server1
Authentication: SQL Server Authentication
Login: sa
Password: mypassword
Result: Works as expected
Whn I connect to the named instance from the same remote client using
SQL Server 2005 Management Studio it is:
Server type: Database Engine
Server name: Server1\server1test
Authentication: SQL Server Authentication
Login: sa
Password: mypassword
Result: Fails
On Jan 25, 12:12 pm, "William $Bill$ Vaughn"
<billvaRemoveT...@.nwlink.com> wrote:
> Let's see your ConnectString.
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speakerwww.betav.com/blog/billvawww.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no right=
s=2E
> __________________________________
> Visitwww.hitchhikerguides.netto get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ----=
--=AD---
> "robboll" <robb...@.hotmail.com> wrote in messagenews:1169744212.563385.41=
730@.v33g2000cwv.googlegroups.com...[vbcol=seagreen]
>
>
>
>
>
>
>=20|||While these aren't ConnectString strings, they do tell me that you're using
SA to access the servers. This is not a good idea, but it's not why you
aren't getting connected. When you install SQL Server it does not support
SQL Server authentication unless it was specifically requested in the
interactive setup process. Each instance must be so configured. The SQL
Server Surface Area Configuration tools can help adjust these settings.
hth
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"robboll" <robboll@.hotmail.com> wrote in message
news:1169751617.893553.179310@.v33g2000cwv.googlegroups.com...
When I connect to the default instance from a remote client using SQL
Server 2005 Management Studio it is:
Server type: Database Engine
Server name: Server1
Authentication: SQL Server Authentication
Login: sa
Password: mypassword
Result: Works as expected
Whn I connect to the named instance from the same remote client using
SQL Server 2005 Management Studio it is:
Server type: Database Engine
Server name: Server1\server1test
Authentication: SQL Server Authentication
Login: sa
Password: mypassword
Result: Fails
On Jan 25, 12:12 pm, "William $Bill$ Vaughn"
<billvaRemoveT...@.nwlink.com> wrote:[vbcol=seagreen]
> Let's see your ConnectString.
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speakerwww.betav.com/blog/billvawww.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> __________________________________
> Visitwww.hitchhikerguides.netto get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ----
-_---
> "robboll" <robb...@.hotmail.com> wrote in
> messagenews:1169744212.563385.41730@.v33g2000cwv.googlegroups.com...
>
>
>
>
>
>
>

Wednesday, March 7, 2012

Connecting to a Remote Server with SQL Management Studio Express

I installed a copy of SQL 2005 Express on another computer here using the
automatic download and install from Microsoft supported by the setup
toolkit.
I can't access this server from another machine on the LAN using SQL
Management Studio Express. I can 'see' the server but cannot connect. Both
machines are running XP, mine is trying to log in as 'Guest'.
Do I need to configure SQL 2005 on the remote machine to use mixed-mode
authentication and try to log in using an SQL password, or is there a way to
make a remote user work with Windows Authentication?
How should I go about this?
Thanks.
You will have to disable the simple filesharhing in XP, otherweise the
client will try to logon using the guest account.
Jens K. Suessmeyer.
http://www.sqlserver2005.de
|||If you haven't done so yet - enable TCP/IP via the SQL Server Surface Area
Configuration tool / Remote Connections on the destination SQL Server. SQL
Server 2005 Express doesn't enable this by default. Also turn on the SQL
Browser service.
M a M
"Jens" wrote:

> You will have to disable the simple filesharhing in XP, otherweise the
> client will try to logon using the guest account.
>
> Jens K. Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
>
|||Thanks. I have done that but apparently have to enable mixed mode
authentication on the server in order to authenticate. How do I do this?
regards.
"M a M" <MaM@.discussions.microsoft.com> wrote in message
news:6045D19B-3B4F-4B27-B3CD-F82DD325E7DA@.microsoft.com...[vbcol=seagreen]
> If you haven't done so yet - enable TCP/IP via the SQL Server Surface Area
> Configuration tool / Remote Connections on the destination SQL Server. SQL
> Server 2005 Express doesn't enable this by default. Also turn on the SQL
> Browser service.
> M a M
> "Jens" wrote:
|||You could simply add the Windows NT account via the Security / Logins of the
Server in question. You have to log into the server locally obviously to make
this change. Either add the NT account or (your request) change the "Server
authentication" to SQL Server and Windows Authentication mode via the
Security tab of the SQL Server properties.
M a M
"Andrew Chalk" wrote:

> Thanks. I have done that but apparently have to enable mixed mode
> authentication on the server in order to authenticate. How do I do this?
> regards.
> "M a M" <MaM@.discussions.microsoft.com> wrote in message
> news:6045D19B-3B4F-4B27-B3CD-F82DD325E7DA@.microsoft.com...
>
>
|||> this change. Either add the NT account or (your request) change the
> "Server
> authentication" to SQL Server and Windows Authentication mode via the ...
How? This is XP with no SQL Management Studio Express. I have to connect
first before I can access the database with SQL MSE. That is the object of
this exercise.
Thanks.
"M a M" <MaM@.discussions.microsoft.com> wrote in message
news:96E18316-203F-46F1-A01D-FDEBE024CCBB@.microsoft.com...[vbcol=seagreen]
> You could simply add the Windows NT account via the Security / Logins of
> the
> Server in question. You have to log into the server locally obviously to
> make
> this change. Either add the NT account or (your request) change the
> "Server
> authentication" to SQL Server and Windows Authentication mode via the
> Security tab of the SQL Server properties.
> M a M
> "Andrew Chalk" wrote:
|||I loaded MSE on the remote machine and changed the logi mode to mixed. After
that, I was able to connect remotely with MSE.
So, my question boils down to this: How do I set the login mode of SQL
Server 2005 Express to mixed WITHOUT Manaagement Studio Express?
Thanks.
"M a M" <MaM@.discussions.microsoft.com> wrote in message
news:96E18316-203F-46F1-A01D-FDEBE024CCBB@.microsoft.com...[vbcol=seagreen]
> You could simply add the Windows NT account via the Security / Logins of
> the
> Server in question. You have to log into the server locally obviously to
> make
> this change. Either add the NT account or (your request) change the
> "Server
> authentication" to SQL Server and Windows Authentication mode via the
> Security tab of the SQL Server properties.
> M a M
> "Andrew Chalk" wrote:
|||HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\MSSQL.1\MSSQLServer change LoginMode from 1 to 2 and restart SQL
Server services.
"Andrew Chalk" wrote:

> I loaded MSE on the remote machine and changed the logi mode to mixed. After
> that, I was able to connect remotely with MSE.
> So, my question boils down to this: How do I set the login mode of SQL
> Server 2005 Express to mixed WITHOUT Manaagement Studio Express?
> Thanks.
> "M a M" <MaM@.discussions.microsoft.com> wrote in message
> news:96E18316-203F-46F1-A01D-FDEBE024CCBB@.microsoft.com...
>
>
|||Thanks!
"M a M" <MaM@.discussions.microsoft.com> wrote in message
news:6DBDB113-6DDE-4FAC-A09E-74FAAECAE75A@.microsoft.com...[vbcol=seagreen]
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
> Server\MSSQL.1\MSSQLServer change LoginMode from 1 to 2 and restart SQL
> Server services.
> "Andrew Chalk" wrote:

Connecting to a Remote Server with SQL Management Studio Express

Connecting to a local database

Hi,
My problem is I have an app that uses MSDE 2000. After the install, it
asks for the name of the local database instance where you would like to
install the app. It only gives me one option, 'localhost'. I can use an
OLEDB provider to specify the actual server name but I cannot connect using
localhost. Why is this happening? I am unable to install the app using the
server name.
Thanks in advance.
J
Hi
In a SQL Serever connection string, 'localhost' is not valid. 'local' is.
'localhost' is a TCP/IP alias for 127.0.0.1
Regards
Mike
"JD" wrote:

> Hi,
> My problem is I have an app that uses MSDE 2000. After the install, it
> asks for the name of the local database instance where you would like to
> install the app. It only gives me one option, 'localhost'. I can use an
> OLEDB provider to specify the actual server name but I cannot connect using
> localhost. Why is this happening? I am unable to install the app using the
> server name.
> Thanks in advance.
> J
>
>
|||"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:39B7B3AA-68F6-4465-8EAE-F366069A427C@.microsoft.com...
> Hi
> In a SQL Serever connection string, 'localhost' is not valid. 'local' is.
'(local)' is valid, 'local' would only be valid is if it was created as an
alias for a valid name, using CLICONFG.EXE, or the system name happened to
be 'local'.

> 'localhost' is a TCP/IP alias for 127.0.0.1
Oddly enough, if TCP/IP is a configured protocol for the installation, SQL
Server listens to the loopback, so 'localhost' is every bit as valid as an
IP, or any other DNS name that resolves to the box in question...
However... none of it will be valid if it's a named instance, in which case
you must use the server\instance notation, as either the server name or in
an alias definition.
So if the app is hardcoded to use the servername 'localhost' (which would be
terrible design, btw) you can use CLICONFG.EXE to define 'localhost' as an
alias for server\instance... and it might even work. :-)
-Mark
[vbcol=seagreen]
> Regards
> Mike
> "JD" wrote:

Connecting to a local database

Hi,
My problem is I have an app that uses MSDE 2000. After the install, it
asks for the name of the local database instance where you would like to
install the app. It only gives me one option, 'localhost'. I can use an
OLEDB provider to specify the actual server name but I cannot connect using
localhost. Why is this happening? I am unable to install the app using the
server name.
Thanks in advance.
JHi
In a SQL Serever connection string, 'localhost' is not valid. 'local' is.
'localhost' is a TCP/IP alias for 127.0.0.1
Regards
Mike
"JD" wrote:

> Hi,
> My problem is I have an app that uses MSDE 2000. After the install, it
> asks for the name of the local database instance where you would like to
> install the app. It only gives me one option, 'localhost'. I can use an
> OLEDB provider to specify the actual server name but I cannot connect usin
g
> localhost. Why is this happening? I am unable to install the app using the
> server name.
> Thanks in advance.
> J
>
>|||"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:39B7B3AA-68F6-4465-8EAE-F366069A427C@.microsoft.com...
> Hi
> In a SQL Serever connection string, 'localhost' is not valid. 'local' is.
'(local)' is valid, 'local' would only be valid is if it was created as an
alias for a valid name, using CLICONFG.EXE, or the system name happened to
be 'local'.

> 'localhost' is a TCP/IP alias for 127.0.0.1
Oddly enough, if TCP/IP is a configured protocol for the installation, SQL
Server listens to the loopback, so 'localhost' is every bit as valid as an
IP, or any other DNS name that resolves to the box in question...
However... none of it will be valid if it's a named instance, in which case
you must use the server\instance notation, as either the server name or in
an alias definition.
So if the app is hardcoded to use the servername 'localhost' (which would be
terrible design, btw) you can use CLICONFG.EXE to define 'localhost' as an
alias for server\instance... and it might even work. :-)
-Mark
[vbcol=seagreen]
> Regards
> Mike
> "JD" wrote:
>

Friday, February 24, 2012

connecting samples to SQL Server 2005 Enterprise edition

ok, I've installed sql server, run the install samples and database, but when I go into SQL Server, the database and samples are not there. How do I connect the two?

thx,

Kat

Right click on the database node --> Attach database --> point to the data directorx where the samples have been installed --> Done.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

Connecting PortalVB ?

When I try to install PortalVB (IBuySpy) it says "Database Server Instance" and a dropdown box saying "localhost".
That should be correct right?
I click 'Configure' and it doesn't work?

Anyone help?

Cheers,
Noth

Ps. I have MSDE installed.just a guess... Might be a login issue...

Connecting legacy application to remote instance of SQL 2005 Express

Hi,
I've just done my first install of SQL 2005 Express and am having
problems connecting from a remote workstation using a VB6 application
that I believe used OLE DB/ADO.
I did get the application to connect, but only by installing an
instance on SQL Express on the remote workstation. I really think
there should be a lighter install that gets the required client
components onto the workstation.
I'm pasting a post I had made to another group below - this has all of
the steps I took in trying to get things connected.
Does anyone know of a better way to get remote workstations connected?
Thanks!
Glenn
I just did my first install of SQL 2005 Express yesterday (I know I'm
about a year behind!).
I ran into a problem connecting to the database from SO Administrator
from another workstation. Just wondering if anyone else has run into
this and found a better solution than I have...
1) Install SQL Server 2005 Express on the 'server'
2) Use the Surface Area Configuration tool to activate remote
connections over TCP/IP or Named Pipes.
3) Set the SQL Server Instance and the SQL Server Broser service to
auto
start
4) Restart SQL Server and Browser
5) At this point I can connect to the server usong SO Admin from my
laptop - which has SQL Server 2005 Developer Edition installed.
6) Attempt to connect from a workstation that has Store Operations 1.3
R1 and hotfix 1.3.1005 installed fails with the following message:
"You must connect to this server using SQL Server Managemnet
Studio or
SQL Server Management Objects (SMO)"
7) downloaded and installed "SQL Native Client" which appears to be
the
only thing that is supposed to be needed for a client to connect to a
SQL 2005 server. Same message from SO Administrator
8) ran the SQL Express installer on the workstation - selected ONLY
The
Client Components part of the install (deselected the default SQL
Engine
install). Same message from SO Admin
9) Ran SQL Express installer again, this time went ahead with the SQL
Engine install. SO Admin will now connect!
10) Ininstall SQL Express - Select to uninstall the SQL Engine
Instance,
but leave the Client Components. SO Admin Still connects!
This seems weird... Has anyone found a less convoluted way of getting
an RMS workstation to connect to a remote SQL 2005 Express database?
Thanks,
Glenn
Glenn Adams
Tiber Creek Consulting
http://www.tibercreek.com
glenn@.tibercreek.com
---
Please DO NOT respond to me directly but post all responses here in
the
newsgroup so that all can share the information.
Glenn Adams
Tiber Creek Consulting
http://www.tibercreek.com
glenn@.tibercreek.com
---
Please DO NOT respond to me directly but post all responses here in the
newsgroup so that all can share the information.If you are new to express these links should help. The first 3 are directly
related to your issue.
http://www.datamasker.com/SSE2005_NetworkCfg.htm Configuring Express
for Remote Access
https://blogs.msdn.com/sqlexpress/a.../05/415084.aspx
Configuring Remote Access
http://www.kbalertz.com/Feedback_914277.aspx Configuring SQL2005 for
remote access
http://msdn.microsoft.com/library/d...r />
rview.asp
Express Overview
http://msdn2.microsoft.com/en-us/library/ms165672.aspx Comparing Express
with MSDE
http://msdn.microsoft.com/sql/defau... />
erinst.asp
User Instances
http://msdn.microsoft.com/sql/expre...qlexcustapp.asp
Embedding Express in Apps
http://blogs.msdn.com/rogerwolterbl.../13/575974.aspx
Backing up Express
Automating Database maintenance in SQL 2005 Express Edition Part I
http://www.sqldbatips.com/showarticle.asp?ID=27
Automating Database maintenance in SQL 2005 Express Edition Part II
http://www.sqldbatips.com/showarticle.asp?ID=29
Andrew J. Kelly SQL MVP
"Glenn Adams [MVP - Retail Mgmt]" <glenn@.nospam.tibercreek.com> wrote in
message news:7pmpd2ticone4b2hpria46o035a4th1rge@.
4ax.com...
> Hi,
> I've just done my first install of SQL 2005 Express and am having
> problems connecting from a remote workstation using a VB6 application
> that I believe used OLE DB/ADO.
> I did get the application to connect, but only by installing an
> instance on SQL Express on the remote workstation. I really think
> there should be a lighter install that gets the required client
> components onto the workstation.
> I'm pasting a post I had made to another group below - this has all of
> the steps I took in trying to get things connected.
> Does anyone know of a better way to get remote workstations connected?
> Thanks!
> Glenn
> I just did my first install of SQL 2005 Express yesterday (I know I'm
> about a year behind!).
> I ran into a problem connecting to the database from SO Administrator
> from another workstation. Just wondering if anyone else has run into
> this and found a better solution than I have...
> 1) Install SQL Server 2005 Express on the 'server'
> 2) Use the Surface Area Configuration tool to activate remote
> connections over TCP/IP or Named Pipes.
> 3) Set the SQL Server Instance and the SQL Server Broser service to
> auto
> start
> 4) Restart SQL Server and Browser
> 5) At this point I can connect to the server usong SO Admin from my
> laptop - which has SQL Server 2005 Developer Edition installed.
> 6) Attempt to connect from a workstation that has Store Operations 1.3
> R1 and hotfix 1.3.1005 installed fails with the following message:
> "You must connect to this server using SQL Server Managemnet
> Studio or
> SQL Server Management Objects (SMO)"
> 7) downloaded and installed "SQL Native Client" which appears to be
> the
> only thing that is supposed to be needed for a client to connect to a
> SQL 2005 server. Same message from SO Administrator
> 8) ran the SQL Express installer on the workstation - selected ONLY
> The
> Client Components part of the install (deselected the default SQL
> Engine
> install). Same message from SO Admin
> 9) Ran SQL Express installer again, this time went ahead with the SQL
> Engine install. SO Admin will now connect!
> 10) Ininstall SQL Express - Select to uninstall the SQL Engine
> Instance,
> but leave the Client Components. SO Admin Still connects!
> This seems weird... Has anyone found a less convoluted way of getting
> an RMS workstation to connect to a remote SQL 2005 Express database?
> Thanks,
> Glenn
> --
> Glenn Adams
> Tiber Creek Consulting
> http://www.tibercreek.com
> glenn@.tibercreek.com
> ---
> Please DO NOT respond to me directly but post all responses here in
> the
> newsgroup so that all can share the information.
> Glenn Adams
> Tiber Creek Consulting
> http://www.tibercreek.com
> glenn@.tibercreek.com
> ---
> Please DO NOT respond to me directly but post all responses here in the
> newsgroup so that all can share the information.

Sunday, February 12, 2012

Connect to SQL2000 & SQL 2005

Our current program use ADO to connect oto SQL2000 and run fine.
We are planning to migrate to SQL2005.
When we clean install the SQL2005, create the database, set compatibility
level to 80 and generate the db structure, and migrate data.
When everything is done, we try to use our program to connect to SQL2005
database and find the connection fail.
Even when we use sa as login user and still fail to connect.
Is there any different in connection for SQL2000 & SQL2005?
I remember I have tried upgrade SQL2000 to SQL2005 before and the connection
had no problem to sql2005.
Is there something I forgot to set?
KanAm Tue, 29 Aug 2006 17:38:51 +0800 schrieb Ivan:

> Our current program use ADO to connect oto SQL2000 and run fine.
> We are planning to migrate to SQL2005.
> When we clean install the SQL2005, create the database, set compatibility
> level to 80 and generate the db structure, and migrate data.
> When everything is done, we try to use our program to connect to SQL2005
> database and find the connection fail.
> Even when we use sa as login user and still fail to connect.
> Is there any different in connection for SQL2000 & SQL2005?
> I remember I have tried upgrade SQL2000 to SQL2005 before and the connecti
on
> had no problem to sql2005.
> Is there something I forgot to set?
> Kan
If you did a standard installation then SQL2005 uses the named instance
SQLExpress wich you have to use in your connect string.
If your SQL2005 runs on the same machine as your SQL2000 then maybe SQL2005
listen on another port than the standard port.
And have you allowed remote access in SQL2005?
bye, Helmut|||No, MDAC will work fine with the SQL Server 2005 instance. Although you
can=B4t use some of the new cool features its compatible. Which error do
you get ? Is the SQL Server 2k5 located on the same machine as the 2k
instance ?
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--

Tuesday, March 27, 2012

Connecting to SQL Server 2005

Connecting to SQL Server 2005

Connecting to SQL Server 2005

Connecting to SQL Server & XP Service Pack 2

Connecting to SQL Server & XP Service Pack 2

Monday, March 19, 2012

Connecting to MSDE2000RelA

Connecting to MSDE named instance

Connecting to Local Database after Application Install

Connecting to Local Database after Application Install

Connecting to Local Database after Application Install

Thursday, March 8, 2012

Connecting to a SQL Server 2005 Instance

Connecting to a SQL Server 2005 Instance

Wednesday, March 7, 2012

Connecting to a Remote Server with SQL Management Studio Express

Connecting to a Remote Server with SQL Management Studio Express

Connecting to a local database

Connecting to a local database

Friday, February 24, 2012

connecting samples to SQL Server 2005 Enterprise edition

Connecting PortalVB ?

Connecting legacy application to remote instance of SQL 2005 Express

Sunday, February 12, 2012

Connect to SQL2000 & SQL 2005

Connect to SQL Server

Blog Archive

About Me