Corrupt a Mailbox / mailbox database (exchange 2010)

Is there a way out to corrupt a mailbox or database itself for lab testing in exchange 2010 ?
Aditya Mediratta

Hi,
Based on my knowledge, most corruptions are caused by MAPI clients that fail to update properties to the satisfaction of MRS. But I haven't found a direct method to corrupt a mailbox for a test. Your understanding will be appreciated.
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

Similar Messages

Reconnect Disconnected Mailbox Server for Exchange 2010- VBScript

Hello everyone. I am trying to run a program where a user can reconnect a disconnected mailbox through 2010 Exchange Servers.
This is an example of the method that I need except this is for 2003 servers but I am looking for 2010. If you can, please help me out.
VBScript Example
'===============================================================
' Purpose: Reconnect a Diconnected Exchange_Mailbox
' to another user object
' Change: cComputerName [string] the computer to access
' Change: cDisconnectedMbox [string] the disconnected mailbox name
' Change: cConnectTo [string] the user account to connect the mailbox to
'===============================================================
On Error Resume Next
Dim cComputerName
Dim cDisconnectedMbox
Dim cConnectTo
Dim objWMIService
Dim oDisMbox
Dim mBox
Const cWMINameSpace = "root/MicrosoftExchangeV2"
Const cWMIInstance = "Exchange_Mailbox"
cComputerName = "MyComputerNETBIOSName"
cDisconnectedMbox = "TestUserA"
cConnectTo = "TestUserB"
strWinMgmts = "winmgmts:{impersonationLevel=impersonate}!//"& _
cComputerName&"/"&cWMINameSpace
Set objWMIService = GetObject(strWinMgmts)
Set oDisMbox = objWMIService.ExecQuery("Select * from Exchange_Mailbox WHERE MailboxDisplayName = '" & cDisconnectedMbox & "'",,48)
For each mBox in oDisMbox
mBox.Reconnect cConnectTo
Wscript.Echo "Mailbox Reconnected"
Next

On Exchange 2010 you need to use the Exchange Management Shell so you need to use the connect-mailbox cmdlet see
http://technet.microsoft.com/en-us/library/bb123490(v=exchg.141).aspx
If your trying to do this from managed code then you can run that cmdlet from managed code see
http://msdn.microsoft.com/en-us/library/bb332449(v=exchg.80).aspx and
http://blogs.technet.com/b/exchange/archive/2009/11/02/3408653.aspx
Cheers
Glen

Database mailbox grow quickly Exchange 2010 SP3

Hello.
Since we migrated from Exchange 2003 to
2010, the growth of our databse mailbox
is excessive. We have a total mailbox
size hovering around 75 GB and the size of
the database is 120 Gb.
Mailbox quotas are very
limited and 90% of users move emails
from mailbox to PST personal folders.
I get the impression that the space freed by removing
emails or move them to PST
is not claimed as White Space
and hence the excessive growth of
the DB.
I have seen that there is a fix to solve this
problem for versions prior to Exchange 2010
SP3 but the current version we have
implemented and it is with SP3.
Any idea to find out what is happening and
how to fix it?
Thanks in advance and best regards.
tzariksi

Hi.
I have reviewed the total size the mailboxes
and Dumpster with the following command:
Get-MailboxDatabase"MailboxDatabase"|Get-MailboxStatistics|SortTotalItemSize-desc|ftdisplayname,TotalItemSize,itemcount,TotalDeletedItemSize
The result is:
•Total Mailbox size(GB)->82,213
•Total Dumpster size(GB)->14,531
•Total ->97,344
The size of the DB using the command:
Get-MailboxDatabase-Status|Sort-ObjectDatabaseSize-Descending|Format-Table
Name,DatabaseSize,AvailableNewMailboxSpace
Is as follows:
Name
DatabaseSize                            AvailableNewMailboxSpace
MailboxDatabase         107.4 GB (115,302,531,072 bytes)        1.438 GB (1,544,486,912 bytes)
The actual disk size occupied
by the MailboxDatabase is->112GB
What else may be using the space in theMailboxDatabase?.
Thanks and regards.
Pedro.
tzariksi

