Date:  11/17/2014 05:07:01 PM Msg ID:  004737
From:  FoxWeb Support Thread:  004734
Subject:  Re: Foxweb confused with fw_enter location?
I'm glad it worked out. Out of curiosity, are you using the VFP runtime DLL?
If yes, then you have to compile fw_enter and fw_exit manually, because they are not directly referenced in the URL.
If you are not using the VFP runtime DLL, then you should have been getting error messages in the FoxWeb error log. 
FoxWeb Support Team email
Sent by Ali Koumaiha on 11/17/2014 12:56:19 PM:
I resolved this.  Wow.. that kicked my behind, to try to figure it out.
so, my main/default fw_enter.prg was not being able to get recompiled.. as it had outsanding references.
so, in my fw_exit.prg i released the class that was used in fw_enter.prg
and i did that, and i did the fwAdmin.fwx to recompile all scripts. it worked.
now all domains are working as they should.  that was wierd though.
Sent by Ali Koumaiha on 11/17/2014 11:46:03 AM:
 I never experienced this before.
On our production server, we have 5 licenses on it. all is good.
one of the domain, i made the default location to c:\OtherDomain for Foxweb,
while all 4 other domains are on the default setting for Foxweb (C:\FoxWeb\Website).
Now, my other domain is NOT reading the fw_enter from the c:\OtherDomain
this is really bizzar.
FW is started as service, then, not as service, i made sure in the FW Control Center, under the virtual servers, that the domain's program root is C:\OtherDomain, while the others are [DEFAULT]. and the default program root is C:\FOXWEB\WEBSITE\
in IIS, i have a created a new website (example) and the binding is configured.
the bizzar part is the fw_enter for the OtherDomain is not being read.