Apache Internal Server Error 500 - You can troubleshoot internal server errors by looking at the Apache error log files. If you followed the install instructions on these KohaOnWindows wiki pages, you'll find the apache log files at C:\Program Files\Apache Group\Apache2\logs. If you got the error while in the OPAC part of Koha, look in the opac-error_log. If you got the error while in the INTRANET part of Koha, look in the intranet-error_log. Open these files in notepad or another text editor and you should find some helpful information about your error. If you have trouble opening the log file because it is locked, make a copy of it first and then open the copy.

Scroll all the way to the end of the file to see the most recent errors. See if you can figure out the error from the information given in the error log. Note that Apache logs even minor errors, so don't be surprised if you find lots of entries. If you need help, post just the last three or four lines of the error log to the koha-win32 mailing list, and we'll see if we can help.

Typing OPAC or INTRANET in the address bar of my browser does not provide access to Koha - instead you get a message The page cannot be displayed. The windows install provides access to the OPAC and Librarian (INTRANET) interfaces by using Apache name-based virtual hosts (see http://httpd.apache.org/docs-2.0/vhosts/ for Apache documentation on this). Two virtual hosts, one named OPAC and one named INTRANET, are configured in the apache httpd.conf configuration file (open this file in notepad and scroll all the way to the end to see this configuration). For name-based virtual hosts to work, windows name-resolution needs to be able to map both of the virtual host names (OPAC and INTRANET) to the IP address of your koha server. To keep things simple, the windows install assumes you are setting up a stand-alone koha test server and uses an IP address of 127.0.0.1 (the local host address).

Since a DNS server may not be available to a stand alone workstation and to keep things simple, the windows install trys to provide name resolution for the OPAC and INTRANET virtual names by adding two lines to the hosts file in your C:\Winnt\system32\drivers\etc directory (for W9x this file is called lmhosts):

      127.0.0.1    opac         #    Koha Library Software OPAC
      127.0.0.1    intranet     #    Koha Library Software INTRANET

If you're not familiar with using a hosts file for name resolution, you can see http://www.labmice.net/networking/lmhosts.htm for more information.

When you type INTRANET on the address bar of your browser, windows should check the hosts file and resolve this to 127.0.0.1, connect to the apache server and then feed the apache server the virtual host name of INTRANET. When you type OPAC as the address it also resolves to 127.0.0.1 except this time it feeds the OPAC name to apache. If no name is given, apache is configured to display the OPAC interface. That's why you can run koha opac by entering 127.0.0.1 or localhost.

Troubleshooting ideas:

1. Were you logged in as a local administrator when you did the install? If not, the install probably could not modify your hosts file. Reinstall koha as a local admin or manually add the above two lines to your hosts file.
2. Check name resolution by opening a DOS command prompt window and typing PING OPAC and then PING INTRANET. Both of these commands should result in replies from 127.0.0.1. If not, something is wrong with your hosts name resolution. See the above link for more help.
3. Check that Enable LMHOSTS lookup is checked under Network Places → Properties → Local Area Connection → Properties → TCP/IP → Properties → Advanced → WINS tab.
4. Make sure your browser isn't going out to the internet to try to resolve the OPAC and INTRANET names. If you use a Proxy Server, you may need to check Bypass proxy server for local addresses under Tools → Internet Options → Connections to stop IE from going out to the Internet to look for Koha.

There also could be that you have higher than the recommended version of the SQL database server. You might want to check that.

Connection error of MySQL4 - if you get the following error:

[Wed Apr 06 00:01:12 2005] [error] [client 127.0.0.1] Premature end of script headers: opac-main.pl
[Wed Apr 06 00:01:13 2005] [error] [client 127.0.0.1] \x07File 'C:\\mysql\\\\share\\charsets\\?.conf' not found (Errcode: 22)
[Wed Apr 06 00:01:13 2005] [error] [client 127.0.0.1] \x07Character set '#33' is not a compiled character set and is not specified in the 'C:\\mysql\\\\share\\charsets\\Index' file
[Wed Apr 06 00:01:13 2005] [error] [client 127.0.0.1] DBI connect('sample191:localhost','koha',…) failed: Client does not support authentication protocol requested by server; consider upgrading MySQL client at c:/usr/koha191/intranet/modules/C4/Context.pm line 369

May be you need to consider rollback to 3.23, the above problem is not easy to solve. I've try difference mysql driver (DBD-mysql and DBD-mysqlpp) and difference mysql config, all not working

What is the first time username and password? - see http://lists.katipo.co.nz/public/koha/2003/002079.html

Windows 2003 Server special note - Windows 2003 Server does not automatically reload to the interface, and hangs at the “Welcome to Koha Version 2.xxx” page

Back to « KohaOnWindows