Shell Command button stopped working

[Scott Caldwell]

Long story short is I tried to install version 6.0 (we are currently running 5.6) and after a failed attempted, I removed it.  But I did notice upon installing it that the Shell Command button in 6.0 didn’t work.  After uninstalling 6 the button doesnt work in 5.6 either.

Also, when i open a normal command window and try to setsite I get a path error now: “The system could not find the path specified”.’

Anyone ever experienced that?

Topic

[bill bearden]

We run CIS on Windows servers. From your use of the phrase “command window”, I am guessing you do too. If you are on *nix, this probably doesn’t apply.

Your second issue first… You state that you can’t setsite in a normal command window. We saw something like that after we installed 6.0 but were still running 5.8.x. We did this on our test server. The 6.0 install changed the Environment Variables for users on the test server. As soon as you open the command window (Start>Run>cmd.exe), do a set command to display them. You might see that CL_INSTALL_DIR is pointing to 6.0. Also, look at the Path variable. I created a file called setenv58.bat so that I could still see the 5.8 sites. But I think this only applies when you are rdp’ed to the CIS server.

On the first issue, there is less to go on so this is some guesswork. There are 3 cases I think of when pushing the shell window button: 1) local client, 2) client on server but connected local, and 3) client on server but connected remote. If you are running the GUI client on the server, make sure you select “Use the Local Config Server” when selecting your site (Server>Change). I believe that if you use local, the button will try to start cmd.exe. But if you use remote, it will try to use telnet, which is sometimes troublesome on Windows.

You might also check the settings in the GUI client at Options>Client>External Command (tab). We leave all these blank.

[Scott Caldwell]

Yes, we are on Windows….

What should the CL_INSTALL_DIR variable be set to? It wasnt in there (maybe got removed when I uninstalled 6?).

[bill bearden]

I don’t know about 5.6. I have only used 5.8.x and 6.0. Things might have changed.

However… The 5.8 CL_INSTALL_DIR I see is L:healthvisioncis5.8

[Scott Caldwell]

bill bearden wrote:

I don’t know about 5.6. I have only used 5.8.x and 6.0. Things might have changed.

However… The 5.8 CL_INSTALL_DIR I see is L:healthvisioncis5.8

Is there an integrator folder under your cis5.8 folder?  Try to guage what my variable should be…

Thanks.

[bill bearden]

Scott,

Yes, there is an integrator under cis5.8.

I was just working on this yesterday because installed CL 6.0 on one of our production servers and ran into this problem again. Here is a .bat file that I used today at the beginning of another script that is run as a scheduled task. The usual disclaimers apply. It is for 5.8 and the older version you are using is 5.6. I changed the default site name to “sitename”.

Code:

@echo off
set CL_INSTALL_DIR=l:healthvisioncis5.8
set HCIROOT=%CL_INSTALL_DIR%integrator
set PATH=%HCIROOT%sbin;%HCIROOT%bin;c:Windowssystem32;c:windows;C:Program FilesWindows NTAccessories;%HCIROOT%usercmds
set HCISITE=sitename
set HCISITEDIR=%HCIROOT%%HCISITE%
set TCL_LIBRARY=%HCIROOT%tcllibtcl8.4

set DBDPATH=%HCIROOT%sitenameexecdatabases
set DBFPATH=%HCIROOT%sitenameexecdatabases
set DBTAF=%DBDPATH%rdm.taf
set DBTMP=%DBDPATH%
set LOCKMGR=lm_cis5.8_sitename
set RDSDLL=%HCIROOT%bin
set RDSLOGIN=cl_cis5.8_sitename

[Scott Caldwell]

Changing the CL_INSTALL_DIR to the proper location fixed the command button.  Thanks for all the help!

[Author]

Replies