+ Post New Thread
Results 1 to 4 of 4
Enterprise Software Thread, Exchange 2013 AD prep- "Object reference not set to an instance of an object." in Technical; Hi I am trying to install Exchange 2013 CU 3. We currently have CU 2 installed. During preparing the organization ...
  1. #1

    FN-GM's Avatar
    Join Date
    Jun 2007
    Location
    UK
    Posts
    15,816
    Thank Post
    873
    Thanked 1,675 Times in 1,458 Posts
    Blog Entries
    12
    Rep Power
    444

    Exchange 2013 AD prep- "Object reference not set to an instance of an object."

    Hi

    I am trying to install Exchange 2013 CU 3. We currently have CU 2 installed. During preparing the organization i get the error "Object reference not set to an instance of an object."

    I googled this and some posts suggest its a dodgy exchange federation relationship. We don't have any or have it enabled.

    Any ideas please?

    Thanks


    Code:
    [01/05/2014 13:05:49.0656] [2] Group CN=Managed Availability Servers,OU=Microsoft Exchange Security Groups,OU=IT System,OU=Groups & Other Accounts,DC=domain,DC=local already exists.
    [01/05/2014 13:05:49.0718] [2] [ERROR] Object reference not set to an instance of an object.
    [01/05/2014 13:05:49.0718] [2] [WARNING] An unexpected error has occurred and a Watson dump is being generated: Object reference not set to an instance of an object.
    [01/05/2014 13:05:50.0591] [1] The following 1 error(s) occurred during task execution:
    [01/05/2014 13:05:50.0591] [1] 0.  ErrorRecord: Object reference not set to an instance of an object.
    [01/05/2014 13:05:50.0591] [1] 0.  ErrorRecord: System.NullReferenceException: Object reference not set to an instance of an object.
       at Microsoft.Exchange.Management.Tasks.InitializeExchangeUniversalGroups.CreateOrMoveEWPGroup(ADGroup ewp, ADOrganizationalUnit usgContainer)
       at Microsoft.Exchange.Management.Tasks.InitializeExchangeUniversalGroups.InternalProcessRecord()
       at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__8()
       at Microsoft.Exchange.Configuration.Core.LatencyTrackerExtension.StartAndEndInternalTracking(LatencyTracker latencyTracker, String groupName, String funcName, Boolean logDetailsAlways, Action action)
       at Microsoft.Exchange.Configuration.Core.CmdletLatencyTracker.StartAndEndInternalTracking(Guid cmdletUniqueId, String groupName, String funcName, Boolean logDetailsAlways, Action action)
       at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__7()
       at Microsoft.Exchange.Configuration.Core.LatencyTrackerExtension.StartAndEndInternalTracking(LatencyTracker latencyTracker, String groupName, String funcName, Boolean logDetailsAlways, Action action)
       at Microsoft.Exchange.Configuration.Core.CmdletLatencyTracker.StartAndEndInternalTracking(Guid cmdletUniqueId, String groupName, String funcName, Boolean logDetailsAlways, Action action)
       at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
       at System.Management.Automation.CommandProcessor.ProcessRecord()
    [01/05/2014 13:05:50.0607] [1] [ERROR] The following error was generated when "$error.Clear(); 
    	initialize-ExchangeUniversalGroups -DomainController $RoleDomainController -ActiveDirectorySplitPermissions $RoleActiveDirectorySplitPermissions
    
    " was run: "Object reference not set to an instance of an object.".
    [01/05/2014 13:05:50.0607] [1] [ERROR] Object reference not set to an instance of an object.
    [01/05/2014 13:05:50.0622] [1] [ERROR-REFERENCE] Id=443949901 Component=
    [01/05/2014 13:05:50.0622] [1] Setup is stopping now because of one or more critical errors.
    [01/05/2014 13:05:50.0622] [1] Finished executing component tasks.
    [01/05/2014 13:05:50.0638] [1] Ending processing Install-ExchangeOrganization

  2. #2

    Join Date
    Apr 2007
    Location
    Croydon
    Posts
    497
    Thank Post
    18
    Thanked 31 Times in 30 Posts
    Rep Power
    20
    Could be a stab in the dark, but the first thing I noticed is that the Managed Availability Servers group is not in the place it gets installed by default. Mine reads CN=Managed Availability Servers,OU=Microsoft Exchange Security Groups,DC=domain,DC=local

    Then I found this (albeit for Exchange 2010): Install Second Exchange Server 2010 in same domain installation Error

    In ADSIEdit if you goto Configuration, Services, Microsoft Exchange, right click on that and select properties, find the attribute otherWellKnownObjects. You can't edit it, but scroll along it's value and you should see where it is looking for the Managed Availability Servers group.

    Is what's in there, the same location as where your group is in AD?

  3. #3

    FN-GM's Avatar
    Join Date
    Jun 2007
    Location
    UK
    Posts
    15,816
    Thank Post
    873
    Thanked 1,675 Times in 1,458 Posts
    Blog Entries
    12
    Rep Power
    444
    Thanks for the help. I can't see where it is, its chopped the path off. See attached.

    Thanks

    Screen Shot 2014-01-05 at 2.55.36 PM.png

  4. #4

    Join Date
    Apr 2007
    Location
    Croydon
    Posts
    497
    Thank Post
    18
    Thanked 31 Times in 30 Posts
    Rep Power
    20
    Try this: Reading the otherWellKnownObjects attribute with PowerShell - Remko Weijnen's Blog (Remko's Blog)

    Looks like you can extract the value using Powershell.

SHARE:
+ Post New Thread

Similar Threads

  1. Replies: 7
    Last Post: 15th November 2013, 01:37 PM
  2. Exchange 2013 Domain Prep
    By FN-GM in forum Enterprise Software
    Replies: 4
    Last Post: 10th June 2013, 06:02 AM
  3. Replies: 3
    Last Post: 3rd May 2013, 03:51 PM
  4. Exchange 2007 - users not able to access Out of office
    By ranj in forum Enterprise Software
    Replies: 13
    Last Post: 31st August 2012, 06:36 PM
  5. Replies: 22
    Last Post: 19th October 2011, 01:59 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •