Accesing the Microsoft Exchange attributes with JNDI

I have found that when you installl Microsoft Exchange 2003, it attaches some classes and attributes to the active directory default clases, in this page it is listed:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wss/wss/wss_ldf_AD_Schema_intro.asp
specifically im interested in the user class, it has an attribute called "auxiliaryClass" and in value it says "ms-Exch-Custom-Attributes Class" (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wss/wss/wss_ldf_classSchema_User.asp)
and finally in that clas i found the atributes that I need to access (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wss/wss/wss_ldf_classSchema_ms_Exch_Custom_Attributes.asp) but i dont know how to access asociated attribute-clases in active directory. I mean i can change the user description, because is a string, but when the value is other class?? how do i change it?
thx in advance (sorry for my english)

lol yes, i feel bad for asking that, i solved the problem 2 hours later...
but i dont understand how, the JNDI search inside the atributes and sub atributes for the class??? i know that really doesnt matther lol because it works and no more.
by the way i have other attribute, i can modify the email in the general tab in the user properties window in active directory, but i need to modify too the email in the "E-mail addresses" tab that appears when the user have a mailbox, especifically the SMTP type email, and dont know where is it, or by what name i can acces it
thx in advance :)

Similar Messages

  • DAG - Backup failing on 1 DB only with error - The Microsoft Exchange Replication service VSS Writer instance ID failed with error code 80070020 when preparing for a backup of database 'DB012'

    Hi Board,
    i´ve search across the board, technet and symantec sites but did not found a hint about my problem.
    we drive a 2 node DAG (Location1-Ex1-mb1 
    Location2-exc1-mb1), on SP2 RU4 patchlevel with 40 Databases.
    Since some time the backup of one - and only one DB - is failing with these events, logged on the Mailboxserver on which the passive DB is hosted.
    Log Name:      Application
    Source:        MSExchangeRepl
    Date:          28.09.2012 00:37:17
    Event ID:      2112
    Task Category: Exchange VSS Writer
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      Location1-Exc1-MB1
    Description: The Microsoft Exchange Replication service VSS Writer instance 1ab7d204-609a-4aea-b0a7-70afb0db38de failed with error code 80070020 when preparing for a backup of database 'DB012'.
    Followed by
    Log Name:      Application
    Source:        MSExchangeRepl
    Date:         
    01.10.2012 03:33:06
    Event ID:      2024
    Task Category: Exchange VSS Writer
    Level:         Error
    Keywords:      Classic
    User:         
    N/A
    Computer:      Location1-Exc1-MB1
    Description:
    The Microsoft Exchange Replication service VSS Writer (Instance 42916d80-36c1-4f73-86d0-596d30226349) failed with error 80070020 when preparing for a backup.
    The backup Application - Symantec Backup Exec 2010 R3 – states, this error
    Snapshot provider error (0xE000FED1): A failure occurred querying the Writer status.
    Check the Windows Event Viewer for details.
    Writer Name: Exchange Server, Writer ID: {76FE1AC4-15F7-4BCD-987E-8E1ACB462FB7}, Last error: The VSS Writer failed, but the operation can be retried (0x800423f3), State: Stable (1).
    Symatec suggests within http://www.symantec.com/business/support/index?page=content&id=TECH184095
    to restart the MS Exchange Replication Service – BUT the mentioned eventID
    8229 isn´t present on any of the both Mailboxservers.
    The affected Database is active on Location2-Exc1-Mb1 Server and in an overall healthy state. I found during my research, that below Location2-Exc1-Mb1 Server, there are not removed shadow copies present!
    This confuses me, since all Backups are normally taken from the passive copy of a Database.
    So my questions to the board are:
    * Does anyone is facing similar issues?
    * Can someone explain why snapshots are present on the Mailboxserver hosting the Active Database, whilst the errors are logged on the passive one?
    -          * Does someone know the conditions, why shadows copies remain and
    aren´t removed in a proper manner?
    What can cause the circumstance, that only 1 DB is facing such issues?
    Any suggestion is welcome!
    BR
    Markus

    Hi Lenora,
    I´ve encreases VSS / Exchange Backup Log levels to expert, before starting
    those things i´ve all tried now:
    - Backup from passive DB (forced within Symantec Backup Exec)
    - Backup from active DB (forced within Symantec Backup Exec)
    - Backup from passive DB without GRT enabled (forced within Symantec Backup Exec)
    - Backup from active DB without GRT enabled(forced within Symantec Backup Exec)
    All those attempts failed.
    But brought some more details - the backup against the active DB states, that there is still a backup in progress and therefore this backup is cancelled by VSS.
    The Solution was, that i´ve needed to restart the Exchange Replication Service on the Mailbox Server hosting the passive DB.
    Backups are working again on all DBs!
    THX for your replys.
    Best regards
    Markus

  • Exchange 2013 SP1 users randomly prompted with "The Microsoft Exchange Administrator has made a change that requires you quit and restart Outlook"

    I got a call to check an issue with a Exchange Server 2013 SP1 environment recently. All server was upgraded from Exchange server 2013 CU2 to Exchange Server 2013 SP1. It was done successfully but many users were being randomly prompted with a popup in their outlook
    client with the following message:-
    “The Microsoft Exchange Administrator has made a change that requires you quit and restart Outlook”
    Although there wasn’t any changes of late in the environment there were random popups like these for multiple users. As the behaviour was not consistent and effecting the entire upgration population
    Please suggest us how to resolve the issue.
    Regards, Md Ehteshamuddin Khan All the opinions expressed here is mine. This posting is provided "AS IS" with no warranties or guarantees and confers no rights.

    Hi,
    Does the issue happen to all Outlook 2013 users? Please create a new Outlook profile to have a try.
    If it fails, please check the msExchHomePublicMDB value in ADSI Edit:
    1. In Adsiedit, expand Configuration-->CN=Services -> CN=Microsoft Exchange -> CN=domain -> CN=Administrative Groups -> CN=Exchange Administrative Group -> CN=Databases.
    2. Right-click the listed database > Properties.
    3. Check whether the msExchHomePublicMDB value is set to an available value. Please change the value to <not set>.
    4. Click OK.
    Then check whether the issue persists.
    Thanks,
    Winnie Liang
    TechNet Community Support

  • "The Microsoft Exchange Administrator has made a change that requires you quit and restart Outlook" in Exchange 2013

    In Exchange 2013, Outlook finds a new connection point made up of the user’s mailbox GUID + @ + the domain portion of the user’s primary SMTP address. This change makes
    it much less likely that users will see the dreaded message “Your administrator has made a change to your mailbox.”
    http://technet.microsoft.com/en-us/library/dd298114(v=exchg.150).aspx
    Although the error message in the topic has been already improved a lot in Exchange 2013, the users may still encounter them in some specific scenarios. We have collected them and let’s discuss them in this thread.
    Symptom
    =======================================
    Consider the following scenario:
    Exchange 2013 was installed for a migration from Exchange 2007/2010.
    The legacy Exchange server is removed after successful migration.
    Exchange 2013 may be updated to Exchange 2013 SP1.
    Some users were being randomly prompted with a popup in their outlook client with the following message when connecting with Exchange 2013 server:
    “The Microsoft Exchange Administrator has made a change that requires you quit and restart Outlook”
    Cause
    =======================================
    The issue may be caused due to Public Folders.
    The msExchHomePublicMDB attribute on Exchange 2013 databases was set to deleted legacy public folder object.
    Solution
    =======================================
    Removed the Public Folder from all the Exchange
    2013 Databases. To do it, we can use ADSIedit.msc and remove the arrtibute - msExchHomePublicMDB from all the Databases:
    1. Open ADSIEdit.
    2. Connect to the Configuration container.3.
    Expand Configuration, expand CN=Configuration,DC=Domain,DC=com.4. Expand CN=Services -> CN=Microsoft Exchange -> CN=Domain -> CN=Administrative Groups -> CN=Exchange
    Administrative Group -> CN=Databases.5. In the right hand pane you will see a list of databases.6.
    Right-click the listed database object -> Properties.7. Check whether the msExchHomePublicMDB value is set to an unavailable value. If you see reference to the old database,
    please clear the value.8. Click OK.9. Check the rest of the databases to make sure
    that they are not populated in the same way.
    References:
    https://social.technet.microsoft.com/Forums/en-US/2f736bdd-1c00-4a22-97a5-95faeadf1495/exchange-2013-sp1-users-randomly-prompted-with-the-microsoft-exchange-administrator-has-made-a?forum=exchange2010
    https://social.technet.microsoft.com/Forums/lync/en-US/7a7b3cf8-8761-421c-9d55-6c84e05531c0/the-administrator-has-made-a-change?forum=exchangesvrclients
    https://social.technet.microsoft.com/Forums/en-US/0d71c843-b662-493c-ab6e-30708929ef18/2013-sp1-problem-the-microsoft-exchange-administrator-has-made-a-change-that-requires-you-quit-and?forum=exchangesvrdeploy
    Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

    This one? http://support.microsoft.com/kb/2934750

  • Outlook 2013 users getting "The Microsoft Exchange administrator has made a change that.....

    Hi,
    We are on Exchange 2013 SP1 and we are randomly seeing all Outlook 2013 clients getting "the Microsoft Exchange administrator has made a change..." forcing them to restart Outlook. Outlook 2010 clients are not affected so seems to be related to
    Outlook anywhere.
    Cant see anything in the event log but seeing some 500 errors in the IIS log.
    any ideas on where to look?
    Kristian

    Hi,
    I finally get to resolve my issue with this :
    http://social.technet.microsoft.com/Forums/lync/en-US/7a7b3cf8-8761-421c-9d55-6c84e05531c0/the-administrator-has-made-a-change?forum=exchangesvrclients
    "Please check in ADSIEdit > Configuration >CN=Services > CN=Microsoft Exchange
    > CN=your ORG name > CN=Administrative Groups > CN=Exchange Administrative Group > CN=Databases, please check the attribute “MSEXCHHomePublicMDB”
    of your databases, if they are pointing towards the deleted Objects, please delete the entries."
    Restart the server, restart computers and it should be OK. If not, you might try to create a public folder (http://social.technet.microsoft.com/Forums/en-US/0d71c843-b662-493c-ab6e-30708929ef18/2013-sp1-problem-the-microsoft-exchange-administrator-has-made-a-change-that-requires-you-quit-and?forum=exchangesvrdeploy)

  • The Microsoft Exchange administrator has made a change that requires you to quit and restart outlook.

    Then I get this once outlook is open:
    Cannot start Microsoft Outlook. Cannot open the Outlook window. The set of folders cannot be opened. The operation cannot be performed because the connection to the server is offline".
    Outlook 2013 client
    Exchange 2010 SBS
    I have recreated the profile, doesn't work. Recreating the OST doesn't work. Starting Outlook in any safe mode doesn't work. Disabling hardware acceleration and add-ins does not work.
    repair account does not work -  I get the Congratulations message, confirming it was able to get everything from the server... and when I restart Outlook:
    "The Microsoft Exchange Administrator has made a change that requires you to quit and restart Outlook".
    BJN
    Also the user in question is not getting new mail.
    And I have tried this
    outlook /resetnavpane to no avail.

    Hi,
    Please confirm if the issue happens to all users in your Exchange server.
    In client side, please check the Connection Status when the issue occurs:
    Please open Outlook - press CTRL key - right click on the Outlook icon from right bottom corner taskbar –Connection Status to check the connection.
    Please notice the Server name, status, protocol and Type information.
    In Exchange server, please check whether all Exchange services are started and running in Exchange 2010. Also check whether there is any error information in Event Viewer.
    If the issue only happens to one user, please update the Outlook client with the latest patches and service packs to have a try.
    Regards,
    Winnie Liang
    TechNet Community Support

  • Exchange 2013 - The Microsoft Exchange Transport service is rejecting message submissions because the service continues to consume more memory than the configured threshold

    Noticed at about noon that no emails had been received all day. Began to investigate and found that the MS Exchange Transport service had been set to deny email submission because it was using too much memory on the server (91%). 
    The error message makes me think that we may have been getting used by malware or something similar.“The Microsoft Exchange Transport service is rejecting message submissions because the service continues to consume more memory than the
    configured threshold.” 
    There are also several warning messages that list particular IP addresses and say that a connection from that IP was denied because there were already the maximum number of connections (20). 
    From what I can tell, all of the IP addresses are from Taiwan. 
    The time period for which some emails may be missing is from close of business yesterday ( 4/3/2014) through about 12:45 today (4/4/2014). 
    From the time I spent reading and trying to figure out the error, I think we may need to readjust our throttling policies to prevent this from happening. 
    The exchange server is currently running at 90%+ CPU and 50%+ memory usage the majority of the time, and I’m not sure how to fix it.
    Also, I cannot get into EMS I get a access denied message from the destination computer. (Exchange server) I want to get into there to change the throttling policy back to default, since we disabled it.
    The Error reads:
    The WinRM client cannot process the request. The WinRM client tried to use Kerberos authentication mechanism, but the destination computer <Exchange> returned an 'access denied' error. Change the configuration to allow Kerberos authentication
    mechanism to be used or specify one of the authentication mechanism supported by the server. (How do I do this?) To use Kerberos, specify the local computer name as the remote destination. (I'm trying to use EMS while logged into the local Exchange server)
    Also verify that the client computer and the destination computer are joined to a domain. (Exchange is on our domain, and the computer trying to connect is the same computer) To use basic, specify the local computer name as the remote destination, specify
    Basic authentication and provide user mane and password. Possible authentication mechanisms reported by server.
    At line:1 char:1
    + New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotingTransportException + FullyQualifiedErrorId : AccessDenied,PSSessionOpenFailed
    I assumed control of this exchange system already in place and I do not have much experience with exchange 2013 or server 2012. I do know 2008, but that doesn't help very much in this situation.
    Recent changes to the system:
    About three days ago we switch our sessions policy to allow many more connections, and I believe this caused the issue. This is what I changed it to:
    Made the registry DWORD (32-bit) "Maximum Allowed Sessions Per User" and modified the value to 1000. Location of registry change @ HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem
    I just changed it to 10 from the 1000. I'm hoping this solves this. So far no.
    Also, I am not the best in the shell or command line interfaces. Any help would be wonderful!

    Hi,
    Yes, could be hardware performance issue. Try recycle the Transport process and see if the issue persists.
    Thanks,
    Simon Wu
    TechNet Community Support

  • Get-mailboxdatabasecopystatus -identity DBNAME | fl gives errors "The Microsoft Exchange Replication service encountered an error while attempting to start a replication instance for". DB is mounted and the DB copies are in healthy status.

    We are getting a SCOM alert " Database copy isn''''t keeping up with the changes on the active database copy and has failed."
    When we go to the mailbox server and check we found all the Mailbox DB's are mounted properly and their copies are in healthy state. Further digging to this problem we found that there are no critical events to this DB in the eventviewer.
    When we runt he get-mailboxdatabasecopystatus -identity DBNAME | Fl then in the ErrorMessage section we get error "The Microsoft Exchange Replication service encountered an error while attempting to start a replication instance for . If the copy doesn't
    recover automatically, administrator intervention may be necessary. Error: The directory is not empty."
    ErrorEventID : 4126
    In the event viewer we get a Information event 4114 saying the DB redundancy health check passed and in the details section we get the same error message mentioned above.
    Also we observed that the "MSExchange Replication" counter "Failed" is set to 1 for this perticular DB but is is set to 0 for the other DB's. Tried restarting the MSEXChange replication service but still the "Failed" counter
    is 1 and the SCOM alert is still active.
    The version is Exchange 2010 SP3 UR5
    Any clues???

    Hi,
    From your description, this issue only affect one mailbox datatabase.
    Please use the Update-MailboxDatabaseCopy command to check result.
    If it doesn't work, please dismount your active database copy and check if this is Clean Shutdown, if it's dirty shutdown, please bring to clean shutdown and mount this database copy. Then run the Update-MailboxDatabaseCopy command again to check result.
    Best regards,
    Belinda Ma
    TechNet Community Support

  • The Microsoft Exchange Address Book was unable to log on to Exchange

    I am currently migrating a exchange 2007 to exchange 2013.
    Exchange 2013 is installed on a seperate Windows Server 2012 server.
    Exhange 2007 is installed on a  seperate Windows Server 2003 R2 server.
    I have moved some mailboxes from exchange 2007 to exchange 2013 and also created some new mailboxes on the exchange 2013 server itself. 
    OWA, ActiveSync , IMAP are all working correctly for those mailboxes , but I am not able to connect to outlook with the exchange option (local connection).
    Outlook 2013:
    When I use autodiscover to connect to the exchange server step 1 & 2 are working correctly (establishing network connection & searching for mailbox settings) but on the 3th step (logging on to the mail server) I receive the following error
    The name cannot be resolved. The Microsoft Exchange Address Book was unable to log on to Exchange. Contact you system administrator if the problem persists.
    When I filll in the exchange server manually (using the normal servername server.hq.corp.domain.local not the guid version) the check name resolves correctly and the profile creation is finishing ok. But when I try to open outlook with that profile it gives
    me the following errors :
    with cached exchange mode selected:
    Cannot start Microsoft Outlook. Cannot open the Outlook windows. The set of folders cannot be opened. 
    You must connect to Microsoft Exchange with the current profile before you can synchronize your folders with your Outlook data file (.ost)
    with cached exchange mode deselected:
    Cannot start Microsoft Outlook. Cannot open the Outlook windows. The set of folders cannot be opened. 
    Microsoft Exchange is not available. Either there are network problems or the Exchange server is down for maintenance
    When I use the Microsoft Connectivity Analyzer it fails on the following step:
    Testing the address book "Check Name" operation for user [email protected] against server [email protected]
    An error occured while attempting to resolve the name. Elapsed Milliseconds: 91 Additional Details: The address book bind operation failed with status -2147221231. NSPI Status 2147746065

    Hi,
    Please run the following command in Exchange server to get Exchange GUID:
    Get-Mailbox UserA | FL Identity,ExchangeGuid
    Then open Outlook, click File > Account Settings > Account Settings > Change (If you can’t open Outlook, go to Control Pane > Mail to change it). In Server Settings, import the [email protected] into the Server box and click Check Name
    to have a try.
    If the name is checked successfully but also can’t open the profile, please close Outlook. In the Start menu, Run command (Windows key + R), type or paste
    outlook.exe /resetnavpane  (Note: Make sure there is a space between the words.)
    Then press Enter (or OK button) to restart Outlook
    Regards,
    Winnie Liang
    TechNet Community Support

  • The Microsoft Exchange Mailbox Replication service was unable to process a request due to an unexpected error. Event 1121

    Hello all,
    We migrated our Exchange server from 2003 to 2010. After the mailbox move requests were finished we had one that was stuck. We basically skipped it as we had a lot of other things to finish over the weekend. Here we are a year later, the old exchange server
    is gone and so is an old DC. I am receiving an error every four minutes in event viewer.
    The Microsoft Exchange Mailbox Replication service was unable to process a request due to an unexpected error.
    Request GUID: '3e46b7cb-2ac0-42c1-98e8-57517a19ee40' 
    Database GUID: '5c6c573b-4f45-4ce3-b296-11cf69c2e2b6'
    Error: Unable to find 'OLD Domain Controller' computer information in domain controller 'OLD Domain Controller' to perform the suitability check. Verify the fully qualified domain name..
    I have checked in EMC for move requests. None are listed. I have checked the DCs listed in EMC properties. Old DC is not listed.
    I also ran these commands in shell to attempt to cancel the stuck request.
    Get-MoveRequest -MoveStatus Completed;Pending;InProgress;Failed;CompletedWithWarning;Suspended;Queued;CompletionWithProgress : Remove-MoveRequest
    NO changes. Still throwing error. Any suggestions? I also tried using the guid and shell to look at the move request. Systems replies no such request.

    Hello,
    Please try to restart iis services to check the result.
    If the issue persists, I recommend you ping you DC server on your exchange server to check if your exchange server can communicate with your DC server.
    If there are other DCs, please try to use set-adserversettings cmdlet to specify a DC for your exchange server.
    Set-AdServerSettings
    http://technet.microsoft.com/en-us/library/dd298063(v=exchg.150).aspx
    Besides, please install the lasted rollup to check the result.
    Cara Chen
    TechNet Community Support

  • The Microsoft Exchange Mailbox Replication service was unable to process a request due to an unexpected error. : Error: An Active Directory Constraint Violation error occurred

    Hello,
    We have a multi domain parent child AD domain infrastructure and now we upgraded our exchange from Exchange 2007 to Exchange 2013. Since last few days, we see the below error on the mailbox server event viewer.
    EVENT ID : 1121
    The Microsoft Exchange Mailbox Replication service was unable to process a request due to an unexpected error. 
    Request GUID: '93a7d1ca-68a1-4cd9-9edb-a4ce2f7bb4cd' 
    Database GUID: '83d028ec-439d-4904-a0e4-1d3bc0f58809' 
    Error: An Active Directory Constraint Violation error occurred on <domain controller FQDN>. Additional information: The name reference is invalid. 
    This may be caused by replication latency between Active Directory domain controllers. 
    Active directory response: 000020B5: AtrErr: DSID-0315286E, #1:
    Our Exchange setup is in parent domain, but we keep on getting this error for various domain controllers in each child domain in the same site. We then configured one of the parent domain domain controller on Exchange. Still we are getting this error for
    the configured parent domain DC.
    Verified the AD replication and there is no latency or pending stuffs.
    Any support  to resolve this issue will be highly appreciated. Thank you in advance.
    Regards,
    Jnana R Dash

    Hi,
    In addition to Ed's suggestion, I would like to clarify the following things for troubleshooting:
    1. Please restart IIS at first.
    2. If the issue persists, please ping your DC on your Exchange server to check if Exchange can communicate with DC.
    Hope it helps.
    Best regards,
    Amy Wang
    TechNet Community Support

  • The Microsoft Exchange Mailbox Replication service was unable to process a request due to an unexpected error

    Since demoting a child domain a few days ago, Exchange 2013 is still trying to contact it and as a result generating errors in the application event logs.  I had a similar problem which I solved by removing some old migration batches, now I have a problem
    with the Microsoft Exchange Mailbox Replication service.
    The event logged is:
    The Microsoft Exchange Mailbox Replication service was unable to process a request due to an unexpected error.
    Request GUID: '0b6c0f5a-0563-48e2-8b97-e0781c6cc69a' 
    Database GUID: '23258311-ad29-41c2-a842-522f48baa267'
    Error: Unable to read from Active Directory. --> The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details Unable to find a suitable directory server for
    domain 'admin.riddlesdown.local'.. --> Unable to find a suitable directory server for domain 'admin.riddlesdown.local'..
    Process Microsoft.Exchange.Directory.TopologyService.exe (PID=2280). Exchange Active Directory Provider could not find an available domain controller in domain admin.riddlesdown.local. This event may be caused by network connectivity issues or
    configured incorrectly DNS server.
    The domain doesn't exist in AD Sites and Services, I have removed all traces from DNS but this is still occurring.  When I run Get-ADServerSettings | fl it reports no trace of the domain or a DC that was previously in it.
    How can I stop these events occurring and is it likely to be causing something else not to work correctly.
    We are running Exchange 2013 CU1

    No, that didn't work.  Here are more details:
    Source: MSExchange ADAccess (EventID: 2130)
    Process Microsoft.Exchange.Directory.TopologyService.exe (PID=2280). Exchange Active Directory Provider could not find an available domain controller in domain admin.riddlesdown.local. This event may be caused by network connectivity issues or configured
    incorrectly DNS server.
    Source: MSExchange ADAccess (EventID: 2119)
    Process Microsoft.Exchange.Directory.TopologyService.exe (PID=2280). Error DNS_ERROR_RCODE_NAME_ERROR (0x8007232B) occurred when DNS was queried for the service location (SRV) resource record used to locate a domain controller for domain admin.riddlesdown.local
     The query was for the SRV record for _ldap._tcp.dc._msdcs.admin.riddlesdown.local
     Common causes of this error include the following:
     - The DNS SRV records required to locate a domain controller for the domain are not registered in DNS. These records are registered with a DNS server automatically when a domain controller is added to a domain. They are updated by the domain controller
    at set intervals. This computer is configured to use DNS servers with following IP addresses:
    10.59.100.7
    10.59.100.8
    fec0:0:0:ffff::1Microsoft.Exchange.Directory.TopologyService.exe
    fec0:0:0:ffff::2Microsoft.Exchange.Directory.TopologyService.exe
    fec0:0:0:ffff::3Microsoft.Exchange.Directory.TopologyService.exe
     - One or more of the following zones do not include delegation to its child zone:
    admin.riddlesdown.local
    riddlesdown.local
    local
    . (the root zone)
    Source: MSExchange Mailbox Replication Service (EventID: 1121)
    The Microsoft Exchange Mailbox Replication service was unable to process a request due to an unexpected error.
    Request GUID: '87f4b926-0621-43d3-afeb-fe475ee6d850' 
    Database GUID: '23258311-ad29-41c2-a842-522f48baa267'
    Error: Unable to read from Active Directory. --> The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details Unable to find a suitable directory server for domain 'admin.riddlesdown.local'..
    --> Unable to find a suitable directory server for domain 'admin.riddlesdown.local'..
    Something is cause the Exchange server to go looking for our old domain, but what and why?

  • #550 5.2.0 STOREDRV.Deliver: The Microsoft Exchange Information Store service reported an error.

    Hi, 
    I created a mailbox few days before, everythign was working fine and suddenly when some one tried to send email on that mailbox it bounced back with following error:
    There's a problem with the recipient's mailbox. Microsoft Exchange will not try to redeliver this message for you. Please try resending this message, or provide the following diagnostic text to your system administrator.
    Sent by Microsoft Exchange Server 2007 
    Diagnostic information for administrators:
    Generating server: Mail01.abc.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:9A000000, 17.27161:00000000CC000000000000000600000000000000,
    255.23226:00000000, 255.27962:FE000000, 255.17082:0F010480, 0.26937:94000000, 4.21921:0F010480, 255.27962:FA000000, 255.1494:00000000, 255.26426:FE000000, 4.7588:0F010480, 4.6564:0F010480, 2.17597:00000000, 2.25805:00000000, 4.8936:0F010480, 4.14312:0F010480,
    4.2199:0F010480, 2.25805:00000000, 4.8936:0F010480, 2.22957:00000000, 2.19693:00000000, 2.17917:00000000, 2.27341:00000000, 4.8936:0F010480, 4.17097:0F010480, 4.8620:0F010480, 255.1750:0F010480, 0.26849:0F010480, 255.21817:0F010480, 0.26297:0F010480, 4.16585:0F010480,
    0.32441:0F010480, 4.1706:0F010480, 0.24761:0F010480, 4.20665:0F010480, 0.25785:EC030000, 4.29881:0F010480". ##
    Original message headers:
    Received: from Mailbox.abc.com ([fe80::892d:93d6:b1ac:b70a]) by mail01
     ([10.72.0.95]) with mapi; Fri, 11 Jan 2013 14:04:55 +0500
    Content-Type: application/ms-tnef; name="winmail.dat"
    Content-Transfer-Encoding: binary
    From: Anwar Amjad <[email protected]>
    To: All-HEC <[email protected]>
    Date: Fri, 11 Jan 2013 14:04:53 +0500
    Subject: FW: Suggestions & New Arrival in HEC Library
    Thread-Topic: Suggestions & New Arrival in HEC Library
    Thread-Index: Ac3vHgwR50OLs2BnQuOzo9jWg4e1gQAvJtUw
    Message-ID: <[email protected]>
    References: <[email protected]>
    In-Reply-To: <[email protected]>
    Accept-Language: en-US
    Content-Language: en-US
    X-MS-Has-Attach: yes
    X-MS-TNEF-Correlator: <[email protected]>
    MIME-Version: 1.0
    X-Auto-Response-Suppress: DR, OOF, AutoReply
    After this error, i treid to send email again and there is no error and email was delivered. What was the cause of this error?
    Hasan

    Hi,
    I tried to start seeding again but it is at same status. I will try again and hopefully it will get resolved.
    But, yesterday i ran in to the most complex issue i have ever seen with Exchange.
    There was a unexpected power cut at our datacentre due to which both the nodes went down.
    After that both the nodes came up. But the all 3 databases were dismounted.
    Therefore, i ran Eseutil /mh resulting dirty shutdown.
    I was able to repair 2 databases.
    But the 3rd one was not mounting with below error.
    Microsoft Exchange Error
    Failed to mount database 'Mailbox Database'.
    Mailbox Database
    Failed
    Error:
    Exchange is unable to mount the database that you specified. Specified database: XXXXX\First Storage Group\Mailbox Database; Error code: MapiExceptionJetErrorAttachedDatabaseMismatch: Unable to mount database. (hr=0x80004005, ec=-1216).
    I was able to mount database somehow. There are 7 User mailboxes (Tier 1) on this database.
    All emails sent to the users in this database are bouncing back with the below error.
    This storage groups holds the mailboxes of my Senior Managements. And their mailboxes are down for almost 20 Hrs. I am spinning my head since yesterday but not able to find any fix. Can you please guide me in this concern.
    Best Regards
    K2
    Kapil Kashyap

  • Unable to initialize the Microsoft Exchange Information Store service. - Error 0x96f.

    PLease help, I've rstored from backup three times with no success I'm getting the following error
    "Unable to initialize the Microsoft Exchange Information Store service.   - Error 0x96f. "
    It's LDap related but i have no idea why :-(
    Best Regards Bernhard

    IPv6 had been disabled for months on my SBS 2008 Server running Exchange 2007 SP1.  I ran 40 or so Windows Updates; subsequently, the next morning Exchange was no longer running; topology issues, event ID 2604, 2114 and 2601 were all over my Application
    Log.  After 12 hours of research I found this post; figured it was worth a shot and instantly all my services for Exchange fired up.  Thanks for the tip; I have no idea which update changed what in regards to needing IPv6 enabled, but that silly
    little check mark fixed it.  
    Thank you for sharing your solution! 
    Dan

  • Exchange Server 2013 SP1 CU5 - The Microsoft Exchange Replication service VSS Writer encountered an exception

    We have 2 server DAG with a witness all servers are Server 2012 R2.  Both members of the DAG are Exchange 2013 SP1 CU5.
    We haven't seen this until recently, but during a VSS enabled storage snapshot the following errors occur.  All of which are related to MSExchangeRepl and the Exchange VSS Writer.
    Event IDs 2140, 2026, 2028, 2030.
    The errors start with the 2140 seen here:
    The Microsoft Exchange Replication service VSS Writer encountered an exception in function Microsoft::Exchange::Cluster::ReplicaVssWriter::CReplicaVssWriterInterop::PrepareSnapshot. HResult -2147467259. Exception Microsoft.Mapi.MapiExceptionDatabaseError: MapiExceptionDatabaseError:
    Unable execute Prepare on snapshot. (hr=0x80004005, ec=1108)
    Diagnostic context:
        Lid: 1494    ---- Remote Context Beg ----
        Lid: 56264   StoreEc: 0x1388    
        Lid: 46280   StoreEc: 0x454     
        Lid: 1750    ---- Remote Context End ----
        Lid: 59216  
        Lid: 34640   StoreEc: 0x454     
        Lid: 52264  
        Lid: 46120   StoreEc: 0x454     
       at Microsoft.Mapi.MapiExceptionHelper.InternalThrowIfErrorOrWarning(String message, Int32 hresult, Boolean allowWarnings, Int32 ec, DiagnosticContext diagCtx, Exception innerException)
       at Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message, Int32 hresult, IExInterface iUnknown, Exception innerException)
       at Microsoft.Mapi.ExRpcAdmin.ProcessSnapshotOperation(Guid mdbGuid, SnapshotOperationCode operationCode, UInt32 flags)
       at Microsoft.Exchange.Cluster.Replay.StoreRpcController.<>c__DisplayClass1c.<SnapshotPrepare>b__1b()
       at Microsoft.Exchange.Cluster.Replay.SafeRefCountedTimeoutWrapper.<>c__DisplayClass2.<ProtectedCallWithTimeout>b__0()
       at Microsoft.Exchange.Data.HA.InvokeWithTimeout.Invoke(Action invokableAction, Action foregroundAction, TimeSpan invokeTimeout, Boolean sendWatsonReportNoThrow, Object cancelEvent)
       at Microsoft.Exchange.Cluster.Replay.SafeRefCountedTimeoutWrapper.ProtectedCallWithTimeout(String operationName, TimeSpan timeout, Action operation)
       at Microsoft.Exchange.Cluster.ReplicaVssWriter.CReplicaVssWriterInterop.SnapshotPrepare(Guid dbGuid, UInt32 flags)
       at Microsoft.Exchange.Cluster.ReplicaVssWriter.CReplicaVssWriterInterop.PrepareSnapshot().

    Hi Julez K,
    According to your description, you could try upgrading to CU6.
    In addition, you could review the Exchange Application (App) Event log and the Exchange System (Sys) Event log for errors , and some related resolutions for your reference.
    http://www.symantec.com/business/support/index?page=content&id=TECH209938
    Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety,
    or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.
    Hope it can be helpful.
    Best regards,
    Eric

Maybe you are looking for