We have a very strange issue with a client using UD4.5
OI version=7.3
We create some standard price lists that gets emailed to clients on a daily basis.
We have changed 3 procedures to increase the speed of the process.
After we run the upgrade OI will close after processing for some time…., could be 5 minutes or 20 minutes..
However in our test environment it doesn't.
After many many hours of testing and checking we found the problem to be as follows:
Our test system runs Network driver2.1
Their system runs UD driver 4.5
When the driver gets changed from 2.1 to 4.5 a dll rclclnt.dll gets deleted.
If we restore this after changing to 4.5 then OI doesn't close, and it works like a dream…
Can someone please advise what this dll does and why it would cause OI to close.
Regards,
When the All Networks Driver 2.1 is selected the RCLCLNT.DLL is the same file as RCLNT21.DLL. The NETDRV program operates by coping the version specific file name to a general file name.
The reason the file doesn't appear when the 4.5 driver is selected is the 2.1 driver code base is different than the 3.0+ code base. The 3.0+ Universal Drivers replace LH.DLL, instead of RCLCLNT.DLL, with a copy of the current driver.
Copying the RCLCLNT.DLL back while the 4.5 driver is selected shouldn't have any effect on the system but it isn't a supported configuration. The system could have issues elsewhere that only manifest themselves when the DLL is present.
I suspect, by changing the network driver on the client without the corresponding service version you aren't actually utilizing the Linear Hash service. The 4.5 client driver would be unable to connect to the 2.1 service which might result in it directly accessing the LK/OV files. Copying the RCLCLNT.DLL back into the system allows the client to communicate with the server which is why it appears to run correctly.
Verify that the service is actually being used. There are several different methods to ensure the REVPARAM files are correct and the 2.1 service is accessing the LK/OV files (instead of the client).
1) On the server use the "Opened Files" view to see if network clients have any *.LK or *.OV files open. If so, the client, and not the service, has opened the files.
2) On the server use Nirsoft OpenedFilesView to see which process has open handles to the LK/OV files.
3) On the server use SysInternals Process Monitor to watch which processes access the LK/OV files.
The LH45SRVC or LHSRVC should be the only process accessing the LK/OV files. If any other process (or system process) is accessing the files then the Linear Hash service is being bypassed.
The Universal Driver 4.5+ include a manager utility to verify the service is in use, view current locks, and stations connected. This is one of the reasons the 2.1 driver is no longer supported.
Does your test client utilize the Linear Hash service or is it accessing the files directly?