Exchange coexistence 2007 2010 and 2013

My environment we have an exchange 2007. We installed 2010, planning to migrate to 2010. We pointed our external namespace to the 2010CAS servers and was just about to migrate to 2010 when it was decided that we would go to Exchange 2013 instead. We installed
Exchange 2013 and then pointed our external namespace to the 2013 CAS. We never migrated a mailbox to 2010. Now that we have started moving mailboxes to 2013 we decided to remove the Exchange 2010 servers. I read that any system/arbitration mailboxes on 2010
had to be moved to 2013 before uninstalling and removing the servers. I ran the command get-mailbox -arbitration and there were 3 mailboxes on the 2010 sever that I moved. I removed the 2010 exch server and now I am getting the following errors when I open
the 2007 EMC.
Microsoft Exchange Warning
Warnings
get-recipient
Completed
Warning:
Object domain.com/Users/SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9} has been corrupted and it is in an inconsistent state. The following validation errors have occurred:
Warning:
The value of property 'RecipientTypeDetails', 8388608, is not defined in the Enum type 'RecipientTypeDetails'.
Warning:
Object domain.com/Users/SystemMailbox{1f05a927-ac20-4215-bc7c-4f1618438874} has been corrupted and it is in an inconsistent state. The following validation errors have occurred:
Warning:
The value of property 'RecipientTypeDetails', 8388608, is not defined in the Enum type 'RecipientTypeDetails'.
Warning:
Object domain.com/Users/FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 has been corrupted and it is in an inconsistent state. The following validation errors have occurred:
Warning:
The value of property 'RecipientTypeDetails', 8388608, is not defined in the Enum type 'RecipientTypeDetails'.
When I run the get-mailbox -arbitration on the 2013 server I get the following mailboxes listed( this is the short version). with no errors. Is there a problem that needs to be resolved.
WindowsEmailAddress
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

Similar Messages

Can Password Reset Work for Non Domain MS Outlook (2007, 2010 and 2013) Clients? NOT OWA, Please

Hi All,
I migrated from Exchange 2007 to Exchange 2013. I have configured expired password reset and it works fine on OWA (for both internally and externally accessed users) and all computers joined to my domain running MS Outlook clients. However, my users wants
it to work for all MS Outlook client of computers not joined to my domain.
How can I go about this? Does expired password reset work on MS Outlook client (2007, 2010 and 2013) computers not joined to the domain?
Please, help

Hello,
Based on my known, I'm afraid that there is no way to reset expired password if your Outlook client computers not joined to the domain.
For external users, we only reset password via owa.
If you have any feedback on our support, please click
here
Cara Chen
TechNet Community Support

Completely different objects in Exchange management consoles 2010 and 2013

HI scripting guys,
First, apologies for the non-specific title. This is not the first incompatibility I am finding (e.g. scripts perfectly working in exchange console 2010 do not work in 2013).
Here is my current problem. I spent a good amount of time, but shame on me could not solve it.
I run the following line:
Get-MailboxPermission $mailbox |select @{Name="Access";Expression={([string]::join(',', $_.AccessRights))}}
and get what I want in EMC 2010:
Access
FullAccess, SendAs, ReadPermission
FullAccess, DeleteItem
FullAccess, DeleteItem
However in EMC 2013 I get the following instead:
Access
System.Collections.ArrayList
System.Collections.ArrayList
System.Collections.ArrayList
Which is a clear sign that at some point the objects are different.
Edit: Just before sending this, I added out-string this way:
Get-MailboxPermission $mailbox |select @{Name="Access";Expression={([string]::join(',', ($_.AccessRights|out-string)))}}
which made the script to work in both consoles but introducing the nasty ellipsis:
Access
FullAccess, SendAs, ReadPermission...
FullAccess, DeleteItem...
FullAccess, DeleteItem...
Piping the above to "format-table -wrap -autosize" is not a solution. It helps with the ellipsis but introduces blank lines:
Access
FullAccess, SendAs, ReadPermission
FullAccess, DeleteItem
FullAccess, DeleteItem
I would greatly appreciate if you can help me with this !
Thank you !

