Goal:
Run cfquery of remote server on local Coldfusion install.
Problem/Symptoms:
The cfquery parameters are printing onto the screen, instead of running query on remote.Example of cfquery parameter printout on screen
Facts:
Running Mac OS X Mojave (10.14.3).
Coldfusion is installed. I can access the CF Admin panel at http://localhost:8500/CFIDE/administrator/index.cfm
Data Source is installed in Coldfusion Admin and status is "OK"
Using Mamp Pro 5.3. It's running -- can start and stop Apache.
Apache is running on port 80
Updated ODBC Actual SQL Server drivers (Version 4.2.0 from ActualTech). Tested connection to server with driver and it is working.
Remote database is using port 1433
I'm sure there are more questions to answer, but hopefully that's a decent start. What am I doing wrong?
Update: 3/17/2019
Feeling stuck here. I've uninstalled and reinstalled CF2018 and MAMP Pro. I've used the wsconfig applet for Adobe Coldfusion (ACF) as described by Brian Lang and I've also tried the manual approach as described by Adobe.
Update: 4/19/2019
I may have figured this out, now that there is a release of Mac OS 10.14.4. Going to test it on another computer to confirm that the process works and that I have all the steps documented, then will share answers.
The solution to this problem had to do with a conflict with Mac OS X and Coldfusion/Apache. Because Mac OS X 10.14.4 fixed the "mod_jk" file that was conflicting with Apache, Coldfusion 2018 can now run on Mac OS X.
In order to solve the problem, I needed to:
upgrade Mac OS X to 10.14.4
stop all other servers
install Coldfusion 2018
set up Coldfusion Apache Connector
set up local virtual host
I confirmed that it worked on another computer, and have documented detailed instructions in this post: https://www.steckinsights.com/configuring-coldfusion-2018-with-apache-on-mac-os-x-mojave/
Fair warning: I think that the mod_jk issue in Mac OS 10.14.3 and prior was the issue, but there were so many different aspects I tested in the process, that there may be unique issues related to your particular computer's configuration. I hope hope this helps anyone out there having issues.
Related
I would like to deploy a Django application in a production environment (Windows Server 2012 R2).
I am unable to configure modwsgi for a WAMP server.
There are a few posts for this topic, however it seems that all are old and not applicable now. All the posts say that I should have the .so file of modwsgi, but I am unable to find this file.
I have downloaded the source code for modwsgi and also .whl file, but don't know how to configure.
System configuration is as follows:
Operating System: Windows Server 2012 R2 (64 bit)
WAMP Server 2.5
Python 3.4
Django 1.7
Have you looked at the official mod_wsgi download area at all?
https://github.com/GrahamDumpleton/mod_wsgi/releases
All the release notes specifically say to read:
https://github.com/GrahamDumpleton/mod_wsgi/tree/master/win32
I was running a webserver and also Coldfusion just fine until I upgraded to Mountain Lion, then it stopped working. I got it working again by turning everything back on that the upgrade disabled, but now I have upgraded to Mavericks nothing is working. I have followed all the steps in various web articles but it won't work. PHP is enabled, everything that was enabled before is set up, including virtual hosts, and all the folders are in the same place.
I get the error: Firefox can't establish a connection to the server at 127.0.0.1. [or localhost, or any of my virtual hosts]
I've gone over everything time after time and I can't figure out why it won't work. I have started, stopped, restarted the webserver numerous times, it is set to start on bootup too. I couldn't even complete the Coldfusion install because I couldn't load the administrator in a browser.
What could the problem be? Where should I look?
This is not a complete answer, but this should help get things started
Try using the command line start. It will probably be complaining about Java 7 not being installed. I recently needed to install Java 7 JDK (not JRE to get things running)
I know to get the rest of it running, I need to point ColdFusion at the proper JVM. You can find the JVM settings at /Applications/ColdFusion10/cfusion/bin/jvm.xml. You should have some setting like
# VM configuration
#
# Where to find JVM, if {java.home}/jre exists then that JVM is used
# if not then it must be the path to the JRE itself
java.home=/Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home
application.home=/Applications/ColdFusion10/cfusion
When you install Java 7, the JRE is at
/Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home/jre
Backup, and edit the jvm.config file to
#
# VM configuration
#
# Where to find JVM, if {java.home}/jre exists then that JVM is used
# if not then it must be the path to the JRE itself
java.home=/Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home/jre
# java.home=/Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home
application.home=/Applications/ColdFusion10/cfusion
If all goes well, you should be able to start ColdFusion
Some additional help
Installing Java on OS X 10.9 (Mavericks)
When you install Java 7
Just saw this thread. ColdFusion 10 is now supported on OS X 10.9 Maverick with the release of CF10 Update 13.
This should work for you now.
(My Python is installed via Homebrew and correctly refered to by the preferences as my project interpreter)
I have a problem with PyCharms Django Shell. If I start the django shell, it runs the command (ports are changing):
/usr/local/Cellar/python/2.7.3/bin/python2.7 -u /Applications/PyCharm.app/helpers/pydev/pydevconsole.py 52135 52136
Now, this wont work, it justs states "PyDev Console: starting" and after a while, it stops.
BUT when I'm disabling my Wifi, it works! Now, what could this be?
(I'm running the latest Mountain Lion OSX, firewall disabled, PyCharm 2.5.2, Django 1.4)
It looks like the problem is related to Mac OS DNS resolution specifics. While trying to resolve this problem with #ruffy, what fixed it was changing the LAN DNS server to Google (8.8.8.8).
I've logged this issue in PyCharm tracker so that we can provide a workaround for it in the future updates.
Related topics:
Mac OSX Lion DNS lookup order
Mac OS X Lion, /etc/hosts Bugs, and DNS Resolution
I had this problem too, but this was caused because my hostname was 'localhost'.
Once I changed my hostname to something else (from the sharing section in Preferences) - it worked like a (Py)Charm.
The problem was somewhere in pydev-console, and I don't know why my solution worked - I only guessed it was the problem because originally the console worked, and then it didn't and the only thing had changed was my hostname (due to some fiddling at work)
start terminal
nano /Applications/PyCharm.app/helpers/pydev/pydevconsole.py
after line 160 add:
160 def process_exec_queue(interpreter):
+ 161 print 'here'
162 while 1:
163 # etcetera
save and run shell again, does it show the print message? If it does, move it into the while loop and repeat the process until you've narrowed down the problem
Apologies if this has been asked already, searching the web reveals lots and lots of threads about installing the Win8 beta on VMware but not the other way around.
I am trying to install VMware Server 2.0.2 on a Windows 8 Preview machine. It appears to install correctly but I cannot then reach the web based homepage to configure virtual machines, i.e.
https://localhost:8333/ui/
gives the error that the "connection attempt to localhost was rejected. The website may be down or your network may not be properly configured".
Has anyone had any success running VMware Server 2.0.2 on Windows 8 Preview? If so were there any gotchas you needed to avoid?
I don't think it will ever be resolved. VMware Server was declared End Of Availability in January 2010; There will be no support for Windows 8.
Your best try would be trying launching the services in compatibility mode, but why would you do that? Why not use the much more advanced VMware Player or VMware Workstation products?
I've found a way to run it on Windows 8.
On my PC with a x64 version of Windows 8, when I installed VMware Server 2, I found there was a service called VMware Host Agent that cannot be run. When I opened the system Service Manager and clicked to launch this service, it gave me the error.
My solution is to create a service with the same command string and set it to start automatically by using the "sc create" command in cmd.exe. And it worked for me!
I develop web applications using Django on Mac OSX 10.6. I use Django's built in local development server which I run on my computer's IP (such as: http://192.168.0.11:8001/). I test my applications in Firefox, Safari and Chrome and all display fine. I use Sun's VirtualBox with 3 different instances of Windows XP that have IE6, IE7 and IE8 on them.
For whatever reason, these sometimes just don't display the Django sites. They come up with 'The page cannot be displayed'. Eight times out of ten, they display fine and function normally but for no reason at all they won't display. Sometimes restarting Django's local development server from the Terminal will fix the problem, sometimes it won't.
Is there some sort of VirtualBox settings or Django settings that I need to set to ensure smooth operation of this? Am I overlooking something? Has anyone else had these problems?
By default the dev server binds to localhost. to run it on all interfaces use ./manage.py runserver 0.0.0.0:8000
I found the best way to do this is using the normal localhost:8000 or localhost:8001 (any port you need, especially if running multiple Django projects at the same time) in the Mac Terminal.
Then in VirtualBox with Windows, using the ipconfig command in the Command Prompt to find out the IP settings. Grab the Default Gateway (mine was 10.0.2.2 for example) then, in the browser, use this as the address to get to your Django project along with the original port setting that was set in the terminal. So in this case: http://10.0.2.2:8000/
I've been running it like this now for almost a week and it seems to of stopped the problems I was getting before totally. I couldn't really tell you why though!