I don't know why, but this only worked ONCE after the reboot and I can't get it to work anymore.
I've even updated my version of the dot net framework on the server.. I was using .NET 2 and now I'm using .NET 4 ... I've rebooted, re-installed the dot net service over and over again, deleted cached files... etc... argh! On Sun, Dec 5, 2010 at 8:31 AM, Rick Root <rick.r...@gmail.com> wrote: > A reboot resolved this problem for me as well.... > > > On Sat, Dec 4, 2010 at 10:58 PM, Rick Root <rick.r...@gmail.com> wrote: > >> On Wed, Dec 1, 2010 at 11:24 AM, Stefan Richter >> <ste...@flashcomguru.com>wrote: >> >>> >>> Errrr so I tried rebooting the server... now getting a blank page which >>> is much, much better. >>> >>> Will keep you posted but it seems ok now. >>> >>> >> So by "blank page" you mean you're successfully claling .NET dll's now? >> >> I'm having the exact same issue... we only use one .NET call, to create >> virtual directories in IIS automatically... but it quit working... Pete >> Freitag's blog entry helped me figure out that I needed to copy the >> neo-dotnetproxy.config file to each instance, which got me to the error you >> were seeing. >> >> I got a little more error information from the error.log in >> C:\Coldfusion9DotNetService (but it really isn't helpful to me) >> >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:339819 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
