"Amit" <A***@discussions.microsoft.com> wrote in message
news:654C4993-2F8E-4F74-AB62-C81DEE5EFA2F@microsoft.com...
>I have a development setup as follows:
>
> 2 machines both running win xp pro, with machine A running .net 2.0 and
> machine B acting as my database server running sql server 2000.
>
> I want to use ASP.NET 2.0 new forms authentication configuration tools but
> I
> want the information stored in my sql server 2000 database rather than the
> standard sql express database.  I ran aspnet_regsql.exe from machine A,
> specified machine B as the server and provided the sql server userid and
> password; however, it cannot connect and gives a timeout exception.
>
> The second machine is running as I can see it in windows explorer, and can
> connect to the database from machine A's SQL Server Enterprise manager.
>
> Could a possible problem be that I need to install .net 2.0 on my database
> server (machine B)?  Currently, its running .net 1.1 but I wouldn't think
> that would make a difference as its just the database server.  Machine B
> is
> running wirelessly through a netgear router.

"Amit" wrote:

> I have a development setup as follows:
>
> 2 machines both running win xp pro, with machine A running .net 2.0 and
> machine B acting as my database server running sql server 2000.
>
> I want to use ASP.NET 2.0 new forms authentication configuration tools but I
> want the information stored in my sql server 2000 database rather than the
> standard sql express database.  I ran aspnet_regsql.exe from machine A,
> specified machine B as the server and provided the sql server userid and
> password; however, it cannot connect and gives a timeout exception.
>
> The second machine is running as I can see it in windows explorer, and can
> connect to the database from machine A's SQL Server Enterprise manager.
>
> Could a possible problem be that I need to install .net 2.0 on my database
> server (machine B)?  Currently, its running .net 1.1 but I wouldn't think
> that would make a difference as its just the database server.  Machine B is
> running wirelessly through a netgear router.

"Peter Bromberg [C# MVP]" wrote:

> Make sure your SQL Server is allowing remote connections and has mixed mode
> (Windows and SQL Server) authentication enabled. Make a page with nothing but
> a a sample connection and try  / catch so you can output the result of any
> exception Message and stacktrace.
> Peter
>
>
> --
> Co-founder, Eggheadcafe.com developer portal:
> http://www.eggheadcafe.com
> UnBlog:
> http://petesbloggerama.blogspot.com
>
>
>
>
> "Amit" wrote:
>
> > I have a development setup as follows:
> >
> > 2 machines both running win xp pro, with machine A running .net 2.0 and
> > machine B acting as my database server running sql server 2000.
> >
> > I want to use ASP.NET 2.0 new forms authentication configuration tools but I
> > want the information stored in my sql server 2000 database rather than the
> > standard sql express database.  I ran aspnet_regsql.exe from machine A,
> > specified machine B as the server and provided the sql server userid and
> > password; however, it cannot connect and gives a timeout exception.
> >
> > The second machine is running as I can see it in windows explorer, and can
> > connect to the database from machine A's SQL Server Enterprise manager.
> >
> > Could a possible problem be that I need to install .net 2.0 on my database
> > server (machine B)?  Currently, its running .net 1.1 but I wouldn't think
> > that would make a difference as its just the database server.  Machine B is
> > running wirelessly through a netgear router.

"Amit" wrote:

> How do I check if SQL allows remote connections and has mixed mode
> authentication?   I checked the "remote login timeout" for SQL server and its
> set at 2000.  Is this the setting you're referring to?
>
> I can run another web application in .net 2.0 fine when I explicitly set the
> connect timeout setting to 2000 in the connection string.
>
> "Peter Bromberg [C# MVP]" wrote:
>
> > Make sure your SQL Server is allowing remote connections and has mixed mode
> > (Windows and SQL Server) authentication enabled. Make a page with nothing but
> > a a sample connection and try  / catch so you can output the result of any
> > exception Message and stacktrace.
> > Peter
> >
> >
> > --
> > Co-founder, Eggheadcafe.com developer portal:
> > http://www.eggheadcafe.com
> > UnBlog:
> > http://petesbloggerama.blogspot.com
> >
> >
> >
> >
> > "Amit" wrote:
> >
> > > I have a development setup as follows:
> > >
> > > 2 machines both running win xp pro, with machine A running .net 2.0 and
> > > machine B acting as my database server running sql server 2000.
> > >
> > > I want to use ASP.NET 2.0 new forms authentication configuration tools but I
> > > want the information stored in my sql server 2000 database rather than the
> > > standard sql express database.  I ran aspnet_regsql.exe from machine A,
> > > specified machine B as the server and provided the sql server userid and
> > > password; however, it cannot connect and gives a timeout exception.
> > >
> > > The second machine is running as I can see it in windows explorer, and can
> > > connect to the database from machine A's SQL Server Enterprise manager.
> > >
> > > Could a possible problem be that I need to install .net 2.0 on my database
> > > server (machine B)?  Currently, its running .net 1.1 but I wouldn't think
> > > that would make a difference as its just the database server.  Machine B is
> > > running wirelessly through a netgear router.

"Peter Bromberg [C# MVP]" wrote:

> For SQL Server 2000, In Enterprise Manager, right click the Database in the
> Left pane, and choose properties.
>
> In the Security tab, you need "Sql Server and Windows" radio. In the
> Connection Tab, you need "Allow other SQL Servers..." if you have other
> Databases that need to connect to it.
>
> Peter
>
> --
> Co-founder, Eggheadcafe.com developer portal:
> http://www.eggheadcafe.com
> UnBlog:
> http://petesbloggerama.blogspot.com
>
>
>
>
> "Amit" wrote:
>
> > How do I check if SQL allows remote connections and has mixed mode
> > authentication?   I checked the "remote login timeout" for SQL server and its
> > set at 2000.  Is this the setting you're referring to?
> >
> > I can run another web application in .net 2.0 fine when I explicitly set the
> > connect timeout setting to 2000 in the connection string.
> >
> > "Peter Bromberg [C# MVP]" wrote:
> >
> > > Make sure your SQL Server is allowing remote connections and has mixed mode
> > > (Windows and SQL Server) authentication enabled. Make a page with nothing but
> > > a a sample connection and try  / catch so you can output the result of any
> > > exception Message and stacktrace.
> > > Peter
> > >
> > >
> > > --
> > > Co-founder, Eggheadcafe.com developer portal:
> > > http://www.eggheadcafe.com
> > > UnBlog:
> > > http://petesbloggerama.blogspot.com
> > >
> > >
> > >
> > >
> > > "Amit" wrote:
> > >
> > > > I have a development setup as follows:
> > > >
> > > > 2 machines both running win xp pro, with machine A running .net 2.0 and
> > > > machine B acting as my database server running sql server 2000.
> > > >
> > > > I want to use ASP.NET 2.0 new forms authentication configuration tools but I
> > > > want the information stored in my sql server 2000 database rather than the
> > > > standard sql express database.  I ran aspnet_regsql.exe from machine A,
> > > > specified machine B as the server and provided the sql server userid and
> > > > password; however, it cannot connect and gives a timeout exception.
> > > >
> > > > The second machine is running as I can see it in windows explorer, and can
> > > > connect to the database from machine A's SQL Server Enterprise manager.
> > > >
> > > > Could a possible problem be that I need to install .net 2.0 on my database
> > > > server (machine B)?  Currently, its running .net 1.1 but I wouldn't think
> > > > that would make a difference as its just the database server.  Machine B is
> > > > running wirelessly through a netgear router.

"Amit" wrote:

