i am in a customers environment (FSM 4.01) that has been treated by some other persons, obviously not really knowing what they did. Now there are some very strange things which prevent us from doing some configuratons work.
When trying to install a new non-FileNet FSM-Client, the Installers GUI doesnt offer the choice to select "FSM Client UNIX" or "FSM Client Windows". It just says "-- No configuration". The Tar-GZ-Files are available and located in %FSM_Root%\repos\install\configurations. Cala_Rex is installed and working properly. Installer also recognizes that the Target-System is an AIX-Box.
When trying to (re-)configure a FileNet System and starting the Installers GUI, it does not load the once configured (e.g. fnis_sys_env.sh) systems automatically via "crx://repos/config/PAM".. i have to start it locally on the FSM-Server and navigate manually to %FSM_Root%\repos\config\PAM and load them from there.
Any suggestions ?
Pinned topic Missing Client-Configuration Templates
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2010-02-16T17:32:48Z at 2010-02-16T17:32:48Z by SystemAdmin
SystemAdmin 110000D4XK53 Posts
Re: Missing Client-Configuration Templates2010-02-16T17:32:48ZThis is the accepted answer. This is the accepted answer.Same solution as the other thread from Freddy, all related to name resolution.
If cala_rex can't find the hostname in the database (Webconsole) it does not get any rights to do actions on that client.