Errors in connecting Visual Fox Pro as linked server in 2005 - HEL

I can set up a linked server to a FoxPro DB in SQL 2000 but it fails when
trying to set up the linked server in 2005. I know the MS site says something
about leaking memory with the linked server but I don't even get a link that
works.
Here is what happens in a Win2003Server, SQLServer2005, latest VFPOLEDB from
MS site environment.
1) If I try to create a linked server from the management studio, it says:
'(null)' is an invalid product name. (Microsoft SQL Server, Error: 15429).
There are only three fields to fill out and product name is not required when
I try to make the linked server in 2000.
2) If I use a SQL command to create the linked server, I can make it without
the product name but it does not work in 2005 but does in 2000.
sp_addlinkedserver 'SERVER1', '', 'VFPOLEDB', 'c:\company.dbc'
Looking for thoughts on how to troubleshoot this!!
Doug Hoogervorst
Think I am closer now. It turns out that MDAC 2.8 SP2 for Windows Server 2003
is not showing VFPOLEDB as a component when I run the component checker. I
have tried regsvr32 to register the dll but no luck. Thoughts on how to get
MDAC to recognize this OLE DB provider?
"djh" wrote:

> I can set up a linked server to a FoxPro DB in SQL 2000 but it fails when
> trying to set up the linked server in 2005. I know the MS site says something
> about leaking memory with the linked server but I don't even get a link that
> works.
> Here is what happens in a Win2003Server, SQLServer2005, latest VFPOLEDB from
> MS site environment.
> 1) If I try to create a linked server from the management studio, it says:
> '(null)' is an invalid product name. (Microsoft SQL Server, Error: 15429).
> There are only three fields to fill out and product name is not required when
> I try to make the linked server in 2000.
> 2) If I use a SQL command to create the linked server, I can make it without
> the product name but it does not work in 2005 but does in 2000.
> sp_addlinkedserver 'SERVER1', '', 'VFPOLEDB', 'c:\company.dbc'
> Looking for thoughts on how to troubleshoot this!!
> Doug Hoogervorst
|||Hi Doug,
As you know, the FoxPro and Visual FoxPro OLE DB data provider is not
installed with MDAC. For the record, it's downloadable from
msdn.microsoft.com/downloads/updates. If you already have it you might want
to verify that you've got the latest version.
Here's what works for me in SQL 2005 using the Linked Server dialog:
Providers list: VFPOLEDB shows as an entry
Linked Servers > New Linked Server ...
Linked Server: MyLinkedServer
Provider: Choose "Microsoft OLE DB Provider for Visual FoxPro
Product name: Visual FoxPro (I think this is optional)
Data source: "C:\Program Files\Microsoft Visual
FoxPro9\Samples\Northwind\Northwind.dbc" (Include quotes since there's
spaces in the string.)
Provider string: VFPOLEDB.1
Location: (blank)
Catalog: (blank)
Security page and Server Options page take defaults.
Cindy Winegarden MCSD, Microsoft Visual FoxPro MVP
cindy_winegarden@.msn.com www.cindywinegarden.com
"djh" <djh@.discussions.microsoft.com> wrote in message
news:F93EBC44-2A78-4801-8DB0-C35F13CE876B@.microsoft.com...[vbcol=seagreen]
> Think I am closer now. It turns out that MDAC 2.8 SP2 for Windows Server
> 2003
> is not showing VFPOLEDB as a component when I run the component checker. I
> have tried regsvr32 to register the dll but no luck. Thoughts on how to
> get
> MDAC to recognize this OLE DB provider?
>
> "djh" wrote:

Errors in connecting Visual Fox Pro as linked server in 2005 - HEL

