Hi. There's something wrong with the client dependency framework in your installation. First of all check that you have ClientDependencyHandler configured in your web.config file. There should be a line under the httpHandler section that reads: '<add verb="*" path="DependencyHandler.axd" type="ClientDependency.Core.CompositeFiles.CompositeDependencyHandler, ClientDependency.Core " />' (from the error messages I suspect that it's missed from there).
Hi Martin just to let you know your not on your own, I'm with ehosting as well and I'm having the same issue. I think they did some server upgrades on sunday so that may be the cause of it.
What I have noticed is that its only failing in my .net 4 umbraco installs, all the older version sites are working fine.
Hopefully I will get a response from them tomorrow and it will be an easy fix, if anyone has any suggestions tho on how it could be fixed would love to here them.
eHosting got back to me regarding this issue. I'll post there reply below and in the "Bugs" section. Although it appear that im still stuck in limbo.
Hello Martin,
Having logged in we can see the errors you mentioned within the browsers JavaScript console. The last error mentions that the file DependencyHandler.axd cannot be loaded. Looking at the source of the page we can see on line 7 that the file is being included to load both some CSS (layout) and some JavaScript (jQuery we assume).
When using the URL that the code has we see the following error from ASP.net:
System.ArgumentException: Could not parse the type set in the request
Looking this up in Google it appears to be an issue relating to the formatting of the request. We can see that the URL includes the HTML character "&" which is designed to be replaced with an ampersand. However, this appears to be causing the above error.
If we replace the "&" with the actual & character then the page loads and outputs the CSS as we would expect. This appears to be an issue with Umbraco itself, and potentially may be related to a .Net update that was performed on the 22nd of September.
We would recommend that you pass this information on to Umbraco for them to look at and hopefully identify the issue and correct this within their application. This should of course assist yourself and any other people seeing the same issue.
We have been looking into the issues you have been facing with Umbraco and we believe we have identified the cause of the issue that you are seeing.
Looking at our security devices on our network we can see that an update to the signatures used to identify security threats were updated at 2am on Tuesday morning. These appear to have enabled a security signature which detects a URL that is potentially dangerous to a web server and drops the connection as a security measure.
Looking at the URL that is being used within Umbraco this would explain why this was not loading - however, this was something that would have happened early Tuesday morning and not on Sunday as originally suggested by yourself.
However, when attempting to load the DependencyHandler.axd file within our browser we still see an ASP.net error page and so it appears this may be something that Umbraco would still need to look into.
If you do continue to see any issues then please do get back to us and we can investigate further.
Not a "solution" but could you do a url rewrite rule to change the & to & on the DependencyHandler.axd request to get around their "security measures"?
Here is the fix from eHosting that got it working.
Hello Hywel,
The issue is specific to the Juniper devices that we use and so it may affect some people as it depends on how the device is configured. The fix for this is permanent and we would not expect this to change as we have manually disabled this signature on our security devices.
We believe the issue with the ampersands does appear to be a bug within Umbraco and we still see this after correcting the issue with the networking blocking the requests. The only way Umbraco would be able to work around the security issue would be to shorten the length of the URL's they are using, but that may not be possible for them to do.
UI not showing/loading
Hi, Im having problems with a new install of Umbraco.
I can login, but after that the UI is not loading. Im getting the following errors in the console.
Any help would be great
Martin
Hi. There's something wrong with the client dependency framework in your installation. First of all check that you have ClientDependencyHandler configured in your web.config file. There should be a line under the httpHandler section that reads: '<add verb="*" path="DependencyHandler.axd" type="ClientDependency.Core.CompositeFiles.CompositeDependencyHandler, ClientDependency.Core " />' (from the error messages I suspect that it's missed from there).
Hi Rodion,
Ive just checked the web.config file.
I have that line that you mentioned in place.
Would permissions cause any problems like this?
Is this fixable or is it a re-install?
Thanks
Hi Martin
It could very well be that the permissions for network service or iusr have not been set correctly so check that they have sufficient permissions.
Also make sure that the app pool is running .NET 4 and integrated mode.
Furthermore try checking the App_Data folder and delete the clientdependency temp files if any exists.
Hope some of these pointers help.
/Jan
Hi Jan,
The permissions that I set at install where following a tutorial showing Umbraco installed with Plesk. It all worked fine.
I recently had my hosting provider rename the system. Would that cause an issue?
Is there a list that I can follow that show what permissions are to be set on which folders.
I am not a developer, so how do I check that the app pool is running .NET 4. I've had a look at the hosting cp and .Net 4 is selected.
I have also checked the ClientDependency folder. There is no files in it. I have also tried deleting this folder, with no success, and reinstated it.
Any help would be grateful.
Thanks
Hi, this has kind of gone form bad to worse.
I am now getting the same error on my other ehosting.com umbraco site.
I did ask for a renaming of the each system that they sit on, but they said that this would not affect the site, as its an administrive issue.
They are going to move me onto a windows 2008 server.
Can I manually change the permissions of the folder structure, or will this cause any issues?
Im not from a developers background, so when it comes to setting up umbraco backend, im a little lost.
Anyone else have issues with ehosting.com?
Thanks
Hi Martin just to let you know your not on your own, I'm with ehosting as well and I'm having the same issue.
I think they did some server upgrades on sunday so that may be the cause of it.
What I have noticed is that its only failing in my .net 4 umbraco installs, all the older version sites are working fine.
Hopefully I will get a response from them tomorrow and it will be an easy fix, if anyone has any suggestions tho on how it could be fixed would love to here them.
Cheers
Hywel
Thanks Hywel,
That puts my mind at ease somewhat. I've been back and forward with ehosting support, and getting nowhere.
Atleast im not on my own.
If i hear anything, I'll post here.
Cheers
Martin
Hi Hywel,
eHosting got back to me regarding this issue. I'll post there reply below and in the "Bugs" section.
Although it appear that im still stuck in limbo.
Hello Martin,
Having logged in we can see the errors you mentioned within the browsers JavaScript console. The last error mentions that the file DependencyHandler.axd cannot be loaded. Looking at the source of the page we can see on line 7 that the file is being included to load both some CSS (layout) and some JavaScript (jQuery we assume).
When using the URL that the code has we see the following error from ASP.net:
System.ArgumentException: Could not parse the type set in the request
Looking this up in Google it appears to be an issue relating to the formatting of the request. We can see that the URL includes the HTML character "&" which is designed to be replaced with an ampersand. However, this appears to be causing the above error.
If we replace the "&" with the actual & character then the page loads and outputs the CSS as we would expect. This appears to be an issue with Umbraco itself, and potentially may be related to a .Net update that was performed on the 22nd of September.
We would recommend that you pass this information on to Umbraco for them to look at and hopefully identify the issue and correct this within their application. This should of course assist yourself and any other people seeing the same issue.
Best Regards,
eHosting Support
latest update from eHosting.... any suggestions?
Hello Hywel,
We have been looking into the issues you have been facing with Umbraco and we believe we have identified the cause of the issue that you are seeing.
Looking at our security devices on our network we can see that an update to the signatures used to identify security threats were updated at 2am on Tuesday morning. These appear to have enabled a security signature which detects a URL that is potentially dangerous to a web server and drops the connection as a security measure.
Looking at the URL that is being used within Umbraco this would explain why this was not loading - however, this was something that would have happened early Tuesday morning and not on Sunday as originally suggested by yourself.
However, when attempting to load the DependencyHandler.axd file within our browser we still see an ASP.net error page and so it appears this may be something that Umbraco would still need to look into.
If you do continue to see any issues then please do get back to us and we can investigate further.
Best Regards,
eHosting Support
Not a "solution" but could you do a url rewrite rule to change the & to & on the DependencyHandler.axd request to get around their "security measures"?
cheers,
doug.
Got the same reply.
eHosting are saying its an Umbraco 4.7.1 issue.
Looks like I may have to move away from eHosting.
Here is the fix from eHosting that got it working.
Hello Hywel,
The issue is specific to the Juniper devices that we use and so it may affect some people as it depends on how the device is configured. The fix for this is permanent and we would not expect this to change as we have manually disabled this signature on our security devices.
We believe the issue with the ampersands does appear to be a bug within Umbraco and we still see this after correcting the issue with the networking blocking the requests. The only way Umbraco would be able to work around the security issue would be to shorten the length of the URL's they are using, but that may not be possible for them to do.
Best Regards,
eHosting Support
Cheers Hywel,
My Umbraco install looks like its fixed now.
fingers crossed.
is working on a reply...