> How do you increase the SQL Server timeout?  Is it the login timeout or
> transaction timeout I should increase?  I guess I'm confused on why one
> application that I upgraded to asp.net2.0 works (although I had to increase
> the timeout in the connection string) while everything else seems to timeout.
>
> "Peter Bromberg [C# MVP]" wrote:
>
> > For SQL Server 2000, In Enterprise Manager, right click the Database in the
> > Left pane, and choose properties.
> >
> > In the Security tab, you need "Sql Server and Windows" radio. In the
> > Connection Tab, you need "Allow other SQL Servers..." if you have other
> > Databases that need to connect to it.
> >
> > Peter
> >
> > --
> > Co-founder, Eggheadcafe.com developer portal:
> > http://www.eggheadcafe.com
> > UnBlog:
> > http://petesbloggerama.blogspot.com
> >
> >
> >
> >
> > "Amit" wrote:
> >
> > > How do I check if SQL allows remote connections and has mixed mode
> > > authentication?   I checked the "remote login timeout" for SQL server and its
> > > set at 2000.  Is this the setting you're referring to?
> > >
> > > I can run another web application in .net 2.0 fine when I explicitly set the
> > > connect timeout setting to 2000 in the connection string.
> > >
> > > "Peter Bromberg [C# MVP]" wrote:
> > >
> > > > Make sure your SQL Server is allowing remote connections and has mixed mode
> > > > (Windows and SQL Server) authentication enabled. Make a page with nothing but
> > > > a a sample connection and try  / catch so you can output the result of any
> > > > exception Message and stacktrace.
> > > > Peter
> > > >
> > > >
> > > > --
> > > > Co-founder, Eggheadcafe.com developer portal:
> > > > http://www.eggheadcafe.com
> > > > UnBlog:
> > > > http://petesbloggerama.blogspot.com
> > > >
> > > >
> > > >
> > > >
> > > > "Amit" wrote:
> > > >
> > > > > I have a development setup as follows:
> > > > >
> > > > > 2 machines both running win xp pro, with machine A running .net 2.0 and
> > > > > machine B acting as my database server running sql server 2000.
> > > > >
> > > > > I want to use ASP.NET 2.0 new forms authentication configuration tools but I
> > > > > want the information stored in my sql server 2000 database rather than the
> > > > > standard sql express database.  I ran aspnet_regsql.exe from machine A,
> > > > > specified machine B as the server and provided the sql server userid and
> > > > > password; however, it cannot connect and gives a timeout exception.
> > > > >
> > > > > The second machine is running as I can see it in windows explorer, and can
> > > > > connect to the database from machine A's SQL Server Enterprise manager.
> > > > >
> > > > > Could a possible problem be that I need to install .net 2.0 on my database
> > > > > server (machine B)?  Currently, its running .net 1.1 but I wouldn't think
> > > > > that would make a difference as its just the database server.  Machine B is
> > > > > running wirelessly through a netgear router.

"Peter Bromberg [C# MVP]" wrote:

> For SQL Server 2000, In Enterprise Manager, right click the Database in the
> Left pane, and choose properties.
>
> In the Security tab, you need "Sql Server and Windows" radio. In the
> Connection Tab, you need "Allow other SQL Servers..." if you have other
> Databases that need to connect to it.
>
> Peter
>
> --
> Co-founder, Eggheadcafe.com developer portal:
> http://www.eggheadcafe.com
> UnBlog:
> http://petesbloggerama.blogspot.com
>
>
>
>
> "Amit" wrote:
>
> > How do I check if SQL allows remote connections and has mixed mode
> > authentication?   I checked the "remote login timeout" for SQL server and its
> > set at 2000.  Is this the setting you're referring to?
> >
> > I can run another web application in .net 2.0 fine when I explicitly set the
> > connect timeout setting to 2000 in the connection string.
> >
> > "Peter Bromberg [C# MVP]" wrote:
> >
> > > Make sure your SQL Server is allowing remote connections and has mixed mode
> > > (Windows and SQL Server) authentication enabled. Make a page with nothing but
> > > a a sample connection and try  / catch so you can output the result of any
> > > exception Message and stacktrace.
> > > Peter
> > >
> > >
> > > --
> > > Co-founder, Eggheadcafe.com developer portal:
> > > http://www.eggheadcafe.com
> > > UnBlog:
> > > http://petesbloggerama.blogspot.com
> > >
> > >
> > >
> > >
> > > "Amit" wrote:
> > >
> > > > I have a development setup as follows:
> > > >
> > > > 2 machines both running win xp pro, with machine A running .net 2.0 and
> > > > machine B acting as my database server running sql server 2000.
> > > >
> > > > I want to use ASP.NET 2.0 new forms authentication configuration tools but I
> > > > want the information stored in my sql server 2000 database rather than the
> > > > standard sql express database.  I ran aspnet_regsql.exe from machine A,
> > > > specified machine B as the server and provided the sql server userid and
> > > > password; however, it cannot connect and gives a timeout exception.
> > > >
> > > > The second machine is running as I can see it in windows explorer, and can
> > > > connect to the database from machine A's SQL Server Enterprise manager.
> > > >
> > > > Could a possible problem be that I need to install .net 2.0 on my database
> > > > server (machine B)?  Currently, its running .net 1.1 but I wouldn't think
> > > > that would make a difference as its just the database server.  Machine B is
> > > > running wirelessly through a netgear router.

"Amit" wrote:

> How do you increase the SQL Server timeout?  Is it the login timeout or
> transaction timeout I should increase?  I guess I'm confused on why one
> application that I upgraded to asp.net2.0 works (although I had to increase
> the timeout in the connection string) while everything else seems to timeout.
>
> "Peter Bromberg [C# MVP]" wrote:
>
> > For SQL Server 2000, In Enterprise Manager, right click the Database in the
> > Left pane, and choose properties.
> >
> > In the Security tab, you need "Sql Server and Windows" radio. In the
> > Connection Tab, you need "Allow other SQL Servers..." if you have other
> > Databases that need to connect to it.
> >
> > Peter
> >
> > --
> > Co-founder, Eggheadcafe.com developer portal:
> > http://www.eggheadcafe.com
> > UnBlog:
> > http://petesbloggerama.blogspot.com
> >
> >
> >
> >
> > "Amit" wrote:
> >
> > > How do I check if SQL allows remote connections and has mixed mode
> > > authentication?   I checked the "remote login timeout" for SQL server and its
> > > set at 2000.  Is this the setting you're referring to?
> > >
> > > I can run another web application in .net 2.0 fine when I explicitly set the
> > > connect timeout setting to 2000 in the connection string.
> > >
> > > "Peter Bromberg [C# MVP]" wrote:
> > >
> > > > Make sure your SQL Server is allowing remote connections and has mixed mode
> > > > (Windows and SQL Server) authentication enabled. Make a page with nothing but
> > > > a a sample connection and try  / catch so you can output the result of any
> > > > exception Message and stacktrace.
> > > > Peter
> > > >
> > > >
> > > > --
> > > > Co-founder, Eggheadcafe.com developer portal:
> > > > http://www.eggheadcafe.com
> > > > UnBlog:
> > > > http://petesbloggerama.blogspot.com
> > > >
> > > >
> > > >
> > > >
> > > > "Amit" wrote:
> > > >
> > > > > I have a development setup as follows:
> > > > >
> > > > > 2 machines both running win xp pro, with machine A running .net 2.0 and
> > > > > machine B acting as my database server running sql server 2000.
> > > > >
> > > > > I want to use ASP.NET 2.0 new forms authentication configuration tools but I
> > > > > want the information stored in my sql server 2000 database rather than the
> > > > > standard sql express database.  I ran aspnet_regsql.exe from machine A,
> > > > > specified machine B as the server and provided the sql server userid and
> > > > > password; however, it cannot connect and gives a timeout exception.
> > > > >
> > > > > The second machine is running as I can see it in windows explorer, and can
> > > > > connect to the database from machine A's SQL Server Enterprise manager.
> > > > >
> > > > > Could a possible problem be that I need to install .net 2.0 on my database
> > > > > server (machine B)?  Currently, its running .net 1.1 but I wouldn't think
> > > > > that would make a difference as its just the database server.  Machine B is
> > > > > running wirelessly through a netgear router.

"Peter Bromberg [C# MVP]" wrote:

