Pete FreitagColdFusion 5 on Windows .NET Enterprise Server RC1
Published on January 13, 2003
By Pete Freitag
By Pete Freitag
I tried installing CF5 a the release candidate of Microsoft's next server platform .NET Server, the results - negative.
Ofcourse my first hint should have been when I first ran setup.exe it told me I was attempting to install ColdFusion on an unrecognized version of windows. I clicked continue anyways, and the install seamed to go smooth. I had to pick "Other Web Server" because IIS 6 wasn't detected (I planned to use apache). After rebooting I received numerous popup windows with the message:
Event Type: Information Event Source: Application Popup Event Category: None Event ID: 26 Date: 1/13/2003 Time: 1:02:12 PM User: N/A Computer: DEVELOPER Description: Application popup: wsm.exe - Unable To Locate Component : This application has failed to start because WINSTRM.dll was not found. Re-installing the application may fix this problem. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.After stopping ColdFusion services the popups stopped. I will work on this some more, but if you have gotten ColdFusion 5 to work on .NET server let me know. I also plan to try installing CFMX on it. I'll post the results when I do.
ColdFusion 5 on Windows .NET Enterprise Server RC1 was first published on January 13, 2003.
The Fixinator Code Security Scanner for ColdFusion & CFML is an easy to use security tool that every CF developer can use. It can also easily integrate into CI for automatic scanning on every commit.
Try Fixinator
CFBreak
The weekly newsletter for the CFML Community
Comments
Yo! You really should go to MX anyway. It is much faster and reliable.
by Patrik Ahlin on 08/11/2004 at 10:28:04 PM UTC
I know this is an old thread but maybe this will help any other weirdos who still need to install CF5 on Win2003/IIS6. :-) You need to add NETWORK SERVICES to the permissions list with read & execute permissions to the file c:\cfusion\bin\iscf.dll. It took me hours to figure that out!
by Gary F on 06/11/2010 at 5:22:44 PM UTC
I looked into the problem, and found
that the winstrm.dll file is missing from the C:\WINDOWS\system32 directory. I placed a copy of winstrm.dll (from my NT 4.0 server) in this directory, and restarted CF Monitoring Service. No error message, and the application appears to be working fine - thus far.