upgrade from 10 to 20 failedsite now hosed! - Questions/Suggestions

Go to solution

Press Ctrl / CMD + C to copy this to your clipboard.

Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at

Chad Rosenthal 272 posts 474 karma points

Dec 14, 2010 @ 00:18

Upgrade from 1.0 to 2.0 failed....site now hosed!

Hi. I'm running the site on a Winders Server 2003 machine. I'm using 4.5.2 and had version 1.0 installed on my site.

I just did an install of the uComponents straight from the package installer, and now my site is basically hosed. Every time I try to view any of the datatypes (including non-uComponents data types), content, xslt's, Macro's, etc I get the following error:

'/WebResource.axd?d=LO6dW4mSA4hDnGTa6ivxSyOZQ0_htV_bPheFAWNCeMhB3L_KMHF6EKHvRgjBGVmmQDiNYeB1RIxSQ3w9Uw50ITwj9bCrfqN51Bu7qjBOoZRJFgC87rFYwIHQOtjyXuNTW067zGyUTRXOYLgVL7oawTIGl4WSU7pR7u_jCBz6XvNgBQwS0&t=634278603827579804' is not a valid virtual path.

[HttpException (0x80004005): '/WebResource.axd?d=LO6dW4mSA4hDnGTa6ivxSyOZQ0_htV_bPheFAWNCeMhB3L_KMHF6EKHvRgjBGVmmQDiNYeB1RIxSQ3w9Uw50ITwj9bCrfqN51Bu7qjBOoZRJFgC87rFYwIHQOtjyXuNTW067zGyUTRXOYLgVL7oawTIGl4WSU7pR7u_jCBz6XvNgBQwS0&t=634278603827579804' is not a valid virtual path.]
   System.Web.VirtualPath.Create(String virtualPath, VirtualPathOptions options) +8859051
   System.Web.VirtualPathUtility.IsAbsolute(String virtualPath) +13
   ClientDependency.Core.IClientDependencyFileExtensions.ResolveFilePath(IClientDependencyFile file) +131
   ClientDependency.Core.FileRegistration.Providers.BaseFileRegistrationProvider.UpdateFilePaths(IEnumerable`1 dependencies, HashSet`1 folderPaths) +487
   ClientDependency.Core.FileRegistration.Providers.WebFormsFileRegistrationProvider.RegisterDependencies(Control dependantControl, List`1 allDependencies, HashSet`1 paths) +30
   ClientDependency.Core.Controls.ClientDependencyLoader.<RenderDependencies>b__0(ProviderDependencyList x) +68
   System.Collections.Generic.List`1.ForEach(Action`1 action) +56
   ClientDependency.Core.Controls.ClientDependencyLoader.RenderDependencies() +51
   ClientDependency.Core.Controls.ClientDependencyLoader.OnPreRender(EventArgs e) +109
   System.Web.UI.Control.PreRenderRecursiveInternal() +80
   System.Web.UI.Control.PreRenderRecursiveInternal() +171
   System.Web.UI.Control.PreRenderRecursiveInternal() +171
   System.Web.UI.Control.PreRenderRecursiveInternal() +171
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +842

Any ideas on how to fix this? When installing, I chose all of the data types, the xslt methods, the 301 redirect, and the drag and drop functionality.

-C

Copy Link

Shannon Deminick 1526 posts 5272 karma points MVP 3x

Dec 14, 2010 @ 00:24

1

This shouldn't be occuring. I'll have to check the source to find out which data type(s) are the problem.

This is basically an issue with IIS 7 and that they changed the way that the VirtualPathProvider handles URLs, especially web resources urls containing query strings.

One way to fix this issue is to upgrade your ClientDependency version as the latest version has a fix for this IIS 7 issue (it's actually an IIS 6 issue, but was 'fixed' in IIS 7, but actually now breaks things)

The latest version of ClientDependency is 1.2 which you can get here:

http://clientdependency.codeplex.com/releases/view/52519

You should be able to just overwrite your ClientDependency DLLs (TAKE BACKUPS FIRST THOUGH!!!!)

Copy Link
Shannon Deminick 1526 posts 5272 karma points MVP 3x

Dec 14, 2010 @ 00:25

0

Just noticed your are running windows server 2003 which is not IIS 7... not seen this error on IIS 6... but hopefully this error might be resolved with a CD upgrade

otherwise, there might be issues with an embedded resource in uComponents.

Copy Link
Chad Rosenthal 272 posts 474 karma points

Dec 14, 2010 @ 00:26

0

Hmm. I reverted my Web.config back to my old one, and now the CMS is working fine. I guess the better question is, what will break because of that....

Copy Link
Shannon Deminick 1526 posts 5272 karma points MVP 3x

Dec 14, 2010 @ 00:27

0

Do you have a DIFF of the changes made to your web.config?

Copy Link
Shannon Deminick 1526 posts 5272 karma points MVP 3x

Dec 14, 2010 @ 00:35

2

I think i just spotted the culprit in the code. I think it is due to the uComponentsModule that is registered in the web.config for v2 which is required for the Shortcuts additions.

I've msg the team to see if we can get a quick patch out but in the meantime, to fix this issue you can either just not have the uComponentsModule declared in your web.config (which will disable the Shortcuts module) or Upgrade to ClientDependency 1.2

Copy Link
Chad Rosenthal 272 posts 474 karma points

Dec 14, 2010 @ 00:36

1

It looks like upgrading the ClientDependency worked for me.

My web.config had the following changes:

<add name="uComponentsModule" type="uComponents.Core.Modules.uComponentsModule, uComponents.Core" /></modules>

was added to my modules and

<add name="uComponentsModule" type="uComponents.Core.Modules.uComponentsModule, uComponents.Core" /></httpModules>

was added to httpModules.

-C

Copy Link
Shannon Deminick 1526 posts 5272 karma points MVP 3x

Dec 14, 2010 @ 00:38

1

great! CD 1.2 will be released with Umbraco Juno. It's got some nice new functionality and bugs fixed.

Copy Link
Max Öhman 42 posts 71 karma points

Dec 14, 2010 @ 09:57

0

damn it! My post didn't show...
And I was rambling on and on about how awesome you guys are for putting down so much time on this community.

Ok, I'll cut to my problem. I get the same error as Chad after installing a data type (XPath CheckBoxList). The reason I wanna ask you guys if I should go ahead with the changes above is, I'm running on Windows server 2008 and IIS 7, is this an okGo or a noGo?

Thanks! /Max

Copy Link
Shannon Deminick 1526 posts 5272 karma points MVP 3x

Dec 14, 2010 @ 09:58

0

Yup, will work just fine.

Copy Link
is working on a reply...

Please Sign in or register to post replies