Hi guys, I had managed to install Gooseberry++ on my XP machine with Xampp 1.6.0a. I also run Clearspace and Drupal on the same setup. However inspite of following PeteE instructions exactly I am struggling to get Hayes going.

I normally don't post unless I am absolutely sure I am doing everything right but after 4 days of double checking and active research on the forums and Google I have given up.

My httpd.conf is nearly identical to PeteE's, I have net 2.0 installed, and also installed mono in the process of trying to make this work. Hayes installs perfectly with no errors, however when I try to access http://deki-hayes I get the opening page but with the following error:

"Your site settings could not be loaded - this could affect your wiki's operations. Please check to ensure that Dekihost is running.
This page's contents could not be loaded"

On top of the page I can see a 400 error, System error, the details say

"Request URI: http://deki-hayes/@api/deki/pages/29...igin=127.0.0.1
Server response
<h1>Bad Request (Invalid Header Name)</h1>

Hoping somebody more informed than me can help me here. Thanks.

This was the problem I ran into. Do you have mono.posix.dll in the web/bin directory? If not copy it from src/redist and restart Deki.

This is an important issue. I would really like to see us running on Xampp. Did you guys resolve this? If so, can one of you doc it?

Thanks for the effort and enthusiasm gang.

Hey Greg, yes, I copied the Mono.Posix.dll from the src/redist folder and put it in web/bin right from the start, I have been following the instructions from PeteE exactly and had come across the mono.posix dll issue reading up on this forum.

When I got the error initially with net 2.0 already installed, I downloaded and installed mono but still get the same error. Then I thought it might be a apache mod proxy error, did some research on that but not made much headway.

When I type http://localhost:8081/host/test I get the xml file, when I try http://localhost/@api/host/test I get a bad request error. I would love to figure this out, is it a problem with dekihost and net or mono or is it a problem with mod proxy and apache, I don't know.

Hey Aaron, will definitely doc it once I manage to resolve this.

Hi guys. I wrote a tutorial on how to get Hayes working on Xampp.

http://forums.opengarden.org/showthr...=2098#post2098

Hey Abarras, thanks for the guide, unfortunately even that doesn't help my case, the only thing I hadn't done that was in your guide was copying the curl dll's to my system32 folder. For a moment I had hope that that could be this issue however I get the same 400 error described above.

This is very frustrating and seems to something unique to my system since all of you guys are getting it working on your XP machines quite easily. I even wiped my xampp installation and started afresh but to no avail. But since you have got it working on xampp, one can rule out apache mod proxy issues which I had suspected. Could this be a net/mono issue on my system, how many other variables can there be?

Are you able to get the default Xampp install working? In other words before you install hayes and mess with the config files, can you access the Xampp pages? That might tell me something.

Oh and you do have the mindtouch.host.bat running right? I mean the window stays open and it gives you a time it took to load?

If http://{hostname}/@api/host/test doesn't work, then the PHP code won't be able to access the dekihost API and it's downhilll from there. So, this is where I'd be focusing my attention on. At first blush, I would expect the proxy to be the guilty party since http://{hostname}:8081/host/test is working.

Did you check that mod_proxy is not commented out at the beginning of the httpd.conf file?

Hi Abarras, yes I had the default Xampp install working, I was running Drupal and Clearspace on tomcat on it. Even Gooseberry+ was working near perfectly.

However I have good news. I just managed to get this running. Finally. I made 2 changes and I don't know which one was affecting the installation and causing the error.

1. .Net Runtime Optimization Service was set to manual in my XP services config, I started the service.

2. I disabled IMON module in Nod32 Antivirus

Curiously one would think its the .Net runtime issue, but it isn't. This seems to be directly related to be turning IMON in NOD32 on and off. With IMON on I get the error described above, turn it off and Hayes works perfectly. How strange, surely there must be an explanation for this, why should my anti virus mess with this?

Thanks a ton for all your help. Appreciated.

Glad to hear you got it working! Perhaps your antivirus was preventing that port from being used? Who knows.