I can set up a linked server to a FoxPro DB in SQL 2000 but it fails when
trying to set up the linked server in 2005. I know the MS site says somethin
g
about leaking memory with the linked server but I don't even get a link that
works.
Here is what happens in a Win2003Server, SQLServer2005, latest VFPOLEDB from
MS site environment.
1) If I try to create a linked server from the management studio, it says:
'(null)' is an invalid product name. (Microsoft SQL Server, Error: 15429).
There are only three fields to fill out and product name is not required whe
n
I try to make the linked server in 2000.
2) If I use a SQL command to create the linked server, I can make it without
the product name but it does not work in 2005 but does in 2000.
sp_addlinkedserver 'SERVER1', '', 'VFPOLEDB', 'c:\company.dbc'
Looking for thoughts on how to troubleshoot this!!
Doug HoogervorstThink I am closer now. It turns out that MDAC 2.8 SP2 for Windows Server 200
3
is not showing VFPOLEDB as a component when I run the component checker. I
have tried regsvr32 to register the dll but no luck. Thoughts on how to get
MDAC to recognize this OLE DB provider?
"djh" wrote:

> I can set up a linked server to a FoxPro DB in SQL 2000 but it fails when
> trying to set up the linked server in 2005. I know the MS site says someth
ing
> about leaking memory with the linked server but I don't even get a link th
at
> works.
> Here is what happens in a Win2003Server, SQLServer2005, latest VFPOLEDB fr
om
> MS site environment.
> 1) If I try to create a linked server from the management studio, it says:
> '(null)' is an invalid product name. (Microsoft SQL Server, Error: 15429).
> There are only three fields to fill out and product name is not required w
hen
> I try to make the linked server in 2000.
> 2) If I use a SQL command to create the linked server, I can make it witho
ut
> the product name but it does not work in 2005 but does in 2000.
> sp_addlinkedserver 'SERVER1', '', 'VFPOLEDB', 'c:\company.dbc'
> Looking for thoughts on how to troubleshoot this!!
> Doug Hoogervorst|||Hi Doug,
As you know, the FoxPro and Visual FoxPro OLE DB data provider is not
installed with MDAC. For the record, it's downloadable from
msdn.microsoft.com/downloads/updates. If you already have it you might want
to verify that you've got the latest version.
Here's what works for me in SQL 2005 using the Linked Server dialog:
Providers list: VFPOLEDB shows as an entry
Linked Servers > New Linked Server ...
Linked Server: MyLinkedServer
Provider: Choose "Microsoft OLE DB Provider for Visual FoxPro
Product name: Visual FoxPro (I think this is optional)
Data source: "C:\Program Files\Microsoft Visual
FoxPro9\Samples\Northwind\Northwind.dbc" (Include quotes since there's
spaces in the string.)
Provider string: VFPOLEDB.1
Location: (blank)
Catalog: (blank)
Security page and Server Options page take defaults.
Cindy Winegarden MCSD, Microsoft Visual FoxPro MVP
cindy_winegarden@.msn.com www.cindywinegarden.com
"djh" <djh@.discussions.microsoft.com> wrote in message
news:F93EBC44-2A78-4801-8DB0-C35F13CE876B@.microsoft.com...[vbcol=seagreen]
> Think I am closer now. It turns out that MDAC 2.8 SP2 for Windows Server
> 2003
> is not showing VFPOLEDB as a component when I run the component checker. I
> have tried regsvr32 to register the dll but no luck. Thoughts on how to
> get
> MDAC to recognize this OLE DB provider?
>
> "djh" wrote:
>

Errors Connecting...

-- EDIT --
I'd like to add that I've updated all the references in my project to SQL 10.0
-

Hello,

I am just getting started evaluating 2008 (July CTP) with our existing codebase. When I connect to the server to initiate the process of installing our database, I get the following exception:
{"This SQL Server version (10.0) is not supported."}. Could this be related to my workstation not having an up to date .NET framework?

The code to connect is:

