Software Deployment

Could you, perhaps, provide LESS information about what you want?

Are we talking about a package? An application?

talking about a package? An application?

[font="trebuchet ms"]Application : Rapid SQL
[font="trebuchet ms"]When user tries to connect to this application he gets an error as
[font="trebuchet ms"]" Cannot load Open Client, please verify that libct.dll and libcd.dll are in your path"
[font="trebuchet ms"]
[font="trebuchet ms"]We were troubleshooting this and just happened to delete the env var LANG =C and launch the application. The issue was resolved. We checked the MSI to see if it puts during installation, but its not present.
[font="trebuchet ms"]The user again reported the same issue. The env var seems to have installed back. I was checking to understand the usuage of this env var, please advice.
[font="trebuchet ms"]
[font="trebuchet ms"] - V

Clearly it's application-specific so your best bet is to contact the vendor. As for the actual error message, I *really* don't think it could be any clearer: you need to add the folder where those DLLs are installed to the user's PATH. Note I say the user's PATH: if you use the System PATH, you'll need to reboot the workstation before it takes effect.

ORIGINAL: VBScab
you'll need to reboot the workstation before it takes effect.


Is that specific to Vista? (have been fortunate to not land a client on it yet, lol) I'm pretty sure that's not the case on Windows XP.

It's the case for all NT-based OSs UNLESS the PATH (or other environment variable) is added via the Control Panel 'System' applet. When that is used, it generates a system-wide message that the environment has changed. Clearly, with the code and concept having been around since 1995-ish, the Windows Installer team evidently took the view that it was a bit "leading edge" and didn't bother implementing it.

via the Control Panel 'System' applet

The first step we did was to update the PATH var, but that didnt solve the issue.
Guess will follow-up with the vendor. Thanks.

The first step we did was to update the PATH var, but that didnt solve the issue.Yes, but was that the System or User PATH? As a User PATH, once the installation has finished, launching the application is a separate process and will thus pick up the addition. If, however, you added to the System PATH, it won't take effect until the system is restarted.

If you're going to talk to the vendor, you want to ask him why his application is so brain-dead that it even cares about the PATH, much less relies on it. This is 2009, for God's sake! PATH should have died with DOS 6.22...

What I wouldn't give to be a third party listening in when Ian calls vendors about problems with packages. I bet it's a hoot! [:D]


ORIGINAL: VBScab

If you're going to talk to the vendor, you want to ask him why his application is so brain-dead that it even cares about the PATH, much less relies on it. This is 2009, for God's sake! PATH should have died with DOS 6.22...

I no longer call vendors about packages, nor indeed their useless applications. I just advise the business unit concerned and ask them if they want to risk their data with software which, for example, continues to try to update itself when the automatic download has failed...Oh, and for good measure, if the failure is the first item, it's more than happy to try the remaining 41 items, even though none will work with older versions...Oh, and for extra good measure, right at the end of that process, it updates the registry to indicate a successful update.

This software cost my client a six-figure sum to buy and a four-figure yearly per-user license...

I too would enjoy listening to Ian's discussions with someone like that.

I often laugh at your priceless comments Ian, you certainly keep the days entertaining.

The error message that you are dealing with is due to the System Environment Path missing the location to your Sybase Open Client. First make sure it is installed (lookup in Add/Remove Programs). It is possible that it is not in Add/Remove programs under the name Sybase Open Client but a part of a different installation. The normal install directory of Sybase openclient is C:\Sybase. Maybe a quicker way to find out where the DLL are is just to search for them and remember the path and put it in the system variable (of course reboot is necessary).

Hope you find it and good luck.

Regards,

ElWygo