jhankdc wrote on Saturday, February 27, 2010:
I made three attempts to install. Each time I was advised "Check that mysqld is running.
ERROR: Could not connect to server!"
I did remove the XAMPP folder each time before trying to reinstall. I have no experience with code so please take that into consideration in trying to help. Thanks!
physmed wrote on Sunday, February 28, 2010:
jhankdc
First question is which version of Windows are you running?
Rick
jhankdc wrote on Sunday, February 28, 2010:
Sorry, should have mentioned that. I’m running XP Pro, Version 2002, Service pack 3.
physmed wrote on Sunday, February 28, 2010:
OK then the next questions are: have you disabled Microsoft’s iis service and did you use the bundled uninstaller each time you uninstalled the package?
Rick
jhankdc wrote on Sunday, February 28, 2010:
OK, I think that we are nearing the extent of my knowledge. I have not disabled Microsoft’s iis service (I don’t know what that is). I honestly can’t remember if I used the bundled uninstaller. I may have uninstalled it using the windows control panel. I do know that I had to go back and delete the XAMPP folder from within windows.
aperezcrespo wrote on Monday, March 01, 2010:
Hi
Go into control panel->Add/Remove Programs->Add/Remove Windows Components. Here you will find IIS. Just clear the check box and then Next.
This will remove IIS.
Then try and reinstalling OEMR with the XAMPP Setup package.
Thanks
physmed wrote on Monday, March 01, 2010:
Then what I need to know next is if openemr server is completely uninstalled from your computer? That is if you go to the start button and click on it and then click on all programs do you see a listing for openemr server? If it is still there open it and look for the uninstaller and run it. Then check to see if the xampp folder is still on the drive and if it is to send it to the trash and empty the trash. Then I would suggest re-downloading the package from Chris Lucerna’s site and trying to do a clean install again. If all goes as planned you will see a new icon on your desktop labeled Openemr server which if double clicked will bring up your browser and the log in page for OpenEMR!
Rick
anonymous wrote on Monday, March 01, 2010:
Hi, I actually developed the windows installer package and I have seen this several times before. The best way to fix it without getting to technical and dissecting your other apps on the server is to change the port in which Apache listens on. To do this edit the following file: C:\xampp\apache\conf\httpd.conf
Edit the following line: Listen 80
Change to: Listen 8080
Then restart the apache server (if you don’t know how then restart the computer). Try to access via firefox: http://localhost:8080/openemr and if it works great! If not then also edit the following file: C:\xampp\apache\conf\extra\httpd-ssl.conf
Edit the following line: Listen 443
Change to: Listen 8443
Then restart the apache server (if you don’t know how then restart the computer). Try to access via firefox: http://localhost:8080/openemr and that should do it. If you need SSL access then you need to goto: http://localhost:8443/openemr
If you require further assistance you can contract us or another professional openemr service provider to login and fix the issue remotely; especially if you need the installation to work on port 80 or 443 instead of 8080 and 8443.
Regards,
EHR Live
www.ehrlive.com
jhankdc wrote on Monday, March 01, 2010:
Thanks folks. IIS was not installed, XAMPP had been completely removed, and I changed to Listen 8080 and and Listen 8443. Thus far my results have remained the same.
My nephew, who is into IT, put Team Viewer on my machine when he had to change power supplies and install a new hard drive. I’m going to check with him today and see if he can help me too.
Chris, one thing that I did notice is that C:\xampp\apache\conf\httpd.conf contains Listen: 80 on two lines and several other instances where 80 exists. Should I change all the 80 references to 8080?
I’ll also give
a try. I think that’s what I originally downloaded and have been attempting to install.
I appreciate your help and will try to work more on getting the package installed later today. Again, thanks! I appreciate all your help.
Jim
jhankdc wrote on Monday, March 01, 2010:
I tried loading the package on my Dell laptop in the office this morning and it set up perfectly. The only glitch that I encountered was an Adobe message that PDF’s could not be viewed due to a browser problem. It asked if I wanted it to fix and I said yes. Seems to have worked and the program appears to be properly installed.
The only real difference between the two computers is that I have Adobe Acrobat installed here and an open source PDF viewer at home.
Do you think that could be causing the problems on my home system?
bradymiller wrote on Wednesday, March 03, 2010:
PDF viewer is not issue. On your computer not working, what do you see if you open the xampp control panel:
C:/xampp/xampp-control (double click this file in your file browser)
-brady
jhankdc wrote on Wednesday, March 03, 2010:
Whatever the problem was, it is now resolved. Last night I decided to attempt to install PatientOS and got partially through it before I encountered some problems and quit. Today I worked on OpenEMR in the office and I just decided to try once more to install it here at home. It installed perfectly.
Whatever the problem was, it appears to be resolved. Thanks to all for trying to help me out.
taariqq wrote on Tuesday, March 09, 2010:
I just discovered when I was trying to install openemr on my machine, that Apache and Team Viewer both listen to the same port. Team Viewer starts first and will not let Apache listen to port 80, and you get the message “This site is running Team Viewer”. A simpler solution that I used was to change the port that Team Viewer listens to, instead of changing the port for Apache and having to type that in into the address bar. Following instructions are from http://tech.nabtron.com/run-teamviewer-with-localhost-webserver-xampp-wamp-etc/310/
The steps to make teamviewer working with any other software that listens to port 80 too is to edit the registry of your windows, to change the values in it , making teamviewer NOT listening and engaging / using the http / 80 port. To get this done, follow this:
1. opening the alternate port
if you are using a firewall, make sure that port 5938 (TCP) is open on your firewall.
2. editing the registry
you need to check the registry.
Goto start -> run -> regedit
Goto location:
select the Key ’GatewayAllowed’ and set its registry value to 0
Now goto the registry location:
and there select the Key ’ListenHttp’ and change its value to 0 too.
Close teamviewer and server and / or restart your computer. Check if its working fine now.
lsalichs wrote on Friday, March 12, 2010:
I am generating claims, but the log is reporting an error related to the rendering provider name. The clearinghouse is reporting the same error: Rendering provider has no NPI.
Is this a bug in the application? I have configured the facilities and providers with their names, NPI’s and everything there is to configure.