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.
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
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.
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
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.
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.
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?