I am having a problem with Flash Connect 3.5.1 and Red Hat Enterprise
ES 4.0

I am happy with historically setting up the Flash Connect side and WWW
account when running the FLASH side on a Windows Server, irrespective
if the WWW account is running on Windows or Linux.

This is the first time I have installed FLASH under Apache running on
Red Hat Enterprise 4.0

The install seems to have worked OK, and if I run the DIAGNOSTICS from
the WWW account it says everything is 100% OK, activated etc.

However, as soon as I run the test program BOO

http://192.168.16.5/cgi-bin/fccgi.exe?w3exec=boo

nothing appears apart from the usual Error 500. The HTTPD server is
running and I have proved this with a basic INDEX page.

I have heared that possibly the Red Hat side has "security" which is
preventing the fccgi.exe from running, but all that seems OK to me.

Any help would be appreciated.

John

Before I get into the tech stuff, I was confused briefly by the
subject to this thread and the mixed references between FLASH, Flash
Connect, etc. The product name is FlashCONNECT, and should at least
be referred to in subjects as Flashconnect or fc or something similar
because "flash" generally refers to "FlashBASIC". RD got into the
silly "flash" thing but like most marketing campaigns never really
carried it through, and even went so far as to say things like "all
BASIC is FlashBASIC, even when it's not flashed". Grrrr. Anyway - I
see the problem is with the FlashConnect web product and not
FlashBASIC...

Immediate ideas:
1) Permissions on cgi-bin or fccgi.exe itself, should be 755 I think.
2) Check the FC docs which has a whole section on troubleshooting and
a step by step procedure for finding out where the issue is.
3) Since your comfortable setting up FC you probably have this set
properly already, but just in case: Your server pool, probably
'default' should point to one of the following:
a) localhost
b) 127.0.0.1
c) the local IP address (192.168.16.5)
d) or the local hostname
4) Ensure FCService is started and running: "ps awux | grep FCS". I'm
not sure if there will be an issue if D3 is running under user Linux
Pick but I don't think so. If so then it may need to be started with
different permissions using sudo or similar. I put a !FCService in
user-coldstart (actually these days we can have a user-coldstart in
all accounts so this goes in the www account now).

I'll guess the issue is permissions or FCService not started.

HTH
T

john (AT) mrpsystems (DOT) co.uk wrote: