RE: ODBC administrator locks up

I have an issue with the ODBC drivers from iACS on my Windows 11 laptop.
We downloaded the latest iACS Windows package and unzipped using File Manager.
Went to install it (as admin) and the install just froze.
Later, found out about the caveat of unzipping files with Windows having issues. So I unzipped the file again using 7Zip.
Reran the install and it completed. But NOW ODBC days that it can't find the .dll file in windows32. But I can see the file in windows32.
So I'm thinking the .dll is corrupted.
Haven't had time (nor authority) to fix the laptop. I need to get together with my tech support people to address this issue.
Tried both 32 and 64 bit options - no luck.

Paul

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Richard Schoen
Sent: Friday, March 29, 2024 2:18 PM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Subject: RE: ODBC administrator locks up

Did you try the 32-but ODBC Administrator ?

Also did you "Run As Administrator" ?

I can't recall the ODBC Administrator every locking up.

Regards,
Richard Schoen
Web: http://www.richardschoen.net
Email: richard@xxxxxxxxxxxxxxxxx

-----Original Message-----
message: 5
date: Fri, 29 Mar 2024 14:44:23 +0000
from: Stephen Landess <steve_landess@xxxxxxxxxxx>
subject: ODBC administrator locks up

All -

I had an old Dell laptop (W10 Pro with 16GB memory) which died last week. I had the most recent IBM ACS client (http://1.1.9.4) running on it and was successfully using ODBC User DSN's created with ACS http://1.1.9.4 on it.

I have installed http://1.1.9.4 on the new laptop (Dell Latitude 5540 with W10 Pro / 16GB memory) and I used the 64-bit ODBC administrator to create some User DSN's on it yesterday, but today when I try to either change any of the User DSN's which I created the ODBC administrator application locks up and I have to cancel the task.

Has anyone had a similar experience ? I am expert at debugging and problem resolution on IBM i systems, but I'm at a loss to figure this Windows problem out.

Regards,
Steve Landess
(512) 289-0387
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.