Hello,
I try to register a remote SQL Server 2000 installed in a W2003, but it
doesn't work. Afer about 5 or 6 seconds, it says: Timeout expired.
In that network , there is not any firewall and port 1433 is open in the
router. What it really surpises me, is that
I can connect via ODBC to any database of that remote SQL Server2000 and
work wuth tables fine !!!
Using the Enterprise Manager from the W2003 server, we have checked
the following:
-Network Configuration button on the General tab
Is TCP/IP enabled?
-In the Connections tab, the Query time-out value is not set too low (600
seconds)
-There is not a maximum concurrent user connections value set
(unlimited).
Also, we can register others remote servers and work fine.
Any idea ?
Thank you very much !
Charles.It's the login timeout you want to try increasing. See my
reply to your post in .connect for steps to do this.
-Sue
On Sat, 17 Apr 2004 12:20:44 +0200, "Charles"
<ccolell@.softeng.es> wrote:
>Hello,
>I try to register a remote SQL Server 2000 installed in a W2003, but it
>doesn't work. Afer about 5 or 6 seconds, it says: Timeout expired.
>In that network , there is not any firewall and port 1433 is open in the
>router. What it really surpises me, is that
>I can connect via ODBC to any database of that remote SQL Server2000 and
>work wuth tables fine !!!
>Using the Enterprise Manager from the W2003 server, we have checked
>the following:
> -Network Configuration button on the General tab
> Is TCP/IP enabled?
> -In the Connections tab, the Query time-out value is not set too low (60
0
>seconds)
> -There is not a maximum concurrent user connections value set
>(unlimited).
>Also, we can register others remote servers and work fine.
>Any idea ?
>Thank you very much !
>Charles.
>
Showing posts with label timeout. Show all posts
Showing posts with label timeout. Show all posts
Friday, February 10, 2012
Can not registre SQL in Enterprise Manager
Hello,
I try to register a remote SQL Server 2000 installed in a W2003, but it
doesn't work. Afer about 5 or 6 seconds, it says: Timeout expired.
In that network , there is not any firewall and port 1433 is open in the
router. What it really surpises me, is that
I can connect via ODBC to any database of that remote SQL Server2000 and
work wuth tables fine !!!
Using the Enterprise Manager from the W2003 server, we have checked
the following:
-Network Configuration button on the General tab
Is TCP/IP enabled?
-In the Connections tab, the Query time-out value is not set too low (600
seconds)
-There is not a maximum concurrent user connections value set
(unlimited).
Also, we can register others remote servers and work fine.
Any idea ?
Thank you very much !
Charles.
It's the login timeout you want to try increasing. See my
reply to your post in .connect for steps to do this.
-Sue
On Sat, 17 Apr 2004 12:20:44 +0200, "Charles"
<ccolell@.softeng.es> wrote:
>Hello,
>I try to register a remote SQL Server 2000 installed in a W2003, but it
>doesn't work. Afer about 5 or 6 seconds, it says: Timeout expired.
>In that network , there is not any firewall and port 1433 is open in the
>router. What it really surpises me, is that
>I can connect via ODBC to any database of that remote SQL Server2000 and
>work wuth tables fine !!!
>Using the Enterprise Manager from the W2003 server, we have checked
>the following:
> -Network Configuration button on the General tab
> Is TCP/IP enabled?
> -In the Connections tab, the Query time-out value is not set too low (600
>seconds)
> -There is not a maximum concurrent user connections value set
>(unlimited).
>Also, we can register others remote servers and work fine.
>Any idea ?
>Thank you very much !
>Charles.
>
I try to register a remote SQL Server 2000 installed in a W2003, but it
doesn't work. Afer about 5 or 6 seconds, it says: Timeout expired.
In that network , there is not any firewall and port 1433 is open in the
router. What it really surpises me, is that
I can connect via ODBC to any database of that remote SQL Server2000 and
work wuth tables fine !!!
Using the Enterprise Manager from the W2003 server, we have checked
the following:
-Network Configuration button on the General tab
Is TCP/IP enabled?
-In the Connections tab, the Query time-out value is not set too low (600
seconds)
-There is not a maximum concurrent user connections value set
(unlimited).
Also, we can register others remote servers and work fine.
Any idea ?
Thank you very much !
Charles.
It's the login timeout you want to try increasing. See my
reply to your post in .connect for steps to do this.
-Sue
On Sat, 17 Apr 2004 12:20:44 +0200, "Charles"
<ccolell@.softeng.es> wrote:
>Hello,
>I try to register a remote SQL Server 2000 installed in a W2003, but it
>doesn't work. Afer about 5 or 6 seconds, it says: Timeout expired.
>In that network , there is not any firewall and port 1433 is open in the
>router. What it really surpises me, is that
>I can connect via ODBC to any database of that remote SQL Server2000 and
>work wuth tables fine !!!
>Using the Enterprise Manager from the W2003 server, we have checked
>the following:
> -Network Configuration button on the General tab
> Is TCP/IP enabled?
> -In the Connections tab, the Query time-out value is not set too low (600
>seconds)
> -There is not a maximum concurrent user connections value set
>(unlimited).
>Also, we can register others remote servers and work fine.
>Any idea ?
>Thank you very much !
>Charles.
>
Can not register SQLServer2000 in Enterprise Manager
Hello,
I try to register a remote SQL Server 2000 installed in a W2003, but it
doesn't work. Afer about 5 or 6 seconds, it says: Timeout expired.
In that network , there is not any firewall and port 1433 is open in the
router. What it really surpises me, is that
I can connect via ODBC to any database of that remote SQL Server2000 and
work wuth tables fine !!!
Using the Enterprise Manager from the W2003 server, we have checked
the following:
-Network Configuration button on the General tab
Is TCP/IP enabled?
-In the Connections tab, the Query time-out value is not set too low (600
seconds)
-There is not a maximum concurrent user connections value set
(unlimited).
Also, we can register others remote servers and work fine.
Any idea ?
Thank you very much !
Charles.
Charles,
Try increasing the login timeout used by Enterprise Manager.
In Enterprise Manager, go to the menu to Tools, then select
Options. Click on the Advanced tab and increase the login
timeout from the default 4 seconds. Try 10 or 15 seconds
instead and see if that helps.
-Sue
On Sat, 17 Apr 2004 12:14:30 +0200, "Charles"
<ccolell@.softeng.es> wrote:
>Hello,
>I try to register a remote SQL Server 2000 installed in a W2003, but it
>doesn't work. Afer about 5 or 6 seconds, it says: Timeout expired.
>In that network , there is not any firewall and port 1433 is open in the
>router. What it really surpises me, is that
>I can connect via ODBC to any database of that remote SQL Server2000 and
>work wuth tables fine !!!
>Using the Enterprise Manager from the W2003 server, we have checked
>the following:
> -Network Configuration button on the General tab
> Is TCP/IP enabled?
> -In the Connections tab, the Query time-out value is not set too low (600
>seconds)
> -There is not a maximum concurrent user connections value set
>(unlimited).
>Also, we can register others remote servers and work fine.
>Any idea ?
>Thank you very much !
>Charles.
>
|||Yes !!!! Thanks a lot Sue.
Have a nice day,
Charles.
"Sue Hoegemeier" <Sue_H@.nomail.please> escribi en el mensaje
news:4eg680hvekta8k50ar1c21fadjcsn7p62i@.4ax.com... [vbcol=seagreen]
> Charles,
> Try increasing the login timeout used by Enterprise Manager.
> In Enterprise Manager, go to the menu to Tools, then select
> Options. Click on the Advanced tab and increase the login
> timeout from the default 4 seconds. Try 10 or 15 seconds
> instead and see if that helps.
> -Sue
> On Sat, 17 Apr 2004 12:14:30 +0200, "Charles"
> <ccolell@.softeng.es> wrote:
(600
>
I try to register a remote SQL Server 2000 installed in a W2003, but it
doesn't work. Afer about 5 or 6 seconds, it says: Timeout expired.
In that network , there is not any firewall and port 1433 is open in the
router. What it really surpises me, is that
I can connect via ODBC to any database of that remote SQL Server2000 and
work wuth tables fine !!!
Using the Enterprise Manager from the W2003 server, we have checked
the following:
-Network Configuration button on the General tab
Is TCP/IP enabled?
-In the Connections tab, the Query time-out value is not set too low (600
seconds)
-There is not a maximum concurrent user connections value set
(unlimited).
Also, we can register others remote servers and work fine.
Any idea ?
Thank you very much !
Charles.
Charles,
Try increasing the login timeout used by Enterprise Manager.
In Enterprise Manager, go to the menu to Tools, then select
Options. Click on the Advanced tab and increase the login
timeout from the default 4 seconds. Try 10 or 15 seconds
instead and see if that helps.
-Sue
On Sat, 17 Apr 2004 12:14:30 +0200, "Charles"
<ccolell@.softeng.es> wrote:
>Hello,
>I try to register a remote SQL Server 2000 installed in a W2003, but it
>doesn't work. Afer about 5 or 6 seconds, it says: Timeout expired.
>In that network , there is not any firewall and port 1433 is open in the
>router. What it really surpises me, is that
>I can connect via ODBC to any database of that remote SQL Server2000 and
>work wuth tables fine !!!
>Using the Enterprise Manager from the W2003 server, we have checked
>the following:
> -Network Configuration button on the General tab
> Is TCP/IP enabled?
> -In the Connections tab, the Query time-out value is not set too low (600
>seconds)
> -There is not a maximum concurrent user connections value set
>(unlimited).
>Also, we can register others remote servers and work fine.
>Any idea ?
>Thank you very much !
>Charles.
>
|||Yes !!!! Thanks a lot Sue.
Have a nice day,
Charles.
"Sue Hoegemeier" <Sue_H@.nomail.please> escribi en el mensaje
news:4eg680hvekta8k50ar1c21fadjcsn7p62i@.4ax.com... [vbcol=seagreen]
> Charles,
> Try increasing the login timeout used by Enterprise Manager.
> In Enterprise Manager, go to the menu to Tools, then select
> Options. Click on the Advanced tab and increase the login
> timeout from the default 4 seconds. Try 10 or 15 seconds
> instead and see if that helps.
> -Sue
> On Sat, 17 Apr 2004 12:14:30 +0200, "Charles"
> <ccolell@.softeng.es> wrote:
(600
>
Can not register SQLServer2000 in Enterprise Manager
Hello,
I try to register a remote SQL Server 2000 installed in a W2003, but it
doesn't work. Afer about 5 or 6 seconds, it says: Timeout expired.
In that network , there is not any firewall and port 1433 is open in the
router. What it really surpises me, is that
I can connect via ODBC to any database of that remote SQL Server2000 and
work wuth tables fine !!!
Using the Enterprise Manager from the W2003 server, we have checked
the following:
-Network Configuration button on the General tab
Is TCP/IP enabled?
-In the Connections tab, the Query time-out value is not set too low (600
seconds)
-There is not a maximum concurrent user connections value set
(unlimited).
Also, we can register others remote servers and work fine.
Any idea ?
Thank you very much !
Charles.Charles,
Try increasing the login timeout used by Enterprise Manager.
In Enterprise Manager, go to the menu to Tools, then select
Options. Click on the Advanced tab and increase the login
timeout from the default 4 seconds. Try 10 or 15 seconds
instead and see if that helps.
-Sue
On Sat, 17 Apr 2004 12:14:30 +0200, "Charles"
<ccolell@.softeng.es> wrote:
>Hello,
>I try to register a remote SQL Server 2000 installed in a W2003, but it
>doesn't work. Afer about 5 or 6 seconds, it says: Timeout expired.
>In that network , there is not any firewall and port 1433 is open in the
>router. What it really surpises me, is that
>I can connect via ODBC to any database of that remote SQL Server2000 and
>work wuth tables fine !!!
>Using the Enterprise Manager from the W2003 server, we have checked
>the following:
> -Network Configuration button on the General tab
> Is TCP/IP enabled?
> -In the Connections tab, the Query time-out value is not set too low (60
0
>seconds)
> -There is not a maximum concurrent user connections value set
>(unlimited).
>Also, we can register others remote servers and work fine.
>Any idea ?
>Thank you very much !
>Charles.
>|||Yes !!!! Thanks a lot Sue.
Have a nice day,
Charles.
"Sue Hoegemeier" <Sue_H@.nomail.please> escribi en el mensaje
news:4eg680hvekta8k50ar1c21fadjcsn7p62i@.
4ax.com...
> Charles,
> Try increasing the login timeout used by Enterprise Manager.
> In Enterprise Manager, go to the menu to Tools, then select
> Options. Click on the Advanced tab and increase the login
> timeout from the default 4 seconds. Try 10 or 15 seconds
> instead and see if that helps.
> -Sue
> On Sat, 17 Apr 2004 12:14:30 +0200, "Charles"
> <ccolell@.softeng.es> wrote:
>
(600[vbcol=seagreen]
>
I try to register a remote SQL Server 2000 installed in a W2003, but it
doesn't work. Afer about 5 or 6 seconds, it says: Timeout expired.
In that network , there is not any firewall and port 1433 is open in the
router. What it really surpises me, is that
I can connect via ODBC to any database of that remote SQL Server2000 and
work wuth tables fine !!!
Using the Enterprise Manager from the W2003 server, we have checked
the following:
-Network Configuration button on the General tab
Is TCP/IP enabled?
-In the Connections tab, the Query time-out value is not set too low (600
seconds)
-There is not a maximum concurrent user connections value set
(unlimited).
Also, we can register others remote servers and work fine.
Any idea ?
Thank you very much !
Charles.Charles,
Try increasing the login timeout used by Enterprise Manager.
In Enterprise Manager, go to the menu to Tools, then select
Options. Click on the Advanced tab and increase the login
timeout from the default 4 seconds. Try 10 or 15 seconds
instead and see if that helps.
-Sue
On Sat, 17 Apr 2004 12:14:30 +0200, "Charles"
<ccolell@.softeng.es> wrote:
>Hello,
>I try to register a remote SQL Server 2000 installed in a W2003, but it
>doesn't work. Afer about 5 or 6 seconds, it says: Timeout expired.
>In that network , there is not any firewall and port 1433 is open in the
>router. What it really surpises me, is that
>I can connect via ODBC to any database of that remote SQL Server2000 and
>work wuth tables fine !!!
>Using the Enterprise Manager from the W2003 server, we have checked
>the following:
> -Network Configuration button on the General tab
> Is TCP/IP enabled?
> -In the Connections tab, the Query time-out value is not set too low (60
0
>seconds)
> -There is not a maximum concurrent user connections value set
>(unlimited).
>Also, we can register others remote servers and work fine.
>Any idea ?
>Thank you very much !
>Charles.
>|||Yes !!!! Thanks a lot Sue.
Have a nice day,
Charles.
"Sue Hoegemeier" <Sue_H@.nomail.please> escribi en el mensaje
news:4eg680hvekta8k50ar1c21fadjcsn7p62i@.
4ax.com...
> Charles,
> Try increasing the login timeout used by Enterprise Manager.
> In Enterprise Manager, go to the menu to Tools, then select
> Options. Click on the Advanced tab and increase the login
> timeout from the default 4 seconds. Try 10 or 15 seconds
> instead and see if that helps.
> -Sue
> On Sat, 17 Apr 2004 12:14:30 +0200, "Charles"
> <ccolell@.softeng.es> wrote:
>
(600[vbcol=seagreen]
>
Can not install SP4 for SQL Server 7.0 on Win2k
Our client applications have being generating timeout
exceptions persistently whiles connecting to SQL Server
7.0. I gathered from the web the problem is a known issue
with SQL Server 7.0 and is fixed in SP4. However,
whenever I try installing the service pack it gets stuck
in the first step and would not continue.
Could somebody offer me some assistance.
Thanks advance.* Look at the sqlsp.log for error messages
* It's a good idea to turn off all 3rd party and non-essential services
before you prform the Service Pack upgrade.
Thanks,
Vikram
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.|||In my case this is a SP4 install on a reinstall of SQL 7.0 with no user databases
I have followed all the tips about turning off all non-essential services, etc., per the kb article and various other docs, but the 7.0 sp4 installation still fails with the messag
"One or more of your user databases have been marked read only, offline or suspect (not recovered). Correct the problem and restart setup.
The log files seem to show everything is ok but the install still fails
I did try one additional test -- running the scm and osql commands shown at the end of the sqlsp.log file.
When I ran the osql command, I get the expected results of 0 but also get an additional message for the ODBC driver manager: "The driver doesn't support the version of ODBC behavior that the application requested (see SQLSetEnvAttr).
I suspect that this additional message is causing the failure
(Running on W2k / SP4)
-- Vikram Jayaram [MS] wrote: --
* Look at the sqlsp.log for error message
* It's a good idea to turn off all 3rd party and non-essential services
before you prform the Service Pack upgrade
Thanks
Vikra
Vikram Jayara
Microsoft, SQL Serve
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups|||How are you installing the setup for sp4. What does the sqlsp.log say? Are
you sure there are no other sql70 instances on the box?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
exceptions persistently whiles connecting to SQL Server
7.0. I gathered from the web the problem is a known issue
with SQL Server 7.0 and is fixed in SP4. However,
whenever I try installing the service pack it gets stuck
in the first step and would not continue.
Could somebody offer me some assistance.
Thanks advance.* Look at the sqlsp.log for error messages
* It's a good idea to turn off all 3rd party and non-essential services
before you prform the Service Pack upgrade.
Thanks,
Vikram
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.|||In my case this is a SP4 install on a reinstall of SQL 7.0 with no user databases
I have followed all the tips about turning off all non-essential services, etc., per the kb article and various other docs, but the 7.0 sp4 installation still fails with the messag
"One or more of your user databases have been marked read only, offline or suspect (not recovered). Correct the problem and restart setup.
The log files seem to show everything is ok but the install still fails
I did try one additional test -- running the scm and osql commands shown at the end of the sqlsp.log file.
When I ran the osql command, I get the expected results of 0 but also get an additional message for the ODBC driver manager: "The driver doesn't support the version of ODBC behavior that the application requested (see SQLSetEnvAttr).
I suspect that this additional message is causing the failure
(Running on W2k / SP4)
-- Vikram Jayaram [MS] wrote: --
* Look at the sqlsp.log for error message
* It's a good idea to turn off all 3rd party and non-essential services
before you prform the Service Pack upgrade
Thanks
Vikra
Vikram Jayara
Microsoft, SQL Serve
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups|||How are you installing the setup for sp4. What does the sqlsp.log say? Are
you sure there are no other sql70 instances on the box?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
Subscribe to:
Posts (Atom)