Products

Solutions

Resources

Partners

Community

Blog

About

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...How to Upgrade DotNetNukeHow to Upgrade DotNetNuke
Previous
 
Next
New Post
11/10/2012 3:58 AM
 
Michael Miller wrote:
I don't believe I'm asking, but I seem to not be able to bring the website down with the app_offline.htm file upgrading 6.2 to 6.2.2 due to a build error!

Any suggestions on a work around?

Thanks,

Mike

 You have to set the fist document that should be used on the IIS to the app_offline.htm file instead the Default.aspx file. After successful upgrade you have to set this back to the Default.aspx.

 
New Post
11/12/2012 3:21 PM
 
the dnn upgrade proccess should be very simple.. simplicity should be the key. i am geting this horrible error Domain Name Does Not Exist In The Database

yes the solution should be very simple but its not.
 
New Post
11/12/2012 7:22 PM
 
Kenneth Herrera wrote:
the dnn upgrade proccess should be very simple.. simplicity should be the key. i am geting this horrible error Domain Name Does Not Exist In The Database

yes the solution should be very simple but its not.

 First please post questions to other issues as discussed on a thread into a new thread.  This helps to follow the process of discussions.

Have you used the Upgrade package?  It Looks to me as you recreate the database, which could be come if you use the installpackage that included a new web.config file. Some of the configuration Looks as missed, or an error was running on the upgrade. 

Please restore database and files from a previuos backup and start the upgrade process from crach using the Upgrade package!

 

 
New Post
12/6/2012 9:48 AM
 
Sebastian Leupold wrote:
make sure, your web.config file has not been touched, especially the database connection.

 Hi - I used the upgrade alternative and decompressed the zip over my Matrix installation, and I didn't tuuched the config file. 
When I tried to enter as super admin, I recieved the following error:

Det går inte att läsa in filen eller sammansättningen ClientDependency.Core eller ett av dess beroenden. Den här sammansättningen har skapats med ett program av en senare version än det aktuella inlästa programmet och kan därför inte läsas in.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. 

Exception Details: System.BadImageFormatException: Det går inte att läsa in filen eller sammansättningen ClientDependency.Core eller ett av dess beroenden. Den här sammansättningen har skapats med ett program av en senare version än det aktuella inlästa programmet och kan därför inte läsas in.

Source Error: 

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Assembly Load Trace: The following information can be helpful to determine why the assembly 'ClientDependency.Core' could not be loaded.

VARN: Loggningen av sammansättningsbindningen är inaktiverad. Du kan aktivera felloggning för sammansättningsbindningar genom att ange registervärdet [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) till 1. Obs! Prestanda kan försämras något med felloggning för sammansättningsbindningar. Du kan inaktivera funktionen genom att ta bort registervärdet [HKLM\Software\Microsoft\Fusion!EnableLog]. 

Stack Trace: 

[BadImageFormatException: Det går inte att läsa in filen eller sammansättningen ClientDependency.Core eller ett av dess beroenden. Den här sammansättningen har skapats med ett program av en senare version än det aktuella inlästa programmet och kan därför inte läsas in.] System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection) +0 System.Reflection.Assembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection) +43 System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) +127 System.Reflection.Assembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) +142 System.Reflection.Assembly.Load(String assemblyString) +28 System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective) +46 [Configurati sException: Det går inte att läsa in filen eller sammansättningen ClientDependency.Core eller ett av dess beroenden. Den här sammansättningen har skapats med ett program av en senare version än det aktuella inlästa programmet och kan därför inte läsas in.] System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective) +613 System.Web.Configuration.CompilationSection.LoadAllAssembliesFromAppDomainBinDirectory() +203 System.Web.Configuration.CompilationSection.LoadAssembly(AssemblyInfo ai) +105 System.Web.Compilation.BuildManager.GetReferencedAssemblies(CompilationSection compConfig) +178 System.Web.Compilation.BuildProvidersCompiler..ctor(VirtualPath configPath, Boolean supportLocalization, String outputAssemblyName) +54 System.Web.Compilation.CodeDirectoryCompiler.GetCodeDirectoryAssembly(VirtualPath virtualDir, CodeDirectoryType dirType, String assemblyName, StringSet excludedSubdirectories, Boolean isDirectoryAllowed) +600 System.Web.Compilation.BuildManager.CompileCodeDirectory(VirtualPath virtualDir, CodeDirectoryType dirType, String assemblyName, StringSet excludedSubdirectories) +125 System.Web.Compilation.BuildManager.CompileResourcesDirectory() +31 System.Web.Compilation.BuildManager.EnsureTopLevelFilesCompiled() +304 [HttpException (0x80004005): Det går inte att läsa in filen eller sammansättningen ClientDependency.Core eller ett av dess beroenden. Den här sammansättningen har skapats med ett program av en senare version än det aktuella inlästa programmet och kan därför inte läsas in.] System.Web.Compilation.BuildManager.ReportTopLevelCompilationException() +58 System.Web.Compilation.BuildManager.EnsureTopLevelFilesCompiled() +512 System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters) +729 [HttpException (0x80004005): Det går inte att läsa in filen eller sammansättningen ClientDependency.Core eller ett av dess beroenden. Den här sammansättningen har skapats med ett program av en senare version än det aktuella inlästa programmet och kan därför inte läsas in.] System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +8921851 System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +85 System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) +333 

Version Information: Microsoft .NET Framework Version:2.0.50727.5466; ASP.NET Version:2.0.50727.5456

What did I do wrong? /
Thanks 
Tomas

 


Trafic injured non profit Site owner/webmaster/admin/user without programming skills, eager to help other injured and sever ill persons.
 
New Post
12/6/2012 2:49 PM
 

Tomas,

 

if you try upgrade to DNN 7.0 you should notice that the min. requements are changed! 

For DNN 7.0 you have to use .NET 4.x !!

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...How to Upgrade DotNetNukeHow to Upgrade DotNetNuke


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