> You have two potential Timeouts to deal with:
>
> The ADO.NET SqlCommand has a CommandTimeout property. And the SqlConnection
> has a timeout property. Your command can timeout on a long running query and
> that has nothing to do with your connection.
> Hope that helps.
> Peter
>
> --
> Co-founder, Eggheadcafe.com developer portal:
> http://www.eggheadcafe.com
> UnBlog:
> http://petesbloggerama.blogspot.com
>
>
>
>
> "Amit" wrote:
>
> > How do you increase the SQL Server timeout?  Is it the login timeout or
> > transaction timeout I should increase?  I guess I'm confused on why one
> > application that I upgraded to asp.net2.0 works (although I had to increase
> > the timeout in the connection string) while everything else seems to timeout.
> >
> > "Peter Bromberg [C# MVP]" wrote:
> >
> > > For SQL Server 2000, In Enterprise Manager, right click the Database in the
> > > Left pane, and choose properties.
> > >
> > > In the Security tab, you need "Sql Server and Windows" radio. In the
> > > Connection Tab, you need "Allow other SQL Servers..." if you have other
> > > Databases that need to connect to it.
> > >
> > > Peter
> > >
> > > --
> > > Co-founder, Eggheadcafe.com developer portal:
> > > http://www.eggheadcafe.com
> > > UnBlog:
> > > http://petesbloggerama.blogspot.com
> > >
> > >
> > >
> > >
> > > "Amit" wrote:
> > >
> > > > How do I check if SQL allows remote connections and has mixed mode
> > > > authentication?   I checked the "remote login timeout" for SQL server and its
> > > > set at 2000.  Is this the setting you're referring to?
> > > >
> > > > I can run another web application in .net 2.0 fine when I explicitly set the
> > > > connect timeout setting to 2000 in the connection string.
> > > >
> > > > "Peter Bromberg [C# MVP]" wrote:
> > > >
> > > > > Make sure your SQL Server is allowing remote connections and has mixed mode
> > > > > (Windows and SQL Server) authentication enabled. Make a page with nothing but
> > > > > a a sample connection and try  / catch so you can output the result of any
> > > > > exception Message and stacktrace.
> > > > > Peter
> > > > >
> > > > >
> > > > > --
> > > > > Co-founder, Eggheadcafe.com developer portal:
> > > > > http://www.eggheadcafe.com
> > > > > UnBlog:
> > > > > http://petesbloggerama.blogspot.com
> > > > >

"Peter Bromberg [C# MVP]" wrote:

> You have two potential Timeouts to deal with:
>
> The ADO.NET SqlCommand has a CommandTimeout property. And the SqlConnection
> has a timeout property. Your command can timeout on a long running query and
> that has nothing to do with your connection.
> Hope that helps.
> Peter
>
> --
> Co-founder, Eggheadcafe.com developer portal:
> http://www.eggheadcafe.com
> UnBlog:
> http://petesbloggerama.blogspot.com
>
>
>
>
> "Amit" wrote:
>
> > How do you increase the SQL Server timeout?  Is it the login timeout or
> > transaction timeout I should increase?  I guess I'm confused on why one
> > application that I upgraded to asp.net2.0 works (although I had to increase
> > the timeout in the connection string) while everything else seems to timeout.
> >
> > "Peter Bromberg [C# MVP]" wrote:
> >
> > > For SQL Server 2000, In Enterprise Manager, right click the Database in the
> > > Left pane, and choose properties.
> > >
> > > In the Security tab, you need "Sql Server and Windows" radio. In the
> > > Connection Tab, you need "Allow other SQL Servers..." if you have other
> > > Databases that need to connect to it.
> > >
> > > Peter
> > >
> > > --
> > > Co-founder, Eggheadcafe.com developer portal:
> > > http://www.eggheadcafe.com
> > > UnBlog:
> > > http://petesbloggerama.blogspot.com
> > >
> > >
> > >
> > >
> > > "Amit" wrote:
> > >
> > > > How do I check if SQL allows remote connections and has mixed mode
> > > > authentication?   I checked the "remote login timeout" for SQL server and its
> > > > set at 2000.  Is this the setting you're referring to?
> > > >
> > > > I can run another web application in .net 2.0 fine when I explicitly set the
> > > > connect timeout setting to 2000 in the connection string.
> > > >
> > > > "Peter Bromberg [C# MVP]" wrote:
> > > >
> > > > > Make sure your SQL Server is allowing remote connections and has mixed mode
> > > > > (Windows and SQL Server) authentication enabled. Make a page with nothing but
> > > > > a a sample connection and try  / catch so you can output the result of any
> > > > > exception Message and stacktrace.
> > > > > Peter
> > > > >
> > > > >
> > > > > --
> > > > > Co-founder, Eggheadcafe.com developer portal:
> > > > > http://www.eggheadcafe.com
> > > > > UnBlog:
> > > > > http://petesbloggerama.blogspot.com
> > > > >

"Amit" wrote:

> Well, its definitely not anything to do with a query.  I'm assuming I should
> be able to get the aspnet_regsql.exe tool to connect to the database, which I
> cannot.  Is there a way to set the timeout of the aspnet_regsql tool or
> should I try to change the timeout of sqlserver? 
>
> Why would an error like this even happen?
>
> "Peter Bromberg [C# MVP]" wrote:
>
> > You have two potential Timeouts to deal with:
> >
> > The ADO.NET SqlCommand has a CommandTimeout property. And the SqlConnection
> > has a timeout property. Your command can timeout on a long running query and
> > that has nothing to do with your connection.
> > Hope that helps.
> > Peter
> >
> > --
> > Co-founder, Eggheadcafe.com developer portal:
> > http://www.eggheadcafe.com
> > UnBlog:
> > http://petesbloggerama.blogspot.com
> >
> >
> >
> >
> > "Amit" wrote:
> >
> > > How do you increase the SQL Server timeout?  Is it the login timeout or
> > > transaction timeout I should increase?  I guess I'm confused on why one
> > > application that I upgraded to asp.net2.0 works (although I had to increase
> > > the timeout in the connection string) while everything else seems to timeout.
> > >
> > > "Peter Bromberg [C# MVP]" wrote:
> > >
> > > > For SQL Server 2000, In Enterprise Manager, right click the Database in the
> > > > Left pane, and choose properties.
> > > >
> > > > In the Security tab, you need "Sql Server and Windows" radio. In the
> > > > Connection Tab, you need "Allow other SQL Servers..." if you have other
> > > > Databases that need to connect to it.
> > > >
> > > > Peter
> > > >
> > > > --
> > > > Co-founder, Eggheadcafe.com developer portal:
> > > > http://www.eggheadcafe.com
> > > > UnBlog:
> > > > http://petesbloggerama.blogspot.com
> > > >
> > > >
> > > >
> > > >
> > > > "Amit" wrote:
> > > >
> > > > > How do I check if SQL allows remote connections and has mixed mode
> > > > > authentication?   I checked the "remote login timeout" for SQL server and its
> > > > > set at 2000.  Is this the setting you're referring to?
> > > > >
> > > > > I can run another web application in .net 2.0 fine when I explicitly set the
> > > > > connect timeout setting to 2000 in the connection string.
> > > > >
> > > > > "Peter Bromberg [C# MVP]" wrote:
> > > > >
> > > > > > Make sure your SQL Server is allowing remote connections and has mixed mode
> > > > > > (Windows and SQL Server) authentication enabled. Make a page with nothing but
> > > > > > a a sample connection and try  / catch so you can output the result of any
> > > > > > exception Message and stacktrace.
> > > > > > Peter
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Co-founder, Eggheadcafe.com developer portal:
> > > > > > http://www.eggheadcafe.com
> > > > > > UnBlog:
> > > > > > http://petesbloggerama.blogspot.com
> > > > > >
>

"Amit" wrote:

> Well, its definitely not anything to do with a query.  I'm assuming I should
> be able to get the aspnet_regsql.exe tool to connect to the database, which I
> cannot.  Is there a way to set the timeout of the aspnet_regsql tool or
> should I try to change the timeout of sqlserver? 
>
> Why would an error like this even happen?
>
> "Peter Bromberg [C# MVP]" wrote:
>
> > You have two potential Timeouts to deal with:
> >
> > The ADO.NET SqlCommand has a CommandTimeout property. And the SqlConnection
> > has a timeout property. Your command can timeout on a long running query and
> > that has nothing to do with your connection.
> > Hope that helps.
> > Peter
> >
> > --
> > Co-founder, Eggheadcafe.com developer portal:
> > http://www.eggheadcafe.com
> > UnBlog:
> > http://petesbloggerama.blogspot.com
> >
> >
> >
> >
> > "Amit" wrote:
> >
> > > How do you increase the SQL Server timeout?  Is it the login timeout or
> > > transaction timeout I should increase?  I guess I'm confused on why one
> > > application that I upgraded to asp.net2.0 works (although I had to increase
> > > the timeout in the connection string) while everything else seems to timeout.
> > >
> > > "Peter Bromberg [C# MVP]" wrote:
> > >
> > > > For SQL Server 2000, In Enterprise Manager, right click the Database in the
> > > > Left pane, and choose properties.
> > > >
> > > > In the Security tab, you need "Sql Server and Windows" radio. In the
> > > > Connection Tab, you need "Allow other SQL Servers..." if you have other
> > > > Databases that need to connect to it.
> > > >
> > > > Peter
> > > >
> > > > --
> > > > Co-founder, Eggheadcafe.com developer portal:
> > > > http://www.eggheadcafe.com
> > > > UnBlog:
> > > > http://petesbloggerama.blogspot.com
> > > >
> > > >
> > > >
> > > >
> > > > "Amit" wrote:
> > > >
> > > > > How do I check if SQL allows remote connections and has mixed mode
> > > > > authentication?   I checked the "remote login timeout" for SQL server and its
> > > > > set at 2000.  Is this the setting you're referring to?
> > > > >
> > > > > I can run another web application in .net 2.0 fine when I explicitly set the
> > > > > connect timeout setting to 2000 in the connection string.
> > > > >
> > > > > "Peter Bromberg [C# MVP]" wrote:
> > > > >
> > > > > > Make sure your SQL Server is allowing remote connections and has mixed mode
> > > > > > (Windows and SQL Server) authentication enabled. Make a page with nothing but
> > > > > > a a sample connection and try  / catch so you can output the result of any
> > > > > > exception Message and stacktrace.
> > > > > > Peter
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Co-founder, Eggheadcafe.com developer portal:
> > > > > > http://www.eggheadcafe.com
> > > > > > UnBlog:
> > > > > > http://petesbloggerama.blogspot.com
> > > > > >
>

"Amit" wrote:

> I still can't get .net 2.0 to connect to sql server 2000 instance. 
>
> I opened another application in vs 2003 and the remote connection worked
> fine so I don't think its the database or wireless connection.  There must be
> some setting in .net 2.0 thats different.  Is there a different way to write
> the connection string?  Please somebody help.  I'm at a loss.  The database
> is configured with the following values, where the columns are minimum,
> maximum, config value, and run value.  As you can see remote access is
> enabled, the login timeout is set at 2000 seconds, and remote query timeout
> is set at infinite.
>
> remote access    0    1    1    1
> remote login timeout (s)    0    2147483647    2000    2000
> remote proc trans    0    1    0    0
> remote query timeout (s)    0    2147483647    0    0
>
> I'm running out of variables to test. 
>
>
> "Amit" wrote:
>
> > Well, its definitely not anything to do with a query.  I'm assuming I should
> > be able to get the aspnet_regsql.exe tool to connect to the database, which I
> > cannot.  Is there a way to set the timeout of the aspnet_regsql tool or
> > should I try to change the timeout of sqlserver? 
> >
> > Why would an error like this even happen?
> >
> > "Peter Bromberg [C# MVP]" wrote:
> >
> > > You have two potential Timeouts to deal with:
> > >
> > > The ADO.NET SqlCommand has a CommandTimeout property. And the SqlConnection
> > > has a timeout property. Your command can timeout on a long running query and
> > > that has nothing to do with your connection.
> > > Hope that helps.
> > > Peter
> > >
> > > --
> > > Co-founder, Eggheadcafe.com developer portal:
> > > http://www.eggheadcafe.com
> > > UnBlog:
> > > http://petesbloggerama.blogspot.com
> > >
> > >
> > >
> > >
> > > "Amit" wrote:
> > >
> > > > How do you increase the SQL Server timeout?  Is it the login timeout or
> > > > transaction timeout I should increase?  I guess I'm confused on why one
> > > > application that I upgraded to asp.net2.0 works (although I had to increase
> > > > the timeout in the connection string) while everything else seems to timeout.
> > > >
> > > > "Peter Bromberg [C# MVP]" wrote:
> > > >
> > > > > For SQL Server 2000, In Enterprise Manager, right click the Database in the
> > > > > Left pane, and choose properties.
> > > > >
> > > > > In the Security tab, you need "Sql Server and Windows" radio. In the
> > > > > Connection Tab, you need "Allow other SQL Servers..." if you have other
> > > > > Databases that need to connect to it.
> > > > >
> > > > > Peter
> > > > >
> > > > > --
> > > > > Co-founder, Eggheadcafe.com developer portal:
> > > > > http://www.eggheadcafe.com
> > > > > UnBlog:
> > > > > http://petesbloggerama.blogspot.com
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > "Amit" wrote:
> > > > >
> > > > > > How do I check if SQL allows remote connections and has mixed mode
> > > > > > authentication?   I checked the "remote login timeout" for SQL server and its
> > > > > > set at 2000.  Is this the setting you're referring to?
> > > > > >
> > > > > > I can run another web application in .net 2.0 fine when I explicitly set the
> > > > > > connect timeout setting to 2000 in the connection string.
> > > > > >
> > > > > > "Peter Bromberg [C# MVP]" wrote:
> > > > > >
> > > > > > > Make sure your SQL Server is allowing remote connections and has mixed mode
> > > > > > > (Windows and SQL Server) authentication enabled. Make a page with nothing but
> > > > > > > a a sample connection and try  / catch so you can output the result of any
> > > > > > > exception Message and stacktrace.
> > > > > > > Peter
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Co-founder, Eggheadcafe.com developer portal:
> > > > > > > http://www.eggheadcafe.com
> > > > > > > UnBlog:
> > > > > > > http://petesbloggerama.blogspot.com
> > > > > > >
> >

"Amit" wrote:

> I still can't get .net 2.0 to connect to sql server 2000 instance. 
>
> I opened another application in vs 2003 and the remote connection worked
> fine so I don't think its the database or wireless connection.  There must be
> some setting in .net 2.0 thats different.  Is there a different way to write
> the connection string?  Please somebody help.  I'm at a loss.  The database
> is configured with the following values, where the columns are minimum,
> maximum, config value, and run value.  As you can see remote access is
> enabled, the login timeout is set at 2000 seconds, and remote query timeout
> is set at infinite.
>
> remote access    0    1    1    1
> remote login timeout (s)    0    2147483647    2000    2000
> remote proc trans    0    1    0    0
> remote query timeout (s)    0    2147483647    0    0
>
> I'm running out of variables to test. 
>
>
> "Amit" wrote:
>
> > Well, its definitely not anything to do with a query.  I'm assuming I should
> > be able to get the aspnet_regsql.exe tool to connect to the database, which I
> > cannot.  Is there a way to set the timeout of the aspnet_regsql tool or
> > should I try to change the timeout of sqlserver? 
> >
> > Why would an error like this even happen?
> >
> > "Peter Bromberg [C# MVP]" wrote:
> >
> > > You have two potential Timeouts to deal with:
> > >
> > > The ADO.NET SqlCommand has a CommandTimeout property. And the SqlConnection
> > > has a timeout property. Your command can timeout on a long running query and
> > > that has nothing to do with your connection.
> > > Hope that helps.
> > > Peter
> > >
> > > --
> > > Co-founder, Eggheadcafe.com developer portal:
> > > http://www.eggheadcafe.com
> > > UnBlog:
> > > http://petesbloggerama.blogspot.com
> > >
> > >
> > >
> > >
> > > "Amit" wrote:
> > >
> > > > How do you increase the SQL Server timeout?  Is it the login timeout or
> > > > transaction timeout I should increase?  I guess I'm confused on why one
> > > > application that I upgraded to asp.net2.0 works (although I had to increase
> > > > the timeout in the connection string) while everything else seems to timeout.
> > > >
> > > > "Peter Bromberg [C# MVP]" wrote:
> > > >
> > > > > For SQL Server 2000, In Enterprise Manager, right click the Database in the
> > > > > Left pane, and choose properties.
> > > > >
> > > > > In the Security tab, you need "Sql Server and Windows" radio. In the
> > > > > Connection Tab, you need "Allow other SQL Servers..." if you have other
> > > > > Databases that need to connect to it.
> > > > >
> > > > > Peter
> > > > >
> > > > > --
> > > > > Co-founder, Eggheadcafe.com developer portal:
> > > > > http://www.eggheadcafe.com
> > > > > UnBlog:
> > > > > http://petesbloggerama.blogspot.com
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > "Amit" wrote:
> > > > >
> > > > > > How do I check if SQL allows remote connections and has mixed mode
> > > > > > authentication?   I checked the "remote login timeout" for SQL server and its
> > > > > > set at 2000.  Is this the setting you're referring to?
> > > > > >
> > > > > > I can run another web application in .net 2.0 fine when I explicitly set the
> > > > > > connect timeout setting to 2000 in the connection string.
> > > > > >
> > > > > > "Peter Bromberg [C# MVP]" wrote:
> > > > > >
> > > > > > > Make sure your SQL Server is allowing remote connections and has mixed mode
> > > > > > > (Windows and SQL Server) authentication enabled. Make a page with nothing but
> > > > > > > a a sample connection and try  / catch so you can output the result of any
> > > > > > > exception Message and stacktrace.
> > > > > > > Peter
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Co-founder, Eggheadcafe.com developer portal:
> > > > > > > http://www.eggheadcafe.com
> > > > > > > UnBlog:
> > > > > > > http://petesbloggerama.blogspot.com
> > > > > > >
> >

