Exchange Server 2010 Public Folder Error!

I found that no one can sent email to our mail-enable public folder. there's a warning like below
Delivery has failed to these recipients or groups:
([email protected]) <[email protected]>
There's a problem with the recipient's mailbox. Please try resending the message. If the problem continues, please contact your helpdesk.
Diagnostic information for administrators:
Generating server: EXCHUB02.domain.com
[email protected]
#550 5.2.0 STOREDRV.Deliver: The Microsoft Exchange Information Store service reported an error. The following information should help identify the cause of this error: "MapiExceptionNotFound:16.18969:B8000000,
17.27161:0000000054000000000000000000000000000000, 255.23226:2B0A0000, 255.27962:44000000, 255.17082:BFF9FFFF, 0.25697:00000000, 4.21921:BFF9FFFF, 255.27962:FA000000, 255.1494:35000000, 255.26426:96000000, 4.18236:BFF9FFFF, 4.7974:BFF9FFFF, 255.1750:43000000,
0.26849:43000000, 255.21817:BFF9FFFF". ##
Original message headers:
Received: from EXCMAIL02.domain.com ([fe80::7c57:574e:f764:e8f7]) by
exchub02.domain.com ([::1]) with mapi; Mon, 7 Apr 2014 15:47:55 +0700
Content-Type: application/ms-tnef; name="winmail.dat"
Content-Transfer-Encoding: binary
From: "Admin" <[email protected]>
To: <[email protected]>
Subject: sdasd
Thread-Topic: sdasd
Thread-Index: Ac9SPhG67LrxITcEQjufincOJHZGwg==
Date: Mon, 7 Apr 2014 15:47:55 +0700
Message-ID: <[email protected]>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator: <[email protected]>
MIME-Version: 1.0
Did you guys know what happen to my public folder? cause i can't find the right solution for my problem.

Please check out the below thread related to your query.
http://social.technet.microsoft.com/Forums/en-US/exchangesvradmin/thread/c1fab3bd-589d-4c7c-8807-2eda93d11c27/
Hope it helps

Similar Messages

Exchange Server 2010 public folder - Events show in SharePoint 2010 Calendar

I want to fetch items to SharePoint 2010 Calendar from Exchange Server 2010 Public Folder Calendar called Event. How can I achieve this ?

May be you can directly fetch whole public folder in sharepoint server
http://www.amrein.com/apps/page.asp?Q=5778
If this helped you resolve your issue, please mark it Answered

Migrate Exchange Server 2010 Public Folder shared calendars to Exchange Server 2013

Dear All,
I have an question about calendars under public folder migrating to new exchange server 2013. When completed the PF migration progress, will it also migrate calendars under sub-folder under PF to new PF mailbox?
For example: in exchange 2010 PF:
In exchange 2013
\Public Folder\sales\A1_calendar
--->
\ Public Folder\sales\A2_calendar
---> ?
\Public Folder\sales\A3_calendar
---> ?
\Public Folder\sales\A4_calendar
---> ?
Thanks in advance.
Regards,
Willis Wong

Hi Willis,
This forum is for general questions and feedback related to Outlook. Since your question is more related to Exchange server, I'd recommend you post a new question in the Exchange forum for further assistance:
https://social.technet.microsoft.com/Forums/office/en-US/home?category=exchangeserver
The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding.
Steve Fan
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

"Exchange Server 2003" Public folder access within OWA

Hello,
I can connect to my exchange server 2003 (I know I have to upgrade) with OWA through an alias (webmail). After connecting in OWA, when I click a button in the navigation bar (contact, rules, ...), it's working OK except for public folders. When I click on
public folders button, IE open a new window with this URL https://<netbios server name>/public instead of https://webmail/public. I googled around and found a thread explaining how this problem can be address by modifying navbar.js. But in my situation
navbar.js and every other files located in ..\exchweb\control doesn't seem to be access anymore, they have been replaced by those here ..\exchweb\6.5.7651.60. There is no navbar.js in this folder but a vw_navbar.js. I can't find the code I have to modify like
in navbar.js to to address the problem.
Thanks for your help.
Chris