one day later, mission accomplished.
joining strings is not necessary and should be removed in that line in ems 2013 because each "row" is a single string. In contrast in ems 2010 the permissions for each user are an array of strings which need to be joined first in order to user
"replace" further. For example in ems 2013 my actual line now looks like this:
Get-MailboxPermission $mailbox |Select @{Name="User";Expression={$_.User.tostring().replace("UVIC\","")}},@{Name="Access";Expression={$_.AccessRights.replace("Full","Full ").replace("Delete","Delete
")}}| sort user| format-table -auto
and the output looks for example like this:
Access
Full Access, Delete Item
Full Access
Full Access
Which is what I wanted to accomplish in the first place.
=============================================
Now since I could not find ANYTHING online about incompatibilities between Exchange management shell 2010 and Exchange management shell 2013 , let me share one more:
it is about "send on behalf" permissions:
after:
$MBox = Get-Mailbox $MailboxName
$SoB=$Mbox.grantsendonbehalfto
things get different to list the users who has Send on behalf permissions for EMS 2013 and EMS 2010
in 2010:
foreach($S in $SoB){$S.name}
while in 2013:
foreach($S in $SoB){$S}
again in EMS 2013 the things are simpler - $S is just a string

Phone edition Aries Polycom CX600 coexistence - Lync 2010 and 2013

Hi all,
Currently busy with a Lync 2010 > 2013 migration where Aries Lync phones like Polycom CX 600 (using a blend of USB tethering, PIN authentication as well as common area phones) are involved. Phones have a blend of different CU releases ranging from .4066
(CU5) to .4451 (CU14)
User migration must be done in stages. That’s presenting a challenge in that Lync 2010 and 2013 must coexist for some time, yet providing seamless support for Lync phones.
The normal migration scenario will be based on a site-by-site migration: users are moved from 2010 to 2013, DHCP options for that site are changed to provide relevant Lync phones the new Lync 2013 pool parameters. HOWEVER, there is a considerable number
of users travelling across sites, and it’s likely occurrence that a user still on 2010 would travel to a site migrated to 2013 (including phones). And the other way round can also occur.
Based on this, my questions are:
1) Can a Lync 2010 user sign-in (USB tethering) on a phone if DHCP is providing options for Lync 2013?
2) Can a Lync 2010 user sign-in (PIN auth) on a phone if DHCP is providing options for Lync 2013?
3) Can a Lync 2013 user sign-in (USB tethering) on a phone if DHCP is providing options for Lync 2010?
4) Can a Lync 2013 user sign-in (PIN auth) on a phone if DHCP is providing options for Lync 2010?
Also, is there any dependancy on a specific CU version for the sign-in process to succeed? Note all discovery records are strict domain matching compliant.
I was hoping LPE would feature a redirect mechanism like with desktop client but based on the very little specific literature available, that does not seem the case. Any advice would be very welcome.
thanks all.
Alessio Giombini | Microsoft Solutions Architect | Twitter: @AlessioGiombini
Lync 2013 Detailed Design Calculator: try it at http://goo.gl/jU1hZR

Hi,
You can refer to the following link of “Lync 2010 – 2013 Migration: Lync phone edition devices”:
http://unifiedme.co.uk/2013/09/lync-2010-2013-migration-lync-phone-edition-devices/
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.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Outlook displays date of birthdays one day too early in MS Office 2007, 2010 and 2013

Hi
We are supporting several clients that has issues with Outlook. Different versions of Windows, Office and different exchange server versions. Some contacts' birthdays
just "magically" changes to one day too early. I have done extensive research with no answer. I have experienced this issue personally as early as about 2005 or 2006 with a Windows Mobile PDA.
Our local time is GMT +2 without daylight-savings. I have checked the settings in Windows (Vista Pro and Win 7 pro
x86 and x64) and the calendar settings, I have reloaded a couple of pc's, created new profiles, installed new server hardware with newer exchange. Even tried a few off-the-wall ideas like resetting all views to default.
Some users' address books are shared, some not. Some uses Apple, Android, BB or Windows phone, some don't. Some connects through VPN, some don't. Some uses
AVG, Avast, Eset Nod, Forticlient, Mcafee, etc....
I have been fighting this problem for months, and can find no conclusive answer that resolves this.
If I manually open the contact and rectify the date, it will stay correct for a very random time period and then shift
again.
I am about to lose a couple of my biggest clients, and probably my job as well, so I need urgent help.
Please no remarks on OS version, Office version or mobile devices, as this is definitely not the issue.
HELP!

Hi,
Have the users check on OWA, does the issue persist? Please also make sure the timezone of Exchange is also properly configured.
I'm not an expert about Exchange, I hope this blog can be helpful:
http://blogs.technet.com/b/fun_with_powershell/archive/2013/04/30/where-is-the-time-zone-property-stored-in-exchange-2010.aspx
To further dig the problem, rectify the date on owa and drop Outlook for a while(or one day), check the result the next day if the problem will come back.
Regards,
Melon Chen
TechNet Community Support

Documents to Go Password Works on Q10 and Playbook but not on MS Excel 2007,2010 nor 2013 on PC

This has been really frustrating for me. I'm a long time BB user (over 6 years) and want to promote BB and its features, but when straigtht forward features don't work and when it hard to find any information on why they don't work is painful.
The excel file that I have I can edit and save it on my Playbook, and Q10, but when I copy the file to my PC and try to open it, I get an error message from excel that the file is corrupted. I have tried different options (i.e., renaming the file then copying it, trying to open it with excel 2007, 2010, and 2013, using the Web App to open it, and it says that I need Rights Management (RM) to open.) Does anyone know of a means to open without using software to break the password. I appreciate any assistance.

Hey garyr501,
Welcome to the BlackBerry® Support Community Forums.
To better assist you I have a couple questions; If you go to the properties of the Excel file on your PC what is the file format? And does this happen with all Excel files created on the BlackBerry smartphone using Documents to Go?
I look forward to hearing back.
Thanks.
-HB
Come follow your BlackBerry Technical Team on twitter! @BlackBerryHelp
Be sure to click Kudos! for those who have helped you.Click Solution? for posts that have solved your issue(s)!

Lync Phone Edition coexistance with lync 2010 and 2013

Hi Everyone
I am currently planning a coexistent network between Lync 2010 and 2013 as I need to get 2013 out urgently. My question is around the Lync phone edition and how to get the phone to find the front end to register the phone to depending on which lync
pool the user is configured to use. Right now all phones are configured with DHCP and are configured to use the 2010 front end server to get its cert provisioned. I also use the HP 4110 and 4120 phones in the office.
How should I configure DHCP so that I do not cut my user off if they are moved the 2013 pool?
Many Thanks
Joe
Joe

Hi,
Check this old Thread
https://social.technet.microsoft.com/Forums/office/en-US/fca0b7be-124e-4480-ba2f-19ca4eebbd53/phone-edition-aries-polycom-cx600-coexistence-lync-2010-and-2013?forum=lyncvoice
http://unifiedme.co.uk/2013/09/lync-2010-2013-migration-lync-phone-edition-devices/
Whenever you see a helpful reply, click on Vote As Helpful & click on Mark As Answer if a post answers your question.

Exchange 2010 and 2013 coexistence Internal and external URL

Hi all,
been reading alot of threads about Outlook anywhere and virtual directories in co-existence exchange 2010 and 2013.
Still i dont get any smarter.
Here is scenario:
Exchange 2010
Cas1
Cas2
Mailbox1
Mailbox2
Casarray is Exchange.casarray,com ( internal dns pointed to CAS1 in exchange 2010).Seems like by default both exchange 2013 cas servers are added to the casarray.
Exchange 2013
CAS+Mailbox
Cas+Mailbox
DNS
mail.exchange.com pointing to VIP (kemp loadbalancer)
Autodiscover ( pointed to same vip ,kemp load balancer)
Outlook anywhere on all servers (2010 and 2013)
Internal ( pointing to VIP on Kemp)
External ( pointing to external IP,then it passes firewall that again passes to kemp)
Problem we are having is when migrating users from Exchange 2010 - 2013.
Users using Outlook 2010
restart of outlook and mail works fine.
OWA works fine
Active sync fails ( need to inherit permission of users AD object),wait couple of hours then mobile can sync again.)
Users using Outlook 2013
Outlook in disconnected status,only fix is to create new profile.
OWA works fine
Active sync fails ( need to inherit permission of users AD object),wait couple of hours then mobile can sync again.)
Question is,what should be set for internal and external url (active sync,owa,ews)on 2010 and 2013 servers?
Where is the config wrong?
Thanks!
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Off2work

Hi Martina,
did the test as mentioned,even tried both CAS 2013 servers.Flush and registerdns didnt help.
Still Outlook is Connected to the cas.exchange.as (which again Points to 1 of Exchange 2010 servers),
Tried repair Outlook profile,no og.Only fix is to setup New account.
Any more tips?
thanks!
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Off2work

Lync 2010 and 2013 coexistence - DNS

Hi all,
we are planning to upgrade from Lync server 2010 to 2013.During this mode,what is best to do regarding DNS?
Should we just keep existing ones and let Lync server proxy users, or do we need to point dns (internal and external) to the new 2013 server?
Like in Exchange 2010 and 2013 coexistence we had to point all dns to 2013 server,or users wont be proxied.
These are the DNS:
lyncdiscoverinternal
meet,dialin,admin
_sipinternaltls._tcp.domain.com
_sipfederationtls._tcp
sip.domain.com
Other DNS i might forgot?
thanks!
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Off2work

If you don't want to cut everyone over at once, you'll need different FQDNs for external web services between the pools, because mobility and meetings will use them both, regardless of where lyncdiscover and meet point.
If you want to keep the same name, that's fine, but you'll have to cut over in one big shot.
Also, pick a different name for the internal vs external web services. Mobility uses the external name, even when connecting on internal WiFi, so you'll want to redirect requests on port 443 to port 4443 for that and make it available internally.
If you have the same name for the internal web services, then internal requests will also use that path, which can cause issues or at the least route through a reverse proxy for no good reason.
Correct about pool FQDN being unique, also internal and external web service FQDNs unless you move everyone in one shot and don't care.
Everything else is pretty much a repoint when you're ready situation.
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
SWC Unified Communications
This forum post is based upon my personal experience and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

OWA receives mail long before Outlook (Exchange 2013 with Outlook 2010 and 2013)

I recently upgraded my Exchange environment to Exchange 2013 SP1. The Outlook users are now experiencing a delay when receiving email. When they do arrive they appear in batches, often 20-45 minutes after they were sent, from a mailbox on the same server.
Additionally, the mail appears instantly when you monitor the inbox using OWA. The users are experiencing this on both Outlook 2010 and 2013 clients configured in both cached and non-cached modes. This appears to be a problem with Outlook connecting to Exchange.
Any suggestion about how to correct this would be greatly appreciated. Thanks!

Hi,
From your description, when users use OWA, they can receive emails normally. But if they use Outlook 2010 or Outlook 2013, there is a delay in receiving emails.
I recommend you use the Outlook safe mode to determine whether the problem is caused by add-ins. Also, please make sure users have installed the Outlook latest Service Pack.
If the issue persist, please create a new profile and check the result.
Hope it helps.
Best regards,
Amy Wang
TechNet Community Support

Outlook 2010 and 2013 are unable to connect but OWA (and mail routing) works fine

Hi-
Not sure why but this past Sunday (just after DST adjustment) outlook clients (using 2010 and 2013) were unable to connect to an Exchange 2013 server. OWA and mail routing (internal and external) is working fine. I've even tried on multiple machines
and all of them experience the same issue. On a new machine with a fresh version of outlook 2013 installed here is what happens:
Click on Outlook 2013
Click Next until the account setup is displayed.
Name and email is auto-populated
Established network connection is good
Searching for email address settings is good (once the self-signed exchange 2013 cert is accepted)
And then the logging onto the mail server fails. The first pop-up is:
The Connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action.
Clicking "OK" is followed up with a window with the Microsoft Exchange connection info.
It lists Microsoft Exchange server which is populated with: GUID@<domain suffix>
Mailbox which is populated with: =SMTP:<Valid Email address>
On the Exchange Server I have noticed that the Web Management Service (WMSVC) is stopped and will not start. Starting the service outputs:
EventID 7024
"The Web Management Service terminated with the following service-specific error: Unspecified error"
Not really helpful :)
Since this is only happening with Outlook on multiple clients I'm expecting something with Exchange or the ability for outlook to connect to exchange.
Thanks in advance!

Hi
I know this is an old post, but I'm having a very similar issue. I have CU6 installed and all other client connectivity apart from internal Outlook connectivity is working fine. I have distributed the new Self-Signed Certificate and the tested to verify
the clients trust it. I have tried on multiple machine with multiple accounts and none of them connect.
I'm at the stage of reinstalling, but I would rather troubleshoot the problem, just in case ever hit the same wall in the future. I have run Test-OutlookConnectivity with the following output;
RunspaceId : 71f8d740-c499-4bbe-8baf-9cbb12566fb8
Server : PW-SC-01.companyname.local
MonitorIdentity : Outlook.Protocol\OutlookRpcDeepTestProbe\NEW2013
RequestId : 75641e34-aa49-4fce-aad7-181b56dd7b29
ExecutionStartTime : 10/11/2014 13:50:03
ExecutionEndTime : 10/11/2014 13:50:03
Error : Error 0x6ba (The RPC server is unavailable) from ClientAsyncCallState.CheckCompletion:
RpcAsyncCompleteCall
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 2
EEInfo: Status: 0x000006BA
EEInfo: Detection location: 1710
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 1
EEInfo: prm[0]: Long val: 0 (0x00000000)
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 13
EEInfo: Status: 0x000006BA
EEInfo: Detection location: 1352
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 1
EEInfo: prm[0]: Long val: -1073606646 (0xC002100A)
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 14
EEInfo: Status: 0xC002100A
EEInfo: Detection location: 1380
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 2
EEInfo: prm[0]: Long val: 12175 (0x00002F8F)
EEInfo: prm[1]: Unicode string: /rpc/rpcproxy.dll?PW-SC-01.companyname.local:6001
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 14
EEInfo: Status: 0x00010000
EEInfo: Detection location: 1385
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 2
EEInfo: prm[0]: Long val: 8 (0x00000008)
EEInfo: prm[1]: Binary Buffer: [48-1263-10248-1262-126-9632122164676121-3988104-118-11373-61-94
-111-112-98-1217048136942-12272-122-91311550483449324830638543192311910198979999101115115461121199
91111091091154699111461171074830231349524949485349505348484990231349574949485349505348484990483449
324830638543192311910198979999101115115461121199911110910911546991114611710748-12613448136942-1227
2-122-913111503-126115048-1261102-126110-22103-15-109-16-121-119-3121-4-106119-119-9369122-5779121
719-98-24-67-32918-98-236-19-10715326827-76102-61100108-12718-438331-37109-102-57-9942-11389-10374
-77-5-4-107109-11847342222-63-48-7468-17-1067033-56111-33-54-16-105-62-76-1282011-1664-12158-4915-
88-53-9-29-2994-49-54-5211-1364-212121-12396-127-353-396185117-681229-434246070-109818119-4858-128
-106-1279248-49110-44-81-121494199-118-17-106-71106828294-93-110-110-106-415084-127126-45-12331421
-61-2757-24-128-28-25111-52113121-56-98-5821527282-47255245104-111-55-1099747-115-11172-287-12526-
79-12430-119421360-107-6430-5410282-52-51-128533354-116672757-77-75-111-72-118-10114-84484825-40-1
8-70-24-9111-61-5391-8034125-12632-16-19-128112030-8-427523101-93-127-5348-127-5648146385291511-14
4325-9648-127-110638529174-127-11848-127-121-12623119101989799991011151154611211999111109109115469
911146117107-1262211211945115994548494611211999111109109115461081119997108-12626651171161116810511
59911111810111446808767111109109115461081119997108-12626651171161116810511599111118101114468087671
11109109115469911146117107-12613808767111109109115461081119997108-12613808767111109109115469911146
11710748196385293741248106843615573148126385291911-14248048136942-12272-122-913115503-12611081-930
6613-74953718-12745-14-25-94107-80-5-45-2231536-1728-12897-8587577-1252765-892896-83-10267-7926-20
-9841-1079-12-29-4315671111357-684036-40-5129-91-24-461066-12306-65-9118-89115191071-30-20-1067161
-83-91-74105-931649-48-96126-13-71-118-8967567-40-64-104-113-31-51-102357125100-50113-103-113123-9
873-627067-25-908-10131118125122-71-115-37-1850-1055851-31410-77-7312-36848124-26104-10711043-2048
-48-12666611759121127-2960-1571-9-95-98-1036911610-74221-32-25114-108749933-7147562114-3635-101-81
-1058-73108-61-78-128-116-715155112714-37-18-84-8331-2716-1174257-76-5-1598-15-12875-98-7329632178
-10714-123-6312212-1028359-56-76-683-873987-2120-845954-7617-71-57999828110], size=926
Exception : Microsoft.Exchange.Rpc.ServerUnavailableException: Error 0x6ba (The RPC server is unavailable)
from ClientAsyncCallState.CheckCompletion: RpcAsyncCompleteCall
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 2
EEInfo: Status: 0x000006BA
EEInfo: Detection location: 1710
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 1
EEInfo: prm[0]: Long val: 0 (0x00000000)
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 13
EEInfo: Status: 0x000006BA
EEInfo: Detection location: 1352
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 1
EEInfo: prm[0]: Long val: -1073606646 (0xC002100A)
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 14
EEInfo: Status: 0xC002100A
EEInfo: Detection location: 1380
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 2
EEInfo: prm[0]: Long val: 12175 (0x00002F8F)
EEInfo: prm[1]: Unicode string: /rpc/rpcproxy.dll?PW-SC-01.companyname.local:6001
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 14
EEInfo: Status: 0x00010000
EEInfo: Detection location: 1385
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 2
EEInfo: prm[0]: Long val: 8 (0x00000008)
EEInfo: prm[1]: Binary Buffer: [48-1263-10248-1262-126-9632122164676121-3988104-118-11373-61-94
-111-112-98-1217048136942-12272-122-91311550483449324830638543192311910198979999101115115461121199
91111091091154699111461171074830231349524949485349505348484990231349574949485349505348484990483449
324830638543192311910198979999101115115461121199911110910911546991114611710748-12613448136942-1227
2-122-913111503-126115048-1261102-126110-22103-15-109-16-121-119-3121-4-106119-119-9369122-5779121
719-98-24-67-32918-98-236-19-10715326827-76102-61100108-12718-438331-37109-102-57-9942-11389-10374
-77-5-4-107109-11847342222-63-48-7468-17-1067033-56111-33-54-16-105-62-76-1282011-1664-12158-4915-
88-53-9-29-2994-49-54-5211-1364-212121-12396-127-353-396185117-681229-434246070-109818119-4858-128
-106-1279248-49110-44-81-121494199-118-17-106-71106828294-93-110-110-106-415084-127126-45-12331421
-61-2757-24-128-28-25111-52113121-56-98-5821527282-47255245104-111-55-1099747-115-11172-287-12526-
79-12430-119421360-107-6430-5410282-52-51-128533354-116672757-77-75-111-72-118-10114-84484825-40-1
8-70-24-9111-61-5391-8034125-12632-16-19-128112030-8-427523101-93-127-5348-127-5648146385291511-14
4325-9648-127-110638529174-127-11848-127-121-12623119101989799991011151154611211999111109109115469
911146117107-1262211211945115994548494611211999111109109115461081119997108-12626651171161116810511
59911111810111446808767111109109115461081119997108-12626651171161116810511599111118101114468087671
11109109115469911146117107-12613808767111109109115461081119997108-12613808767111109109115469911146
11710748196385293741248106843615573148126385291911-14248048136942-12272-122-913115503-12611081-930
6613-74953718-12745-14-25-94107-80-5-45-2231536-1728-12897-8587577-1252765-892896-83-10267-7926-20
-9841-1079-12-29-4315671111357-684036-40-5129-91-24-461066-12306-65-9118-89115191071-30-20-1067161
-83-91-74105-931649-48-96126-13-71-118-8967567-40-64-104-113-31-51-102357125100-50113-103-113123-9
873-627067-25-908-10131118125122-71-115-37-1850-1055851-31410-77-7312-36848124-26104-10711043-2048
-48-12666611759121127-2960-1571-9-95-98-1036911610-74221-32-25114-108749933-7147562114-3635-101-81
-1058-73108-61-78-128-116-715155112714-37-18-84-8331-2716-1174257-76-5-1598-15-12875-98-7329632178
-10714-123-6312212-1028359-56-76-683-873987-2120-845954-7617-71-57999828110], size=926
at Microsoft.Exchange.Rpc.ClientAsyncCallState.CheckCompletion()
at Microsoft.Exchange.Rpc.ExchangeClient.ClientAsyncCallState_Connect.End(IntPtr&
contextHandle, TimeSpan& pollsMax, Int32& retryCount, TimeSpan& retryDelay, String& dn
PoisonedCount : 0
ExecutionId : 63105129
SampleValue : 33.5194
ExecutionContext : Mailbox logon verification
EMSMDB.Connect()
Task produced output:
- TaskStarted = 10/11/2014 13:50:03
- TaskFinished = 10/11/2014 13:50:03
- Exception = Microsoft.Exchange.Rpc.ServerUnavailableException: Error 0x6ba (The RPC
server is unavailable) from ClientAsyncCallState.CheckCompletion: RpcAsyncCompleteCall
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 2
EEInfo: Status: 0x000006BA
EEInfo: Detection location: 1710
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 1
EEInfo: prm[0]: Long val: 0 (0x00000000)
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 13
EEInfo: Status: 0x000006BA
EEInfo: Detection location: 1352
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 1
EEInfo: prm[0]: Long val: -1073606646 (0xC002100A)
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 14
EEInfo: Status: 0xC002100A
EEInfo: Detection location: 1380
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 2
EEInfo: prm[0]: Long val: 12175 (0x00002F8F)
EEInfo: prm[1]: Unicode string: /rpc/rpcproxy.dll?PW-SC-01.companyname.local:6001
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 14
EEInfo: Status: 0x00010000
EEInfo: Detection location: 1385
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 2
EEInfo: prm[0]: Long val: 8 (0x00000008)
EEInfo: prm[1]: Binary Buffer: [48-1263-10248-1262-126-9632122164676121-3988104-118-11373-61-94
-111-112-98-1217048136942-12272-122-91311550483449324830638543192311910198979999101115115461121199
91111091091154699111461171074830231349524949485349505348484990231349574949485349505348484990483449
324830638543192311910198979999101115115461121199911110910911546991114611710748-12613448136942-1227
2-122-913111503-126115048-1261102-126110-22103-15-109-16-121-119-3121-4-106119-119-9369122-5779121
719-98-24-67-32918-98-236-19-10715326827-76102-61100108-12718-438331-37109-102-57-9942-11389-10374
-77-5-4-107109-11847342222-63-48-7468-17-1067033-56111-33-54-16-105-62-76-1282011-1664-12158-4915-
88-53-9-29-2994-49-54-5211-1364-212121-12396-127-353-396185117-681229-434246070-109818119-4858-128
-106-1279248-49110-44-81-121494199-118-17-106-71106828294-93-110-110-106-415084-127126-45-12331421
-61-2757-24-128-28-25111-52113121-56-98-5821527282-47255245104-111-55-1099747-115-11172-287-12526-
79-12430-119421360-107-6430-5410282-52-51-128533354-116672757-77-75-111-72-118-10114-84484825-40-1
8-70-24-9111-61-5391-8034125-12632-16-19-128112030-8-427523101-93-127-5348-127-5648146385291511-14
4325-9648-127-110638529174-127-11848-127-121-12623119101989799991011151154611211999111109109115469
911146117107-1262211211945115994548494611211999111109109115461081119997108-12626651171161116810511
59911111810111446808767111109109115461081119997108-12626651171161116810511599111118101114468087671
11109109115469911146117107-12613808767111109109115461081119997108-12613808767111109109115469911146
11710748196385293741248106843615573148126385291911-14248048136942-12272-122-913115503-12611081-930
6613-74953718-12745-14-25-94107-80-5-45-2231536-1728-12897-8587577-1252765-892896-83-10267-7926-20
-9841-1079-12-29-4315671111357-684036-40-5129-91-24-461066-12306-65-9118-89115191071-30-20-1067161
-83-91-74105-931649-48-96126-13-71-118-8967567-40-64-104-113-31-51-102357125100-50113-103-113123-9
873-627067-25-908-10131118125122-71-115-37-1850-1055851-31410-77-7312-36848124-26104-10711043-2048
-48-12666611759121127-2960-1571-9-95-98-1036911610-74221-32-25114-108749933-7147562114-3635-101-81
-1058-73108-61-78-128-116-715155112714-37-18-84-8331-2716-1174257-76-5-1598-15-12875-98-7329632178
-10714-123-6312212-1028359-56-76-683-873987-2120-845954-7617-71-57999828110], size=926
at Microsoft.Exchange.Rpc.ClientAsy
FailureContext :
ExtensionXml :
ResultType : Failed
RetryCount : 0
ResultName : 75641e34aa494fceaad7181b56dd7b29-OutlookRpcDeepTestProbe/NEW2013
IsNotified : False
ResultId : 1748063
ServiceName : InvokeNow
StateAttribute1 : Momt
StateAttribute2 : UnknownIssue
StateAttribute3 : PW-SC-01.companyname.local
StateAttribute4 : Unknown
StateAttribute5 : {C54AD38D-1E00-4F53-ABAE-26518C3FF82F}
StateAttribute6 : 0
StateAttribute7 : 0
StateAttribute8 : 0
StateAttribute9 : 0
StateAttribute10 : 0
StateAttribute11 : Momt
StateAttribute12 :
StateAttribute13 : VgEAVAdXaW5kb3dzQwBBCEtlcmJlcm9zTA9QV0NPTU1TXG5hdGhhbmhVLlMtMS01LTIxLTIwNTc0OTEwMzItMzE4NDA2NDk3OC
0xNTQ2MTE0ODM1LTI2MzJHHQAAAAcAAAAtUy0xLTUtMjEtMjA1NzQ5MTAzMi0zMTg0MDY0OTc4LTE1NDYxMTQ4MzUtNTEzBwAA
AAdTLTEtMS0wBwAAAAdTLTEtNS0yBwAAAAhTLTEtNS0xMQcAAAAIUy0xLTUtMTUHAADAE1MtMS01LTUtMC0zNDc3ODcxMTMHAA
AALlMtMS01LTIxLTIwNTc0OTEwMzItMzE4NDA2NDk3OC0xNTQ2MTE0ODM1LTQxODcHAAAALVMtMS01LTIxLTIwNTc0OTEwMzIt
MzE4NDA2NDk3OC0xNTQ2MTE0ODM1LTUxMgcAAAAuUy0xLTUtMjEtMjA1NzQ5MTAzMi0zMTg0MDY0OTc4LTE1NDYxMTQ4MzUtND
E3NAcAAAAuUy0xLTUtMjEtMjA1NzQ5MTAzMi0zMTg0MDY0OTc4LTE1NDYxMTQ4MzUtMzU3MAcAAAAuUy0xLTUtMjEtMjA1NzQ5
MTAzMi0zMTg0MDY0OTc4LTE1NDYxMTQ4MzUtNDEyMgcAAAAuUy0xLTUtMjEtMjA1NzQ5MTAzMi0zMTg0MDY0OTc4LTE1NDYxMT
Q4MzUtMTE2NAcAAAAuUy0xLTUtMjEtMjA1NzQ5MTAzMi0zMTg0MDY0OTc4LTE1NDYxMTQ4MzUtMTE0MQcAAAAuUy0xLTUtMjEt
MjA1NzQ5MTAzMi0zMTg0MDY0OTc4LTE1NDYxMTQ4MzUtNDE1MwcAAAAuUy0xLTUtMjEtMjA1NzQ5MTAzMi0zMTg0MDY0OTc4LT
E1NDYxMTQ4MzUtNDE0NQcAAAAtUy0xLTUtMjEtMjA1NzQ5MTAzMi0zMTg0MDY0OTc4LTE1NDYxMTQ4MzUtNTE4BwAAAC5TLTEt
NS0yMS0yMDU3NDkxMDMyLTMxODQwNjQ5NzgtMTU0NjEx
StateAttribute14 :
StateAttribute15 :
StateAttribute16 : 0
StateAttribute17 : 0
StateAttribute18 : 0
StateAttribute19 : 0
StateAttribute20 : 0
StateAttribute21 : /o=companyname/ou=first administrative group/cn=Recipients/cn=NathanH
StateAttribute22 : EMSMDB.Connect()
StateAttribute23 : https://pw-sc-01.companyname.local:444/rpc/rpcproxy.dll?PW-SC-01.companyname.local:6001
StateAttribute24 : Negotiate
StateAttribute25 : [33]10/11/2014 13:50:03 [FAILED!] EMSMDB.Connect();
Identity : fcd6159dd8fe42aebf10100cc4934356
IsValid : True
ObjectState : New

ActiveSync with 2010 and 2013 coexistance

I have setup Exchange 2013 within my network that has Exchange 2010 already running. Everything is working with coexistance exept for ActiveSync.
A user can access OWA just fine it shows the Exchange 2013 login but direct them to the mailbox of 2010 fine.
I have created a new user under 2013 and migrated a user from 2010 to 2013 and with either of them I can access active sync just fine. So if the user is in the 2013 database it works fine. Its the proxy or redirect to 2010 that isn't
working.
The log appears to show the connection and then has a error of 500. See here.
2015-01-13 13:06:32 192.168.128.5 POST /Microsoft-Server-ActiveSync/default.eas User=rogerssa&DeviceId=ApplDNQLK1S3FF9R&DeviceType=iPhone&Cmd=Ping&CorrelationID=<empty>;&ClientId=DESTC9PC0KXF0GJ0HZA&cafeReqId=ea63a976-9574-4ebc-b508-dcb4fd213e18; 443
domain\rogerssa 50.158.150.99 Apple-iPhone6C1/1201.365 - 500 0 0 46
2015-01-13 13:06:32 192.168.128.5 POST /Microsoft-Server-ActiveSync/default.eas User=rogerssa&DeviceId=ApplDNQLK1S3FF9R&DeviceType=iPhone&Cmd=Ping&CorrelationID=<empty>;&ClientId=DESTC9PC0KXF0GJ0HZA&cafeReqId=c144c115-d97f-41d4-96f4-dd132c227db3; 443
domain\rogerssa 50.158.150.99 Apple-iPhone6C1/1201.365 - 500 0 0 31
If I could just get this fixed it would make my migration move along.

Can you check if the authentication methods in both CAS (2010 and 2013) are equal? If there are different methods, the AES connection will fail and drop the error 500.
If that is not the issue, please use the site http://www.exrca.com and upload the results to th thread.
Have a nice day!
Microsoft Premier Field Engineer - http://www.comunicacionunificada.cl

How to enable the SharePoint 2010 and 2013 Developer Dashboard for specific WebApplication or Sitecollection?

How to enable the SharePoint 2010 and 2013 Developer Dashboard for specific Web Application or Site collection(not for all Web Application)?
Vishal Goyal

Hi Vishal,
I don't think there is option for specific site collection or web application,but there is option of enabling developer dashboard on specific master pages and that is one on of the way you could do it.
look article on below link to enable developer dashboard on specific master pages
https://msdn.microsoft.com/en-us/library/office/ff512745%28v=office.14%29.aspx?f=255&MSPPError=-2147217396
Let me know if this helps.
Thanks
Bhism

Language pack resource files in SharePoint 2010 and 2013

Hi,
We are translating the Language pack for SharePoint 2013 in Albanian language.
Comparing to SharePoint 2010 resource files, there are less of them in SharePoint 2013 but they are bigger in size. Are they merged and in that case which of them are merged? Any other info relating to this issue would help
me a lot.
Thanks,

Hi,
Although the 2010 and 2013 are different versions, most of the files contain the same words. I just thought that maybe someone knows if and if yes, which of the files are joined together in 2013 since there are less files in 2013 but bigger in size. All
this because that Albanian LP doesn't exist and we have to translate another LP.
If someone has had experience in translating Language Packs in SharePoint 2010 or 2013, any information would help me a lot.
Thank you

Hebrew typing problem in Word 2010 and 2013 in Windows 7 64bit

Hello,
When I am trying in Word (2010 and 2013 32bit installation) to edit a line (inserting a new word for instance in the middle of the line) or start a new line in RTL or LTR Hebrew paragraph I must first type the SPACE char and then to type any other letter. When
I try firs to type a regular letter it is not typed.
It happens only if the Word is installed on a Windows 7 professional 64bit version on my HP 8570p laptop. I formatted the laptop and installed the same OS but 32bit, installed the Office 2010 and the Word works perfect in any language. I formatted the Laptop
again, re-installed again the 64bit OS, installed the Office 2010 again and same symptom - cant type Hebrew letters if not starting with SPACE. If I try to edit the same paragraph with English letters it works OK. When I start a new line with English letters
it works OK. It seem that this symptom happens when the type direction is right-to-left (after ALT-right SHIFT stroke).
This symptom is only in Word. In PowerPoint, in Excel or any other Office application it works fine.
When using Word 365 (not installed localy even I have a local Word 2013 installation) the Hebrew typing is working fine.
I didn't change the default setting options of the Word not after installing the 32bit OS nor the 64bit OS.
I prefer to use the 64bit OS and not the 32bit OS so I do not consider moving to 32bit OS.

Hello,
When I am trying in Word (2010 and 2013 32bit installation) to edit a line (inserting a new word for instance in the middle of the line) or start a new line in RTL or LTR Hebrew paragraph I must first type the SPACE char and then to type any other letter. When
I try firs to type a regular letter it is not typed.
It happens only if the Word is installed on a Windows 7 professional 64bit version on my HP 8570p laptop. I formatted the laptop and installed the same OS but 32bit, installed the Office 2010 and the Word works perfect in any language. I formatted the Laptop
again, re-installed again the 64bit OS, installed the Office 2010 again and same symptom - cant type Hebrew letters if not starting with SPACE. If I try to edit the same paragraph with English letters it works OK. When I start a new line with English letters
it works OK. It seem that this symptom happens when the type direction is right-to-left (after ALT-right SHIFT stroke).
This symptom is only in Word. In PowerPoint, in Excel or any other Office application it works fine.
When using Word 365 (not installed localy even I have a local Word 2013 installation) the Hebrew typing is working fine.
I didn't change the default setting options of the Word not after installing the 32bit OS nor the 64bit OS.
I prefer to use the 64bit OS and not the 32bit OS so I do not consider moving to 32bit OS.

Exchange coexistence 2007 2010 and 2013

Similar Messages

Maybe you are looking for