Removing mailbox server from Exchange 2010 DAG - Node not fully cleaned up

Hi,
We are in the process of decommissioning some old Exchange 2010 servers. I have just attempted to remove one of our mailbox servers and have received a number of errors, related to its removal from the DAG.
I have already removed the Public Folder replicas and all mailbox database copies. I then tried to evict the server from the DAG and received the following warning:
I then ran the command that was recommended, from another server and in an administrative command prompt:
I have looked in this log on both the server I ran the command on, a CAS server, and the mailbox server itself and can see no evidence of this error 2 that is listed here.
If I run the Powershell command to look at the DAG I cannot see it there any more. I am assuming that this error message might only be an issue if I was planning on re-using this server somewhere else in Exchange or perhaps adding this server to another
DAG. But I just want to decommission it.
Can anyone put my mind at rest as to whether this is a genuine concern or not. If not my next step is to uninstall Exchange 2010 from this server and turn it off.

Hi Belinda,
I get the following:
[PS] C:\Windows\system32>Get-DatabaseAvailabilityGroup
Name Member Servers
Operational Servers
DAG01 {WSR-EX-01, WSR-EX-101, WSR21}
It doesn't look like that server is part of the DAG any more as far as I can see. I just can't explain that error message reported from the cluster command. As far as I can see the server is isolated. I already removed its database copies as a pre-requisite
before removing it from the DAG as per this guide:
http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_27039933.html
I found a nice little script that gave reports on your Public Folder configuration and it highlighted that some of our folders were not being replicated properly across our mailbox servers. This helped me in removing these services from the server.
It is currently doing nothing at this time as far as Exchange Services are concerned.

New mailbox move request Exchange 2010 : queued

I have deployed new Exchange 2010 server in Exchange 2003 Organization. It is simple setup one Exchange 2003 and New Exchange 2010.
I was trying to move mailbox from Exchange 2003 to 2010 and it has status of QUEUE “indefinetly”.. I have tried several mailboxes and result is the same.
Then I decided to create new database on Exchange 2010 sever. I have crate new mailbox on Exchange 2010 sever, send and receive some emails. And then try to move mailbox to new database. Same results.
I run test MSR replication and is ok.
I have increase msr LOGGING TO Maximum, no errors. I have rebooted server several times, no differences…

Hi,
Based on the description, status of mailbox move request from Exchange 2003 to Exchange 2010 is "indefinitely".
Please make sure mailbox databases in Exchange 2010 and Exchange 2003 are mounted.
Have you moved mailbox using the New-MoveRequest with the BadItemLimit and the AcceptLargeDataLoss parameters? If not, it's worth to do it again. Before you create a new move request, please check if there is any previous move request. If there is, please
clear the previous move request and then move the mailbox.
If the issue persists, please try to move mailbox to another database in Exchange 2003 and then move to Exchange 2010 to check the result.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Connecting CAS Server to Mailbox Server in Exchange 2010

Currently, we are running the CAS,HUB,and Mailbox role on the same Exchange 2010 SP3 server. At some point I would like to separate this out. Should be an easy question: what command gets/sets the settings which points a CAS array to a mailbox database?
So I want CAS_SERVER1 -> DB1,DB2 and CAS_SERVER2 -> DB3,DB4

Hi,
In Exchange 2010, Outlook look for the “rcpclientaccessserver” attribute on the user’s Database to find the CAS server. You can manually set it by the following command:
Set-mailboxdatabase –rcpclientaccessserver xxx
Thanks,
Simon Wu
TechNet Community Support

Auto-Mapping Exchange 2013 Mailboxs in an Exchange 2010 Mailbox

We're in the middle of migrating mailboxes from Exchange 2010 to Exchange 2013. Many of our users have Auto-Mapped mailboxes as well. In my testing, I've found that I cannot Auto-Map a mailbox that's on Exchange 2013 in a Exchange 2010 mailbox. I can manually
add it and it works fine. Is this by design with this type of coexistence or is there a fix for it? Our current Exchange 2010 environment is at SP3 with UR2.
Orange County District Attorney

