I'm trying to learn MySQL for a database course in which we use MAMP to set up the server. Everything was fine at first, but a few days ago I couldn't connect to MySQL with MAMP. In trying to solve this I removed both MAMP and MAMP PRO from my PC completely (instead of using the provided uninstaller). As a result I cannot reinstall MAMP as the installer still detects that I installed MAMP earlier and tries to uninstall it. In trying to fix my mistake I found that I still have references (I think they are .exe files) to MAMP and MAMP PRO in the windows apps section (. However when I try to remove them I get an error bar saying:
-) C:/MAMP/unins000.exe
and
-) cannot find file C:/MAMP/unins000.exe.
So I cannot remove said files, meaning that I cannot reinstall MAMP
I tried the MicrosoftProgram_Install_and_Uninstall and ccleaner first to install MAMP, however this resulted in the same error.
I also found some threads that show how to restore a file's directory through the command line, yet the problem with this is that I cannot find the directory of the remaining MAMP files.
As I'm not really into this field I have no idea of where to look to solve this. I'm however intrigued by this problem I would like to understand how this is possible and how to solve this.
In the end I would like to remove those MAMP references so I can reinstall MAMP.
Or (only if I really can't fix this) someone knows a similar program that works as well or better.
Related
I hope this is the right place to ask. I was thinking serverfault might not be correct, since the computer in question is not a server. Feel free to migrate if StackOverflow is not right.
I usually install IIS on servers but have installed it on Workstations before. I actually had the same problem with another machine of the same model a few weeks ago but can't remember how I resolved it. I must have installed additional features or run some powershell-command that did not resolve the issue on this machine.
I installed IIS the correct way using the Windows Features, as described in the answers to this question. I've actually removed and reinstalled it since then, but it hasn't resolved my problem.
The WWW publishing service is running and I can open the IIS Manager, but it's completely empty, unlike here where the IIS Manager at least shows the local computer
When I type localhost into a browser I don't see the IIS Startpage, I get the error ERR_CONNECTION_REFUSED
You can see that all the required checkboxes are checked:
And the service seems to be running.
I've since tried installing IIS using
DISM:
Powershell:
And I checked the status using the iisreset command which was mentioned in the comments here (second linked question upstairs):
It restarts without any error and says everything is working fine.
Has anyone ever encountered this before or might know what I could try to get IIS actually working?
Edit:
I just noticed, while trying to uninstall IIS, that I can not uninstall it. I used Windows-Features and confirmed to reboot when prompted, but while rebooting Windows does a rollback and IIS is still available. So I can't even uninstall it.
Also just found this similar quesion on SuperUser. I'm still trying some suggestions there. So far to no avail.
Thanks for the comments.
I was on vacation, but a colleague was able to fix the problem.
Unfortunately, the solution was to reset Windows 11. He was then able to install IIS through Windows Features and it worked.
No idea why it didn't work in the first place, or why it got to this unrecoverable state. But now everything is fine.
I've been here before and even wrote an article on how I was able to connect Coldfusion 2018 with Mac OS X Mojave, but since the upgrade to Mac OS X 10.15 Catalina, I haven't been able to get Coldfusion to work correctly on virtual hosts (ie. http://local.mylocalsite.com).
Goal: install Apache connector for Coldfusion so that I can run my dev site from within the /Sites folder like I would any other site.
Problem: Apache is working and I can access websites from the /Sites folder using the virtual host (ie. local.mydevsite.com), but although Coldfusion is running (I can access the Coldfusion Administrator), my computer does not seem to recognize that Coldfusion is supposed to run. I don't know if this is Apache or Coldfusion's responsibility.
What I've tried: I've tried using the GUI connector, as well as trying to confirm the settings via command line. I have XAMPP installed, which I believe that DesktopServer (an application by ServerPress) is relying on, but that's probably not relevant; but what I'm getting at is that I believe XAMPP relies on Mac's default installation of Apache.
I've also tried to go into every file that is referenced in any instruction document to determine if there is anything out of place. Part of my confusion is that there are many instances of some of these files and I'm not sure which one is active. Here are some of the files I've looked into:
/Applications/XAMPP/xamppfiles/etc/extra/httpd-vhosts.conf
/Applications/XAMPP/xamppfiles/apache2/conf/httpd.conf
/Applications/XAMPP/xamppfiles/apache2/conf/mod_jk.so
/private/etc/apache2/httpd.conf
/private/etc/apache2/mod_jk.conf
/private/etc/apache2/extra/httpd-vhosts.conf
From what I can tell, the main settings for Apache are stored in the /private/etc/apache2 folder, but I want the XAMPP version of https-vhosts.conf because that's where DesktopServer is pulling their virtual hosts from. Regardless, I don't think it matters which vhosts file is being used because Coldfusion won't run on any of the local sites from my /Sites folder that are loading correctly when I visit local.anylocaldevsite.com.
Thoughts? This is either a really dumb question because no one else is asking it, or there aren't many Mac users who also use Coldfusion. Would love assistance if anyone has a clue. Thanks!
Update: This isn't an exact answer, but the recommendation to try CommandBox was a win. I installed CommandBox and then ran the "ColdBox" application in the root of my project and the site opened up in my browser like a gem. Wonderful. Thank you! I can call that the "answer" if no one objects, but I know that it's more of a workaround than an exact fix.
I've got a strange problem. My xampp seems to run just fine, at least the control panel says so. A couple of months back I was able to use xampp properly as well. But now, if I try to load anything in htdocs the browser tells me that the website is not available.
The only things that have changed since I used xampp successfully:
I've briefly installed wampp, but decided to deinstall it again. As far as I can tell, I have removed snd deinstalled everything succesfully.
And, I'm using an other internet connection. Is there a possibility that the firewall of the modem messes xampp up?
Any ideas are greatly appreciated.
PS: I did not post the config files of xampp, because I haven't changed them since everything worked properly, so I hardly think that it is relevant.
Considering your problem and the information I have gathered from you.
The best solution is:
Make a backup of all your files in htdocs.Uninstall Xampp completely.Download and install once again.
Note:
Latest Xampp versions comes with MariaDB unlike mysql.Now some versions of MariaDB is unstable.This would create problems when you are actually working with database and sql queries.
Either download and install Xampp which comes with Mysql or find a version of xampp which comes with a stable version of MariaDB and the latest PhpMyAdmin version.
Reinstalling solves issues like this most of the time.There may have been some kind of server conflict when you installed WAMP.So an all new installation is best.
You could also try clearing the browser history and cookie as an alternative.
I am trying to install drupal 7.24 using MAMP on OS X Mavericks.
I have installed drupal using MAMP hundreds of times before.
I am able to unpack the drupal core files into /Applications/MAMP/htdocs/drupal.
I am able to pull up the install.php at localhost:8888/drupal/.
I create my database using the phpmyadmin with MAMP.
I go to install drupal, enter in my databse information with user:root and pass:root.
Here is where my issue comes in. The tables are created fine in the database, however, the install script loops back to the first step. I continue through again and it asks me to enter database information again. At which point, I do, and the same issue occurs. Randomly it will let me through to set up my site with a drupal error of "No active batch."
I have tested an install of drupal 7.24 on another server with no issues. The only thing different is that I have upgraded to OSX Mavericks. I have tried installing drupal using MAMP now on two different Macbook Pros running Mavericks and have had the same exact issue.
I have google'd this issue but can't seem to find similar issues. I will keep looking. If you have any ideas as to what would be causing the drupal install to fail, it would be much appreciated. Until then, I will use Acquia.
Thanks!
I had the same exact issue yesterday and couldn't figure this out for hours. Today I was able to successfully get past the loop back problem you describe above. I cannot say exactly what the root cause of this issue is but it seems to be a display/timing issue.
Once you enter in the database creds and click submit, the loop back to step one occurs. DO NOT re-enter the database creds here. At this point you can do one of the following:
Wait for about 20 seconds and hit 'control' + 'R'
Continuously hit 'control' + 'R' (refresh) until the page moves forward to the installation loader.
You will see the modules being installed. Then it will show you completed. Let me know if this works for you.
The instructions above worked for me. I waited for about 1 minute after I got stuck and pressed CMD + R to refresh the page. The module installation process begun (saw the progress bar) and Drupal was successfully installed.
Have been running Python 2.7.2 for several months, was using the 32-bit version on my 64-bit computer.
Today ran the installer for 2.7.3, 64-bit. Now I cannot get idle to start. I see answers here for Python in program files, I am running Win7, and I believe the correct location for this machine is in C:\, not in program files. At least that is where I had 2.7.2 and it worked.
So trying
C:\Python27\Lib\idlelib\idle.py
or
C:\Python27\Lib\idlelib\idle.pyw
neither of those would open Idle. With the .py one a console window flashes open for a split second and disappears. On the .pyw one, nothing at all happens as far as I can see. And the pyw one says right on the screen in File Type: "no console"
The old shortcut in the Start menu, under properties says 'target: python 2.7.2', but I don't see a way to change the target.
Also tried opening from Powershell, command line, Python command line, run. None of those worked.
When I downloaded 2.7.3, it said it was overwriting the files in Python27.
Now uninstall offers two programs to uninstall: 2.7.3 and 2.7.2 , but as far as I can tell there is a single Python program on disk and that one thinks it is 2.7.3. I started to uninstall and try a fresh install, but thought I'd ask first rather than risk further screwing up my machine. Thanks in advance for any help. I did read and try to use all the answers in similar questions here on the site.
I ran in to this today. Basically there was already an older version installed and installing over it (I think it was 2.7.2) with 2.7.3 64 bit broke it bad.
At first the CLI python would work but IDLE refused to launch without even an error. Uninstalling/reinstalling did nothing several times, and the problems got weirder as it couldn't find the msi's it had just downloaded, etc. Then I noticed that it wasn't deleting everything in the Python27 folder.
Manually deleting the folder wasn't enough and I found that it was storing another folder under App Data\Roaming (Windows 7). Removing this one finally allowed the re-installation to work (and show up as a newly installed program instead of acting like it had always been there by not highlighting it).
I was about to give up on the 64 bit version and try the 32 but it seems like the Python uninstaller/installer aren't cleaning everything up properly file wise (if it were registry entries I'd still be digging).