Hi, Have successfully installed Microsoft Exchange 2007 on a Windows 2003 x64 (SP2) platform. Everything worked 100%. I then tried to install Microsoft Windows Update Services, however due to a limitation in running 32-bit and 64-bit .NET in IIS I could not run the Update Services and OWA at the same time. This led me to download and install MSWSUS 3.0 RC. I had to install .NET 2.0 64-bit and OWA and WSUS 3.0 are now working successfully. The problem is that the edgetransport.exe service is no longer starting and I cannot connect to the SMTP service on the server anymore. I have searched through this forum and did see a thread regarding start-up accounts however my MSExchange Transport service account is set to Network Service. Am sure it has something to do with .NET, is Exchange 2007 compatibile with .NET 2.0 x64? Any help would be appreciated, Thanks in advance Kidjo

Have managed to go into more detail, after restarting the server, I get the following error in my application log: Event Type:ErrorEvent Source:.NET Runtime 2.0 Error ReportingEvent Category:NoneEvent ID:1000Date:4/15/2007Time:10:05:14 AMUser:N/AComputer:QBJHBSVDC01Description:Faulting application edgetransport.exe, version 8.0.685.24, stamp 45726da8, faulting module mscorwks.dll, version 2.0.50727.42, stamp 4333c83c, debug? 0, fault address 0x00000000001908c0. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. The link does not take me anywhere though. If I try to manually register the dll via the run command I get the following error: C:\windows\microsoft.net\framework64\v2.0.50727\mscorworks.dll was loaded but the DllRegisterServer entry point was not found This file cannot be registered

Ok all is up and running again. I think my problems came from trying to get WSUS with SP1 working (I had installed .NET framework with SP1) I think I made a MAJOR mess with .NET so I removed all instances of .NET from the server and rebooted in case files were in use. I then installed .NET Framework 2.0 x64 (NetFx64.exe) I then installed .NET Framework 2.0 x64 update (NDP20-KB926776-X64.exe) (I waited for the .NET optimization to complete this takes a while, but saw that others had had issues when to trying to install / configure other stuff whilst it was running so waited) By this time WSUS 3.0 RC1 had had enough and was no longer working so I removed that (there is an option which allows you to keep all the configuration settings, (nice one MS)) and then re-installed it and it came back to life. Finally OWA had also given up so I removed the virtual directory in IIS and then recreated it with the cmdlet found here: http://technet.microsoft.com/en-us/library/bb123752.aspx After performing an IISRESET all was back in order SWEET! I then did the acid test and tried to start the MSExchange Transport service and it started at which point I cracked open a beer to celebrate. I then rebooted the server to see if everything would start normally and that there were no major issues in the event log. Apart from WSUS complaining about services which had not started (but when you check in ISM they had) all was ok. I think WSUS does a slightly premature check on the web-services after a reboot which brings up warnings which I'm ignoring. Cheers.