This issues is fixed in UR5 so suggest you to upgrade Exchange 2010 to SP3 UR5.
Reference Thread: http://social.technet.microsoft.com/Forums/exchange/en-US/a2aa4163-f74b-401f-aec5-13324e6b29c8/exchange-2010-mailbox-not-able-to-access-automapped-exchange-2013-cu3-mailbox?forum=exchangesvradmin
Blog |
Get Your Exchange Powershell Tip of the Day from here

OOF not working for mailboxes homed on Exchange 2010 server during migration

Hi There
I'm troubleshooting an issue during a exchange 2010 to exchange 2013 migration where the OOF is not working for users homed on the exchange 2010 mailbox servers. This applies to users using outlook 2010 and outlook 2013 .OWA works perfectly and you can also
enable OOF via exchange powershell.
Users homed on the exchange 2013 servers does not have any issues.
The exchange 2010 servers is on SP3 rollup 4 and the 2013 servers on SP1 only without any rollups installed.
So my question will be - have anyone experienced this issue during migration and will patching the exchange 2010 servers to rollup 5 or 6 and the exchange 2013 to sp1 rollup 5 fix the OOF issue then? If requested the client to patch to these levels, but
in the meantime I'm checking if anyone else had similar issues.
Any pointers will be welcome.

Hi ,
1.Please check the problematic exchange 2010 user account can able to access the ews virtual directory internal url and you can check that via browser's.It will prompt for the user name and password , please provide that .
EWS url wopuld be like - https://mail.youdomain.com/EWS/Exchange.asmx
2.Then the second step would be autodiscover check for the problematic user account.you can find that via test email configuration .There you came to know whether outlook is fetching up the proper url for ews and autodiscover.
3.Then please un check the proxy settings in browsers and check the same.
4.please use the command to check the auto discover
test-outlookwebservices
Please check the below links also.
http://exchangeserverpro.com/exchange-2013-test-outlook-web-service/
http://www.proexchange.be/blogs/exchange2007/archive/2009/07/14/your-out-of-office-settings-cannot-be-displayed-because-the-server-is-currently-unavailable-try-again-later.aspx
http://port25guy.com/2013/07/20/user-cannot-set-an-out-of-office-in-exchange-20102013-or-eventid-3004-appears-in-your-event-log/
http://www.theemailadmin.com/2010/06/exchange-server-2010-out-of-office/
Regards
S.Nithyanandham
Thanks S.Nithyanandham

Owa working but outlook cant connecting to the new mailbox in Hosted exchange 2010 SP1

hi i recently join one organization they having Hosted Exchange 2010 Sp1 i created one new organization Unit and created
new MailBox but didnt give any permissions so when i try to connect to OWA then i log in and send and recive e-mails but when i try to connect to Outlook it say the name not found ...........
please help me

Hi sorry for so late respons i was on leaves .
new User not connected automatically getting the message "user name Not found " also when i try to connect manually the error message " there is problem with the security certificate. the name on the security certificate is invalid or does not match ..." also
Outlook some problem with some old Mailboxes
from Exerca i get the following errors i.e Certificate related
The Microsoft Connectivity Analyzer is attempting to test Autodiscover for [email protected].
Autodiscover was tested successfully.
Additional Details
Elapsed Time: 2927 ms.
Test Steps
Attempting each method of contacting the Autodiscover service.
The Autodiscover service was tested successfully.
Attempting to test potential Autodiscover URL https://xyz.co.uk/AutoDiscover/AutoDiscover.xml
Testing of this potential Autodiscover URL failed.
Additional Details
Elapsed Time: 417 ms.
Test Steps
Attempting to resolve the host name xyz.co.uk in DNS.
The host name resolved successfully.
Additional Details
Testing TCP port 443 on host xyz.co.uk to ensure it's listening and open.
The port was opened successfully.
Additional Details
Testing the SSL certificate to make sure it's valid.
The SSL certificate failed one or more certificate validation checks.
Additional Details
Test Steps
The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server xyz.co.uk on port 443.
The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
Additional Details
Validating the certificate name.
Certificate name validation failed.
Tell me more about this issue and how to resolve it
Additional Details
Attempting to test potential Autodiscover URL https://autodiscover.xyz.co.uk/AutoDiscover/AutoDiscover.xml
Testing of this potential Autodiscover URL failed.
Additional Details
Test Steps
Attempting to resolve the host name autodiscover.xyz.co.uk in DNS.
The host name resolved successfully.
Additional Details
Testing TCP port 443 on host autodiscover.xyz.co.uk to ensure it's listening and open.
The port was opened successfully.
Additional Details
Testing the SSL certificate to make sure it's valid.
The SSL certificate failed one or more certificate validation checks.
Additional Details
Elapsed Time: 270 ms.
Test Steps
The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server autodiscover.xyz.co.uk on port 443.
The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
Additional Details
Validating the certificate name.
Certificate name validation failed.
Tell me more about this issue and how to resolve it
Additional Details
Attempting to contact the Autodiscover service using the HTTP redirect method.
The Autodiscover service was successfully contacted using the HTTP redirect method.
.......................... Please help me how to resolve

