With the new skinning changes in DotNetNuke, it may be helpful to give an overview of available approaches to skin developers.

Each of these approaches attempts to answer the question "How do I embed and customize all that great functionality that DNN provides in my skin?" In other words, given that we have a pre-set base of options for functionality (core skin objects), and each of those options exposes certain customization points (skin object properties) that I'd like to set…how the heck do I get it done?

The answer may depend on which technologies you are familiar with (or willing to learn), but let's examine each of the different approaches and see if one clicks for you.

Note: For the sake of simp ...

If you have recently edited your reporting services web.config and can no longer access your reports you may want to check if your web.config file contains an xmlns attribute on the configuration element. If it does, you will not be able to access your report manager.  Simply removing the attribute will solve this issue.

I ran into this issue today after i edited a property in the web.config using the IIS tool (under asp.net tab). As i had no idea what had originally caused the issue it took a few hours to figure out that it was because i had edited the web.config with IIS.

Here is the error message that the report manager would display:

"The report server is not responding. Verify that the report server is running and can be accessed from this computer."

Here is the error message from the log file:& ...