Learn More





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...Upgrading DNN P...Upgrading DNN P...CS0103: The name chkAcceptTerms does not existCS0103: The name chkAcceptTerms does not exist
New Post
1/20/2019 4:19 PM

 Long time DNN user (was a member of the IBuySpy group on here attempting to bring a 7.4.2 portal up to 9.2.2.  I have made it through the gauntlet to 8.0.4, but ran into the following error attempting to upgrade to 9.1.1.  I did not see this when I tested using plain vanilla 8.0.4 on the exact same server. I am using Windows Server 2016, .NET 4.6 (also tried with .NET 4.7) and IIS 10. I was able to get pass the error by editing UpgradeWizard.ascx and hardcoding the needed responses there.  I have searched here, Google, the DNNTracker and GitHub, but have not found a really good answer. Lots of folks suggest upgrading csc.exe using the Nuget.exe and the Microsoft .Net Compilers package, but no one seems to have a good example of how that gets into the Framework64 folder.  And I not certain that is the issue given I was able to successfully upgrade the plain vanilla 8.0.4 installation using the exact same 9.1.1. code on the same server.  I am thinking there is something lingering in the shadows of my 7.4.2 installation that might even have been around when it was a DNN 5.0 installation.  I found an old .NET 2.0 empty <system.codedom> entry in the Web.Config which I removed without any happiness - still same error.  Any ideas would be very much appreciated. 

 Currently, I am working in a local VM dev environment, but the target is to upgrade my current 7.4.2 Azure installation.  I am taking all sorts of notes and will share my experience here, but would like to fill in this hole before I do. 


Compilation Error

Description: An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately.

Compiler Error Message: CS0103: The name 'chkAcceptTerms' does not exist in the current context

Source Error:


Line 255:            // EVENT HANDLER FUNCTIONS

Line 256:            //****************************************************************************************

Line 257:            var $acceptTerms = $('#<%= chkAcceptTerms.ClientID %>');

Line 258:            if ($acceptTerms.length) {

Line 259:                $ {

Source File: c:\inetpub\eqdnnprod\Install\UpgradeWizard.aspx    Line: 257

Microsoft (R) Visual C# Compiler version 4.7.3062.0

for C# 5

Copyright (C) Microsoft Corporation. All rights reserved.

This compiler is provided as part of the Microsoft (R) .NET Framework, but only supports language versions up to C# 5, which is no longer the latest version. For compilers that support newer versions of the C# programming language, see

New Post
1/21/2019 2:20 PM

More testing...

I just did a plain vanilla run through the following upgrades on the exact same server with no changes in server software/configuration since yesterday.

  1. I first installed 7.4.2 straight up and no additional modules or any edits or changes.
  2. I then upgraded that installation to 8.0.4 with no errors or issues.
  3. I then upgraded that 8.0.4 installation to 9.1.1 with no errors or issues
  4. I then upgraded that 9.1.1 installation to 9.2.2 again with no error or issues.

So, it would seem there is an issue with my current DNN installation, since the plain vanilla upgrade from 7.4.2 to 9.2.2 went without any errors.  I am suspecting SolParts, because I am using the MinimalExtropy and DNN-Blue skins. However, per a previous post on this issue, I removed the SolParts register and DNNActions entries from the containers, and I do not understand why the upgradewizard.ascx would use my containers anyway. 

I know I am not the only person who has come across this issues, as I have found several others doing a simple Google search. But nothing out there seems to have any idea what is going on.  I also looked to see if there was any software out there that would clean up an upgraded installation with left behind stuff - I see lots of stuff that was supposed to be removed when modules were removed, but was left behind. 

At this point, I am not comfortable moving what I have into production without solving why the 9.1.1 and 9.2.2 upgrades fail with the above errors.  

New Post
1/21/2019 2:38 PM
>>I know I am not the only person who has come across this issues, as I have found several others doing a simple Google search.

Can you share your search terms? I used this [1] and I didn't seem to find anyone hitting this problem.


Best wishes,
- Richard
Agile Development Consultant, Practitioner, and Trainer
New Post
1/21/2019 3:38 PM


Hi Richard,

So, I did not find results with those exact terms - wish I had. However, if you omit the "chkAcceptTerms" and just search for the rest of that error message you will find a number of them both related to DNN and not related.  If I hard code the answer in the code to ":checked" it gets pass that point then fails on not being able to resolve: "chkImprovementProgram" and in both parts of the code it is trying to get the value of the clientID for both of those objects. So this suggests something is not right with accessing whatever is being used to access the DOM or those objects are not being loaded into the DOM - both have their DIV entries marked with runat="server" so they should be loaded.   

Also, if you search for: "Compiler only supports language versions up to C# 5" you will also find both DNN and non-DNN related results.  The second search is the one that sent me on the rabbit trail trying to upgrade the csc.exe to what is the current one in the NuGet gallery - but again given I just went through a plain vanilla upgrade from 7.4.2 -> 8.0.4 -> 9.1.1 -> 9.2.2 without any problems on the exact same Dev VM, I am pretty certain the issue is not with the csc.exe.  I am thinking it is some remnant left behind from the dark past of my installation given it has come through many upgrades from 6.1.2 to 8.0.4.  

New Post
1/21/2019 4:03 PM
Ok. Full disclosure - never hit this problem myself. All that follows are guesses.

In your quoted code...

Line 257: var $acceptTerms = $('#>%= chkAcceptTerms.ClientID %<');

The plan is to generate a bit of jQuery based javascript. In that...

chkAcceptTerms.ClientID is intended to generate into that JS the specific client side ID that ASP.NET has chosen to generate for the chkAcceptTerms control on the page.

The message you have indicates that this bit of code has become mated with a version of the .aspx file that does not contain a runat=server item with that id.

I will confidently state that it will not be anything to do with versions of the C# compiler. IMO that is red-herring.

So I have some suggestions. (They are incomplete.)
- take a look at your UpgradeWizard.aspx file. Is/are the items there?
- wonder about UpgradeWizard.aspx anyway. I have a recollection that it was removed from DNN for a security exposure. Should it even be there for the version you are trying to get to?

Best wishes,
- Richard
Agile Development Consultant, Practitioner, and Trainer
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...CS0103: The name chkAcceptTerms does not existCS0103: The name chkAcceptTerms does not exist

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