PF Migration, Multiple Databases (Exchange 2010 to Exchange 2013)

Hey All
We have 3x Public Folder Databases in our exchange environment, I have successfully migrated one of the public folder databases over and see all of your content.
My question is this:
Do I need to run the migration process for each database? or if I run it for one database will that migrate all Public Folder data over to 2013?
Thanks,
Robert
Robert

Hi Robert,
The key point here is to collect and migrate all public folders from PF databases. In most cases several PF databases just have replicas of the same Public Folders, so no need for processing each database specifically.
Enumerate all Public Folders you have in previous Exchange version, compare the list to the Public Folders you have migrated to Exchange 2013 using the most up to date source. If both lists match each other - you have migrated all necessary public folders
and you don't need to process other PF databases.
▲ Vote if Helpful / Mark if Answer
MCSE: Messaging 2013 Charter / Private Cloud / Server Infrastructure
MaximumExchange.ru

Move mailbox from exchange 2010 2003 , Transient error MapiExceptionLogonFailed has occurred.

We are currently migrating from Exchange 2003 to Exchange 2010, same domain.
We have successfully moved some mailboxes from exchange 2003 to exchange 2010 without any problems.
Now we need to move 1 mailbox back from exchange 2010 to exchange 2003.
After creating the moverequest it stucks on 0% and the log shows the error below.
After using Bing I found this post -> http://social.technet.microsoft.com/Forums/exchange/en-US/ef41ae05-8816-4c0c-968a-c48f0e3d50b5/move-mailbox-back-from-exchange-2010-to-exchange-2003-failure?forum=exchangesvrdeploylegacy
This suggest ->
After I give FULL permissions to each Mailbox Stores on Exchange 2003 server, I was able to move my mailbox back onto the Exchange 2003 server. In details:
Simply right click Storage Group\Mailbox Store and go to Security, in there you may see Exchange Servers group already there, if no add it in, then give it FULL permissions! and thats it!
Create a new move request but still stuck on 0% and error as below
20-3-2014 16:32:10 [ex2010p11] 'contoso.com/Users/exadmin' created move request.
20-3-2014 16:32:11 [ex2010p21] The Microsoft Exchange Mailbox Replication service 'exchangep21.contoso.com' (14.3.151.0 caps:07) is examining the request.
20-3-2014 16:32:11 [ex2010p21] Connected to target mailbox 'Primary (82b54f9e-27ff-44d2-9142-f949d567e1e7)', database 'ex2003\Basic\Basic', Mailbox server 'ex2003.contoso.com' Version 0.0 (Build 7638.0).
20-3-2014 16:32:11 [ex2010p21] Connected to source mailbox 'Primary (82b54f9e-27ff-44d2-9142-f949d567e1e7)', database 'EX2010DB', Mailbox server 'ex2010p20.contoso.com' Version 14.3 (Build 174.0).
20-3-2014 16:32:11 [ex2010p21] Request processing started.
20-3-2014 16:32:11 [ex2010p21] Transient error MapiExceptionLogonFailed has occurred. The system will retry (1/60).
Error details: MapiExceptionLogonFailed: Unable to make connection to the server. (hr=0x80040111, ec=1010)
Diagnostic context:
Lid: 13720 dwParam: 0x6D9 Msg: EEInfo: Flags: 0
Lid: 11672 dwParam: 0x6D9 Msg: EEInfo: NumberOfParameters: 4
Lid: 8856 dwParam: 0x6D9 Msg: EEInfo: prm[0]: Unicode string: ncacn_ip_tcp
Lid: 8856 dwParam: 0x6D9 Msg: EEInfo: prm[1]: Unicode string: ex2003
Lid: 12952 dwParam: 0x6D9 Msg: EEInfo: prm[2]: Long val: -545057711
Lid: 12952 dwParam: 0x6D9 Msg: EEInfo: prm[3]: Long val: 382312662
Lid: 45169 StoreEc: 0x824
Lid: 44273
Lid: 59431 EMSMDB.EcDoConnectEx called [length=163]
Lid: 34855 EMSMDB.EcDoConnectEx returned [ec=0x3F2][length=56][latency=0]
Lid: 56945
Lid: 59431 EMSMDB.EcDoConnectEx called [length=163]
Lid: 34855 EMSMDB.EcDoConnectEx returned [ec=0x3F2][length=56][latency=0]
Lid: 59505 StoreEc: 0x3F2
Lid: 52465 StoreEc: 0x3F2
Lid: 60065
Lid: 33777 StoreEc: 0x3F2
Lid: 59805
Lid: 52209 StoreEc: 0x3F2
Lid: 56583
Lid: 52487 StoreEc: 0x3F2
Lid: 19778
Lid: 27970 StoreEc: 0x3F2
Lid: 17730
Lid: 25922 StoreEc: 0x3F2
at Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message, Int32 hresult, SafeExInterfaceHandle iUnknown, Exception innerException)
at Microsoft.Mapi.ExRpcConnection.Create(ConnectionCache connectionCache, ExRpcConnectionCreateFlag createFlags, ConnectFlag connectFlags, String serverDn, String userDn, String user, String domain, String password, String httpProxyServerName,
Int32 ulConMod, Int32 lcidString, Int32 lcidSort, Int32 cpid, Int32 cReconnectIntervalInMins, Int32 cbRpcBufferSize, Int32 cbAuxBufferSize, Client xropClient, Byte[] clientSessionInfo, TimeSpan connectionTimeout)
at Microsoft.Mapi.MapiStore.OpenMapiStore(String serverDn, String userDn, String mailboxDn, Guid guidMailbox, Guid guidMdb, String userName, String domainName, String password, String httpProxyServerName, ConnectFlag connectFlags, OpenStoreFlag
storeFlags, CultureInfo cultureInfo, Boolean wantRedirect, String& correctServerDN, ClientIdentityInfo clientIdentity, String applicationId, Client xropClient, Boolean wantWebServices, Byte[] clientSessionInfo, TimeSpan connectionTimeout)
at Microsoft.Mapi.MapiStore.OpenMailbox(String serverDn, String userDn, String mailboxDn, String userName, String domainName, String password, String httpProxyServerName, ConnectFlag connectFlags, OpenStoreFlag storeFlags, CultureInfo cultureInfo,
WindowsIdentity windowsIdentity, String applicationId)
at Microsoft.Exchange.MailboxReplicationService.MapiUtils.OpenSystemMailbox(Guid mdbGuid, String serverDN, String dcName, NetworkCredential cred, String& systemMailboxDn)
at Microsoft.Exchange.MailboxReplicationService.LocalMailbox.OpenSystemMailbox()
at Microsoft.Exchange.MailboxReplicationService.LocalMailbox.Microsoft.Exchange.MailboxReplicationService.IMailbox.SaveSyncState(Byte[] key, String syncStateStr)
at Microsoft.Exchange.MailboxReplicationService.MailboxWrapper.<>c__DisplayClass57.<Microsoft.Exchange.MailboxReplicationService.IMailbox.SaveSyncState>b__56()
at Microsoft.Exchange.MailboxReplicationService.ExecutionContext.Execute(GenericCallDelegate operation)
at Microsoft.Exchange.MailboxReplicationService.MailboxWrapper.Microsoft.Exchange.MailboxReplicationService.IMailbox.SaveSyncState(Byte[] key, String syncState)
at Microsoft.Exchange.MailboxReplicationService.MailboxCopierBase.ClearSyncState()
at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.<>c__DisplayClass23.<CleanupOrphanedDestinationMailbox>b__22(MailboxMover mbxCtx)
at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.ForeachMailboxContext(MailboxMoverDelegate del)
at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.CleanupOrphanedDestinationMailbox(Object[] wiParams)
at Microsoft.Exchange.MailboxReplicationService.CommonUtils.CatchKnownExceptions(GenericCallDelegate del, FailureDelegate failureDelegate)
Error context: --------
Operation: IMailbox.SaveSyncState
OperationSide: Target
Primary (82b54f9e-27ff-44d2-9142-f949d567e1e7)
Key: F2FA63B0116C564EA4C598D69786443D9E4FB582FF27D2449142F949D567E1E7E0CA914F6695624C98892FA527AAA91E
SyncStateLength: 0
20-3-2014 16:32:41 [ex2010p21] The Microsoft Exchange Mailbox Replication service 'ex2010p21.contoso.com' (14.3.151.0 caps:07) is examining the request.
20-3-2014 16:32:41 [ex2010p21] Connected to target mailbox 'Primary (82b54f9e-27ff-44d2-9142-f949d567e1e7)', database 'ex2003\Basic\Basic', Mailbox server 'ex2003.contoso.com' Version 0.0 (Build 7638.0).
20-3-2014 16:32:41 [ex2010p21] Connected to source mailbox 'Primary (82b54f9e-27ff-44d2-9142-f949d567e1e7)', database 'EX2010DB', Mailbox server 'ex2010p20.contoso.com' Version 14.3 (Build 174.0).
20-3-2014 16:32:41 [ex2010p21] Request processing started.
20-3-2014 16:32:41 [ex2010p21] Transient error MapiExceptionLogonFailed has occurred. The system will retry (2/60).

