Hi all,
After a lot of coffee, angry users, and frustration at finding the dialogs for the Q1 2009 SP2 working great on my development machine, but not on IIS 7, I finally found the solution to the problem. Now, if you search these forums, you will find other possible problems that might be applicable to you. For example, you might need to change the dialoghandler.aspx references under system.webServer in your web.config to dialoghandler.axd. That seems to have helped some.
In my case, however, none of the solutions I tried on the forums made a dent. It wasn't until I tried loading the dialogs from the editor while logged in to the web server, where I have failed request tracing enabled (which only displays detailed information if you're accessing your site locally).
Turns out, if you have request filtering enabled, and you have a maximum querystring length set to, say, the neighborhood of 500, the web server will truncate that gigantic querystring that the dialogs are passed by the editor (and, I'm assuming, other controls).
To see if this is what you are running into, and to resolve it if it is, do the following:
1. Open notepad as an administrator.
2. Open applicationHost.config in c:\windows\system32\inetsrv\config
3. Do a search for maxUrl and maxQueryString. They'll be under the requestFiltering section of the file, in the requestLimits node.
For me, setting the maxQueryString to 1000 did the trick. maxUrl will need to be at least that, since it'll include host and path information, as well.
For me, the worst part was that ASP.Net wasn't ever getting the error since the request was being trapped by a native module higher up the food chain, and as far as I knew, it was a simple 404. Turns out it was a 404.something else, a .13 I think.
Anyway, I hope this helps someone butting heads with the problem. Yesterday was pretty stressful for me. GP's a high-load site with a lot of members that expect I won't break stuff with every push! =)
After a lot of coffee, angry users, and frustration at finding the dialogs for the Q1 2009 SP2 working great on my development machine, but not on IIS 7, I finally found the solution to the problem. Now, if you search these forums, you will find other possible problems that might be applicable to you. For example, you might need to change the dialoghandler.aspx references under system.webServer in your web.config to dialoghandler.axd. That seems to have helped some.
In my case, however, none of the solutions I tried on the forums made a dent. It wasn't until I tried loading the dialogs from the editor while logged in to the web server, where I have failed request tracing enabled (which only displays detailed information if you're accessing your site locally).
Turns out, if you have request filtering enabled, and you have a maximum querystring length set to, say, the neighborhood of 500, the web server will truncate that gigantic querystring that the dialogs are passed by the editor (and, I'm assuming, other controls).
To see if this is what you are running into, and to resolve it if it is, do the following:
1. Open notepad as an administrator.
2. Open applicationHost.config in c:\windows\system32\inetsrv\config
3. Do a search for maxUrl and maxQueryString. They'll be under the requestFiltering section of the file, in the requestLimits node.
For me, setting the maxQueryString to 1000 did the trick. maxUrl will need to be at least that, since it'll include host and path information, as well.
For me, the worst part was that ASP.Net wasn't ever getting the error since the request was being trapped by a native module higher up the food chain, and as far as I knew, it was a simple 404. Turns out it was a 404.something else, a .13 I think.
Anyway, I hope this helps someone butting heads with the problem. Yesterday was pretty stressful for me. GP's a high-load site with a lot of members that expect I won't break stuff with every push! =)