Exchange 2010/2013/2016 Cannot find server in AD for database…

Symptom:

Exchange Databases are not visible under database, get-mailboxdatabase or when creating new user.

erorr message in event log :

Server für Datenbank MailboxDB (077f8b6f-3cf4-49af-8241-b90021c115c4) wurde nicht gefunden.

<Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event”&gt;
– <System>
<Provider Name=”MSExchangeApplicationLogic” />
<EventID Qualifiers=”49156″>3055</EventID>
<Level>2</Level>
<Task>3</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime=”2015-10-23T08:18:50.000000000Z” />
<EventRecordID>3022407</EventRecordID>
<Channel>Application</Channel>
<Computer>computeraccountl</Computer>
<Security />
</System>
– <EventData>
<Data>ProcessOrgExtensions</Data>
<Data>Microsoft.Exchange.Data.Storage.UnableToFindServerForDatabaseException: Der aktive Server für Datenbank mailboxdatabse (077f8b6f-3cf4-49af-8241-b90021c115c4) wurde nicht gefunden. bei Microsoft.Exchange.Data.Storage.ActiveManager.ActiveManagerImplementation.GetServerInformationForDatabaseInternal(IADDatabase database, DatabaseLocationInfo minimalLocationInfo, IFindMiniServer findMiniServer) bei Microsoft.Exchange.Data.Storage.ActiveManager.ActiveManager.GetServerInformationForDatabase(Guid databaseId, IADDatabase database, DatabaseLocationInfo dbLocationInfo, GetServerForDatabaseFlags gsfdFlags, IPerformanceDataLogger perfLogger) bei Microsoft.Exchange.Data.Storage.ActiveManager.ActiveManager.GetServerForDatabase(Guid databaseId, GetServerForDatabaseFlags gsfdFlags, IPerformanceDataLogger perfLogger) bei Microsoft.Exchange.Data.Storage.DatabaseLocationProvider.GetLocationInfo(Guid mdbGuid, Boolean bypassCache, Boolean ignoreSiteBoundary) bei Microsoft.Exchange.Data.Storage.ExchangePrincipalFactory.InternalFromADUser(IGenericADUser user, ADObjectId mdb, DatabaseLocationInfo databaseLocationInfo, RemotingOptions remotingOptions, Boolean asArchive, Boolean isContentIndexing, Nullable`1 aggregatedMailboxGuid) bei Microsoft.Exchange.Data.Storage.ExchangePrincipalFactory.FromADUser(ADSessionSettings adSettings, IGenericADUser user, RemotingOptions remotingOptions, String domainController) bei Microsoft.Exchange.Data.Storage.ExchangePrincipalFactory.FromADUser(ADUser user, String domainController) bei Microsoft.Exchange.Data.ApplicationLogic.Extension.OrgExtensionTable.CreateExchangeService(String domain, RequestData requestData)</Data>
</EventData>
</Event>

Cause:

Wrong Server set in msExchMasterServer and msExchOwningServer are pointing to non-existing exchange server

Solution:

Recreated all System mailboxes.Old ones are pointing to non existing server.

Set correct server on msExchMasterServer and msExchOwningServer for affected  mailboxdatabase in ADSI EDIT.

Advertisements

Outlook not connection after migration Exchange 2010 to 2013/2016

Symptoms:

Migrated users from 2010 are not able to connect to exchange with outlook Client.

Profile in outlook fails on step logon to server with error message:

The connection to Microsoft exchange is unavailable

Issue is relevat to Exchange 2013 and 2016

Workaround:

Recycle MSExchangeAutodiscoverAppPool after migration. New Profile.

Exchange 2010- Information Store not starting. Service-specific error code 1006

Symptoms:

Information Store is not starting.

“Service-specific error code 1006“

Cause:

Antivirus is causing MSexchange Information store not to start.

Solution:

Uninstall Antivirus software.

https://support.microsoft.com/en-us/kb/319754

1.Click Start, click Run, type regedit in the Open box, and then click OK.

2.Browse to the following registry subkey:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\VirusScan

3.On the Registry menu, click Export Registry File.

4.In the File name box, type virusscan, and then click Save.

NOTE: If you later need to restore this registry key, you can do so by double-clicking the Virusscan.reg file that you saved.

5.In the right pane of the Registry Editor window, right-click the Enabled value, and then click Modify.

6.In the Value data box, type 0 (zero), and then click OK.

7.Quit Registry Editor, and then restart the computer.

Public Folders Migration Exchange 2007 – 2013 Issue

Symptom:

[PS] C:\Windows\system32>New-PublicFolderMigrationRequest -SourceDatabase (Get-PublicFolderDatabase -Server srv.domain.com) -CSVData (Get-Content D:\install\MAP.csv -Encoding Byte)

Das Postfach konnte nicht in den Modus für die Quellsynchronisierung umgeschaltet werden.

Hierfür sind folgende Gründe möglich:

Ein anderer Administrator verschiebt das Postfach zurzeit.

Das Postfach ist gesperrt.

Der Microsoft Exchange-Postfachreplikationsdienst (MRS) verfügt nicht über die richtigen Berechtigungen.

Netzwerkfehler verhindern, dass MRS die Sitzung mit dem Postfachserver sauber abschließt. Wenn dies der Fall ist,

kann dieser Fehler in MRS noch für bis zu 2 Stunden auftreten. Diese Dauer wird von den TCP-KeepAlive-Einstellungen

auf dem Postfachserver gesteuert. Warten Sie, bis das Postfach freigegeben wurde, bevor Sie erneut versuchen, dieses

Postfach zu verschieben.

+ CategoryInfo          : NotSpecified: (:) [New-PublicFolderMigrationRequest], RemoteTransientException

+ FullyQualifiedErrorId : [Server=srv,RequestId=f0cc4d07-49ea-4078-84a2-61be38da3073,TimeStamp=06.10.2015

12:54:32] [FailureCategory=Cmdlet-RemoteTransientException] 579D5E22,Microsoft.Exchange.Management.RecipientTasks

.NewPublicFolderMigrationRequest

+ PSComputerName        : srv.domain.com

Cause: 

Old exchange 2007 Version

Solution:

Most of Internet sites are sugesting to increase the TCP keepaliveinterval in registry. But in this case the solution was to update the exchange 2007.

Installed SP3 RU15