Hello，
When you move mailbox from exchange 2010 to exchange 2003, please check if the following situations exist:
http://technet.microsoft.com/en-us/library/dd638157(v=exchg.141).aspx
Before you move mailbox again, please clear the previous move request.
I recommend you use EXBPA to check your exchange server 2003 and exchange 2010.
Please check if inheritable permission is missing on the mailbox store on Exchange Server 2003.
Cara Chen
TechNet Community Support

Exchange 2010 Mailbox move issue

Hi
I have moved around 100 mailboxes from DB to other DB in the same server.
Now all these mailboxes are in Disconnected state.
The problem is, these mailboxes are appearing twice under disconnected mailbox window. One is from old db and other is from New DB.
The reason for the same shows for Old DB is Soft Deleted and for new DB is Disabled.
IS this a general behaviour? Currently when the user access the mailbox, it says its locked for moving.
How can renable these mailboxes and make user accessible? Do i need to wait till retention period over?
I have set the deleted mailboxes rentention to 2 days. Will this make mailboxes active after 2 days?
regards Sundaresan.C

Yes this is general behavour; Soft Deleted mailboxes - introduced in Exchange 2010 SP1
more info can be found here; http://technet.microsoft.com/en-us/library/dd298174(v=exchg.141).aspx
This example purges the soft-deleted mailbox for Phil from mailbox database MBD01.
Remove-StoreMailbox -Database MBD01 -Identity Phil -MailboxState SoftDeleted