.....
Microsoft.SqlServer.Management.Smo.Server server = null;
try
{
SqlConnection sqlConnection = new SqlConnection(@."Integrated Security=SSPI; Data Source=" + tserver);

//build a "serverConnection" with the information of the "sqlConnection"
Microsoft.SqlServer.Management.Common.ServerConnection serverConnection =
new Microsoft.SqlServer.Management.Common.ServerConnection(sqlConnection);

//The "serverConnection is used in the ctor of the Server.
server = new Server(serverConnection);

// The actual connection is made when a property is retrieved so try to get version.
// an error means could not connect, most likely due to security
//string x = server.Information.Version.ToString();
System.Version x = server.Information.Version;
}
catch(Exception ex)
{
server = null;
Errors = "Unable to connect to the " + tserver + " server.\r\n" + ex.Message;
}
......
You probably need to use the updated assemblies. After installing SQL Server 2008, you will find them in C:\Program Files\Microsoft SQL Server\100\SDK\Assemblies.

In particular Microsoft.SQLServer.Smo.dll|||My problem was that I missed updating the assemblies in a couple of the DLL's in the project, which caused the problem.

error_number() won't return error code

hi all,

i have sql statement in ExecuteSQLTask, connecting to AdventureWorks

BEGIN TRY
insert into person.contacts(contactid) values (1);
END TRY
BEGIN CATCH
SELECT ERROR_NUMBER() AS ErrorNumber;
END CATCH;

i purposely put a table that does not exist in the database to catch
the error. however, the error number that is 208 won't appear, instead
the whole error message will be displayed.

if i change the query in try block to
insert into person.contact(contactid) values (1);

it'll return the error number 544, which is correct.

what did i do wrong?
thanks!

You did nothing wrong.

Try/Catch doesn't catch all errors, specifically compile time errors (there are a few others). Try running the following, "more obvious" compile time error. This compile time error won't be caught either, since the execution of the statements never happens.

BEGIN TRY

PRINT 'Inside Try-Block'

'This is not sql'

END TRY

BEGIN CATCH

SELECT error_number() as 'Error In Try Block'

END CATCH

|||

thanks jaegd for your reply.. it didn't say in BOL that try/catch doesn't catch all errors or maybe i left that out.

anyhow, my problem is not solved. is there an alternative where i can catch any errors that occur?

|||See the following BOL reference for the constructs which Try/Catch does not trap.
http://msdn2.microsoft.com/en-us/library/ms175976.aspx

However, To catch almost every error (including compile time and deferred name resolution errors), you can use dynamic SQL in combination with sp_executesql.

BEGIN TRY
DECLARE @.not_sql NVARCHAR(100)
SET @.not_sql = 'This is not sql'
EXEC sp_executesql @.not_sql

END TRY
BEGIN CATCH
SELECT ERROR_NUMBER() AS ErrorNumber
END CATCH

Note that almost every error is caught with this method, because broken client connections are not

trapped, hopefully for relatively obvious reasons (you have no

connection).|||thanks a lot jaegd

error:40 connecting with sql server 2000

Hi
I am getting this really annoying error that I cant resolve.
I have created a website that accesses a SQL SERVER 2000 database and
it works perfectly on my home machine. The error has occurred when I
have transferred it to my hosts server.
This is the error:
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: Named Pipes Provider, error: 40 - Could not
open a connection to SQL Server)
This is my connection string:
<add key="ConnectionString" value="Provider=sqloledb;Data
Source=hostsserver****,1433;Initial
Catalog=db******;User Id=dbo*******;Password=********; "/>
It says I am trying to connect to a SQL SERVER 2000 database as this is
what I devloped the site on so I do not know why it thinks I am trying
to connect to SQL SERVER 2005.
Can anyone help?Is your host database server and your home database server the same? It look
s
like that your host database server is in SQL Server 2005.
By the way do you use outside host provider? If yes, you might want to
consider giving them an e-mail. Looking at the connection string, I don't se
e
any problem:
"Provider=SQLOLEDB;Data Source=Your_Server_Name;Initial Catalog=
Your_Database_Name;UserId=Your_Username;
Password=Your_Password;" .
So I am thinking that the host database server might be on different port
number than 1433 or use a named instance?
Lucas
"chrisbarber1@.gmail.com" wrote:

