Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

FIX: A 32-bit application using the SLI interface fails to load a custom DLL used to process a BIND request


View products that this article applies to.

Symptoms

Assume that a 32-bit version of wsli3270.dll is loaded on behalf of a third-party software to locate a specific Dynamic Link Library (DLL) . However, the C:\Program Files\Microsoft Host Integration Server\SysWOW64 folder is only looked up and did not search the path to locate the custom DLL. Additionally, when you call SLI_OPEN, the application may fail.

↑ Back to the top


Cause

The SLI code is using the HISLoadLibrary function instead of LoadLibrary when trying to find a user DLL.

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. 

↑ Back to the top


Resolution

This issue is fixed in the following cumulative update for Host Integration Server:

↑ Back to the top


References

Learn about the terminology that Microsoft uses to describe software updates.

↑ Back to the top


Keywords: Host Integration Server 2016, kbContentAuto, kbSupportTopic, kb, kbfix, kbqfe, kbHotfixAuto, CI100542

↑ Back to the top

Article Info
Article ID : 4474098
Revision : 6
Created on : 4/12/2019
Published on : 4/12/2019
Exists online : False
Views : 242