pf » ColdFusion 5 on Windows .NET Enterprise Server RC1

January 13, 2003

ColdFusion 5 on Windows .NET Enterprise Server RC1

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.

Permalink | Add Comment |

add to del.icio.us

3 people found this page useful, what do you think?

Trackbacks

Trackback Address: 79/ED610E8DFF2D6DD9C55171AD951CA39E

Comments

On 01/27/2004 at 12:14:46 PM MST mike wrote:

i had the same problem today on Windows2003. It is related to the CF monitoring service so I disabled that service and it has been fine. I have not been able to find any information from microsoft or macromedia on why this is happening

PS: make sure to follow these directions when install cf 5 on 2k3 http://www.macromedia.com/support/coldfusion/ts/documents/install_cf_win2003.htm

On 03/11/2004 at 11:48:26 PM MST Ed wrote:

I followed Mike's suggestion, and disabled CF Monitoring Service, which eliminated the error message.

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.

On 08/11/2004 at 10:28:04 PM MDT Patrik Ahlin wrote: