Can't run aspnet_regsql.e xe on remote machine

[Amit]

I cannot run aspnet_regsql.e xe on a remote machine. The remote machine is
running MSSQL 2000 and is behind my local network. Its basically a sandbox
machine.

I specify my remote machine's name (Nightcrawler), SQL Server user name and
password at the "Select the Server and Database" screen.

I get the following error.

System.Web.Http Exception: Unable to connect to SQL Server database. --->
System.Data.Sql Client.SqlExcep tion: Timeout expired. The timeout period
elapsed prior to completion of the operation or the server is not responding.

I also have tried entering the IP address of the remote machine with no luck.

Please help!!

Thanks

[Gabriel Lozano-Morán]

Hello Amit,

Create a new .NET 2.0 console application on your client machine and copy
paste the following code. In this code I assume that you use a trusted connection,
you can try with SQL Server authentication by removing the trusted_connect ion
from the connection string and specifying the UID and PWD:

using System;
using System.Data.Sql Client;

namespace ConsoleApplicat ion1
{
internal class Program
{
private static void Main(string[] args)
{
string connectionStrin g = "server=Nightcr awler;Trusted_C onnection=true; UID=userid;PWD= password;";
using (SqlConnection connection = new SqlConnection(c onnectionString ))
{
connection.Open ();
SqlCommand command = new SqlCommand("SEL ECT name FROM sysdatabases
ORDER BY name", connection);
using (SqlDataReader reader = command.Execute Reader())
{
while (reader.Read())
{
Console.WriteLi ne(reader.GetSt ring(0));
}
}
}
Console.ReadKey ();
}
}
}

If you run this on the same machine from where you are trying to run ASPNET_REGSQL.e xe
it should throw the same exception. As far as I know you can't change the
command timeout that for ASPNET_REGSQL.e xe, the command timeout is defaulted
to 30 secs.

Gabriel Lozano-Morán
The .NET Aficionado
http://www.pointerx.net

[Gabriel Lozano-Morán]

As replied on your other post enter the following text as your server name:

Nightcrawler;Co nnect Timeout=180

This will increase the connection timeout to 3 minutes but it might be
interesting investigating why connecting to the server takes longer than 15
secs. You could ask for help on this matter on one of the SQL Server
newsgroups.

Gabriel Lozano-Morán
The .NET Aficionado
http://www.pointerx.net
"Gabriel Lozano-Morán" <ab***@frontbri dge.comwrote in message
news:e9******** *************** ***@news.micros oft.com...

Hello Amit,

Create a new .NET 2.0 console application on your client machine and copy
paste the following code. In this code I assume that you use a trusted
connection, you can try with SQL Server authentication by removing the
trusted_connect ion from the connection string and specifying the UID and
PWD:

using System;
using System.Data.Sql Client;

namespace ConsoleApplicat ion1
{
internal class Program
{
private static void Main(string[] args)
{
string connectionStrin g =
"server=Nightcr awler;Trusted_C onnection=true; UID=userid;PWD= password;";
using (SqlConnection connection = new
SqlConnection(c onnectionString ))
{
connection.Open ();
SqlCommand command = new SqlCommand("SEL ECT name FROM
sysdatabases ORDER BY name", connection);
using (SqlDataReader reader = command.Execute Reader())
{
while (reader.Read())
{
Console.WriteLi ne(reader.GetSt ring(0));
}
}
}
Console.ReadKey ();
}
}
}

If you run this on the same machine from where you are trying to run
ASPNET_REGSQL.e xe it should throw the same exception. As far as I know you
can't change the command timeout that for ASPNET_REGSQL.e xe, the command
timeout is defaulted to 30 secs.

Gabriel Lozano-Morán
The .NET Aficionado
http://www.pointerx.net

[Gabriel Lozano-Morán]

As replied on your other post enter the following text as your server name:

Nightcrawler;Co nnect Timeout=180

This will increase the connection timeout to 3 minutes but it might be
interesting investigating why connecting to the server takes longer than 15
secs. You could ask for help on this matter on one of the SQL Server
newsgroups.

Gabriel Lozano-Morán
The .NET Aficionado
http://www.pointerx.net
"Gabriel Lozano-Morán" <ab***@frontbri dge.comwrote in message
news:e9******** *************** ***@news.micros oft.com...

Hello Amit,

Create a new .NET 2.0 console application on your client machine and copy
paste the following code. In this code I assume that you use a trusted
connection, you can try with SQL Server authentication by removing the
trusted_connect ion from the connection string and specifying the UID and
PWD:

using System;
using System.Data.Sql Client;

namespace ConsoleApplicat ion1
{
internal class Program
{
private static void Main(string[] args)
{
string connectionStrin g =
"server=Nightcr awler;Trusted_C onnection=true; UID=userid;PWD= password;";
using (SqlConnection connection = new
SqlConnection(c onnectionString ))
{
connection.Open ();
SqlCommand command = new SqlCommand("SEL ECT name FROM
sysdatabases ORDER BY name", connection);
using (SqlDataReader reader = command.Execute Reader())
{
while (reader.Read())
{
Console.WriteLi ne(reader.GetSt ring(0));
}
}
}
Console.ReadKey ();
}
}
}

If you run this on the same machine from where you are trying to run
ASPNET_REGSQL.e xe it should throw the same exception. As far as I know you
can't change the command timeout that for ASPNET_REGSQL.e xe, the command
timeout is defaulted to 30 secs.

Gabriel Lozano-Morán
The .NET Aficionado
http://www.pointerx.net

[Amit]

Dude, thank you! I didn't even realize injecting a connect timeout would
work, but it did. I used Nightcrawler;Co nnect Timeout=180 and it was able to
find all the databases on that server. It took maybe 15-20 seconds....don' t
know why, maybe because its a slow machine or its going over wireless.

Much thanks Gabriel! Ahh...relief.

Amit

"Gabriel Lozano-Morán" wrote:

As replied on your other post enter the following text as your server name:

Nightcrawler;Co nnect Timeout=180

This will increase the connection timeout to 3 minutes but it might be
interesting investigating why connecting to the server takes longer than 15
secs. You could ask for help on this matter on one of the SQL Server
newsgroups.

Gabriel Lozano-Morán
The .NET Aficionado
http://www.pointerx.net
"Gabriel Lozano-Morán" <ab***@frontbri dge.comwrote in message
news:e9******** *************** ***@news.micros oft.com...

Hello Amit,

Create a new .NET 2.0 console application on your client machine and copy
paste the following code. In this code I assume that you use a trusted
connection, you can try with SQL Server authentication by removing the
trusted_connect ion from the connection string and specifying the UID and
PWD:

using System;
using System.Data.Sql Client;

namespace ConsoleApplicat ion1
{
internal class Program
{
private static void Main(string[] args)
{
string connectionStrin g =
"server=Nightcr awler;Trusted_C onnection=true; UID=userid;PWD= password;";
using (SqlConnection connection = new
SqlConnection(c onnectionString ))
{
connection.Open ();
SqlCommand command = new SqlCommand("SEL ECT name FROM
sysdatabases ORDER BY name", connection);
using (SqlDataReader reader = command.Execute Reader())
{
while (reader.Read())
{
Console.WriteLi ne(reader.GetSt ring(0));
}
}
}
Console.ReadKey ();
}
}
}

If you run this on the same machine from where you are trying to run
ASPNET_REGSQL.e xe it should throw the same exception. As far as I know you
can't change the command timeout that for ASPNET_REGSQL.e xe, the command
timeout is defaulted to 30 secs.

Gabriel Lozano-Morán
The .NET Aficionado
http://www.pointerx.net