Hello all,

Since upgrading to 7.1.2 I'm getting a fair number of these exceptions in the application log...

Exception information: 

Exception message: no map was found for the dependency key: be7d89d3ac6d5d93d82a38c14bb19400 ,CompositeUrlType.MappedId requires that a map is found

at ClientDependency.Core.CompositeFiles.CompositeDependencyHandler.ProcessRequestInternal(HttpContextBase context, String fileset, ClientDependencyType type, Int32 version, Byte[] outputBytes)
at ClientDependency.Core.CompositeFiles.CompositeDependencyHandler.System.Web.IHttpHandler.ProcessRequest(HttpContext context)
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)


Request information: 

Request URL: http://www.******.org/DependencyHandler.axd/be7d89d3ac6d5d93d82a38c14bb19400.0.css 

Request path: /DependencyHandler.axd/be7d89d3ac6d5d93d82a38c14bb19400.0.css 

User host address: **.***.**.*** 

User: 
Is authenticated: False 
Authentication Type: 
Thread account name: NT AUTHORITY\NETWORK SERVICE 

Thread information: 
Thread ID: 48 
Thread account name: NT AUTHORITY\NETWORK SERVICE 
Is impersonating: False 
Stack trace: at ClientDependency.Core.CompositeFiles.CompositeDependencyHandler.ProcessRequestInternal(HttpContextBase context, String fileset, ClientDependencyType type, Int32 version, Byte[] outputBytes)
at ClientDependency.Core.CompositeFiles.CompositeDependencyHandler.System.Web.IHttpHandler.ProcessRequest(HttpContext context)
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

 

I've tried fiddling with various settings in the client resource management, resetting app pools, rebooting, etc. to no avail and Google and searches of these forums have brought no joy. 

Any ideas of what might be causing this would be most helpful.

 

Thank you,

 

Dave

Hi ya,

First of all thank you very much for your reply. Yes, I find the behavior quite odd as well. We have a several DNN7 instances going and this is only one we're seeing the issue with.

The site is running .NET v4, 32bit False, Integrated with the max worker process set to 1 so it's not a web garden. We do have .NET framework v4.5 installed on the server but as I said other DNN7 sites on the same box are not generating the exception.

It's a weird one, which is why I posted a cry for help ; )

Thanks again,

Dave

 

Do you think if would do any good to take a backup, stop the app pool and site and then refresh all of the files with release 7.1.2?