> I just installed CF7 on our dev box, I let choose the > option to coexist with > the cf6 instance already on the server, so it was setup > using the inbuilt > webserver.
> I then disconnected CF6 from IIS and connected CF7 to IIS. > All sites have > index.cfm as the default document but for some reason its > not being picked > up as i get directory browsing error message when i try > and access a site... > any ideas? Wouldn't that mean your CF7 instance is still set up to use the built-in webserver rather than to use IIS? ... Generally speaking, if the plan is to connect CF7 to IIS, I would say don't use the coexist option in the installation -- tell it to install into IIS and select which IIS websites you want to install into (instead of all websites) if you want to maintain some CF6 websites. I use separate websites in my development environment to maintain & test multiple versions of CF Server, so I never use the coexist option during installation. s. isaac dealey 954.522.6080 new epoch : isn't it time for a change? add features without fixtures with the onTap open source framework http://www.fusiontap.com http://www.sys-con.com/author/?id=4806 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Discover CFTicket - The leading ColdFusion Help Desk and Trouble Ticket application http://www.houseoffusion.com/banners/view.cfm?bannerid=48 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:203626 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
