OI 4.1.3a and W98 (OpenInsight 32-bit Specific)
At 17 NOV 2003 12:26:09PM Mike O'Neal wrote:
Hello all:
A client of ours had been running our application on OI 4.1.2 for several months without any network problems. Last week I upgraded them from OI 4.1.2 to OI 4.1.3a, and now none of their Windows 98 machines can open OpenInsight or our software at all. No changes were made to the network or workstation environment during this process. OpenEngine opens O.K., but clicking on openinsight.exe briefly shows the hour glass and then nothing happens (no error message reported). Reinstalled the workstation client, also asked the MIS folks there to stop and start the NLM, no joy.
The Windows 2000 machines are O.K, this is on a Novell 4.x system.
Any ideas?
TIA,
Mike O.
At 17 NOV 2003 12:26PM Pat McNerthney wrote:
Mike,
One of the changes between 4.1.2 and 4.1.3a was the addition of the language specific dlls, OILang*.dll. If OI is unable to locate or load the language dll it is looking for, then OI just quitely terminates. To see the behavior you are seeing on your Win98 boxes matches the behavior of OI in the case of not being able to load it's language dll, rename OILang*.dll to OILang*.ddd and then try to launch OI.
OI 4.1.3 requires this language dll to reside in the current working directory (or default directory), and will not find it if you are running your all your executables from a different directory.
HTH,
Pat
At 17 NOV 2003 12:26PM Mike O'Neal wrote:
Thanks for the quick reply, Pat, I'll forward this information to our site.
Quick question regarding the SYSREPOSLANGUAGE table in general. We have had trouble during upgrades with this in that we sometimes receive an 'unable to open sysreposlanguage' table after installing an OI upgrade, and we are then locked out of our app. One way suggested to us around this would be to deploy this table as part of our own application. Any problem with deploying this table ourselves, and can we put it in a folder *below* the working directory?
Thanks much,
Mike O.
At 17 NOV 2003 12:26PM Mike O'Neal wrote:
] Thanks for the quick reply, Pat, I'll forward this information to our site.
Hi Pat - Afraid that re-naming the .dll'S did not work. To follow up from the previous message, their SYSREPOSLANGUAGE table is now in a folder called SYSLANG in the GLOBAL application that is *below* the working folder. Is that O.K.?
Mike O.
At 17 NOV 2003 12:26PM Pat McNerthney wrote:
Mike,
The point of renaming these dlls was to replicate the problem, not fix it. If after renaming off these dlls you end up with the same exact identical behavior as before, then it is a good bet that this is where your original problem is. If the behavior is the same, then there is something about your Win98 machines that is preventing OI from either finding or loading the OILandENU.dll.
Also, this is a completely separate, unrelated issue from the SYSREPOSLANGUAGE issue (except for the fact that they both involve language support). I personally am not knowledgable about the issues involved in getting SYSREPOSLANGUAGE upgraded.
Pat
At 17 NOV 2003 12:26PM Mike O'Neal wrote:
]The point of renaming these dlls was to replicate the problem, not ]fix it. If after renaming off these dlls you end up with the same ]exact identical behavior as before, then it is a good bet that this ]is where your original problem is. If the behavior is the same, then ]there is something about your Win98 machines that is preventing OI ]from either finding or loading the OILandENU.dll.
Gotcha.
They *are* getting the identical problem as before *and* renaming the .dll's also prevents the 2000 and XP machines from logging in. Could it be that the .dll's need to be registered somehow on the 98 machines?
Mike O.