_sqlsrv2.exe processes hung up

[microedgenh]

Several of our customers use Crystal Reports with our software and Progress 10.1B. We have run into an issue with some of them that the [FONT='Calibri','sans-serif']_sqlsrv2.exe processes are not "let go" when they are done with their crystal report so eventually, no one has a successful ODBC connection. One of my programmers found a knowledgebase item stating the solution was to make the 4gl broker the primary broker and the sql the secondary. However, I have heard and read that Progress recommends the sql broker as the primary. Any thoughts on why these processes are not ending on their own and which broker should to be primary? Thanks, Ann.[/FONT]

 

[Casper]

We use the sql broker as a secondary broker (10.1B). No problems with that. I believe there where some issues prior to 9.1B or C which required the SQL broker to be the primary. That isn't an issue in 10.1B.

Do you still see clients connected to the _sqlsrv2 processes?
(with _connect you can see which users are connected):

DEFINE VARIABLE iPidNum AS INTEGER NO-UNDO.
DEFINE BUFFER b_connect FOR _connect.
ASSIGN iPidNum = 61532. /* pidnum _sqlsrv2 process */
FOR EACH _connect WHERE _connect-pid = iPidNum,
EACH b_connect WHERE b_connect._connect-server = _connect._connect-usr:
DISP b_connect.
END.

Are you sure the process hangs or are they just users who don't close there crystal report and stay connected to the database?

Casper.