Error in moving exchange 2010 mailboxes to Exchange 2013 SP1 during migration

Dear All,
We were running Exchange 2010 SP3 with MBX/HT/CAS role in single server. Now we are migrating our exchange 2010 to Exchange 2013 SP1. After configuring co-existence and during the mailbox move from Exchange 2010 to Exchange 2013 SP1, we are facing below
error. Please help to troubleshot. As per our search on net, people were suggesting that it can be due to not able to resolve NetBIOS name. We checked same and we are able to ping both servers by NetBIOS and FQDN names.
[PS] C:\Windows\system32>New-MoveRequest -Identity
'[email protected]' -TargetDatabase "CI-DB01"
MapiExceptionNetworkError: Unable to make connection to the server. (hr=0x80004005, ec=2423)
Diagnostic context:
    Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 1722
    Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 323
    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0
    Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 0
    Lid: 62184
    Lid: 16280   dwParam: 0x0 Msg: EEInfo: ComputerName: n/a
    Lid: 8600    dwParam: 0x0 Msg: EEInfo: ProcessID: 6004
    Lid: 12696   dwParam: 0x0 Msg: EEInfo: Generation Time: 0414-08-21T09:10:43.8970000Z
    Lid: 10648   dwParam: 0x0 Msg: EEInfo: Generating component: 18
    Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 1237
    Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 313
    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0
    Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 0
    Lid: 62184
    Lid: 16280   dwParam: 0x0 Msg: EEInfo: ComputerName: n/a
    Lid: 8600    dwParam: 0x0 Msg: EEInfo: ProcessID: 6004
    Lid: 12696   dwParam: 0x0 Msg: EEInfo: Generation Time: 0414-08-21T09:10:43.8970000Z
    Lid: 10648   dwParam: 0x0 Msg: EEInfo: Generating component: 18
    Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 10060
    Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 311
    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0
    Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 3
    Lid: 12952   dwParam: 0x0 Msg: EEInfo: prm[0]: Long val: 22964
    Lid: 15000   dwParam: 0x0 Msg: EEInfo: prm[1]: Pointer val: 0x0
    Lid: 15000   dwParam: 0x0 Msg: EEInfo: prm[2]: Pointer val: 0xFE01A8C000000000
    Lid: 62184
    Lid: 16280   dwParam: 0x0 Msg: EEInfo: ComputerName: n/a
    Lid: 8600    dwParam: 0x0 Msg: EEInfo: ProcessID: 6004
    Lid: 12696   dwParam: 0x0 Msg: EEInfo: Generation Time: 0414-08-21T09:10:43.8970000Z
    Lid: 10648   dwParam: 0x0 Msg: EEInfo: Generating component: 18
    Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 10060
    Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 318
    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0
    Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 0
    Lid: 53361   StoreEc: 0x977
    Lid: 51859
    Lid: 33649   StoreEc: 0x977
    Lid: 43315
    Lid: 58225   StoreEc: 0x977
    Lid: 39912   StoreEc: 0x977
    Lid: 54129   StoreEc: 0x977
    Lid: 50519
    Lid: 59735   StoreEc: 0x977
    Lid: 59199
    Lid: 27356   StoreEc: 0x977
    Lid: 65279
    Lid: 52465   StoreEc: 0x977
    Lid: 60065
    Lid: 33777   StoreEc: 0x977
    Lid: 59805
    Lid: 52487   StoreEc: 0x977
    Lid: 19778
    Lid: 27970   StoreEc: 0x977
    Lid: 17730
    Lid: 25922   StoreEc: 0x977
    + CategoryInfo          : NotSpecified: (:) [New-MoveRequest], RemoteTransientException
    + FullyQualifiedErrorId : [Server=Exch01,RequestId=f6886977-92f1-4148-991b-aa76b449aff5,TimeStamp=8/21/2014 9:1
   0:43 AM] [FailureCategory=Cmdlet-RemoteTransientException] 7FCC37,Microsoft.Exchange.Management.RecipientTasks.New
