This is the second Exchange Server in the Org. it is running on a 2K3 server. Thever on the other server is 2k3. Install goes fine until about 2 min in to installing the Client Access Roll. Then setup bombs with "Object reference not set to an instance of an object". Here is a the end of the log:..................................................Finished installing ASP.NET (2.0.50727) without registering the scriptmap. [10/26/2009 4:04:16 PM] [2] Process standard error: [10/26/2009 4:04:16 PM] [2] Ending processing.[10/26/2009 4:04:16 PM] [1] Executing 'install-ClientAccessIisWebServiceExtensions', handleError = False[10/26/2009 4:04:16 PM] [2] Launching sub-task '$error.Clear(); install-ClientAccessIisWebServiceExtensions'.[10/26/2009 4:04:16 PM] [2] Beginning processing.[10/26/2009 4:04:16 PM] [2] [WARNING] An unexpected error has occurred and debug information is being generated: Object reference not set to an instance of an object.[10/26/2009 4:04:16 PM] [2] [ERROR] Object reference not set to an instance of an object.[10/26/2009 4:04:17 PM] [1] Exception : System.Management.Automation.CmdletInvocationException: Object reference not set to an instance of an object. ---> System.NullReferenceException: Object reference not set to an instance of an object. at Microsoft.Exchange.Management.IisTasks.IsapiExtension.IntStringToBoolean(String intString) at Microsoft.Exchange.Management.IisTasks.IsapiExtension.Parse(String extensionString) at Microsoft.Exchange.Management.IisTasks.IsapiExtensionList..ctor(String hostName) at Microsoft.Exchange.Management.IisTasks.InstallIisWebServiceExtensions.InternalProcessRecord() at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord() at System.Management.Automation.Cmdlet.DoProcessRecord() at System.Management.Automation.CommandProcessor.ProcessRecord() --- End of inner exception stack trace --- at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate) at System.Management.Automation.Parser.PipelineNode.Execute(Array input, Pipe outputPipe, ArrayList& resultList) at System.Management.Automation.Parser.StatementListNode.Execute(Array input, Pipe outputPipe, ArrayList& resultList)[10/26/2009 4:04:17 PM] [1] [WARNING] An unexpected error has occurred and debug information is being generated: Object reference not set to an instance of an object.[10/26/2009 4:04:17 PM] [1] [ERROR] Object reference not set to an instance of an object.[10/26/2009 4:04:17 PM] [1] [ERROR] Object reference not set to an instance of an object.Any help would be appreciated.

Hi,Is this the first exchange 2007 server in the network? Please run readiness check from ExBPA and then check the report.Exchange 2007 Readiness Check now available in ExBPA http://msexchangeteam.com/archive/2006/07/28/428506.aspxRegards,Xiu

Yes. It is the first Exchange 2K7 box. I have another installation of exch 2k3 andAD references to a crashed 2k3 server that I am attempting to bring back online. The crashed server was just acting as an edge server for a short time. Prior to that, it was a primary mail server.I ran the Readiness Check and fixed some minor issues but it had no effect on the installation. Readiness shows no errors. Only a warning about a second SMTP connector that is not on port 25, on the existing mail server.Any ideas?Thanks,Rick

Hi,If you are going to dismiss the exchange 2003 server,then I recommend you to bring it back online and then make it to be the back-end.After that,please try to isntall Exchange 2007 again. How to Remove the Last Legacy Exchange Server from an Organizationhttp://technet.microsoft.com/en-us/library/bb288905.aspx Regards,Xiu