Skip to Content
0

ADS v11.10 sp_MgKillUser() Error 7050

Dec 22, 2016 at 02:48 PM

133

avatar image

We have a program which is using Data Dictionary connections. Sometimes when the program crashes or is closed in an unexpected way, these Data Dictionary connections will stay open forever (until we restart the server OR until we use the sp_MgKillUser stored procedure in Data Architect).

To counter this problem I tried to make a functions that searches for all active users on the Data Dictionary and then calls the sp_MgKillUser function to kill their connections. This is working for every user except for my own user. When trying to disconnect my own user, ADS gives me a 7050 error, saying that the user isn't connected to the database. I have monitored the connected users using Advantage Data Architect and my user IS connected to the database.

Is this a bug in ADS or is there another (cleaner) way to close 'stale' connections?

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

4 Answers

Hakan Haslaman
Dec 22, 2016 at 02:50 PM
0

Hello Thomas,

Which ADS Version your are using exactly (with extension)?
If you open ARC and check connected users, are the user shown as connected?
If yes, if they are connected via TCP/IP or UDP/IP?
Which OS you are using for the Client and for the Server?

Share
10 |10000 characters needed characters left characters exceeded
Thomas Hens Dec 23, 2016 at 06:40 AM
0

I'm using ADS Version 11.10.0.24

When I open ARC the users are shown as connected.

The communicationtype is TCP/IP

The OS used for the Client is Windows 7 SP1 and for the Server Microsoft Server 2012 R2

Share
10 |10000 characters needed characters left characters exceeded
Hakan Haslaman
Dec 23, 2016 at 06:47 AM
0

May you can try to reduce the client time out value in the ADScfg.exe and disable the IPC connection on the server.

Share
10 |10000 characters needed characters left characters exceeded
Thomas Hens Dec 27, 2016 at 03:38 PM
0

Now I'm able to close connections for my own user.
But the solutions caused another issue. Creating/initializing TAdsSettings AFTER killing my connections with sp_MgKillUser causes an exception (Error 6624: A Winsock virtual circuit was reset remotely). The only solution I found was restarting the whole application.

Is there an easier way to let the application know that I killed his connections?

(I tried disconnecting and reconnecting,...)

Share
10 |10000 characters needed characters left characters exceeded