Board index MS SQL Server

timeout expired.

timeout expired.

Post by Debasis » Sat, 01 Sep 2001 02:20:41



I am getting timeouts on everything I do and I can't even
expand the server
in Enterprise manager without getting the following error:
_________________________________________
A connection could not be established to XXXXXXX (name of
the server)

Reason:  Timeout expired.

Please verify SQL Server is running and check your SQL
Server registration
properties (by right-clicking on the XXXXXXXX node) and
try again.
______________________________________________
I know SQL Server is running.  

-----------------------------------------------------------

Initially I was able to connect to the remote SQL server
after I reinstall the TCP/IP on the SQL server m/c, and I
was able to expand db on EM.

THis worked fine for couple of days, then the problem
started again, i.e. now I am not able to connect / expand
remote SQL server from EM .

Surprisingly, I am able to connect to the same remote
server from QA.
Any suggestion or link will be highly appreciated. Lewis
or jennifer have u found any solution?

 
 
 
Top

timeout expired.

Post by Doo » Sat, 01 Sep 2001 02:53:54


Change you timeout settting:

EM
Tools
Options
Advanced Tab

I set mine to 30, default at install is only 4

--
Doo
~~~~~~~~~~~~~~~~
Sr. Data Architect / DBA
PlanetJam Media Group

~~~~~~~~~~~~~~~~

Quote:> I am getting timeouts on everything I do and I can't even
> expand the server
> in Enterprise manager without getting the following error:
> _________________________________________
> A connection could not be established to XXXXXXX (name of
> the server)

> Reason:  Timeout expired.

> Please verify SQL Server is running and check your SQL
> Server registration
> properties (by right-clicking on the XXXXXXXX node) and
> try again.
> ______________________________________________
> I know SQL Server is running.

> -----------------------------------------------------------

> Initially I was able to connect to the remote SQL server
> after I reinstall the TCP/IP on the SQL server m/c, and I
> was able to expand db on EM.

> THis worked fine for couple of days, then the problem
> started again, i.e. now I am not able to connect / expand
> remote SQL server from EM .

> Surprisingly, I am able to connect to the same remote
> server from QA.
> Any suggestion or link will be highly appreciated. Lewis
> or jennifer have u found any solution?


 
 
 
Top

timeout expired.

Post by Burton Kin » Sat, 01 Sep 2001 03:33:44


Is this SQL 2000?  I've seen a lot of connectivity issues with SQL 2000 and would like to see Microsoft own up to the issue that it's a problem.

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

 
 
 
Top

1. [OBDC SQL Server Driver][Timeout Expired] - How to reconfigure the timeout

When running a query on a very large database, I receive this error after
30-50 seconds:
[Microsoft][OBDC SQL Server Driver][Timeout Expired]

We are using NT and 98. I receive this error message running the queries on
the client and the server. We just switched over from Access 97, which was
unable to handle the amount of data. Using Access 97 ODBC pass-through
queries, we recevied a similar error message, but it was a simple fix -
select properties and change the timeout.

This doesn't happen with queries that return only a small number of rows.
The queries I am receiving the error message on are attempting to return 7-8
million rows.

The default timeout setting is 10 minutes, and so far that is the only
setting I can find.

I appreciate any help on this matter!

2. Using indicators to set values to null

3. ?Timeout expired

4. Instance?

5. [ODBC SQL Server Driver]Timeout expired

6. pgsql/src/backend/parser (parse_func.c parse_oper.c)

7. Timeout expired.

8. DTS SQL

9. Timeout expired

10. Timeout Expired Message

11. timeout expired and/or PCAnywhere hangs???

12. Timeout Expired


All times are UTC
Board index