I can't belive that this problem I will wrote is not first hit in Google or pinned thread in DNN forums :-)

I am using DNN for couple of years and I am also developer. When I used it on Win2003 server everything worked, regarding on any version of DNN. But now I've moved to Win2008R2 64bit. I thought it would be great, but I found a lot of problems:

1. probing path in web.config is not working. If I do not move all DLL's from bin/providers to bin/, I get error that it doesn't find libraries. Although that probing path is pointing to bin/providers. I googled but with no luck, even if tried to find solution on not DNN problems.

2. Also binding redirect in web.config is not working, so I cannot use dll redirect if some module use different dll of Telerik.

It looks like ASP.NET engine doesnt read this section in web.config.

Please tell if some is using Windows 2008R2 standard od web edition without problems I mentiod?

Best regards, Gregor

Hi Gregor,

I've been pretty successful with running both DNN 5 & 6 versions on a Windows 2008 R2 Standard machine for quite some time now. It's possible that you could have some incorrect settings or a misconfiguration somewhere with your probing path and binding redirect.

---

Ricardo Serenil
Ricardo.serenil@PowerDNN.com
+001-877-743-8366

PowerDNN.com - World Leader in DotNetNuke Hosting and DNN Hosting
DNN Hosting Australia - DNN Hosting UK - DNN Hosting US

Thank you very much for your proposal. I have already tried everything and nothing solved my issue. Then I found out. I guess this is bug in .NET framework or is this know issue.

I tried to install all my DNN installation in folder that has hash in it, for example C:\#WWW. It looks that # is reserved character and in background compiling framework cannot access files if # is in path. When I installed in C:\WWW everything started to work as exprected.

So I post this if maybe someone else will have same issue.

Once again thank you for your help.

Best regards, Gregor