I didn't see a solution in the list archives for this issue, but I ran into the same problem today with apache 2.0.50. For me the solution was to create /usr/local/apache/etc/srm.conf and /usr/local/apache/etc/access.conf, both just empty files. Fp.exe gets upset if those files don't exist. I don't know why it picks those particular files to look for. They bear no relation to my setup whatsoever, so it must be hardcoded somewhere -- maybe I wasn't reading the install script prompts closely enough :)  Though I imagine that error is pretty generic, so this solution might only affect a small subset of the ones out there.
 
But as soon as I created them, that error stopped popping up. Hope this is of use to someone!
_______________________________________________
Apache-FP mailing list
[EMAIL PROTECTED]
http://lists.joshie.com/mailman/listinfo/apache-fp

Donations:
http://www.amazon.com/paypage/PT5LZITM9L227 

Reply via email to