.NET runtime error on installation step 4 - exchange server 2007
Posted on 2007-11-16
On running step 4 of exchange 2007 setup I receive the following error: "Exchange Setup encountered an error" with only an OK button. No logs are generated in the usual places.
The event log contains a .NET 2 Runtime Error; Event ID 1000:
Faulting application exsetupui.exe, version 8.0.685.24, stamp 45726fdf, faulting module kernel32.dll, version 5.2.3790.4062, stamp 462643a7, debug? 0, fault address 0x000000000000dd10.
I have .NET installed and updated - there are no more updates shown on windows updates.
I then try to run the setup using the setup.com unattended installation and receive the following error messages:
Unhandled Exception: System.IO.FileNotFoundException: Could not load file or ass
embly 'Microsoft.Exchange.Setup.Common, Version=22.214.171.124, Culture=neutral, Public
KeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find th
e file specified.
File name: 'Microsoft.Exchange.Setup.Common, Version=126.96.36.199, Culture=neutral, P
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\M
icrosoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure lo
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fus
Exchange Server setup encountered an error.
Again, the .NET error is logged in event log.
The server in question is an HP ML310 with Server 2003 R2 (with Service Pack 2) Standard x64 Edition. It was 2GB RAM and a Xeon 3050 (2.13Ghz).
This is a totally fresh build and install. It is not part of our internal AD domain as I intend the server to be used as an Edge Server - ADAM is installed. (I have already successfully installed the majority of Exchange 2007 on a similar machine for the other roles!!)
I have tried installing using a networked DVD drive and also by copying the files locally - both supported options by microsoft.
If any more details are required, then please post. Thanks in advance - this is driving me nuts!!
My initial thoughts are obviously an error with .NET but none of the hotfixes available appear to work, and microsoft appear not to be aware of the problem. The fact that no other logs are generated is also a PITA!