Hi,

Which powerbuilder version are you using?

Which popup is showing? (attached image would help)

If it's a system error which is popping up, you could do a HALT; or HALT CLOSE; but it's still ugly.

Maybe there's a setting for the connection on SQL Server which keeps the connection alive for some time that you can play with? (It's been a while I've been using sql server, so maybe someone else can give more information on that possibility).

regards

I found this information, here: https://community.spiceworks.com/topic/372789-sqlstate-08s01-08001-connection-failure

HTH

---

Are your ports configured correctly? Firewall allows access?

Poblano

Hi,

A PB app getting stuck on "Communication link failure sql error 08S01" has an issue in its DB error recovery logic. You can subclass SQLCA or any other transaction object to capture DBError event and react accordingly. Comm. link suggests a DISCONNECT;. Why disconnect? Because that command probably fails but it sends signals to DB client that you are giving up on current connection. Perhaps even a destroy of said transaction object would kill that error situation. FreeDBLibrary = true on application object may be needed.

Recovery is then to possibly create new transaction object of same class (if code destroy that object) and a new CONNECT could re-establish DB connection.

NOTE: Sometimes bad connection hangs in a pool on the client so first CONNECT may fail albeit next CONNECT succeeds "just because".

In any case, as pointed out by Miguel in earlier response you always have the option to HALT CLOSE or HALT to allow PB process to kill itself.

HTH /Michael

I remember first time a SQL Anywhere database suddenly had a VPN over internet between DB server and our PB client. Suddenly we had connectivity issues and timeout issues we never saw before. Took some code rewriting and a bunch of hard learning to cope with "guaranteed network connectivity" being a thing of the past.

Hi Louis;

   This error could also be related to 08501 ... "Communication link failure is a mid-stream failure of the connection from client to SQL Server. This typically points to problems with your networking layer, typically networking hardware. For example a router in your network could be dropping connections, or a network card that is going bad".

  Like 08S01 - which points to a TCP/IP network failure.

Regards .. Chris

Thanks everyone, I've decided to try this on the dbparm line , I'll post later with results.

ConnectOption='SQL_DRIVER_CONNECT,SQL_DRIVER_NOPROMPT'"

Thanks,

Lou