I've seen that done successfully. It's been years since helping a customer set it up and don't remember the details but it worked for hundreds of clients pointing to a shared server drive. We may have added registry entries on each client to make it appear the client was installed but I don't remember,
You should be able to figure out why you're getting a 2195 by tracing the client connect attempt. Maybe you don't have write access to the share or something along those lines; or maybe it's missing expected registry entries? You might try replicating the MQ registry entries from the server with client installed, with appropriate substitutions, to one of the client wannabes.
HTH, Marty
Benjamin F. Zhou wrote:
Hi,
since quite many developers need to access MQ via WindowsClient. I tried to install the client software once on a shared network drive, then just add that location, say L:\ibm\mqseries\bin, to system path, and define the MQSERVER environment variable.
But this doesn't seem to work. and I got reason code 2195 - unexpected error. I also checked the registry, don't really see any entry of significance related to this problem.
Has anyone tried this before with success?
thanks a lot.
Benjamin F. Zhou Mercedes-Benz USA x.2474
Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