Hi Chris,
This symptom can be caused if we enabled any redirection on /Public virtual directory. You can check the /Public settings and configuration files to remove the redirection. We can also reset the reset the default virtual directories as the KB introduced:
http://support.microsoft.com/kb/883380
Best Regards,
Tracy

Exchange server 2010 POP3 users error

My exchange server 2003 server migrate to server 2010. After migration pop3 users cannot connect mail server, Then I'm restart POP3 service, after restating service , clients are working properly .But after five days, face in same issue. After restart service
again ,clients are working properly,
Pls give me permanent solution for that issue

Hi,
Please follow Ed to install SP3 UR6 for test.
Thanks
Mavis
Mavis Huang
TechNet Community Support

When sending e-mail messages to a mail-enabled public folder that have been replicated from old Exchange Server 2000/2003/2007, Exchange Server 2010 environment mails are rejected with NDR.

Hi, I would like to share with you issue that I’ve solved regarding mail-enabled PF that migrated from Exchange 2000/2003/2007 to 2010, I’ve searched & contacted my MVP leader – there’s no official KB regarding this issue right
now, so I’m posting here in order to share this among others.
Note: There’s article(s) that talked about PF replication from Exch2000/2003/2007 to 2010 – this is the same issue as well.
Symptoms
E-mail messages that been sent to mail-enabled public folder in Exchange Server 2010 environment rejected with the following NDR:
“#< #5.2.0 smtp;554 5.2.0 STOREDRV.Deliver.Exception:ObjectNotFoundException; Failed to process message due to a permanent exception with message The Active Directory user wasn’t found. ObjectNotFoundException: The Active Directory
user wasn’t found.> #SMTP#”
Sometimes Exchange Server 2010 is documented as well Event ID 1020 on the Event Viewer with this information:
“Log Name: Application
Source: MSExchange Store Driver
Event ID: 1020
Level: Error
Description:
The store driver couldn’t deliver the public folder replication message "Hierarchy ([email protected])" because the following error occurred: The Active Directory user wasn't found.”
Cause
In an environment where Microsoft Exchange Server 2000 or Microsoft Exchange Server 2003 previously existed, and all those servers have been removed, there is a chance that an Administrative Group (First Administrative Group or another custom Administrative
Group) remains with a Servers container, but no servers inside it.
During replication, when the Exchange 2010 Store Driver sees the empty Servers container in Active Directory, it's expecting a System Attendant object inside the container and when it is not found the error occurs.
Resolution
To work around the issue, delete the empty Servers container. This can't be done through Exchange System Manager. Use the ADSI Edit tool to remove it using the following steps:
Warning If you use the ADSI Edit snap-in, the LDP utility, or any other LDAP version 3 client, and you incorrectly modify the attributes of Active Directory objects, you can cause serious problems. These problems may require you to reinstall Microsoft Windows
2003 Server, Microsoft Windows Server 2008, Microsoft Exchange 2010 Server or both Windows and Exchange. Microsoft cannot guarantee that problems that occur if you incorrectly modify Active Directory object attributes can be solved. Modify these attributes
at your own risk.
1.
Start the ADSI Edit MMC Snap-in. Click Start, then
Run, and type adsiedit.msc, and then click OK.
2.
Connect & Expand the Configuration Container [YourServer.DNSDomainName.com], and then expand
CN=Configuration,DC=DNSDomainName,DC=com.
3.
Expand CN=Services, and then CN=Microsoft Exchange, and then expand
CN=YourOrganizationName.
4.
You will see an empty Administrative Group. Expand the
CN=YourAdministrativeGroupName.
5.
Expand CN=Servers.
6.
Verify there are no server objects listed under the
CN=Servers container.
7.
Right click on the empty CN=Servers container and choose
Delete.
8.
Verify the modification, and try to send again the E-mail to the mail-enabled public folder.
Applies to
Exchange Server 2010, Standard Edition
Exchange Server 2010, Enterprise Edition
Netanel Ben-Shushan, MCSA/E, MCTS, MCITP, Windows Expert-IT Pro MVP. IT Consultant & Trainer | Website (Hebrew): http://www.ben-shushan.net | IT Services: http://www.ben-shushan.net/services | Weblog (Hebrew): http://blogs.microsoft.co.il/blogs/netanelb
| E-mail: [email protected]