> Hi
> I am getting this really annoying error that I cant resolve.
> I have created a website that accesses a SQL SERVER 2000 database and
> it works perfectly on my home machine. The error has occurred when I
> have transferred it to my hosts server.
> This is the error:
> 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: Named Pipes Provider, error: 40 - Could not
> open a connection to SQL Server)
>
> This is my connection string:
> <add key="ConnectionString" value="Provider=sqloledb;Data
> Source=hostsserver****,1433;Initial
> Catalog=db******;User Id=dbo*******;Password=********; "/>
>
> It says I am trying to connect to a SQL SERVER 2000 database as this is
> what I devloped the site on so I do not know why it thinks I am trying
> to connect to SQL SERVER 2005.
> Can anyone help?
>|||Thanks for your reply.

> Is your host database server and your home database server the same?
Yes both are on sql server 2000

> By the way do you use outside host provider? If yes, you might want to
> consider giving them an e-mail.
The host providor has been absolutely hopeless.

> So I am thinking that the host database server might be on different port
> number than 1433 or use a named instance?
I'll look in to this although on the hosts control panel definately
says 1433.
Any other ideas?|||<chrisbarber1@.gmail.com> wrote in message
news:1149755323.823279.142210@.u72g2000cwu.googlegroups.com...
> Hi
> I am getting this really annoying error that I cant resolve.
> I have created a website that accesses a SQL SERVER 2000 database and
> it works perfectly on my home machine. The error has occurred when I
> have transferred it to my hosts server.
> This is the error:
> 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: Named Pipes Provider, error: 40 - Could not
> open a connection to SQL Server)
>
It really sounds like the ISP is full of it and somehow your site is trying
to connect to a 2005 server with remote connections turned off.

> This is my connection string:
> <add key="ConnectionString" value="Provider=sqloledb;Data
> Source=hostsserver****,1433;Initial
> Catalog=db******;User Id=dbo*******;Password=********; "/>
>
> It says I am trying to connect to a SQL SERVER 2000 database as this is
> what I devloped the site on so I do not know why it thinks I am trying
> to connect to SQL SERVER 2005.
> Can anyone help?
>|||Check the value of instance config parameter: "remote access" and see
whether it is enabled..
> sp_configure 'remote access'
Jayesh
<chrisbarber1@.gmail.com> wrote in message
news:1149755323.823279.142210@.u72g2000cwu.googlegroups.com...
> Hi
> I am getting this really annoying error that I cant resolve.
> I have created a website that accesses a SQL SERVER 2000 database and
> it works perfectly on my home machine. The error has occurred when I
> have transferred it to my hosts server.
> This is the error:
> 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: Named Pipes Provider, error: 40 - Could not
> open a connection to SQL Server)
>
> This is my connection string:
> <add key="ConnectionString" value="Provider=sqloledb;Data
> Source=hostsserver****,1433;Initial
> Catalog=db******;User Id=dbo*******;Password=********; "/>
>
> It says I am trying to connect to a SQL SERVER 2000 database as this is
> what I devloped the site on so I do not know why it thinks I am trying
> to connect to SQL SERVER 2005.
> Can anyone help?
>

error:40 connecting with sql server 2000

