Focal Point
Error Parsing MASTER File xxx (FOC36305)

This topic can be found at:
https://forums.informationbuilders.com/eve/forums/a/tpc/f/7971057331/m/7981087331

July 09, 2004, 12:37 PM
Alfred
Error Parsing MASTER File xxx (FOC36305)
I installed WebFOCUS 5.2.1 (Win2000 Client).
If I start to open an .fex procedure or create a new one and select a masterfile the following error shows up:

Error Parsing Master File xxx (FOC36305) APPROOT is not defined, APP Commands are disabled (FOC227). The focexec procedure cannot be found : yyy

Can somebody help me, thanks Alfred
July 09, 2004, 01:36 PM
pruittlr
You might want to check the app path entries in the edasprof.prf file.

APP ENABLE
APP PATH catcadsa mfdcadsa ibisamp
(the lowercase directory names are where your master files and fexes are located)

App root should have been set when you installed the software. The root would be whatever drive you installed on, such as c:\ibi\apps.


Raelene
July 12, 2004, 02:24 PM
Alfred
Thank you, in the c:\ibi\srv52\wfs\etc\edasprof.prf file was only the entry
APP ENABLE
APP PATH ibisamp
I installed the software again but it did'nt help.
My masterfile and fex files are on the WebFocus Server and not on the Client.

Alfred
July 15, 2004, 09:34 PM
Bob Jude Ferrante
it sounds as if you're using DevStudio, is that correct? And you're trying to use it to edit a FOCEXEC?

1. Is your server started before you start using DevStudio? If the server is not running, you will get errors like this one... it can't parse a master file because it uses the server to do the parsing. If the server is down, or inaccessible, that explains it.

2. Do you have a Web server like IIS installed on your development server? The old client/server way to connect to the WebFOCUS server is no longer supported in 5.2. You need a Web server or to configure your development server to use the HTTP listener (there is a tech memo - TM4546 on the IBI support site that describes how to configure this.)

3. Make sure in DevStudio that your client path is correctly set up for the WebFOCUS Environment you are using.

If all else fails, call tech support.

Cheers
July 20, 2004, 01:32 PM
Alfred
Thanks, I did an installation mistake, I installed as well the WebFocus Reporting Server on the Client so it pointed to this.
After a new installation it worked ok
(also I had to clean the registry from all WebFocus entries) A tool to do this would be not bad.

Alfred