Sounds like you are looking in the wrong Administrative Group container which is why you are seeing your Exchange 2010 servers in there.
When you install Exchange 2003 only you will see a container named by default as "CN=First Administrative Group" container. But this could be named anything if you changed the Organization Name on the installation when you installed the first
Exchange 2003 server into the domain/forest.
You will notice that when you install Exchange 2010 part of the AD setup is to create a new configuration container and is named by default "CN=First Administrative Group (FYDIBOHF23SPDLT)".
So it sounds like you are not looking in the right location within ADSIEdit.
You may find the following article also helpful for this issue which is the same resolution:
http://blogs.technet.com/b/sbs/archive/2012/05/17/empty-cn-servers-container-causing-issues-with-public-folders-on-small-business-server-2011.aspx
I recommend though that you ensure your Exchange 2003 servers are fully uninstalled or no longer present in your environment before you go deleting the Servers container though.. The following Microsoft article will help with this:
http://technet.microsoft.com/en-gb/library/gg576862(v=exchg.141).aspx

Exchange 2010 - Public Folder Managment

I seem to have hit a bit of a stale mate with our exchange 2010 public folder management and while i think i see things set up wrongly - i'm not sure how to fix or what the consequences are if i did (and since i haven't yet built a sandbox test environment) i thought i would ask the spiceworks community for some helps and tips.So a little back ground first :two physical locations - one UK one USStretch DAGS with US-MBX replicating to UK-CAS and UK-MBX replicating to US-CASALL servers on the same domainProblem i am trying to resolve :One of our users based here in the UK travels to and manages some US staff now. US staff put holidays into a calendar in a public folder. The UK based manager would like to see this calendar.Sounds easy right? (maybe it is and i just need a clip around the napper with the manual).When i look at the public...
This topic first appeared in the Spiceworks Community

Are you using OWA or Outlook to view the public folders?
If you're using OWA, the reason you can't see the folders is that OWA in Exchange 2003 uses WebDAV, which is no longer present in Exchange 2010.
If you're using Outlook, you'll need to use the troubleshooting logs to determine the cause of the problems.
It could be related to Outlook trying to connect directly to 2010 mailbox server instead of CAS. Because normally the mailbox server is installed without the CAS role, it does not allow a direct Outlook connection. Or it could be something else,
like authentication.

Exchange 2010 public folder not showing on exchange 20003 mailbox

Hi,
I have public folder on exchange 2003 and separate public folder on exchange 2010. On exchange 2010 user mailbox, I can see both 2003 and 2010 public folders. On exchange 2003 user mailbox, I can only see 2003 public folders. It is not the permission issue
as I have given the user "owner" right and see not able 2010 public folder inless i move 2003 user mailbox to 2010 exchange.
Appreciate if anyone could help me if to point me to directions or any hotfix I can run?
Thank you very much.
Pwint

Are you using OWA or Outlook to view the public folders?
If you're using OWA, the reason you can't see the folders is that OWA in Exchange 2003 uses WebDAV, which is no longer present in Exchange 2010.
If you're using Outlook, you'll need to use the troubleshooting logs to determine the cause of the problems.
It could be related to Outlook trying to connect directly to 2010 mailbox server instead of CAS. Because normally the mailbox server is installed without the CAS role, it does not allow a direct Outlook connection. Or it could be something else,
like authentication.

Exchange 2013 Public Folder Error

