Install Forms 11g FM on Windows 2008 64 bit

Question

Has anyone been able to install FM 11g (Forms etc) on Windows 2008 Server 64 bit.
Every time I attempt an install I get the OUI checking for swap space and monitor configuration. After that the OUI goes away and nothing else happens.
The entries in the installactions file is below.
Using paramFile: D:\Install\Disk1\install\win64\oraparam.ini
Checking swap space: must be greater than 500 MB. Actual 7154 MB Passed
Checking monitor: must be configured to display at least 256 colors. Actual 65536 Passed
The commandline for unzip:
D:\Install\Disk1\install\win64\unzip -qqqo ..\..\stage\Components\oracle.jdk\6.0.10.33.0\1\DataFiles/"*.jar" -d "C:\Users\S-OTG~1.MAT\AppData\Local\Temp\2\OraInstall2009-09-22_08-56-31AM"
I have installed the WLS using the 64 bit version of JRockit with no problems.

Answer 1

I reviewed your SR and wanted to clarify a few things. In the SR, you were not exactly told that installing (in general) was not supported on Win2008(x64). You were simply told that you could not use the 32bit download on a 64bit machine or install the Builders on x64. If you were told something else in a call I apologize as that information may have not been correct. Additionally, the SR is very confusing because you go from talking about Win2008 to XP to 2003 back to 2008 and so on. This is a very difficult way to troubleshoot. Dealing with one problem at a time will almost always result in the fastest resolution time. That said, here are the facts based on the platforms you mentioned in the SR.
1. Windows 2008 (64bit): This platform is intended for deployment (server). Although it may be possible to install the Forms/Reports Builders on this platform, Oracle is currently not supporting the Builders on any 64bit platform. Plans to support 64bit Operating Systems for Builders is still under review. So, for now, you must use the 64bit download to install on a 64bit platform. If you choose to attempt the installation of the Builders on this platform, you do it at your own risk.
2. Windows XP and Vista (32bit): These platforms are generally considered "client" platforms. These platforms are supported for using Builders. Technically they are not supported to be used as servers. Therefore, HTTP Server and Web Cache are not supported on these platforms. More details are explained in the Release Notes:
http://download.oracle.com/docs/cd/E12839_01/relnotes.1111/e10132/intro.htm#sthref8
3. Windows 2003 (32bit): This platform can be used with both the deployment components and the design-time components. That said, being a 32bit platform, I would not recommend trying to run a prod system and attempt to develop on it as well. Certainly, doing application maintenance on this machine would be fine, but if you were running a prod environment here, I would not suggest running the Builders full time too. 4gig of RAM or more would definitely be needed. See the following:
http://support.microsoft.com/kb/283037
Now, the actual problems you had/have:
Configuration failing when installing on Win2008 (64) - Looking at the SR, this appears to have been the result of trying to use the 32bit installation on the 64bit box. Upon initial release of the product, 64bit Windows distributions were not available. However, they are now and must be used on 64bit Windows 2008 and 2003 platforms. Refer to the OTN Download area.
Also seen in the error log was a connection issue. This is often caused as a result of several things, but the most common causes are WLS (node manager) is not running or the machine is under powered (usually lack of RAM). Regardless of what is documented, experience shows that a Windows machine will need to have at least 3.5 gig of RAM in order to support the installation process. This assumes that nothing else is running during the installation process unless it is absolutely needed. It seems that 4gig or more offers the most likely chance of a successfull installation on the first attempt.
Regarding the error which suggests that a given service already exists. This could likely happen if you attempted an installation, but it failed then you attempted to re-run the installation without first doing a thorough clean-up.
On the XP installation it appears that there was some memory issues. From the log: java.lang.OutOfMemoryError. As I mentioned, for the most likely chance of success, the machine should have at least 3.5 gig of RAM. If you are just installing the Builders you can have less, but if the config portion fails, you will probably see the connection failure seen in your other attempts. When/if this failure occurs, do not exit or do anything with the installer. Allow a minute or two (or more) for the new instance to completely start then select the Retry option. You will likely find that the configuration will complete successfully.
Also, important for any installation type.... When installing WLS, UNcheck the Launch Quick Start option that appears near the end of the WLS installation. Running this creates a default or demo instance. Unless you are planning to use this example instance, leaving it out can give back as much as 500 meg RAM in some cases. If you have already installed it and don't want to reinstall, stop whatever processes start as a result of that example instance.
SUMMARY
1. Be sure you are installing the correct software for your platform type. 64bit software for 64bit OS
2. On Windows, ensure that you have either installed the Loopback adapter or added your host name to the hosts file. Refer to Section 2.3:
http://download.oracle.com/docs/cd/E12839_01/install.1111/e10421/install.htm#CHDEAAGD
3. Ensure that the machine has at least 3.5 gig RAM. For systems with less, expect to see failures during the configuration portion of the install. Use "Retry" to overcome this.
4. Builders are only supported on 32bit platforms at this time:
http://download.oracle.com/docs/cd/E12839_01/relnotes.1111/e10132/intro.htm#sthref8
5. Ensure that WLS node manager is running before installing FMw
I don't think I missed anything, but just be sure to review the Installation Guide AND the Release Notes.