Offisite DB Connection Failure

I am trying to write a simple program for test purpose with VB .Net 2005 and SQL Server Express 2005. My server is not even in the same state as me, but I have the following on the server:

Server 2003 Web Edition SP1
SQL Server Express 2005

I am writing in the following:
Visual Basic 2005 Pro Edition

I have read where you can setup Express to allow TCP/IP connection, and I have done what it stated HERE (http://www.datamasker.com/SSE2005_NetworkCfg.htm). However, I am still not able to connect to the DB on the remote server.

I go to:
Tools --> Connect to Server --> Type IP and get the connection failed to connec to server "xxx.xxx.xxx.xxx"
I even tried:
Tools --> Connect to Server --> Type IP\SQLEXPRESS and get the connection failed to connec to server "xxx.xxx.xxx.xxx"

Has anyone been able to do this, or am I wasting my time? If I can get the SQL Server to do as requested then I am going to purchase and work with it, however, I want to test out before I spend the $$$$$ to begin the full project. If anyone can be of assistance here I would appreciate it.

Thanks in advance.Can you access the server on a remote machine on the same location as the server is (that is, in the same domain, at least without going through a firewall) ? It might have something to do with TCP/IP port 1433 that is not opened in the firewall ... and believe me, you don't want that !!!
Is your SQL server directly accessible from the Internet with IP address xxx.xxx.xxx.xxx ? Or should some routing be done because it's behind a firewall ? I would check your network admin for some assistence ...

Gr,
Yveausql

ODBC-driver reconnect after network failure?

Hi!
Im wondering if its possible to have the ODBC-driver to reconnect after
there has been an network failure ( without having to recreate the
CDatabase-object and its CRecordsets in VC7++ )?
Anyone has any ideas?
Sorry, all the existing SQL drivers I know of are not designed to do this.
So you have to do this programmatically yourself.
Matt Neerincx [MSFT]
This posting is provided "AS IS", with no warranties, and confers no rights.
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.
"Markus Frank" <markus.frank@.gabria.se> wrote in message
news:eQhQX9lnFHA.2152@.TK2MSFTNGP14.phx.gbl...
> Hi!
> Im wondering if its possible to have the ODBC-driver to reconnect after
> there has been an network failure ( without having to recreate the
> CDatabase-object and its CRecordsets in VC7++ )?
> Anyone has any ideas?
>

ODBC-driver reconnect after network failure?

Hi!
Im wondering if its possible to have the ODBC-driver to reconnect after
there has been an network failure ( without having to recreate the
CDatabase-object and its CRecordsets in VC7++ )'
Anyone has any ideas?Sorry, all the existing SQL drivers I know of are not designed to do this.
So you have to do this programmatically yourself.
Matt Neerincx [MSFT]
This posting is provided "AS IS", with no warranties, and confers no rights.
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.
"Markus Frank" <markus.frank@.gabria.se> wrote in message
news:eQhQX9lnFHA.2152@.TK2MSFTNGP14.phx.gbl...
> Hi!
> Im wondering if its possible to have the ODBC-driver to reconnect after
> there has been an network failure ( without having to recreate the
> CDatabase-object and its CRecordsets in VC7++ )'
> Anyone has any ideas?
>

OdbcCommand Parameter Failure

Hi,

I tried to create a utility method to accept the name of a stored procedure and an array of OdbcParameter objects. When I try to add the parameters from the array in the code, the parameters aren't recognized:

foreach (OdbcParameter prmin prm_array)cmd.Parameters.add (prm);

OR

cmd.Parameters.AddRange (prm_array);

However, when I hardcode the parameters without using the argument of the function, it works perfectly:

cmd.Parameters.Add ("@.login", OdbcType.VarChar, 50,"Joe");cmd.Parameters.Add ("@.password", OdbcType.VarChar, 50,"Bob");

I know the method calling the utility function is passing the parameters correctly; in fact, if I hard code the parameters in the utility function but add them with a foreach like above or using the AddRange function, it just does not recognize the parameters.

I've worked too long on this so I'm using an inelegant solution, but this nuance is very frustrating. Any possible insight?

~ mellamokb

Is the cmd object an ODBCCommand object. If not, this sure won't work.|||

Yep. I only use Odbc.... objects.

~ mellamokb

|||

can you post the entire function, this would be helpful

thanks

|||Yes, if it was not recognized, what runtime exception or compile time error was thrown?|||

I got it to work by reconstructing the parameters from an OdbcParameter array passed and by using the AddWithValue command:

foreach (OdbcParameter prmin prm_array) cmd.Parameters.AddWithValue(prm.ParameterName, prm.Value);

I'll call that good enough; but it doesn't make sense why cmd.Parameters.Add(prm_object) is different than cmd.Parameters.Add([parameter_name], [datatype], [datasize], [value]) when the prm_object and the hard-coded parameters are the same information.

This situation is independent of the function it is in; I've generalized to any situation, and there's no reason why it would work in a modified test case but not in the utility function I've created.

But I've seen stranger things, I guess.

Kevin Yu: The runtime exception is simply that the command cannot find the needed parameter, as if I hadn't passed it at all, when I use Add(prm_object); but using the four parameter version of Add works fine, even if the four parameters are the same as the four used to construct the new OdbcParameter object.

~ mellamokb

odbc sql server driver

I am getting an error that reads:
Microsoft ODBC SQL Server Driver Communication Link failure: SQL Server Error
What do I do to correct this problem.
Thanks,
CK
CK,
What are you doing to get the error?
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
CK wrote:
> I am getting an error that reads:
> Microsoft ODBC SQL Server Driver Communication Link failure: SQL Server Error
> What do I do to correct this problem.
> Thanks,
> CK

odbc sql server driver

I am getting an error that reads:
Microsoft ODBC SQL Server Driver Communication Link failure: SQL Server Erro
r
What do I do to correct this problem.
Thanks,
CKCK,
What are you doing to get the error?
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
CK wrote:
> I am getting an error that reads:
> Microsoft ODBC SQL Server Driver Communication Link failure: SQL Server Er
ror
> What do I do to correct this problem.
> Thanks,
> CK

odbc sql server driver

I am getting an error that reads:
Microsoft ODBC SQL Server Driver Communication Link failure: SQL Server Error
What do I do to correct this problem.
Thanks,
CKCK,
What are you doing to get the error?
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
CK wrote:
> I am getting an error that reads:
> Microsoft ODBC SQL Server Driver Communication Link failure: SQL Server Error
> What do I do to correct this problem.
> Thanks,
> CK