When I try to create a Public Folder in Exchange Admin Center for Exchange Standard 2013 I get an error that says: "The process failed to get the correct properties". If I create the Public Folder from shell "New-PublicFolder -Name
"Bldg 1 & 2" -Path "\Projects\10000 to 10099"", when I browse to it from Admin Center I receive the same error.
If I try to edit the properties using Admin Center I get a popup that says "error - The process failed to get the correct properties - Click here for help..."
I have attempted this as "administrator" with membership in the following groups:
Schema Admins, Organization Management, Group Policy Creator Owners, Exchange Services, Exchange Domain Servers, Enterprise Admins, Domain Admins, Administrators.

Hi,
Did we migrate to Exchange 2013 from legacy?
We cannot starting recreating Public Folders on Exchange Server 2013 until all users have been migrated to Exchange Server 2013. For how to migrate from legacy Public Folders to Exchange Server 2013 Public Folders, see
Migrate Public Folders to Exchange 2013 From Previous Versions.
Would you like to collect event logs for the further troubleshooting?
Please contact me if there is any problem.
Thanks
Mavis
Mavis Huang
TechNet Community Support
Hi Mavis,
Yes, this was an upgrade, but all previous versions of Exchange have been uninstalled.
I'd be more then happy to send any log files in, but I'd need assistance knowing which ones you'd require.
Thanks,
Peter

Exchange Server 2010 OWA Error 405 StaticFileModule

I am running Exchange Server 2010
(Version 14.1 - Build 218.15) on Windows Server 2008 R2. This is a all-in-one-server roles installation. Everything is working fine except forms-based authentication. When enabled I get HTTP Error 405.0 "Method not allowed". The page
you are looking for cannot be displayed because an invalid method (HTTP verb) is being used.
Details are:
Module StaticFileModule
Notification ExecuteRequestHandler
Handler StaticFile
Error Code 0x80070001
Requested URL https://localhost:443/owa/auth/owaauth.dll
Physical Path C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\owa\auth\owaauth.dll
Logon Method Basic
Logon User administrator
When in EMC, Client Access, on OWA & ECP tabs I change authentication forms-based to standard with basic check box and restart IIS the Web Access works fine.
I have already tested solutions like recreating Virtual Directories, Allow .Net 2.0, etc. I have also checked all the modules and the associated mappings in IIS one by one for every VM. I believe this is an error in a .config file. If you have encountered
a situation like this please help.

Hi Pantelis,
Please make sure that the client sends a request that contains a valid HTTP method.
1. Click Start, type Notepad in the Start Search box, right-click
Notepad, and then click Run as administrator.
Note If you are prompted for an administrator password or for a confirmation, type the password, or provide confirmation.
2. On the File menu, click Open. In the
File name box, type %windir%\system32\inetsrv\config\applicationhost.config, and then click
Open.
3. In the ApplicationHost.config file, locate the <handlers> tag.
4. Make sure that all the handlers use valid HTTP methods.
5. Save the ApplicationHost.config file.
More details to see: http://support.microsoft.com/kb/942051
Please also try to re-build OWA Virtural Directory. To see:
http://support.microsoft.com/kb/941201
Thanks
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Mavis Huang
TechNet Community Support

Exchange Server 2010 SP3 Installation with UM Language Pack Error

Hi All,
Kindly help me in this issue, When I Install Exchange Server 2010 SP3, I faced an error in UM role setup as the below,
and when i searched on it i found solution like "Download the UM language packs and tried to install directly" so i downloaded "UMLanguagePack.en-US" from the below URL:
http://www.microsoft.com/en-eg/download/details.aspx?id=36769
and when i tried to install it, i faced the below error:
also i searched on this error and i found solution in registry as the below:
Try remove registry key for the above error :
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\<Your Version >\UnifiedMessagingRole\LanguagePacks"
and after i did it, i found first error be solved and the second error still the same as the below:
Error:
A Setup failure previously occurred while installing the UnifiedMessaging role. Either run Setup again for just
this role, or remove the role using Control Panel.
Is there a solution on this issue please i wanna solve it As soon as possible?
Thanks in advance,