Hi
I am getting this really annoying error that I cant resolve.
I have created a website that accesses a SQL SERVER 2000 database and
it works perfectly on my home machine. The error has occurred when I
have transferred it to my hosts server.
This is the error:
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: Named Pipes Provider, error: 40 - Could not
open a connection to SQL Server)
This is my connection string:
<add key="ConnectionString" value="Provider=sqloledb;Data
Source=hostsserver****,1433;Initial
Catalog=db******;User Id=dbo*******;Password=********; "/>
It says I am trying to connect to a SQL SERVER 2000 database as this is
what I devloped the site on so I do not know why it thinks I am trying
to connect to SQL SERVER 2005.
Can anyone help?Is your host database server and your home database server the same? It looks
like that your host database server is in SQL Server 2005.
By the way do you use outside host provider? If yes, you might want to
consider giving them an e-mail. Looking at the connection string, I don't see
any problem:
"Provider=SQLOLEDB;Data Source=Your_Server_Name;Initial Catalog=Your_Database_Name;UserId=Your_Username;Password=Your_Password;" .
So I am thinking that the host database server might be on different port
number than 1433 or use a named instance?
Lucas
"chrisbarber1@.gmail.com" wrote:
> Hi
> I am getting this really annoying error that I cant resolve.
> I have created a website that accesses a SQL SERVER 2000 database and
> it works perfectly on my home machine. The error has occurred when I
> have transferred it to my hosts server.
> This is the error:
> 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: Named Pipes Provider, error: 40 - Could not
> open a connection to SQL Server)
>
> This is my connection string:
> <add key="ConnectionString" value="Provider=sqloledb;Data
> Source=hostsserver****,1433;Initial
> Catalog=db******;User Id=dbo*******;Password=********; "/>
>
> It says I am trying to connect to a SQL SERVER 2000 database as this is
> what I devloped the site on so I do not know why it thinks I am trying
> to connect to SQL SERVER 2005.
> Can anyone help?
>|||Thanks for your reply.
> Is your host database server and your home database server the same?
Yes both are on sql server 2000
> By the way do you use outside host provider? If yes, you might want to
> consider giving them an e-mail.
The host providor has been absolutely hopeless.
> So I am thinking that the host database server might be on different port
> number than 1433 or use a named instance?
I'll look in to this although on the hosts control panel definately
says 1433.
Any other ideas?|||<chrisbarber1@.gmail.com> wrote in message
news:1149755323.823279.142210@.u72g2000cwu.googlegroups.com...
> Hi
> I am getting this really annoying error that I cant resolve.
> I have created a website that accesses a SQL SERVER 2000 database and
> it works perfectly on my home machine. The error has occurred when I
> have transferred it to my hosts server.
> This is the error:
> 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: Named Pipes Provider, error: 40 - Could not
> open a connection to SQL Server)
>
It really sounds like the ISP is full of it and somehow your site is trying
to connect to a 2005 server with remote connections turned off.
> This is my connection string:
> <add key="ConnectionString" value="Provider=sqloledb;Data
> Source=hostsserver****,1433;Initial
> Catalog=db******;User Id=dbo*******;Password=********; "/>
>
> It says I am trying to connect to a SQL SERVER 2000 database as this is
> what I devloped the site on so I do not know why it thinks I am trying
> to connect to SQL SERVER 2005.
> Can anyone help?
>|||Check the value of instance config parameter: "remote access" and see
whether it is enabled..
> sp_configure 'remote access'
Jayesh
<chrisbarber1@.gmail.com> wrote in message
news:1149755323.823279.142210@.u72g2000cwu.googlegroups.com...
> Hi
> I am getting this really annoying error that I cant resolve.
> I have created a website that accesses a SQL SERVER 2000 database and
> it works perfectly on my home machine. The error has occurred when I
> have transferred it to my hosts server.
> This is the error:
> 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: Named Pipes Provider, error: 40 - Could not
> open a connection to SQL Server)
>
> This is my connection string:
> <add key="ConnectionString" value="Provider=sqloledb;Data
> Source=hostsserver****,1433;Initial
> Catalog=db******;User Id=dbo*******;Password=********; "/>
>
> It says I am trying to connect to a SQL SERVER 2000 database as this is
> what I devloped the site on so I do not know why it thinks I am trying
> to connect to SQL SERVER 2005.
> Can anyone help?
>

error:26 when connecting to sql server express...

I've got an ASP.net 2.0 application that I published and moved to a publicly available server. From my machine it works fine, but not from the production machine.

I'm attempting to connect to a machine that has sql server express installed.

The message in the browser:

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)

So, I went by the kb article and made sure tcpip is enabled. This uses port 3288. server browser is enabled and the machine accepts remote connections.My connection string is (minus the ip & user/pwd):

<add name="IRRMAConnectionString" connectionString="Data Source=<ip_address>\SQLEXPRESS,3288;Initial Catalog=IRRMA;User ID=<user>;password=<pwd>" providerName="System.Data.SqlClient"/>

