Installation problems with h5ai webindex - apache

So i've been trying to install h5ai webindex in my webserver, but the thing is, i can't manage to install it correctly, since h5ai folders insists on showing up, when i open any folder created by me that is listed, and then refresh the page the index reverts to the apache default one. If anyone could help me through the installation process i would be very thankfull.
Any help would be appreciated.
Thanks in advance.

Have you modified the default index-file list, as specified on the h5ai website? It seems your problem is related to that as Apache doesn't seem to care about the h5ai index file.
Also, are you sure you rebooted your web-server?

Related

How to uninstall XAMPP when its not in a root directory?

I have accidentally copied my XAMPP files into my Users\ ...\Desktop folder and now cannot uninstall it with the regular installer as it will only work if the files were in the root C:.
Attempting to delete the files with "right click -> delete" don't work either.
I have tried to just have two installations at the same time. One being in the Users\ ...\Desktop and one in C:, but apache still woudln't start.
Here's the error message in the C:\ version
Here's the error message in the Users..\Desktop version
I am more looking for how to uninstall the Users\ ...\Desktop version rather than troubleshoot it but the images might help show the problem.
Cheers!
Figured it out.
I moved the files to a USB stick so they are off my computer (you could probably just delete them normally), then ran cmd as administrator and typed "sc delete "Apache2.4"
and then ran XAMPP and worked a charm

Joomla Mootools file getting truncated

I am trying to run Joomla on my local machine. I have installed wamp 2.0 and everything installed ok with it and I managed to see it running. I have now come to install Joomla 1.5.18 but I am having a problem with the mootools file on the installation wizard.
When running through the installation process in FireFox with firebug turned on I get errors about the mootools file missing a }. When I view the file through windows explorer it is complete and everything is fine with it but when I click on the error in firebug to see the error the file is truncated which I assume is why it is not working and complaining about a missing }. To test the file I created a test page which pulls in the same mootools file and this works fine (running locally and not through Joomla ).
Does anyone know why this is happening and how to fix it? I think it must be a problem with wamp as like I said the file is fine and runs ok if I run it from the file system, however I know nothing about servers so this is a guess. Maybe a limit on the size of a file which can be returned as the mootools file is around 7000 characters long.
I have tried un-installing both Joomla and Wamp but none this has not worked and I still get the same error. Thanks
I'm just curious, have you tried installing a newer version of Joomla? 1.5.8 is a little bit old and you may have better luck using something a version or two newer. Alternately speaking, if you're not a big fan of installing WAMP and then manually installing Joomla, you can use a Bitnami Joomla stack. Basically, Bitnami installs Apache, mySQL, PHP, and Joomla all in one quick and easy install.
I hope that some of this helps!
I would suggest that your problem is not with the Mootools package but with your template or modules that are loaded in. Can you turn off all of your modules and reenable them one by one until you see the error again?

Changing the working directory for a process remotely

I've got an application that has a bug right now, but we're unable to update the end-user to get the fix out. What a possible workaround would be is to change the working directory to the application's install directory, but from what I can tell, there's no way to do that outside of the program itself. Is there some sort of Windows API call that can change other processes' working directories, or is that not available due to security issues? I figure it's not possible.
You can change the directory that it initially starts in with a shortcut. If that is not enough, I don't believe what you want is possible without injecting a custom dll into the process after the fact.
Why do you want to change the working directory? Maybe you could modify the PATH environment variable in some way to change the order of directories your app searches for files.

DotNetNuke Module does not show on page, steps to trouble shoot?

I have a DotNetNuke Module created in DNN 4.9.2. It runs fine on my dev machine but when I post it to the live server, I just get a blank screen, well my skin with no content.
I have installed and then uninstalled, then reinstalled the module, same issue.
I must be overlooking something. Can anyone outline some ideas on how to trouble shoot this issue. I have done the following:
Check code - exact match
Check DNN Event Log - clean
Look for errors - none
Restart Site - same issue
Check Windows Logs - clean
Bang Head against desk - same issue, although now I have a headache
Any other ideas would be great
Make sure that the "Mode" selection at the top of the control panel isn't on Layout.
Are you running as an administrator? Otherwise, do you know that the user has rights to see the module?
The answer was a bug in my code. The reason I didn't see an error was because that an xslt file path was wrong and it didn't kick in my try catch. I corrected the path and violĂ .

ClickOnce Application Not Opening

I have a VB.NET ClickOnce application that I am trying to install on my computer. Previously, I was able to install and run these apps without issue. Now when I install the application, I can see the flash of a window opening, and then nothing. (There are also no processes left hanging or anything when viewed with the task manager.)
After some digging around I noticed that there are files in my Temporary Internet Files with names like "FusionBindError" and then my application name and different DLL names.
I have done everything I can find on the net to do, reinstall applications, reinstalled the .NET Framework, deleted my Local Settings folder and relogged in.
Does anyone out there have any other ideas for me to try?
I tried the Mage.exe suggestion, but it failed to help. Same with the other installation location suggestion. The application flashes at the bottom of the screen but does not open. I have tried using FUSLOGVW to check the bindings and nothing shows up in there. (Good or bad, there are no binding entries.)
Have you tried using mage.exe? This is a command-line tool that comes with .NET framework. Start up a VS command prompt, and try mage -cc. This will clear your applicaiton cache and will force a new click-once download. This is the first thing I do when my click-once applications fail and it works 99% of the time.
A couple of suggestions:
FusLogVW isn't working for you because you have to enable assembly binding failure logging inside the registry. This MSDN article describes how to do this.
Another thing that comes to mind is, perhaps the ClickOnce app install, or perhaps the whole ClickOnce store is corrupted. Try deleting the ClickOnce app store then reinstalling the application.
It's possible that new prerequisites were added that you don't have on hand. If the URL you are using points directly to "my.application" or whatever your equivalent is, prerequisites won't be processed.
So try pointing to the setup.exe that is created in the same directory as the .application file.
Other than that, it sounds like you're doing all the right stuff...
Also, it could be useful to run the fuslogvw utility on a machine where the application actually works. Or reflector.
And then see if indeed any of its dependencies being loaded surprise you.
Also, for these types of errors, be sure to check if disabling the antivirus resident protection helps. Sometimes it causes problems accessing assemblies' manifests and such.
I uninstalled my Kensington Mouse software, and that resolved my installation errors.
Who knew that mouse software that I never used could cause so much trouble??
Sometimes if your machine is working for days this problem will show up. Try to restart your machine. The same problem happened to me and it disappeared when I restarted my machine.