MoveRequest
+ PSComputerName        : Exch01.domain.local
Please help as we are stuck here!!
Thanks in advance!!

Can yo ping server by name not by FQDN? e.g. ping server1.
Make sure firewall/antivirus not blocking communication. Disable antivirus and try
Thanks,
MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Exchange 2013 / 2010 co-existence - Outlook won't connect to Exchange 2010 mailboxes

Greetings! I have a lab set up at home where I have been testing co-existence of Exchange 2013 and 2010 for a future corporate upgrade project.
I am running into some odd behavior. Any mailbox that has been migrated to Exchange 2013 works just fine, however, when I try to set up Outlook for a mailbox still on Exchange 2010 I receive errors. OWA works just fine for these Exchange
2010 mailboxes, it is just Outlook that has the problem. This is what I am running into:
1. Outlook uses autodiscover to locate server settings. It fails at the 'logging on to mail server' step saying that Exchange isn't available; Outlook must be connected, etc.
2. It then gives me the settings box for Exchange server and Mailbox. This is auto populated with one of the Exchange 2013 servers (there are 3 of them, all have both MBX and CAS role). If I then change the server to the Exchange 2010 CAS server,
and hit 'check names', it underlines the very same entries (like it found them this time) that were there initially and goes on to finish the configuration.
3. When I launch Outlook with this Exchange 2010 user, it fails to open with the error message that the set of folders couldn't be opened.
I've been doing as much research on this as I can. I've tried disabling IPv6 to no avail. It seems as if perhaps the issue is with Exchange 2013 proxying the request back to the Exchange 2010 servers but I am not sure what to check in that regards.
Any suggestions? Thanks in advance!