I can ping the db server from my app server. On my dev machine it connects. Windows firewall is turned off on the db server.

This seems to be an issue with a firewall, I think?

Any direction would be appreciated.

Thanks,

Scott Jones

Scott@.fourindianajones.com

You should check this out and go from there.

http://blogs.msdn.com/sql_protocols/archive/2007/05/13/sql-network-interfaces-error-26-error-locating-server-instance-specified.aspx

I would say it has to do with the UDP 1434 or the sqlbrowser.exe in the exceptions. But once you follow all the steps you should get closer to the resolution.

error:26 when connecting to sql server express...

I've got an ASP.net 2.0 application that I published and moved to a publicly available server. From my machine it works fine, but not from the production machine.

I'm attempting to connect to a machine that has sql server express installed.

The message in the browser:

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)

So, I went by the kb article and made sure tcpip is enabled. This uses port 3288. server browser is enabled and the machine accepts remote connections.My connection string is (minus the ip & user/pwd):

<add name="IRRMAConnectionString" connectionString="Data Source=<ip_address>\SQLEXPRESS,3288;Initial Catalog=IRRMA;User ID=<user>;password=<pwd>" providerName="System.Data.SqlClient"/>

I can ping the db server from my app server. On my dev machine it connects. Windows firewall is turned off on the db server.

This seems to be an issue with a firewall, I think?

Any direction would be appreciated.

Thanks,

Scott Jones

Scott@.fourindianajones.com

You should check this out and go from there.

http://blogs.msdn.com/sql_protocols/archive/2007/05/13/sql-network-interfaces-error-26-error-locating-server-instance-specified.aspx

I would say it has to do with the UDP 1434 or the sqlbrowser.exe in the exceptions. But once you follow all the steps you should get closer to the resolution.

error:26 Error Locating Server/Instance Specified

I am having trouble connecting to Sql Server 2005 Express from asp.net
2.0 app on Windows Server 2003. I am using Sql Server Authentication,
and I tried the below article's suggestions a number of times. When I
login to to the machine, and login, I am able to get authenticated.
However, when I debug my application, I get the error below. Do I have
to give the sql server authenticaed account I created certain
permissions? Whould I set a port, and use the ipaddress rather than
the server name? Any suggestions would be greatly appreciated.
http://support.microsoft.com/kb/914277
My Error:
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)
My Connection String:
<add key="ConnectionString"
value="server=MyServerName;uid=MyUserName;pwd=MyPasswd;database=MyDB"/>On Feb 1, 5:20=A0pm, carlos <carlosubu...@.gmail.com> wrote:
> I am having trouble connecting to Sql Server 2005 Express from asp.net
> 2.0 app on Windows Server 2003. I am using Sql Server Authentication,
> and I tried the below article's suggestions a number of times. When I
> login to to the machine, and login, I am able to get authenticated.
> However, when I debug my application, I get the error below. Do I have
> to give the sql server authenticaed account I created certain
> permissions? Whould I set a port, and use the ipaddress rather than
> the server name? Any suggestions would be greatly appreciated.
> http://support.microsoft.com/kb/914277
> My Error:
> 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)
> My Connection String:
> =A0<add key=3D"ConnectionString"
> value=3D"server=3DMyServerName;uid=3DMyUserName;pwd=3DMyPasswd;database=3D=MyDB"/>
Update:
I changed the connection string to use the ipaddress, and a port that
I set in the TCPIP settings, and now i'm getting the below message:
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: TCP Provider, error: 0 - No connection could
be made because the target machine actively refused it.)
I'm thinking this may be a permission problem'|||Hi Carlos,
By default, SQL Server 2005 Express, Evaluation, and Developer editions
allow local client connections only. Enterprise, Standard, and Workgroup
editions also listen for remote client connections over TCP/IP.
you ned to enable Remote Connections option using
Surface Area Configuration for Services and Connections (Remote Connections)
- Database Engine
You must restart the Database Engine instance's service to apply changes.
Regards,
Amol R. Lembhe
"carlos" wrote:
> On Feb 1, 5:20 pm, carlos <carlosubu...@.gmail.com> wrote:
> > I am having trouble connecting to Sql Server 2005 Express from asp.net
> > 2.0 app on Windows Server 2003. I am using Sql Server Authentication,
> > and I tried the below article's suggestions a number of times. When I
> > login to to the machine, and login, I am able to get authenticated.
> > However, when I debug my application, I get the error below. Do I have
> > to give the sql server authenticaed account I created certain
> > permissions? Whould I set a port, and use the ipaddress rather than
> > the server name? Any suggestions would be greatly appreciated.
> >
> > http://support.microsoft.com/kb/914277
> >
> > My Error:
> >
> > 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)
> >
> > My Connection String:
> > <add key="ConnectionString"
> > value="server=MyServerName;uid=MyUserName;pwd=MyPasswd;database=MyDB"/>
> Update:
> I changed the connection string to use the ipaddress, and a port that
> I set in the TCPIP settings, and now i'm getting the below message:
> 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: TCP Provider, error: 0 - No connection could
> be made because the target machine actively refused it.)
> I'm thinking this may be a permission problem'
>

