Bobbee, It might be related to the value of HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem\NtfsDisable8d ot3NameCreation in the registry.
Some apps require the ability to refer to a short file name. But, like you said, the value of that on both computers should have been the same in your case. Regards, Dan Egner BMC Software, Inc -----Original Message----- From: Robert Broderick [mailto:[EMAIL PROTECTED] Sent: Thursday, March 03, 2005 7:23 AM To: [email protected] Subject: Re: WMQ on Windows Here is anther wierd instance of path problems. Had two machines. One Ghost of another. I received the machines right after the took the image and installed the second machine from the Ghost image. I installed MQ on the Ghost machine and it worked fine. I installed MQ on the Root Image machine and MQ was failing all over the place. Couldn't create QMGRS,Commands didn't work, etc. I reinstalled a couple of times. I finally installed to "C:\MQ" and everything worked fine. I never checked the PATH of the two machine because they should have been ident. So one having more PATH than the other should not have been a consideration. WIERD!!! Now I install everything to c:\IBM\...... >From: [EMAIL PROTECTED] >Reply-To: MQSeries List <[email protected]> >To: [email protected] >Subject: Re: WMQ on Windows >Date: Wed, 2 Mar 2005 15:24:49 -0500 > >I believe there's a limit to the path size parameter. I have typically >changed this env variable by using the short path names (those with the >~ ). > > > > > > > > > > "Thomas, Don" > <[EMAIL PROTECTED]> To: >[email protected] > Sent by: MQSeries List cc: > <[EMAIL PROTECTED] Subject: WMQ on >Windows > wien.ac.at> > > > 03/02/2005 03:15 PM > Please respond to > MQSeries List > > > > > > >Group, > > > I have a pet peeve that maybe one of you can help me with. >When MQ is installed on a Windows server, be it NT or 2000, we all know >that the PATH statement is updated with the appropriate MQ directories. >However, when MQ is not among the first things installed, and the MQ >entries are further down the PATH statement, some applications, Candle >and Microfocus among them, can't seem to find the MQ libraries. I have >to edit the PATH statement and move the MQ entries to the beginning and >reboot the server before these applications can resolve the various >.dll references. Can anyone explain why this is or know of an easier >way to get around this? > > >Don Thomas >MASC - Coraopolis >Phone:+1-412-893-1659 >mailto:[EMAIL PROTECTED] > > > >Instructions for managing your mailing list subscription are provided >in the Listserv General Users Guide available at http://www.lsoft.com > >Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html > >Instructions for managing your mailing list subscription are provided >in the Listserv General Users Guide available at http://www.lsoft.com >Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
