Ok, I started doing your path....

I installed the CF again with the internal only. Then I modified the XML
file to disable the internal server, as well as modify the cacheRealPath.
Then I rebooted and ran the "remove all connectors" bat. No connectors
installed. Ok fine, so I ran the connector to install the IIS one. I then
got an error regarding the Jrun server was not found - confirm that it is
started. So I assume this is because I disabled the internal webserver... So
- where is it I went wrong? Did you actually disable the internal server
before installing the connector, or did you actually do it after? Or maybe I
disabled the wrong thing in the XML file. Having another look now.

Dustin

On 8/21/02 2:59 AM, "Niklas Richardson" <[EMAIL PROTECTED]> spit this
out onto my computer screen:

> Just found your original post after digging through my emails.
> 
> I had a very similar problem with this and the multiple sites problem.
> 
> I found that if I ran the "Remove_ALL_connectors.bat" in the
> D:\CFusionMX\bin\connectors\ directory, (do a reboot if you fancy it),
> and then run the "IIS_connector.bat" it all seemed to work properly.
> 
> Oh, and this was after changing the XML file to stop the
> RealPathCaching, and turning off the internal webserver.  Remember you
> need to reboot to have these changes take affect.  So probably a safe
> way path to take is:
> 
> (1) Change that XML file
> (2) Reboot
> (3) Remove all connectors
> (4) Reboot (just to be safe)
> (5) Run IIS connector
> (6) Hopefully be home free!!!  Worked for me!!
> 
> Cheers
> 
> Niklas
> 
> UK ColdFusion User Group
> Chairman
> 
> 
>> -----Original Message-----
>> From: Niklas Richardson [mailto:[EMAIL PROTECTED]]
>> Sent: Wednesday, August 21, 2002 10:55 AM
>> To: [EMAIL PROTECTED]
>> Subject: RE: [ cf-dev ] List for server admin? WAS: [ cf-dev ] quiet
>> 
>> 
>> Getting the jist of what Taz has replied it sounds like you're having
>> issues with IIS and CFMX.
>> 
>> It is known that if you install CFMX you should install it under
>> standalone mode as there is a problem with setting up the
>> connector with
>> IIS.
>> 
>> Basically, after installing under standalone mode, to connect
>> to IIS you
>> run the IIS connector batch file which can be found in
>> d:\cfusionmx\bin\connectors.  Then it should all work fine and dandy.
>> 
>> Also, after doing that you can turn off the internal webserver by
>> changing a setting in an XML document.  If you want to do that let me
>> know and i'll get the path for the XML doc.
>> 
>> However, any changes you make to the internal webserver you have to
>> reboot the machine, as recycling the CFMX services doesn't recycle the
>> JRUN service which runs the internal webserver.  A bit of pain really,
>> but easily catches people out!
>> 
>> Hope that helps.
>> 
>> Regards
>> 
>> Niklas
>> 
>> UK ColdFusion User Group
>> Chairman
>> 
>> 
>>> -----Original Message-----
>>> From: Taz [mailto:[EMAIL PROTECTED]]
>>> Sent: Tuesday, August 20, 2002 9:41 PM
>>> To: [EMAIL PROTECTED]
>>> Subject: Re: [ cf-dev ] List for server admin? WAS: [ cf-dev ] quiet
>>> 
>>> 
>>> 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]
>>> 
>>> 
>> 
>> 
>> -- 
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>> For human help, e-mail: [EMAIL PROTECTED]
>> 
>> 
> 



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


Reply via email to