.NET 3 is required to install EPIserver CMS

Vote:
 
Hi. I have a Windows 2003 R2 x64 and is trying to install EpiServer 5 using EpiServer Manager 2.0.18.2. I get the following error: ".NET 3 is required to install EPIserver CMS". .NET 2 and .NET 3 is installed. Regards Morten.
#15786
Mar 25, 2008 19:07
Vote:
 
Hi Morten, We don't support CMS on 64 bit platforms. The reason you are getting this message, is because we don't find the 32 bits assemblies that are installed by .NET 3.0. Regards, Tibi
#16362
Mar 25, 2008 19:08
Vote:
 
Hi. Is there any plan to fix this? I personally think that it is a horrible decision, due to the reason that it isn't that much work to support .NET x86 and .NET x64, as far as I see it. Most x86 bits programs can run on x64 bit platforms without any problems. Regards Morten.
#16363
Mar 25, 2008 19:08
Vote:
 
And by the way Björn Olsson writes in the thread "EPiServer Manager and Windows XP x64.", that he can install and run EPIserver 5 on x64 platform.
#16364
Mar 25, 2008 19:08
Vote:
 
Hi Morten, you have to install the 32 bit version of .NET 3.0 from here http://go.microsoft.com/fwlink/?LinkId=70848, but this will make it possible for you to run the 32 bit release of EPiServerCMS in 32 bit mode on a 64 bit platform, which is not the same as running 64 bit on 64 bit platform. Regards, Tibi
#16365
Mar 25, 2008 19:08
Vote:
 
Hi. The only problem is that the installation (.NET setup) does not allowed you to install .NET x86 on x64 platform. It says that "Setup does not support 64-bit platforms" :) Regards Morten.
#16366
Mar 25, 2008 19:08
Vote:
 
Hi Morten! As of today EPiServer CMS does not support running in 64-bit mode. This was originally planned for the CMS release but was postponed. You should however be able to run EPiServer CMS in 32-bit mode on a 64 bit machine although this does not give you any better performance than running on a 32-bit machine (at least as far as I know). We know that there are issues with the installation and these will be fixed when we add 64-bit support to the platform. I can not say when we will have a release our with 64 bit support at the moment.
#16367
Mar 25, 2008 19:08
Vote:
 
Hi! As Linus noted above, we currently don't have support for x64 platforms, but I didn't anticipate that this particular problem would occur. The manager determines if .NET 3.0 is installed by looking at a registry key, as described in this document: http://msdn2.microsoft.com/en-us/library/aa480198.aspx#netfx30_topic14 The same registry key should also exist for .NET 3.0 in a x64 environment unless the x86 and x64 versions of 3.0 set up different keys. x64-versions of Windows WILL create a separate registry branch for 32bit programs, as is stated in this document: http://support.microsoft.com/kb/896459. But that wouldn't apply to your problem since you are running the 64bit version of ASP.NET 3.0. So, the bottom line is that I can't see why this problem occurs, but I would be interested in finding out where ASP.NET 3.0 has stored it's registry values in your environmet. Could you provide that information for me?
#16368
Mar 25, 2008 19:08
Vote:
 
Key Name: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.0\Setup Class Name: Last Write Time: 18-09-2007 - 10:15 Key Name: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.0\Setup\Windows Communication Foundation Class Name: Last Write Time: 18-09-2007 - 10:05 Value 0 Name: ReferenceInstallPath Type: REG_SZ Data: C:\Program Files\Reference Assemblies\Microsoft\Framework\v3.0\ Value 1 Name: InstallSuccess Type: REG_DWORD Data: 0x1 Value 2 Name: Version Type: REG_SZ Data: 3.0.04506.30 Value 3 Name: RuntimeInstallPath Type: REG_SZ Data: C:\WINDOWS\Microsoft.NET\Framework64\v3.0\Windows Communication Foundation\ Key Name: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.0\Setup\Windows Presentation Foundation Class Name: Last Write Time: 18-09-2007 - 10:06 Value 0 Name: Type: REG_SZ Data: Windows Presentation Foundation x64 Value 1 Name: ProductVersion Type: REG_SZ Data: 3.0.6920.0 Value 2 Name: InstallRoot Type: REG_SZ Data: C:\WINDOWS\Microsoft.Net\Framework64\v3.0\WPF\ Value 3 Name: WPFReferenceAssembliesPathx64 Type: REG_SZ Data: C:\Program Files\Reference Assemblies\Microsoft\Framework\v3.0\ Value 4 Name: WPFCommonAssembliesPathx64 Type: REG_SZ Data: C:\WINDOWS\system32\ Value 5 Name: WPFNonReferenceAssembliesPathx64 Type: REG_SZ Data: C:\WINDOWS\Microsoft.Net\Framework64\v3.0\WPF\ Key Name: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.0\Setup\Windows Workflow Foundation Class Name: Last Write Time: 18-09-2007 - 10:15 Value 0 Name: InstallSuccess Type: REG_DWORD Data: 0x1 Value 1 Name: InstallDir Type: REG_SZ Data: C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\v3.0\ Value 2 Name: ProductVersion Type: REG_SZ Data: 3.0.0.0 Value 3 Name: FileVersion Type: REG_SZ Data: 3.0.4203.2 Value 4 Name: MajorBuildNum Type: REG_SZ Data: 4203 Value 5 Name: Type: REG_SZ Data: Windows Workflow Foundation
#16369
Mar 25, 2008 19:08
This thread is locked and should be used for reference only. Please use the Episerver CMS 7 and earlier versions forum to open new discussions.
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.