Hi,
Don´t disable IPV6 on an Exchange Server, it is, in my opinion not necessary - also applies for AD.
You can use your original SSL Cert for your new Ex 2013 environment.
In dns you want two host A records: mail.domain.com and autodiscover.domain.com
On your 2013 set your internal and external virtual directories to mail.domain.com
leave autodiscover and Powershell alone.
Also set the autodiscover URI to your Certificate name ie. mail.domain.com
Set-ClientAccessServer -Identity "YourCASServer" -AutoDiscoverServiceInternalUri "https://mail.domain.com/autodiscover/autodiscover.xml"
Thanks. I wanted to give some additional info before I run any commands. I currently have an A record for autodiscover and it is pointed to the Exchange 2013 DAG/cluster IP. I have a 3 entries for mail.domain, for DNS round robin; basically
it is listed 3 times for the IP of each of my Exchange 2013 servers. Does any of this sound problematic?

Exchange 2010 mailbox not able to access auto-mapped Exchange 2013 CU3 mailbox

Hi,
We are in co-existence with Exchange 2010 SP3 and Exchange 2013 CU3.
Outlook Anywhere and Autodiscover pointed towards Exchange 2013 CAS servers. Everything works fine irrespective where is mailbox is located Exchange 2010 or 2013.
When I tried to access auto-mapped mailbox from Exchange 2010 as primary mailbox accessing auto-mapped Exchange 2013 mailbox "Cannot expand the folder. 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".
Exchange 2013 OutlookAnywhere "Externalclientauthenticationmethod" is Basic and "Internalclientauthencitcationmethod" is NTLM. Everything is setup as per the Tech-net recommendations.
Checked both these articles but still it is not working:
http://support.microsoft.com/kb/2839517
http://support.microsoft.com/kb/2834139
Please let me know if there are any other ideas.
Raman

Hi,
I recommend you refer to the following articles to troubleshoot the issue:
Troubleshooting Mailbox Auto-Mapping : Autodiscover
Details about the shared mailbox that is to be accessed will be returned to the Outlook client by the autodiscover process. This is really handy to know if you are ever in the position where you need to troubleshoot why the auto-mapping feature isn’t working
correctly
Troubleshooting Mailbox Auto-Mapping : Permissions
When you use either the Exchange Management Console or the Exchange Management Shell to grant a user with full access permission against another mailbox, permissions changes are made to allow this as you might expect. Certain Active Directory attributes
are also updated to reflect both the Active Directory account of the mailbox being accessed as well as the Active Directory account of the accessing mailbox. Specifically, you can check the contents of the msExchDelegateListLink and msExchDelegateListBL Active
Directory attributes to see these details and it is worth checking these if you have any suspicions that things aren’t working correctly.
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support

Corrupt a Mailbox / mailbox database (exchange 2010)

Similar Messages

Maybe you are looking for