"Amit" wrote:

> Well, its definitely not anything to do with a query.  I'm assuming I should
> be able to get the aspnet_regsql.exe tool to connect to the database, which I
> cannot.  Is there a way to set the timeout of the aspnet_regsql tool or
> should I try to change the timeout of sqlserver? 
>
> Why would an error like this even happen?
>
> "Peter Bromberg [C# MVP]" wrote:
>
> > You have two potential Timeouts to deal with:
> >
> > The ADO.NET SqlCommand has a CommandTimeout property. And the SqlConnection
> > has a timeout property. Your command can timeout on a long running query and
> > that has nothing to do with your connection.
> > Hope that helps.
> > Peter
> >
> > --
> > Co-founder, Eggheadcafe.com developer portal:
> > http://www.eggheadcafe.com
> > UnBlog:
> > http://petesbloggerama.blogspot.com
> >
> >
> >
> >
> > "Amit" wrote:
> >
> > > How do you increase the SQL Server timeout?  Is it the login timeout or
> > > transaction timeout I should increase?  I guess I'm confused on why one
> > > application that I upgraded to asp.net2.0 works (although I had to increase
> > > the timeout in the connection string) while everything else seems to timeout.
> > >
> > > "Peter Bromberg [C# MVP]" wrote:
> > >
> > > > For SQL Server 2000, In Enterprise Manager, right click the Database in the
> > > > Left pane, and choose properties.
> > > >
> > > > In the Security tab, you need "Sql Server and Windows" radio. In the
> > > > Connection Tab, you need "Allow other SQL Servers..." if you have other
> > > > Databases that need to connect to it.
> > > >
> > > > Peter
> > > >
> > > > --
> > > > Co-founder, Eggheadcafe.com developer portal:
> > > > http://www.eggheadcafe.com
> > > > UnBlog:
> > > > http://petesbloggerama.blogspot.com
> > > >
> > > >
> > > >
> > > >
> > > > "Amit" wrote:
> > > >
> > > > > How do I check if SQL allows remote connections and has mixed mode
> > > > > authentication?   I checked the "remote login timeout" for SQL server and its
> > > > > set at 2000.  Is this the setting you're referring to?
> > > > >
> > > > > I can run another web application in .net 2.0 fine when I explicitly set the
> > > > > connect timeout setting to 2000 in the connection string.
> > > > >
> > > > > "Peter Bromberg [C# MVP]" wrote:
> > > > >
> > > > > > Make sure your SQL Server is allowing remote connections and has mixed mode
> > > > > > (Windows and SQL Server) authentication enabled. Make a page with nothing but
> > > > > > a a sample connection and try  / catch so you can output the result of any
> > > > > > exception Message and stacktrace.
> > > > > > Peter
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Co-founder, Eggheadcafe.com developer portal:
> > > > > > http://www.eggheadcafe.com
> > > > > > UnBlog:
> > > > > > http://petesbloggerama.blogspot.com
> > > > > >
>

"Amit" wrote:

> Well, its definitely not anything to do with a query.  I'm assuming I should
> be able to get the aspnet_regsql.exe tool to connect to the database, which I
> cannot.  Is there a way to set the timeout of the aspnet_regsql tool or
> should I try to change the timeout of sqlserver? 
>
> Why would an error like this even happen?
>
> "Peter Bromberg [C# MVP]" wrote:
>
> > You have two potential Timeouts to deal with:
> >
> > The ADO.NET SqlCommand has a CommandTimeout property. And the SqlConnection
> > has a timeout property. Your command can timeout on a long running query and
> > that has nothing to do with your connection.
> > Hope that helps.
> > Peter
> >
> > --
> > Co-founder, Eggheadcafe.com developer portal:
> > http://www.eggheadcafe.com
> > UnBlog:
> > http://petesbloggerama.blogspot.com
> >
> >
> >
> >
> > "Amit" wrote:
> >
> > > How do you increase the SQL Server timeout?  Is it the login timeout or
> > > transaction timeout I should increase?  I guess I'm confused on why one
> > > application that I upgraded to asp.net2.0 works (although I had to increase
> > > the timeout in the connection string) while everything else seems to timeout.
> > >
> > > "Peter Bromberg [C# MVP]" wrote:
> > >
> > > > For SQL Server 2000, In Enterprise Manager, right click the Database in the
> > > > Left pane, and choose properties.
> > > >
> > > > In the Security tab, you need "Sql Server and Windows" radio. In the
> > > > Connection Tab, you need "Allow other SQL Servers..." if you have other
> > > > Databases that need to connect to it.
> > > >
> > > > Peter
> > > >
> > > > --
> > > > Co-founder, Eggheadcafe.com developer portal:
> > > > http://www.eggheadcafe.com
> > > > UnBlog:
> > > > http://petesbloggerama.blogspot.com
> > > >
> > > >
> > > >
> > > >
> > > > "Amit" wrote:
> > > >
> > > > > How do I check if SQL allows remote connections and has mixed mode
> > > > > authentication?   I checked the "remote login timeout" for SQL server and its
> > > > > set at 2000.  Is this the setting you're referring to?
> > > > >
> > > > > I can run another web application in .net 2.0 fine when I explicitly set the
> > > > > connect timeout setting to 2000 in the connection string.
> > > > >
> > > > > "Peter Bromberg [C# MVP]" wrote:
> > > > >
> > > > > > Make sure your SQL Server is allowing remote connections and has mixed mode
> > > > > > (Windows and SQL Server) authentication enabled. Make a page with nothing but
> > > > > > a a sample connection and try  / catch so you can output the result of any
> > > > > > exception Message and stacktrace.
> > > > > > Peter
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Co-founder, Eggheadcafe.com developer portal:
> > > > > > http://www.eggheadcafe.com
> > > > > > UnBlog:
> > > > > > http://petesbloggerama.blogspot.com
> > > > > >
>

"Peter Bromberg [C# MVP]" wrote:

> try connectionstrings.com.
> a typical connection string (simplified version):
> "server=192.168.10.103;database=mydatabase;uid=sa;pwd=blah";
>
> --
> Co-founder, Eggheadcafe.com developer portal:
> http://www.eggheadcafe.com
> UnBlog:
> http://petesbloggerama.blogspot.com
>
>
>
>
> "Amit" wrote:
>
> > I still can't get .net 2.0 to connect to sql server 2000 instance. 
> >
> > I opened another application in vs 2003 and the remote connection worked
> > fine so I don't think its the database or wireless connection.  There must be
> > some setting in .net 2.0 thats different.  Is there a different way to write
> > the connection string?  Please somebody help.  I'm at a loss.  The database
> > is configured with the following values, where the columns are minimum,
> > maximum, config value, and run value.  As you can see remote access is
> > enabled, the login timeout is set at 2000 seconds, and remote query timeout
> > is set at infinite.
> >
> > remote access    0    1    1    1
> > remote login timeout (s)    0    2147483647    2000    2000
> > remote proc trans    0    1    0    0
> > remote query timeout (s)    0    2147483647    0    0
> >
> > I'm running out of variables to test. 
> >
> >
> > "Amit" wrote:
> >
> > > Well, its definitely not anything to do with a query.  I'm assuming I should
> > > be able to get the aspnet_regsql.exe tool to connect to the database, which I
> > > cannot.  Is there a way to set the timeout of the aspnet_regsql tool or
> > > should I try to change the timeout of sqlserver? 
> > >
> > > Why would an error like this even happen?
> > >
> > > "Peter Bromberg [C# MVP]" wrote:
> > >
> > > > You have two potential Timeouts to deal with:
> > > >
> > > > The ADO.NET SqlCommand has a CommandTimeout property. And the SqlConnection
> > > > has a timeout property. Your command can timeout on a long running query and
> > > > that has nothing to do with your connection.
> > > > Hope that helps.
> > > > Peter
> > > >
> > > > --
> > > > Co-founder, Eggheadcafe.com developer portal:
> > > > http://www.eggheadcafe.com
> > > > UnBlog:
> > > > http://petesbloggerama.blogspot.com
> > > >
> > > >
> > > >
> > > >
> > > > "Amit" wrote:
> > > >
> > > > > How do you increase the SQL Server timeout?  Is it the login timeout or
> > > > > transaction timeout I should increase?  I guess I'm confused on why one
> > > > > application that I upgraded to asp.net2.0 works (although I had to increase
> > > > > the timeout in the connection string) while everything else seems to timeout.
> > > > >
> > > > > "Peter Bromberg [C# MVP]" wrote:
> > > > >
> > > > > > For SQL Server 2000, In Enterprise Manager, right click the Database in the
> > > > > > Left pane, and choose properties.
> > > > > >
> > > > > > In the Security tab, you need "Sql Server and Windows" radio. In the
> > > > > > Connection Tab, you need "Allow other SQL Servers..." if you have other
> > > > > > Databases that need to connect to it.
> > > > > >
> > > > > > Peter
> > > > > >
> > > > > > --
> > > > > > Co-founder, Eggheadcafe.com developer portal:
> > > > > > http://www.eggheadcafe.com
> > > > > > UnBlog:
> > > > > > http://petesbloggerama.blogspot.com
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > "Amit" wrote:
> > > > > >
> > > > > > > How do I check if SQL allows remote connections and has mixed mode
> > > > > > > authentication?   I checked the "remote login timeout" for SQL server and its
> > > > > > > set at 2000.  Is this the setting you're referring to?
> > > > > > >
> > > > > > > I can run another web application in .net 2.0 fine when I explicitly set the
> > > > > > > connect timeout setting to 2000 in the connection string.
> > > > > > >
> > > > > > > "Peter Bromberg [C# MVP]" wrote:
> > > > > > >
> > > > > > > > Make sure your SQL Server is allowing remote connections and has mixed mode
> > > > > > > > (Windows and SQL Server) authentication enabled. Make a page with nothing but
> > > > > > > > a a sample connection and try  / catch so you can output the result of any
> > > > > > > > exception Message and stacktrace.
> > > > > > > > Peter
> > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > > Co-founder, Eggheadcafe.com developer portal:
> > > > > > > > http://www.eggheadcafe.com
> > > > > > > > UnBlog:
> > > > > > > > http://petesbloggerama.blogspot.com
> > > > > > > >
> > >

"Peter Bromberg [C# MVP]" wrote:

> try connectionstrings.com.
> a typical connection string (simplified version):
> "server=192.168.10.103;database=mydatabase;uid=sa;pwd=blah";
>
> --
> Co-founder, Eggheadcafe.com developer portal:
> http://www.eggheadcafe.com
> UnBlog:
> http://petesbloggerama.blogspot.com
>
>
>
>
> "Amit" wrote:
>
> > I still can't get .net 2.0 to connect to sql server 2000 instance. 
> >
> > I opened another application in vs 2003 and the remote connection worked
> > fine so I don't think its the database or wireless connection.  There must be
> > some setting in .net 2.0 thats different.  Is there a different way to write
> > the connection string?  Please somebody help.  I'm at a loss.  The database
> > is configured with the following values, where the columns are minimum,
> > maximum, config value, and run value.  As you can see remote access is
> > enabled, the login timeout is set at 2000 seconds, and remote query timeout
> > is set at infinite.
> >
> > remote access    0    1    1    1
> > remote login timeout (s)    0    2147483647    2000    2000
> > remote proc trans    0    1    0    0
> > remote query timeout (s)    0    2147483647    0    0
> >
> > I'm running out of variables to test. 
> >
> >
> > "Amit" wrote:
> >
> > > Well, its definitely not anything to do with a query.  I'm assuming I should
> > > be able to get the aspnet_regsql.exe tool to connect to the database, which I
> > > cannot.  Is there a way to set the timeout of the aspnet_regsql tool or
> > > should I try to change the timeout of sqlserver? 
> > >
> > > Why would an error like this even happen?
> > >
> > > "Peter Bromberg [C# MVP]" wrote:
> > >
> > > > You have two potential Timeouts to deal with:
> > > >
> > > > The ADO.NET SqlCommand has a CommandTimeout property. And the SqlConnection
> > > > has a timeout property. Your command can timeout on a long running query and
> > > > that has nothing to do with your connection.
> > > > Hope that helps.
> > > > Peter
> > > >
> > > > --
> > > > Co-founder, Eggheadcafe.com developer portal:
> > > > http://www.eggheadcafe.com
> > > > UnBlog:
> > > > http://petesbloggerama.blogspot.com
> > > >
> > > >
> > > >
> > > >
> > > > "Amit" wrote:
> > > >
> > > > > How do you increase the SQL Server timeout?  Is it the login timeout or
> > > > > transaction timeout I should increase?  I guess I'm confused on why one
> > > > > application that I upgraded to asp.net2.0 works (although I had to increase
> > > > > the timeout in the connection string) while everything else seems to timeout.
> > > > >
> > > > > "Peter Bromberg [C# MVP]" wrote:
> > > > >
> > > > > > For SQL Server 2000, In Enterprise Manager, right click the Database in the
> > > > > > Left pane, and choose properties.
> > > > > >
> > > > > > In the Security tab, you need "Sql Server and Windows" radio. In the
> > > > > > Connection Tab, you need "Allow other SQL Servers..." if you have other
> > > > > > Databases that need to connect to it.
> > > > > >
> > > > > > Peter
> > > > > >
> > > > > > --
> > > > > > Co-founder, Eggheadcafe.com developer portal:
> > > > > > http://www.eggheadcafe.com
> > > > > > UnBlog:
> > > > > > http://petesbloggerama.blogspot.com
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > "Amit" wrote:
> > > > > >
> > > > > > > How do I check if SQL allows remote connections and has mixed mode
> > > > > > > authentication?   I checked the "remote login timeout" for SQL server and its
> > > > > > > set at 2000.  Is this the setting you're referring to?
> > > > > > >
> > > > > > > I can run another web application in .net 2.0 fine when I explicitly set the
> > > > > > > connect timeout setting to 2000 in the connection string.
> > > > > > >
> > > > > > > "Peter Bromberg [C# MVP]" wrote:
> > > > > > >
> > > > > > > > Make sure your SQL Server is allowing remote connections and has mixed mode
> > > > > > > > (Windows and SQL Server) authentication enabled. Make a page with nothing but
> > > > > > > > a a sample connection and try  / catch so you can output the result of any
> > > > > > > > exception Message and stacktrace.
> > > > > > > > Peter
> > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > > Co-founder, Eggheadcafe.com developer portal:
> > > > > > > > http://www.eggheadcafe.com
> > > > > > > > UnBlog:
> > > > > > > > http://petesbloggerama.blogspot.com
> > > > > > > >
> > >

"Amit" wrote:

> I still can't get .net 2.0 to connect to sql server 2000 instance. 
>
> I opened another application in vs 2003 and the remote connection worked
> fine so I don't think its the database or wireless connection.  There must be
> some setting in .net 2.0 thats different.  Is there a different way to write
> the connection string?  Please somebody help.  I'm at a loss.  The database
> is configured with the following values, where the columns are minimum,
> maximum, config value, and run value.  As you can see remote access is
> enabled, the login timeout is set at 2000 seconds, and remote query timeout
> is set at infinite.
>
> remote access    0    1    1    1
> remote login timeout (s)    0    2147483647    2000    2000
> remote proc trans    0    1    0    0
> remote query timeout (s)    0    2147483647    0    0
>
> I'm running out of variables to test. 
>
>
> "Amit" wrote:
>
> > Well, its definitely not anything to do with a query.  I'm assuming I should
> > be able to get the aspnet_regsql.exe tool to connect to the database, which I
> > cannot.  Is there a way to set the timeout of the aspnet_regsql tool or
> > should I try to change the timeout of sqlserver? 
> >
> > Why would an error like this even happen?
> >
> > "Peter Bromberg [C# MVP]" wrote:
> >
> > > You have two potential Timeouts to deal with:
> > >
> > > The ADO.NET SqlCommand has a CommandTimeout property. And the SqlConnection
> > > has a timeout property. Your command can timeout on a long running query and
> > > that has nothing to do with your connection.
> > > Hope that helps.
> > > Peter
> > >
> > > --
> > > Co-founder, Eggheadcafe.com developer portal:
> > > http://www.eggheadcafe.com
> > > UnBlog:
> > > http://petesbloggerama.blogspot.com
> > >
> > >
> > >
> > >
> > > "Amit" wrote:
> > >
> > > > How do you increase the SQL Server timeout?  Is it the login timeout or
> > > > transaction timeout I should increase?  I guess I'm confused on why one
> > > > application that I upgraded to asp.net2.0 works (although I had to increase
> > > > the timeout in the connection string) while everything else seems to timeout.
> > > >
> > > > "Peter Bromberg [C# MVP]" wrote:
> > > >
> > > > > For SQL Server 2000, In Enterprise Manager, right click the Database in the
> > > > > Left pane, and choose properties.
> > > > >
> > > > > In the Security tab, you need "Sql Server and Windows" radio. In the
> > > > > Connection Tab, you need "Allow other SQL Servers..." if you have other
> > > > > Databases that need to connect to it.
> > > > >
> > > > > Peter
> > > > >
> > > > > --
> > > > > Co-founder, Eggheadcafe.com developer portal:
> > > > > http://www.eggheadcafe.com
> > > > > UnBlog:
> > > > > http://petesbloggerama.blogspot.com
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > "Amit" wrote:
> > > > >
> > > > > > How do I check if SQL allows remote connections and has mixed mode
> > > > > > authentication?   I checked the "remote login timeout" for SQL server and its
> > > > > > set at 2000.  Is this the setting you're referring to?
> > > > > >
> > > > > > I can run another web application in .net 2.0 fine when I explicitly set the
> > > > > > connect timeout setting to 2000 in the connection string.
> > > > > >
> > > > > > "Peter Bromberg [C# MVP]" wrote:
> > > > > >
> > > > > > > Make sure your SQL Server is allowing remote connections and has mixed mode
> > > > > > > (Windows and SQL Server) authentication enabled. Make a page with nothing but
> > > > > > > a a sample connection and try  / catch so you can output the result of any
> > > > > > > exception Message and stacktrace.
> > > > > > > Peter
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Co-founder, Eggheadcafe.com developer portal:
> > > > > > > http://www.eggheadcafe.com
> > > > > > > UnBlog:
> > > > > > > http://petesbloggerama.blogspot.com
> > > > > > >
> >

"Amit" wrote:

> I still can't get .net 2.0 to connect to sql server 2000 instance. 
>
> I opened another application in vs 2003 and the remote connection worked
> fine so I don't think its the database or wireless connection.  There must be
> some setting in .net 2.0 thats different.  Is there a different way to write
> the connection string?  Please somebody help.  I'm at a loss.  The database
> is configured with the following values, where the columns are minimum,
> maximum, config value, and run value.  As you can see remote access is
> enabled, the login timeout is set at 2000 seconds, and remote query timeout
> is set at infinite.
>
> remote access    0    1    1    1
> remote login timeout (s)    0    2147483647    2000    2000
> remote proc trans    0    1    0    0
> remote query timeout (s)    0    2147483647    0    0
>
> I'm running out of variables to test. 
>
>
> "Amit" wrote:
>
> > Well, its definitely not anything to do with a query.  I'm assuming I should
> > be able to get the aspnet_regsql.exe tool to connect to the database, which I
> > cannot.  Is there a way to set the timeout of the aspnet_regsql tool or
> > should I try to change the timeout of sqlserver? 
> >
> > Why would an error like this even happen?
> >
> > "Peter Bromberg [C# MVP]" wrote:
> >
> > > You have two potential Timeouts to deal with:
> > >
> > > The ADO.NET SqlCommand has a CommandTimeout property. And the SqlConnection
> > > has a timeout property. Your command can timeout on a long running query and
> > > that has nothing to do with your connection.
> > > Hope that helps.
> > > Peter
> > >
> > > --
> > > Co-founder, Eggheadcafe.com developer portal:
> > > http://www.eggheadcafe.com
> > > UnBlog:
> > > http://petesbloggerama.blogspot.com
> > >
> > >
> > >
> > >
> > > "Amit" wrote:
> > >
> > > > How do you increase the SQL Server timeout?  Is it the login timeout or
> > > > transaction timeout I should increase?  I guess I'm confused on why one
> > > > application that I upgraded to asp.net2.0 works (although I had to increase
> > > > the timeout in the connection string) while everything else seems to timeout.
> > > >
> > > > "Peter Bromberg [C# MVP]" wrote:
> > > >
> > > > > For SQL Server 2000, In Enterprise Manager, right click the Database in the
> > > > > Left pane, and choose properties.
> > > > >
> > > > > In the Security tab, you need "Sql Server and Windows" radio. In the
> > > > > Connection Tab, you need "Allow other SQL Servers..." if you have other
> > > > > Databases that need to connect to it.
> > > > >
> > > > > Peter
> > > > >
> > > > > --
> > > > > Co-founder, Eggheadcafe.com developer portal:
> > > > > http://www.eggheadcafe.com
> > > > > UnBlog:
> > > > > http://petesbloggerama.blogspot.com
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > "Amit" wrote:
> > > > >
> > > > > > How do I check if SQL allows remote connections and has mixed mode
> > > > > > authentication?   I checked the "remote login timeout" for SQL server and its
> > > > > > set at 2000.  Is this the setting you're referring to?
> > > > > >
> > > > > > I can run another web application in .net 2.0 fine when I explicitly set the
> > > > > > connect timeout setting to 2000 in the connection string.
> > > > > >
> > > > > > "Peter Bromberg [C# MVP]" wrote:
> > > > > >
> > > > > > > Make sure your SQL Server is allowing remote connections and has mixed mode
> > > > > > > (Windows and SQL Server) authentication enabled. Make a page with nothing but
> > > > > > > a a sample connection and try  / catch so you can output the result of any
> > > > > > > exception Message and stacktrace.
> > > > > > > Peter
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Co-founder, Eggheadcafe.com developer portal:
> > > > > > > http://www.eggheadcafe.com
> > > > > > > UnBlog:
> > > > > > > http://petesbloggerama.blogspot.com
> > > > > > >
> >

"Peter Bromberg [C# MVP]" wrote:

