Hi Beth,

You say the skin loads fine with your old Web.config file in place. Can you zip the old Web.config and email it to me? Maybe that will help me spot the difference and figure out which change is the most likely culprit. 

Best,

Joe

Hi Beth,

Did you transfer your Web.config customizations from the old Web.config to the new one?

Maybe the error could be caused by it not having some of those customizations.

I noticed in your old Web.config you have the whole <system.web section wrapped inside a location element like this:

<location allowOverride="true">

</location>

and I also noticed these items which I don't remember every being in our Web.config so I assume it is needed for some reason on your end:

<buildProviders>
<add extension=".htm" type="System.Web.Compilation.PageBuildProvider" />
<add extension=".html" type="System.Web.Compilation.PageBuildProvider" />
</buildProviders>

<add name="PageHandlerFactory-HTML" path="*.html" verb="*" type="System.Web.UI.PageHandlerFactory" resourceType="Unspecified" preCondition="integratedMode" />
<add name="PageHandlerFactory-HTM" path="*.htm" verb="*" type="System.Web.UI.PageHandlerFactory" resourceType="Unspecified" preCondition="integratedMode" requireAccess="None" />

and also a lot of rewrite rules inside:

<rewrite>
<rules>

</rules>
</rewrite>

I would look for those things in your old Web.config and try to copy them into the same locations in the new one and see if that solves it.

The location element and the rewrite rules seem like the most likely to cause errors if missing and needed.

Best,

Joe

Hi Beth,

The only things in your log are typical expected errors when you run against a new db, it throws some database errors until you visit the setup page which creates the database objects.

Can you try removing the entire <staticContent> section from Web.config and see if that makes any difference?

Really images are static files and by default they are served directly by IIS and not handled by any .NET code, so the only things we will see in the log are errors that originate in .NET code.

There are some new things in the staticContent section that are for defining some mime types needed for our new audio and video players, but possibly this is causing some kind of IIS error with other static files.

Best,

Joe

Hi Beth,

The audio and video players may work just fine for you if the mime types are already registered in IIS. I found I needed to add them on my machine using those settings in Web.config. Someone else reported an error caused by the addition of <mimeMap settings but when we added the removes first it solved it for him.

<remove... for each of them first it solved it for him.

So I thought those settings would be fine in all cases because IIS will report an error if those mime types are not registered and you try to uplaod or play a file of that type, but it also gives an error if you try to add mime types that are already registered in IIS, so I thought by putting the <remove.. first and then adding them it would solve it in all cases (and it did fix it in some cases of both situations), but apparently it can still cause problems in some cases, I'm not sure why at this point but it is good to know since it will probably come up again.

Best,

Joe