istool client
Posted: Wed Feb 24, 2010 2:28 pm
Hello all,
After installing Fix Pack 1, we've noticed a problem with the istool.exe (Information Server Command Line Interface) on the client machine. It seems that the patch has removed the existing istool.exe (C:\Program Files\IBM\InformationServer\v8101\Clients\istools\cli\) and installed a new istool.bat in that directory. However, the shortcut from Programs menu still points to the exe, so it shows the following error: "The item 'istool.exe' that this shortcut refers to has been changed or moved, so this shortcut will no longer work properly."
We found that the file is actually present in
C:\Program Files\IBM\InformationServer\v8101\Updates\8.1.FixPack.1\Clients\istools\cli\istool.exe
So, we just copied the istool.exe file from the FixPack directory to the original istools\cli directory, and it seems to be working ok now.
Did something wrong happen during our Fix Pack install? We've tried the vanilla install multiple times with the same result. Anyone else have this issue?
I'm not really looking for any other work-around, since we've got it working already. Just want to know if the problem is on our side, or if it's a problem with the IBM installer.
thanks in advance,
Rob
After installing Fix Pack 1, we've noticed a problem with the istool.exe (Information Server Command Line Interface) on the client machine. It seems that the patch has removed the existing istool.exe (C:\Program Files\IBM\InformationServer\v8101\Clients\istools\cli\) and installed a new istool.bat in that directory. However, the shortcut from Programs menu still points to the exe, so it shows the following error: "The item 'istool.exe' that this shortcut refers to has been changed or moved, so this shortcut will no longer work properly."
We found that the file is actually present in
C:\Program Files\IBM\InformationServer\v8101\Updates\8.1.FixPack.1\Clients\istools\cli\istool.exe
So, we just copied the istool.exe file from the FixPack directory to the original istools\cli directory, and it seems to be working ok now.
Did something wrong happen during our Fix Pack install? We've tried the vanilla install multiple times with the same result. Anyone else have this issue?
I'm not really looking for any other work-around, since we've got it working already. Just want to know if the problem is on our side, or if it's a problem with the IBM installer.
thanks in advance,
Rob