Missing Helicon.Ape.dll

[JohnnyFusion Profile]

Hi: running coldfusion 9 on a Win 2008 platform and have hit a wall regarding dowloading files > 1GB. So, I'm trying to install Ape (free version) and seem to have installed it OK the license manager sees the site. So I followed the manual installation for single site installation and patched the web.config file and copied the httpd.conf from Program Files/Helicon/Ape to a new folder in the root of my website.

I can't complete step 1 - there is no Helicon.Ape.dll in the Program Files/Helicon folder created when I installed Helicon Ape.

Finally, the example to use this appears to be;
<Cfheader name="X-Sendfile" value="#filename# />
<cfheader name="content-disposition" value="attachment;filename="fullpathforfile.mov" />
<cfcontent type="video/Quicktime">

My working version that fails at 1GB includes the #filename# with the <cfcontent tag although (I'm guessing) without the .dll nothing is going to work.

Can you help with the missing file? and any other comments

[Yaroslav]

Please check also C:\Program Files (x86)\Helicon\Ape\ManualInstall\Bin for Helicon.Ape.dll file

The bad news is that x-sendfile will not probably work with ColdFusion. The problem is ColdFusion is known to break normal IIS request processing sequence, causing all other modules not to function after ColdFusion module. If it is acceptable for you I suggest you to try free Railo or Open BlueDragon instead of ColdFusion - http://www.helicontech.com/articles/run ... roduction/
http://www.helicontech.com/articles/ins ... on-on-iis/ These are free compatible alternatives to Adobe ColdFusion, which are known to work correctly with IIS using our Zoo integration solution.
Alternatively you may try to use BonCode connector to run ColdFusion with IIS http://boncode.blogspot.com/2012/06/cf- ... -with.html I have not tested this solution but it will not probably have the problems with traditional ColdFusion connectors.

[JohnnyFusion Profile]

That is unfortunate that this won't work.

BTW - there is no \manualInstall folder - the installation just creates \Ape

I cannot change ColdFusion for another product & I have had issues with Railo. I'll continue to look for another fix.

Thanks!

[Yaroslav]

What about using BonCode connector and running ColdFusion with Tomcat? This should work, but I have no time to try it now. If you have test environment I suggest you to try this solution. Helicon Ape should work with BonCode connector. As for ManualInstall folder - are you downloading Ape from our web site? Make sure you are using latest version available.

[JohnnyFusion Profile]

Thanks Yaroslav
I am directly downloading from the Helicontech.com website & after installing the free version, there are no subfolders below /APE - I'm going to try upgrading to CF10 on a staging platform first before venturing into the Tomcat & BonCode world. I can make the argument to update CF from 9 to 10 easier than other methods.

This would have been a great solution & if CF10 exhibits the same 1GB limitation, I'll be back.

[Yaroslav]

My bad! I did not mentioned you are using Free version of Helicon Ape in your first post. Free version does not support manual installation procedure. Please read this article, it has instructions how to install Helicon Ape manually on a single web site http://www.helicontech.com/articles/how ... d-hosting/
If you will need a temporary registration key to complete your trial period I will gladly provide you one.

And the question is why you are using manual install, since I guess this server is under your control. If you don't want to install Helicon Ape for all web sites on a server, there is a checkbox during automatic installation process for it. Uncheck this box and Helicon Ape will not be installed globally. You will then be able to enable Helicon Ape for particular web sites using Ape Manager, without bothering with manual installation.

As for CF issue - the problem is not a ColdFusion itself, but the IIS connector it uses out of the box. This connector has a bug which disables all other IIS modules to process request after CF connector. The problem is not connected with Helicon Ape, other modules will not work either. And you can resolve this issue just by changing IIS to CF connector used. Unfortunately I'm not a big prof. with CF, I think you may find a solution on CF specific resources.

BTW, we are planning to integrate CF with Helicon Zoo to use Zoo as a IIS connector in future. This will help to resolve many problems, including large file downloads and slow POST issues.