I solved the below error by editing in registry:
Error:
A Setup failure previously occurred while installing the UnifiedMessaging role. Either run Setup again for just this role, or remove the role using Control Panel.
Solution:
Open regedit (Start -> run), navigate to the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v14
Under each role, UnifiedMessagingRole, have a look for an action and watermark entry, Delete these 2 keys, and retry. it solve this error, and You can now run the installation again of your "UMLanguagePack.en-US". and its done and installed now.
After "UMLanguagePack.en-US" Installation, i tried to continue installation of Exchange Server 2010 SP3, but I faced the same first error in UM role setup as the below,
What can i Do? please help urgently.

Exchange Server 2010 EMC Error

Hi, I have installed Exchange Server 2010 SP3 in Windows Server 2012 Domain Controller. After the successful installation, I am not able to view the options in the Exchange Management Console. It gives the error "The WinRM client cannot process the
request. It Cannot determine the content type of the HTTP response from the destination computer. The content type is absent or invalid."
Can anyone help on this issue to solve this. Thanks in advance.
Regards
Babu

Hi
Installing exchange 2010 or any version on a domain controller is not recommended.
Please check that all the IIS App pools are started, the relevant services are started etc. Is this in a production environment?

Exchange Server 2010 get error HResult = -2147024891 when Accessing Virtual Directories on CAS

I've just installed a Exchange 2010 server in an Exchange 2007 server environment.
The 2007 enviroment include two exchange server "Server-A" and "Server-B"
and "Server B" has dead on hardware issue for half year.
When I go to Microsoft Exchange On-Premises -> ServerConfiguration -> Client Access and receive the following error message
An IIS directory entry couldn't be created. The error message is Access is denied. . HResult = -2147024891 It was running the command 'Get-OabVirtualDirectory'
I try run the “Get-OwaVirtualDirectory” in powershell and get following result
From the power Shell command prompt .. Run
[PS] C:\Windows\system32>Get-OwaVirtualDirectory
An IIS directory entry couldn’t be created. The error message is Access is denied.
. HResult = -2147024891
+ CategoryInfo : NotInstalled: (<Server-B\Exchange (Default Web Site):ADObjectId) [Get-OwaVirtualDirectory]
, IISGeneralCOMException
+ FullyQualifiedErrorId : 4B12EB5D,Microsoft.Exchange.Management.SystemConfigurationTasks.GetOwaVirtualDirectory
I've google that i need to add "Exchange Trusted Subsystem" as a member in local admin group in Exchange 2007
but my exchange 2007 "Server-B" already dead, how should i fix it?
Appreciate for any help!!

re-create the new virtual directories does not work for me.
still got the error
An IIS directory entry
couldn’t be created. The error message is Access is denied.
. HResult = -2147024891
+ CategoryInfo : NotInstalled: (<Server-B\Exchange (Default Web Site):ADObjectId) [Get-OwaVirtualDirectory]
, IISGeneralCOMException
+ FullyQualifiedErrorId : 4B12EB5D,Microsoft.Exchange.Management.SystemConfigurationTasks.GetOwaVirtualDirectory
I don't understand why change new exchange server 2010 setting require me to have permission to access
my dead exchange server 2007

Exchange Server 2010 SP3 Databases are not mounting after the recovery process

Hi,
We are using Exchange server 2010 SP3 in our office. Databases are stored in an ISCSI drive mapped with the exchange. We are taking daily full backup of my Exchange server using Symantec Backup exe 2012. As a testing purpose I created a test environment
same like my existing live environment to check the disaster recovery and backup. Thankfully disaster recovery worked well and I am able to open the exchange management console and powershell. But I am not able to mount the recovered databases ending
with an error saying "Couldn't mount the database that you specified. Specified database: officialrecover; Error code:
An Active Manager operation failed.........." and even I am not able to use the utility eseutil.exe to the database with an error "access to source database failed with jet error 1811". I am able to create a new database and mount
it.
I am using Windows Server Ent 2008 R2 64 Bit with Exchange Server 2010 SP3 in the Live environment with 3 partitions called C (279 GB), E (4.46 TB, ISCSI), F (976 GB) in my Live environment.
For test it is Windows Server Ent 2008 R2 64 Bit with Exchange Server 2010 SP3 with 3 partitions C (240 GB), E (1.4 TB), & F (240 GB).
Please help me with your valid comments to solve and mount the database and close the issue for ever.
With Regards
Jay