Error: SQL Server does not exist or access denied. (Error code 17).

Hello everyone.

I am trying to install Project Server, and i'm having issues with sharepoint, and connecting to SQL:

dataserver is running sbs2003 sql2003 and analsys services.

server2 is running server2003 is to be the application server for project.

ProjectDb is the database that i have setup in sql.

username is the account that can control everything as administrer.

in Sharepoint is asks for the database server: <<dataserver>>

SQL Server database name: <<ProjectDb>>

I'm using windoes authentication and then i click ok, and get the error message.

I've also see the error message can not find the SQL Server, and access denied. Under ODBC i have installed the sql server information under System DSN.

Any help would be great.

Thanks

Everett Buel

Start by confirming that SQL Server is running and that you can access it directly. I take it this is SQL Server 2000, so you should have Query Analyzer installed and you can use it to try to connect to your database. Also (more basic) check to confirm that the SQL Server service is started.|||

SQL is running I have the Query Analyzer installed. All services are started. I can access the Sql Server from my desktop so i know that part is working.

But when I try to start up the data connection of the sharepoint services on the server running server 2003 i still get the error message.

Data services are all running on both servers.

Thanks for your reply

Everett Buel

|||

It would be nice if you two finished this thread. I can't tell you how many times I've gone searching the MS web site for resolution of error messages only to find this type of non-solution. If this is all you can do then why don't you delete the useless thread.

Bryce

Error: SQL Server does not exist or access denied. (Error code 17).

Hello everyone.

I am trying to install Project Server, and i'm having issues with sharepoint, and connecting to SQL:

dataserver is running sbs2003 sql2003 and analsys services.

server2 is running server2003 is to be the application server for project.

ProjectDb is the database that i have setup in sql.

username is the account that can control everything as administrer.

in Sharepoint is asks for the database server: <<dataserver>>

SQL Server database name: <<ProjectDb>>

I'm using windoes authentication and then i click ok, and get the error message.

I've also see the error message can not find the SQL Server, and access denied. Under ODBC i have installed the sql server information under System DSN.

Any help would be great.

Thanks

Everett Buel

Start by confirming that SQL Server is running and that you can access it directly. I take it this is SQL Server 2000, so you should have Query Analyzer installed and you can use it to try to connect to your database. Also (more basic) check to confirm that the SQL Server service is started.|||

SQL is running I have the Query Analyzer installed. All services are started. I can access the Sql Server from my desktop so i know that part is working.

But when I try to start up the data connection of the sharepoint services on the server running server 2003 i still get the error message.

Data services are all running on both servers.

Thanks for your reply

Everett Buel

|||

It would be nice if you two finished this thread. I can't tell you how many times I've gone searching the MS web site for resolution of error messages only to find this type of non-solution. If this is all you can do then why don't you delete the useless thread.

Bryce