Re: SQLCLI problems: Now we know that the QSQCLI activation group is getting purged . . . -- MIDRANGE-L

Subject: Re: SQLCLI problems: Now we know that the QSQCLI activation group is getting purged . . .
From: James Lampert <jamesl@xxxxxxxxxxxxxxxxx>
Date: Mon, 30 Jan 2012 08:52:28 -0800
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Just about the last thing I found out about this mystery on Friday was that wherever the jobs are locking up trying to call SQL, the QSQCLI activation group is getting purged. And based on the error messages I get when I simulate this on our system, the purge is causing the lockup, and not the other way around.

But it's nothing we're doing, and the customer swears up and down that it's nothing he's doing. (and that the purge isn't showing up in the joblogs; I haven't had a chance to check that for myself yet).

Any ideas?

--
JHHL

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: SQLCLI problems: Now we know that the QSQCLI activation group is getting purged . . . , Michael Ryan

This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.