Products

Solutions

Resources

Partners

Community

Blog

About

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...HotFix "critical error" with HTML moduleHotFix "critical error" with HTML module
Previous
 
Next
New Post
7/3/2017 10:50 AM
 
Cancel that... the other ones that upgraded didn't have that line. I'm still looking.
 
New Post
7/3/2017 11:17 AM
 
OK, I now have two sites throwing the exception error. Both have Telerik 2013.2.717.40.

The versions that work have 2013.1.403.40
 
New Post
7/3/2017 11:21 AM
 
I think it is the problem with the Telerik version. Good version that works is 2013.1.403.40. Bad version getting this error message is: 2013.2.717.40. I've replicated this on two sites. Now, how to change the Telerik version on the sites that don't work? Any suggestions?
 
New Post
7/3/2017 1:05 PM
 
OK, I just found my error. You MUST have this in the config file exactly.
" <trust level="Full" />"
Once I changed it to this, it worked just fine.
 
New Post
7/3/2017 2:18 PM
 

Hi,

I'm still having issues. All four of these particular sites are hosted with Godaddy. It appears that when I set up the hosting on the original site (about 3 years) plesk defaulted to "Medium" trust. Which I didn't notice and didn't cause any issues with DNN or the modules used on the site. Then I setup the other 3 over the next year or so, and it appears plesk defaulted to "Full" trust.  Those sites installed the hotfix without issue, but the older one running in Medium Trust gave me the error when accessing the patch Telerik component.

I tried just setting the hosting space to "Full Trust" via the ASP.NET section of plesk, which does add the code fragment you mention to the web.config file. But, when starting the site I quickly get a server side error "The connection name 'SiteSqlServer' was not found in the applications configuration or the connection string is empty."

My guess is that since the site was built and maintained over the years as a Medium Trust environment that something in the web.config hasn't been configured correctly for Full Trust. In fact, although all four sites are running basically the same framework, the working web.config files are almost 80 lines longer than the one that throws the error. So quite a bit of difference.

I did find one section that might be relevant. The working web.config files have a section commented as "<!-- Connection String for SQL Server 2005 Express -->" with an add name command starting with "add name="SiteSqlServer" connectionString="Server=" and containing the server ID, database ID and password". 

This particular section isn't in the web.config that is set for Medium Trust.

I might try adding the missing section to the problematic web.config file after getting a full backup of the site and database.

Thanks and BTW - I did get your PM, but my reply bounced.

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...HotFix "critical error" with HTML moduleHotFix "critical error" with HTML module


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out