Hello,

First of all, i would like to apologize for asking the guestion which
have already been asked here probably thousand times.

I have experienced difficulties installing Farcry 3.0.1 under IIS in
the shared hosting environment.
I've followed both pdf tutorial and mr.Coughlin's video tutorial on
installing Farcry in IIS environment, but with no luck.
 I don't have physical access to administration of hosting server and
after some long dispute with server admin, i was given following
mappings and paths:
E:\wwwroot\hosting\somesite.ee\www\ - this is a location of physical
access path, where installion files (3 folders-
farcry_core,farcry_pliant and fourq) of Farcry reside.
In CF admin there is a logical path (mapping) "farcry" - E:\wwwroot
\hosting\somesite.ee
\www  and ColdFusion Source Name "somesite_ee", which is pointed to
the appropriate database (SQL).
In IIS there is also  an alias 'farcry' - mapping E:\wwwroot\hosting
\somesite.ee
\www\farcry_core\admin.

I've instantly tried  to install Farcry and to run it under my home
site directory (which is E:\wwwroot\hosting\somesite.ee\www) with
those given settings and application name "somesite_ee". However,
after succesful(?) installion, Cold Fusion gave me a huge variety of
errors, starting from "template /Application.cfm is not found" and
finishing with Java exceptions: java init failed:
net.sf.javainetlocator.InetAddressLocator (while trying to access
installed site) and while trying to access login.cfm, ColdFusion
spitted out Java exception stating that Java virtual machine memory is
out of stack range.

Would FarCry CMS install with provided settings?


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"farcry-dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/farcry-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to