Dustin,

Sorry, I completely missed that one.

Okay, its taken me a while to read through the thread of it, and I've had to
go back over it a couple of times... was suitably impressed with

"THE END

NOVEL WRITTEN BY: Dustin"

Anyway, I'm not an expert but I'm assuming that MX embeds the dll mappings
into IIS the same way as previous versions did... basically maping the file
extensions '.cfm' etc. to CF's dlls.
Looking at that macromedia documentation, its all command prompt work that
basically does what you can do through IIS. If you open IIS and select the
server, then open the properties window so that you can check the
application mappings

um... Master Properties (edit): Home Directory tab: Configuration...

Here you can set the dll mappings without having to go through all that
command line shit, which means you can browse for the specific dll file...
so that can't get knacked!

Setting this in the server properties should mean that it's set for all
sites... you might want to check the site folders when you test though.

Another thing to check is Services... just to make sure that all of the CF
server services are runnning. Obviously IIS is running okay, but perhaps one
of the CF services is stopping...? (clutching at straws? You're damn right!)

If none of the above works... and nobody else on this list has contradicted
what I've said here (I refer back the the point that I've not installed MX..
I'm still running on 4.5 and 5), then I would suggest that you remove CF,
clean out all of its settings from the registry, uninstall IIS, and then
start from scratch.

Failing that... buy a shotgun and take it out on the server.

Taz

> Ah I asked a big one a few days ago, and there was no response.. so I
> figured no one knew the answer on this list. I have been having major
issues
> with an install on IIS5 (W2K). I can repost if need be. I believe the
> original email was entitled "errors errors errors".


-- 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
For human help, e-mail: [EMAIL PROTECTED]


Reply via email to