Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

QA

Ideas Test

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...500 error after upgrade to 9500 error after upgrade to 9
Previous
 
Next
New Post
5/11/2017 7:49 AM
 
Richard Howells


Richard Howells's Avatar

www.dynamisys.co.uk
Joined: 3/26/2006
Posts: 2001
Almost certainly you need a row in the PortalAlias table to identify the local URL you are using to access the site. You can just hack that directly into the database table following the pattern of what's already there.
Best wishes,
- Richard
Agile Development Consultant, Practitioner, and Trainer
www.dynamisys.co.uk
 
New Post
5/11/2017 8:46 AM
 
ade

Joined: 6/5/2007
Posts: 16
Thanks Richard, I'll give it a try when I get home.

I took a quick look before I left this morning, and I suspect that I gave some misleading information in my previous post last night. The DNN9 distribution, the DNN8 distribution AND the DNN9 Upgrade distribution all seem to include the same fairly old version of Newtonsoft.Json.dll - all v7. My site is looking for v9, and the current published version is v10. So I think I must have copied the dll from my pre-upgraded site, NOT the DNN9 distribution, which means, I suspect, that a 3rd party module has upgraded the Newtonsoft dll on my live site, and every subsequent DNN upgrade distribution has overwritten it with the old v7 dll, which causes the 500 error. This is quite possible, and if I think back it could be the EasyDNNSolutions gallery module which I installed shortly after upgrading to DNN8, or maybe a skins module. I will investigate, but it would be nice I guess if DNN doesn't *need* to upgrade some dlls, ie the upgrade distribution includes the same version as the previous installation, then it doesn't actually do it.

Ade
 
New Post
5/11/2017 5:11 PM
 
ade

Joined: 6/5/2007
Posts: 16

Hmmm ... I look in my PortalAlias table and I see 7 different entries all for Portal 0, including the alias I'm connecting to to log in! But as soon as I log in via the local alias I get redirected to the online site, which has two aliases in the table, one for each language.

Am I missing something?

Ade

 
 
New Post
5/12/2017 4:47 PM
 
Richard Howells


Richard Howells's Avatar

www.dynamisys.co.uk
Joined: 3/26/2006
Posts: 2001
I don't know anything about the multi language support. I'd try local aliases to match the two languages, but I'm just guessing.
Best wishes,
- Richard
Agile Development Consultant, Practitioner, and Trainer
www.dynamisys.co.uk
 
New Post
5/13/2017 11:46 AM
 
DNNMonster

Joined: 4/9/2009
Posts: 159
I experienced that exact same issue and resolved it with binding redirects in the web.config and a sub directory in the bin to hold the different versions of NewtonSoft. Here is an example of the relevant web.config that worked for my situation. You'll have to get the right dll versions and create the directory structure in your bin.
     
            
       
             <dependentAssembly>
        <assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" culture="neutral" />
        <bindingRedirect oldVersion="1.0.0.0-7.0.2.0" newVersion="7.0.0.0" />
        <bindingRedirect oldVersion="7.0.2.1-8.9.0.0" newVersion="8.0.0.0" />
        <bindingRedirect oldVersion="9.0.0.0-9.9.0.0" newVersion="9.0.0.0" />
        <codeBase version="7.0.0.0" href="bin/NewtonSoft.Json/V7.0.1/Newtonsoft.Json.dll" />
        <codeBase version="8.0.0.0" href="bin/NewtonSoft.Json/V8.0.3/Newtonsoft.Json.dll" />
        <codeBase version="9.0.0.0" href="bin/NewtonSoft.Json/V9.0/Newtonsoft.Json.dll" />
      </dependentAssembly>
       
       
       
       
       
     
       
       
       
       
       
       
     








 
 Page 3 of 4
Previous1234Next 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...500 error after upgrade to 9500 error after upgrade to 9


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