Jared is correct that in essence the message is saying the DB cannot be found.
When you restored to your recovery server are all the paths the same, i.e. if the DB existed on E:\XYZ on the production server it must be the same on the recovery server
When you restored into the recovery site do you have AD restored into that site as well?
For the recovery server are you using iSCSI storage for it as well? If so am I correct to assume that you have copies of the databases just for use on this server and are not trying to reference the same instance of the DB from the production
and test/recovery server?
I have also seen an issue where DB's getting written to disk from Symantec mess up the header of the DB. If you want to validate that the DB is actually intact and accessible you might want to check out our DigiScope product
http://www.lucid8.com/product/digiscope.asp using a free DEMO license. If it works i.e. you are able to mount in DigiScope from same location where its failing on the recovery server we know the
DB your pointing at is good and accessible from the current path but something else is amiss in your configuration
Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline Exchange Mailbox and Public Folder EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003 -->
2007 --> 2010 --> 2013 with Lucid8's
DigiScope

SBS 2003 to 2011 Migration - Exchange Server 2010 cannot be installed

Hello,
We have a Small Business Server 2003 server that we are trying to migrate to SBS 2011 using the out of the box migration process. After the install, the SBS console showed a couple installation issues - the big one turned out to be "Exchange Server
2010 cannot be installed".
Here is the end of 'ExchangeSetup.log' showing various error messages:
[11/29/2014 23:00:07.0489] [2] Active Directory session settings for 'Get-ExchangeServer' are: View Entire Forest: 'True', Configuration Domain Controller: 'MB-MAINSERVER04.Contoso.local', Preferred Global Catalog: 'MB-MAINSERVER04.Contoso.local', Preferred Domain Controllers: '{ MB-MAINSERVER04.Contoso.local }'
[11/29/2014 23:00:07.0490] [2] Beginning processing get-exchangeserver -Identity:'MB-MAINSERVER04' -DomainController:'MB-MAINSERVER04.Contoso.local' -ErrorAction:'SilentlyContinue'
[11/29/2014 23:00:07.0506] [2] Searching objects "MB-MAINSERVER04" of type "Server" under the root "$null".
[11/29/2014 23:00:07.0518] [2] Previous operation run on domain controller 'MB-MAINSERVER04.Contoso.local'.
[11/29/2014 23:00:07.0518] [2] Previous operation run on domain controller 'MB-MAINSERVER04.Contoso.local'.
[11/29/2014 23:00:07.0518] [2] Preparing to output objects. The maximum size of the result set is "unlimited".
[11/29/2014 23:00:07.0522] [2] Unexpected Error
[11/29/2014 23:00:07.0522] [2] The operation couldn't be performed because object 'MB-MAINSERVER04' couldn't be found on 'MB-MAINSERVER04.Contoso.local'.
[11/29/2014 23:00:07.0523] [2] Ending processing get-exchangeserver
[11/29/2014 23:00:07.0523] [1] Executing:
if ($server -eq $null)
new-exchangeserver -DomainController $RoleDomainController -Name $RoleNetBIOSName
[11/29/2014 23:00:07.0545] [2] Active Directory session settings for 'New-ExchangeServer' are: View Entire Forest: 'True', Configuration Domain Controller: 'MB-MAINSERVER04.Contoso.local', Preferred Global Catalog: 'MB-MAINSERVER04.Contoso.local', Preferred Domain Controllers: '{ MB-MAINSERVER04.Contoso.local }'
[11/29/2014 23:00:07.0545] [2] Beginning processing new-exchangeserver -DomainController:'MB-MAINSERVER04.Contoso.local' -Name:'MB-MAINSERVER04'
[11/29/2014 23:00:07.0599] [2] [ERROR] Could not find the default Administrative Group 'Exchange Administrative Group (FYDIBOHF23SPDLT)'.
[11/29/2014 23:00:07.0600] [2] Ending processing new-exchangeserver
[11/29/2014 23:00:07.0607] [1] The following 1 error(s) occurred during task execution:
[11/29/2014 23:00:07.0607] [1] 0. ErrorRecord: Could not find the default Administrative Group 'Exchange Administrative Group (FYDIBOHF23SPDLT)'.
[11/29/2014 23:00:07.0607] [1] 0. ErrorRecord: Microsoft.Exchange.Data.Directory.SystemConfiguration.DefaultAdministrativeGroupNotFoundException: Could not find the default Administrative Group 'Exchange Administrative Group (FYDIBOHF23SPDLT)'.
at Microsoft.Exchange.Data.Directory.SystemConfiguration.ADSystemConfigurationSession.GetAdministrativeGroup()
at Microsoft.Exchange.Data.Directory.SystemConfiguration.ADSystemConfigurationSession.GetAdministrativeGroupId()
at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeServer.PrepareDataObject()
at Microsoft.Exchange.Configuration.Tasks.SetTaskBase`1.InternalValidate()
at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
[11/29/2014 23:00:07.0609] [1] [ERROR] The following error was generated when "$error.Clear();
if ($server -eq $null)
new-exchangeserver -DomainController $RoleDomainController -Name $RoleNetBIOSName
" was run: "Could not find the default Administrative Group 'Exchange Administrative Group (FYDIBOHF23SPDLT)'.".
[11/29/2014 23:00:07.0609] [1] [ERROR] Could not find the default Administrative Group 'Exchange Administrative Group (FYDIBOHF23SPDLT)'.
[11/29/2014 23:00:07.0609] [1] [ERROR-REFERENCE] Id=ProvisionServerComponent___84489810458648f5ac6e47811394a284 Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[11/29/2014 23:00:07.0610] [1] Setup is stopping now because of one or more critical errors.
[11/29/2014 23:00:07.0610] [1] Finished executing component tasks.
[11/29/2014 23:00:07.0618] [1] Ending processing Install-BridgeheadRole
[11/29/2014 23:00:07.0626] [0] The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
[11/29/2014 23:00:07.0633] [0] End of Setup
[11/29/2014 23:00:07.0633] [0] **********************************************
[11/29/2014 23:39:03.0429] [0] **********************************************
[11/29/2014 23:39:03.0435] [0] Starting Microsoft Exchange Server 2010 Setup
[11/29/2014 23:39:03.0435] [0] **********************************************
[11/29/2014 23:39:03.0456] [0] Local Time Zone: (UTC-08:00) Pacific Time (US & Canada).
[11/29/2014 23:39:03.0457] [0] Operating System version: Microsoft Windows NT 6.1.7600.0.
[11/29/2014 23:39:03.0469] [0] Setup version: 14.1.438.0.
[11/29/2014 23:39:03.0473] [0] Logged on user: Contoso2K3\Administrator.
[11/29/2014 23:39:06.0763] [0] Command Line Parameter Name='mode', Value='Install'.
[11/29/2014 23:39:06.0776] [0] ExSetupUI was started with the following command: '-mode:install'.
[11/29/2014 23:39:07.0413] [0] Setup is choosing the domain controller to use
[11/29/2014 23:39:07.0730] [0] Setup is choosing a local domain controller...
[11/29/2014 23:39:08.0459] [0] Setup has chosen the local domain controller MB-MAINSERVER04.Contoso.local for initial queries
[11/29/2014 23:39:08.0747] [0] PrepareAD has been run, and has replicated to this domain controller; so setup will use MB-MAINSERVER04.Contoso.local
[11/29/2014 23:39:08.0748] [0] Setup is choosing a global catalog...
[11/29/2014 23:39:08.0758] [0] Setup has chosen the global catalog server MB-MAINSERVER04.Contoso.local.
[11/29/2014 23:39:08.0819] [0] Setup will use the domain controller 'MB-MAINSERVER04.Contoso.local'.
[11/29/2014 23:39:08.0820] [0] Setup will use the global catalog 'MB-MAINSERVER04.Contoso.local'.
[11/29/2014 23:39:08.0823] [0] Exchange configuration container for the organization is 'CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Contoso,DC=local'.
[11/29/2014 23:39:08.0830] [0] Exchange organization container for the organization is 'CN=Contoso2K3,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Contoso,DC=local'.
[11/29/2014 23:39:08.0867] [0] Setup will search for an Exchange Server object for the local machine with name 'MB-MAINSERVER04'.
[11/29/2014 23:39:08.0914] [0] No Exchange Server with identity 'MB-MAINSERVER04' was found.
[11/29/2014 23:39:09.0061] [0] The following roles have been unpacked: BridgeheadRole ClientAccessRole MailboxRole AdminToolsRole
[11/29/2014 23:39:09.0062] [0] The following datacenter roles are unpacked:
[11/29/2014 23:39:09.0064] [0] The following roles are installed: AdminToolsRole
[11/29/2014 23:39:09.0066] [0] The local server has some Exchange files installed.
[11/29/2014 23:39:09.0320] [0] Setup will use the path 'C:\Program Files\Windows Small Business Server\Bin\CMPNENTS\EXCHANGE14_SP1' for installing Exchange.
[11/29/2014 23:39:09.0332] [0] The installation mode is set to: 'Install'.
[11/29/2014 23:39:13.0558] [0] An Exchange organization with name 'Contoso2K3' was found in this forest.
[11/29/2014 23:39:13.0560] [0] Active Directory Initialization status : 'True'.
[11/29/2014 23:39:13.0561] [0] Schema Update Required Status : 'False'.
[11/29/2014 23:39:13.0562] [0] Organization Configuration Update Required Status : 'False'.
[11/29/2014 23:39:13.0563] [0] Domain Configuration Update Required Status : 'False'.
[11/29/2014 23:39:13.0564] [0] The locally installed version is 14.1.218.15.
[11/29/2014 23:39:13.0565] [0] Exchange Installation Directory : 'C:\Program Files\Microsoft\Exchange Server\V14'.
[11/29/2014 23:39:13.0920] [0] Applying default role selection state
[11/29/2014 23:39:13.0961] [0] Setup is determining what organization-level operations to perform.
[11/29/2014 23:39:13.0962] [0] Because the value was specified, setup is setting the argument OrganizationName to the value Contoso2K3.
[11/29/2014 23:39:13.0963] [0] Setup will run from path 'C:\Program Files\Microsoft\Exchange Server\V14\'.
[11/29/2014 23:39:13.0972] [0] InstallModeDataHandler has 0 DataHandlers
[11/29/2014 23:39:13.0972] [0] RootDataHandler has 1 DataHandlers
[11/29/2014 23:39:15.0491] [0] Setup encountered an exception when trying to access the setup state file: Could not find file 'C:\ExchangeSetupLogs\exchangeInstallState.xml'.
[11/29/2014 23:39:26.0117] [0] End of Setup
[11/29/2014 23:39:26.0117] [0] **********************************************
I should add that the source server's AD configuration might not be perfect due to this being the second attempt at a SBS 2011 migration install.
I'd be grateful for any help I can get on this as SBS migration has been plauged with multiple setbacks already. I really need to get this done! ;)
Thanks,
Voon

Thank you Larry and Al for your replies.
I used the 'official' migration
guide plus this page (http://www.techieshelp.com/step-by-step-guide-to-migrating-to-sbs-2011/)
as my migration references. The SBS migration prep tool gave no errors on the source server when I ran it.
I have a full system drive image plus a a system state backup from before migration. Though I am very loathed to rollback the migration and attempt a new one - again. I will do some searching to see if I can resolve the Exchange server problem and continue
the migration/installation. If not, then its a system state restore for me. One of Al's links had a resource for doing a thorough check of AD - which something I'd run if I have to another migration attempt.
I am also really tempted to open up a paid MS support ticket for them to help me fix this problem. :)

Exchange Server 2010 Public Folder Error!

Similar Messages

Maybe you are looking for