Interesting installation experience on 64 bit machine
The other day a team approached me stating that they had some issues in running and accessing a .net application on their newely configured Win2K3 64 bit dual core server. They were getting some sort of access denied when they moved their app from 32 bit to 64 bit. I told them that just by moving to 64 bit can't result in such issue and asked them to cross check and install .net 2.0 framework for 64 bit.
They had not installed it but soon reverted with another error while trying to do the installation - "Error creating process <C:\Docume~1\user\local settings\temp\1\IXP000.TMP\Install.exe>. Reason: C:\SYSROOT\system32\advpack.dll". I then refered them to this forum thread.
The team came back with another interesting error that said - "The image file c:\netfx64\install.exe is valid, but is for a machine type other than current machine.". The message seemed to hint that this wasn't a 64 bit machine, but the team confirmed that indeed it was.
So I asked them to verify if they were using a 64 bit OS by pointing to this support article, and interestingly it turns out that they were actually working with a 64 bit machine but with a 32 bit OS setup on it. If you read the support article you will realize that there is a minor difference in the way the System details are shown. In a 32 bit system it reads Microsoft Windows Server 2003 Enterprise Edition, while in a 64 bit system it reads Microsoft Windows Server 2003 Enterprise x64 Edition.
I am waiting for the team to install teh 64 bit OS and then get back to me. In the meantime I thought to share this to highlight that be careful of what OS you are really running on your 64 bit system to avoid unpleasant surprises.