> try connectionstrings.com.
> a typical connection string (simplified version):
> "server=192.168.10.103;database=mydatabase;uid=sa;pwd=blah";
>
> --
> Co-founder, Eggheadcafe.com developer portal:
> http://www.eggheadcafe.com
> UnBlog:
> http://petesbloggerama.blogspot.com
>
>
>
>
> "Amit" wrote:
>
> > I still can't get .net 2.0 to connect to sql server 2000 instance. 
> >
> > I opened another application in vs 2003 and the remote connection worked
> > fine so I don't think its the database or wireless connection.  There must be
> > some setting in .net 2.0 thats different.  Is there a different way to write
> > the connection string?  Please somebody help.  I'm at a loss.  The database
> > is configured with the following values, where the columns are minimum,
> > maximum, config value, and run value.  As you can see remote access is
> > enabled, the login timeout is set at 2000 seconds, and remote query timeout
> > is set at infinite.
> >
> > remote access    0    1    1    1
> > remote login timeout (s)    0    2147483647    2000    2000
> > remote proc trans    0    1    0    0
> > remote query timeout (s)    0    2147483647    0    0
> >
> > I'm running out of variables to test. 
> >
> >
> > "Amit" wrote:
> >
> > > Well, its definitely not anything to do with a query.  I'm assuming I should
> > > be able to get the aspnet_regsql.exe tool to connect to the database, which I
> > > cannot.  Is there a way to set the timeout of the aspnet_regsql tool or
> > > should I try to change the timeout of sqlserver? 
> > >
> > > Why would an error like this even happen?
> > >
> > > "Peter Bromberg [C# MVP]" wrote:
> > >
> > > > You have two potential Timeouts to deal with:
> > > >
> > > > The ADO.NET SqlCommand has a CommandTimeout property. And the SqlConnection
> > > > has a timeout property. Your command can timeout on a long running query and
> > > > that has nothing to do with your connection.
> > > > Hope that helps.
> > > > Peter
> > > >
> > > > --
> > > > Co-founder, Eggheadcafe.com developer portal:
> > > > http://www.eggheadcafe.com
> > > > UnBlog:
> > > > http://petesbloggerama.blogspot.com
> > > >
> > > >
> > > >
> > > >
> > > > "Amit" wrote:
> > > >
> > > > > How do you increase the SQL Server timeout?  Is it the login timeout or
> > > > > transaction timeout I should increase?  I guess I'm confused on why one
> > > > > application that I upgraded to asp.net2.0 works (although I had to increase
> > > > > the timeout in the connection string) while everything else seems to timeout.
> > > > >
> > > > > "Peter Bromberg [C# MVP]" wrote:
> > > > >
> > > > > > For SQL Server 2000, In Enterprise Manager, right click the Database in the
> > > > > > Left pane, and choose properties.
> > > > > >
> > > > > > In the Security tab, you need "Sql Server and Windows" radio. In the
> > > > > > Connection Tab, you need "Allow other SQL Servers..." if you have other
> > > > > > Databases that need to connect to it.
> > > > > >
> > > > > > Peter
> > > > > >
> > > > > > --
> > > > > > Co-founder, Eggheadcafe.com developer portal:
> > > > > > http://www.eggheadcafe.com
> > > > > > UnBlog:
> > > > > > http://petesbloggerama.blogspot.com
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > "Amit" wrote:
> > > > > >
> > > > > > > How do I check if SQL allows remote connections and has mixed mode
> > > > > > > authentication?   I checked the "remote login timeout" for SQL server and its
> > > > > > > set at 2000.  Is this the setting you're referring to?
> > > > > > >
> > > > > > > I can run another web application in .net 2.0 fine when I explicitly set the
> > > > > > > connect timeout setting to 2000 in the connection string.
> > > > > > >
> > > > > > > "Peter Bromberg [C# MVP]" wrote:
> > > > > > >
> > > > > > > > Make sure your SQL Server is allowing remote connections and has mixed mode
> > > > > > > > (Windows and SQL Server) authentication enabled. Make a page with nothing but
> > > > > > > > a a sample connection and try  / catch so you can output the result of any
> > > > > > > > exception Message and stacktrace.
> > > > > > > > Peter
> > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > > Co-founder, Eggheadcafe.com developer portal:
> > > > > > > > http://www.eggheadcafe.com
> > > > > > > > UnBlog:
> > > > > > > > http://petesbloggerama.blogspot.com
> > > > > > > >
> > >

"Peter Bromberg [C# MVP]" wrote:

> try connectionstrings.com.
> a typical connection string (simplified version):
> "server=192.168.10.103;database=mydatabase;uid=sa;pwd=blah";
>
> --
> Co-founder, Eggheadcafe.com developer portal:
> http://www.eggheadcafe.com
> UnBlog:
> http://petesbloggerama.blogspot.com
>
>
>
>
> "Amit" wrote:
>
> > I still can't get .net 2.0 to connect to sql server 2000 instance. 
> >
> > I opened another application in vs 2003 and the remote connection worked
> > fine so I don't think its the database or wireless connection.  There must be
> > some setting in .net 2.0 thats different.  Is there a different way to write
> > the connection string?  Please somebody help.  I'm at a loss.  The database
> > is configured with the following values, where the columns are minimum,
> > maximum, config value, and run value.  As you can see remote access is
> > enabled, the login timeout is set at 2000 seconds, and remote query timeout
> > is set at infinite.
> >
> > remote access    0    1    1    1
> > remote login timeout (s)    0    2147483647    2000    2000
> > remote proc trans    0    1    0    0
> > remote query timeout (s)    0    2147483647    0    0
> >
> > I'm running out of variables to test. 
> >
> >
> > "Amit" wrote:
> >
> > > Well, its definitely not anything to do with a query.  I'm assuming I should
> > > be able to get the aspnet_regsql.exe tool to connect to the database, which I
> > > cannot.  Is there a way to set the timeout of the aspnet_regsql tool or
> > > should I try to change the timeout of sqlserver? 
> > >
> > > Why would an error like this even happen?
> > >
> > > "Peter Bromberg [C# MVP]" wrote:
> > >
> > > > You have two potential Timeouts to deal with:
> > > >
> > > > The ADO.NET SqlCommand has a CommandTimeout property. And the SqlConnection
> > > > has a timeout property. Your command can timeout on a long running query and
> > > > that has nothing to do with your connection.
> > > > Hope that helps.
> > > > Peter
> > > >
> > > > --
> > > > Co-founder, Eggheadcafe.com developer portal:
> > > > http://www.eggheadcafe.com
> > > > UnBlog:
> > > > http://petesbloggerama.blogspot.com
> > > >
> > > >
> > > >
> > > >
> > > > "Amit" wrote:
> > > >
> > > > > How do you increase the SQL Server timeout?  Is it the login timeout or
> > > > > transaction timeout I should increase?  I guess I'm confused on why one
> > > > > application that I upgraded to asp.net2.0 works (although I had to increase
> > > > > the timeout in the connection string) while everything else seems to timeout.
> > > > >
> > > > > "Peter Bromberg [C# MVP]" wrote:
> > > > >
> > > > > > For SQL Server 2000, In Enterprise Manager, right click the Database in the
> > > > > > Left pane, and choose properties.
> > > > > >
> > > > > > In the Security tab, you need "Sql Server and Windows" radio. In the
> > > > > > Connection Tab, you need "Allow other SQL Servers..." if you have other
> > > > > > Databases that need to connect to it.
> > > > > >
> > > > > > Peter
> > > > > >
> > > > > > --
> > > > > > Co-founder, Eggheadcafe.com developer portal:
> > > > > > http://www.eggheadcafe.com
> > > > > > UnBlog:
> > > > > > http://petesbloggerama.blogspot.com
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > "Amit" wrote:
> > > > > >
> > > > > > > How do I check if SQL allows remote connections and has mixed mode
> > > > > > > authentication?   I checked the "remote login timeout" for SQL server and its
> > > > > > > set at 2000.  Is this the setting you're referring to?
> > > > > > >
> > > > > > > I can run another web application in .net 2.0 fine when I explicitly set the
> > > > > > > connect timeout setting to 2000 in the connection string.
> > > > > > >
> > > > > > > "Peter Bromberg [C# MVP]" wrote:
> > > > > > >
> > > > > > > > Make sure your SQL Server is allowing remote connections and has mixed mode
> > > > > > > > (Windows and SQL Server) authentication enabled. Make a page with nothing but
> > > > > > > > a a sample connection and try  / catch so you can output the result of any
> > > > > > > > exception Message and stacktrace.
> > > > > > > > Peter
> > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > > Co-founder, Eggheadcafe.com developer portal:
> > > > > > > > http://www.eggheadcafe.com
> > > > > > > > UnBlog:
> > > > > > > > http://petesbloggerama.blogspot.com
> > > > > > > >
> > >

> That didn't work.  I'm not supposed to enter a connection string like
> that in the aspnet_regsql tool.
>
> "Peter Bromberg [C# MVP]" wrote:
>
>> try connectionstrings.com.
>> a typical connection string (simplified version):
>> "server=192.168.10.103;database=mydatabase;uid=sa;pwd=blah";
>> --
>> Co-founder, Eggheadcafe.com developer portal:
>> http://www.eggheadcafe.com
>> UnBlog:
>> http://petesbloggerama.blogspot.com
>> "Amit" wrote:
>>
>>> I still can't get .net 2.0 to connect to sql server 2000 instance.
>>>
>>> I opened another application in vs 2003 and the remote connection
>>> worked fine so I don't think its the database or wireless
>>> connection.  There must be some setting in .net 2.0 thats different.
>>> Is there a different way to write the connection string?  Please
>>> somebody help.  I'm at a loss.  The databa