Exchange 2007 - 2010 Outlook doesn't autodiscover after mailbox move

We currently are in the process of migrating from Exchange 2007 to 2010. When I move a mailbox to 2010, Outlook (2010 in this case), fails to connect to the new environment. Restarting outlook does not help. I am forced to change the
servername in the mail applet. How can we make this happen automagically?

That URL points to the autodiscover.xml page on the 2010 CAS servers. Returns the typical
<?xml version="1.0" encoding="utf-8"
?>
- <Autodiscover
xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
- <Response>
- <Error Time="01:46:57.9070185"
Id="814683946">
<ErrorCode>600</ErrorCode>
<Message>Invalid Request</Message>
<DebugData
/>
</Error>
</Response>
</Autodiscover>

Similar Messages

Exchange 2007/2010 Console doesn't show up Exchange 2007 Databases after RBAC Implementation

I have implemented a RBAC model after which Exchange 2010/2007 Console won't show up Exchange 2007 Mailbox Databases.
Everything was working fine up until the Users were members of "Exchange Recipient Administrators" Group.
I have created Custom Roles based on PArent Roles, Mail Recipients, Mail Recipient Creation, Distribution Groups & Public Folders and assigned that to a universal security group "Helpdesk operations". I removed membership for Helpdesk operations
from "Exchange Recipient Administrators" Group and assigned the Custom Roles to "Helpdesk Operations" using the cmdlet below:
New-ManagementRoleAssignment "Custom Role" -SecurityGroup "HelpDesk Operations"
Exchange 2010 console shows Exchange 2010 Databases but not Exchange 2007 DAtabases. Exchange 2007 console doesn't show up any databases on New-Mailbox and simply displays a message "No Objects Found".
Even Get-MailboxDatabase REturns blank output on Exchange 2007 SHell. Please help me with this and let me know in case if there is something that i need to be looking at!
any help on this is much appreciated.
M.P.K ~ ( Exchange | 2003/2007/2010/E15(2013)) ~~ Please remember to click “Vote As Helpful" if it really helps and "Mark as Answer” if it answers your question, “Unmark as Answer” if a marked post does not actually answer your question. ~~ This
Information is provided is "AS IS" and confers NO Rights!!

Hi,
I recommend you use the following cmdlet and check the result.
Get-MailboxDatabase -Server "Exchange 2007 server name"
In my environment, if I don't specify the Server parameter on Exchange 2010 Management Shell, Exchange 2007 mailbox database can't be displayed. If I specify the Server parameter, Exchange 2007 mailbox database will be displayed.
What's more, please check if the account you use has been delegated the Exchange View-Only Administrator role.
Here is a thread for your reference.
Get-MailboxDatabase
http://technet.microsoft.com/en-us/library/bb676367(v=exchg.80).aspx
Hope it helps.
Best regards,
Amy
Amy Wang
TechNet Community Support

Exchange OWA Page Blank For Random Users After Mailbox Moves

We have three Exchange server. msexch1, msexch2, msexch3. msexch1 is currently offline. msexch1 and msexch have the CAS and MBX roles installed and are in a DAG. We moved all mailboxes from msexch1 to the other two servers. Since then we have users reporting
that when they logon to owa they get a blank page. The resulting url is owa/auth.owa. The domain we use is exchange.ourdomain.com. The fqdn of each exchange server is msexch2.ourdomain.com, etc. We use round robin dns for our exchange servers, therefore we
have two entries for exchange.ourdomain.com. For the purposes of this question lets say the ip of msexch2.ourdomain.com is 10.10.10.52 and msexch3.ourdomain.com is 10.10.10.53 and we have two entries in our dns for exchange.ourdomain.com, one for 10.10.10.52
and the other 10.10.10.53.
When a user experiences this issue I have found that when I ping exchange.ourdomain.com to determine which exchange server they are "connected" to; if I force them to use the other one they are then able to access owa just fine. For example, I
have a user whom is getting a blank page after they logon to owa. I ping exchange.ourdomain.com which returns 10.10.10.52 for an ip address, which tells me they are connected to msexch2.ourdomain.com. When I enter in the url https://msexch3.ourdomain.com/owa
to force them to logon using the other server, they are able to owa owa without any issues. When I use the url https://msexch2.ourdomain.com they receive a blank page after logon (as expected because this is the server they are trying to contact via dns exchange.ourdomain.com)
I have tried recreating both owa virtual directories which did nothing. I am at my wits end here and would greatly appreciate any assistance.

Hi,
According to your description, I understand that OWA get blank after move mailbox to another mailbox server, and you deploy DNS round robin in your environment.
If I misunderstand you concern, please do not hesitate to let me know.
It may be caused by OWA proxy cannot work correctly, please try below steps to double check:
1. Get a mailbox place in msexch3 and login OWA with
https://msexch3.ourdomain.com/owa.
2. Get other mailbox place in msexch2 and login OWA with
https://msexch3.ourdomain.com/owa.
If the steps 2 cannot proxy URL to https://msexch2.ourdomain.com/owa, it may be the key reason.
Please clarify the environment of your Exchange:
1. Which version are you used?
2. Check the authentication of OWA: Get-OwaVirtualDirectory | FL Identity,*URL*,*Auth*
OWA is configured to use integrated windows authentication on each virtual directory, and the external URL under is blank.
Also, please run below command to double check the health of Outlook Web App service:
Get-ServerHealth “msexch3” |?{$_.AlertValue –Eq “Unhealth”}
Thanks
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Allen Wang
TechNet Community Support

Exchange 2007 and outlook 2010 frequent disconnects

Hi,
Im having issues on SBS 2008 with exchange 2007 and outlook 2010.
Every so often users disconnect and outlook then requires them to put there password in but if you restart outlook all is fine till the next time its random aswell.
I have checked in IIS if windows and basic authentication are enabled which they are.
If i dont use outlook anywhere i still get this problem.
I have looked on the internet but everything i try doesnt seem to help me any ideas ?
Thanks

Hi,
Before going further, would you please let me confirm whether all users (with all Outlook) encounter this same
issue? Did you install any update or any third-party application on the server before this issue occurred?
à
Im having issues on SBS 2008 with exchange 2007 and outlook 2010.
Would you please let me confirm whether installed Exchange Server 2007 SP2 (or SP3)? Did you install all necessary
Update Rollups for the Exchange Server 2007?
Please type
outlook.exe /safe in RUN to start Outlook in Safe Mode, then check if this issue still exists. Meanwhile, please navigate to the website which contains Exchange Virtual Directories in IIS Manager, then enable kernel-mode authentication for each directory
and monitor the result.
If any update, please feel free to let me know.
Hope this helps.
Best regards,
Justin Gu

Exchange 2007/2010/2013 UM coexistence

We currently have an Exchange 2007/2010 environment in production along with Lync 2010 (UM provided).
I have installed a number of Exchange 2013 server and will be migrating ( over a LONG time ) to the new system.
In the meantime, I need to have all services co-existent across all three Exchange versions.
It looks like I have everything workign now except UM for Lync 2010.
I tried adding the Exchange 2013 server into the existing 2007/2010 dial plan and am having issues.
Here is what i did.
EAC
- Installed certificate on all Exchange 2013 servers
- Enabled Unified Messaging on all the servers
- Select server
- Set TLS
- Associated 2007/2010 Dial Plan
- Set UM service on certificate on all servers
- Restarted UM service
- Did the above for all MB and CAS servers
- Wait about an hour
Lync fails to send calls to voice mail, giving me events 45024 and 44022 on the Lync FE stating that Lync could not connect to the Exch MB servers and the attempt to connect to UM failed.
Any suggestions?
Do I need to rerun the following ?
- Exchucutl.ps1
- Ocsumutil.exe
Thanks!
Tom

When I go into the Exchange EAC Unified messaing / UM IP Gateway screen I see the Um IP Gateways configured in the legacy Exchange systems and had hoped that these existing gateway definitions would suffice.
Does exchucutil.ps1 need to run from a 2013 Exch server to initialize these gateways in Exch 2013?
On my fist attempt, VM was failing for my 2007/2010 users. I had not even started to test with a 2013 user. I successfully backed out by dis-associating the dial plan in the Exchange EAC console from all the Exch 2013 servers.
If I run exchucutil.ps1, try again, and it fails, what is my backout plan? Do I need to rerun exchucutil.ps1 on a legacy Exchange system? or will merely dis-associateing the diual plan in Exchange 2013 again suffice.
Thanks Tom
After typing this, I realize that this is probably more of an Exchange question so I posted the question there. I apologize now for any cross posting misbehavour.
Posted to -
http://social.technet.microsoft.com/Forums/exchange/en-US/6fbfad13-3480-46c6-804d-3757110e61c7/exchange-um-coexistence-exch-20072010-and-exch-2013?forum=exchangesvrunifiedmessaging

Outlook 2011 for Mac with Microsoft Exchange 2007/2010

Hi,
For already a fews days I am troubleshooting a Mac Outlook 2011 <> Exchange sync issue. I've got exact the same symptoms in two totally different environments.
- Environment one:
Exchange 2007 SP3 RU 14 (8.3.379.2)
Outlook 2011 14.4.7
- Environment two:
Exchange 2010 SP1 RU 8 (14.1.438.0)
Outlook 2011 14.4.7
Problem:
Autodiscover and EWS synchronisation test from Microsoft Exchange Connectivity Analyzer is succesfull. Configuring an new (Exchange) e-mail account with Outlook2007/2010/2013 fully based on autodiscover works with no errors.
Configure Outlook 2011 based on autodiscover when connected to the internal LAN works. Configure Outlook 2011 based on autodiscover or by hand doesn't work from WAN.
I am unable to synchronize Outlook 2011 with Exchange when WAN connected (No error in logging). I am able to synchronize OS X Mail (Default OSX Mail client) with the same Exchange server.
Conclusion: the autodiscover function that Outlook 2011 uses does not work from WAN, the autodiscover function that Outlook 2007/2010/2013 and Exchange Connectivity Analyzer is using does work from WAN. Do I need to configure something special for synchronization
with Outlook 2011 other than explained above when working from WAN?
When testing EWS with 3th party tooling(EWS Editor) and Exchange Connectivity Analyzer everything is working as it should be. (all mailbox data is shown). If you need any more information about the context I am happy to provide.
Regards,
Mikkie van Falier

Hey hpujary.
Welcome to the BlackBerry Support Community Forums.
At this time, only contacts can be synchronized with BlackBerry Link software and a BlackBerry 10 Smartphones. The functionality to provide more options for PIM synchronization may be added in the future. I cannot say for certain that the issue outlined in KB27248 is resolved for BlackBerry 10 Smartphones as the functionality does not exist to confirm.
Cheers.
-Sawks
Come follow your BlackBerry Technical Team on Twitter !@BlackBerryHelp
Be sure to click Like! for those who have helped you.
Click Accept as Solution for posts that have solved your issue(s)

Troubleshooting and Introduction for Exchange 2007/2010 AutoDiscover - Details about "Test E-mail AutoConfiguration"

AutoDiscover is a new feature in Exchange 2007, to provide access to Microsoft Exchange features (OAB, Availability service, UM) for Outlook 2007
clients or later.
We can determine whether problems related to AutoDiscover via OWA.
For example:
OOF is not working in Outlook Client but it is working in OWA.
When we realized this issue is not related to Outlook Client side and network side after performing some troubleshooting steps, it should be something
abnormal on AutoDiscover.
There is a common tool to check AutoDiscover in Outlook, Test E-mail AutoConfiguration.
Today, we will introduce AutoDisocver and “Test E-mail AutoConfiguration” in details. Hope it is helpful for AutoDiscover troubleshooting and self-learning.
1. Differences between “Test E-mail AutoConfiguration” and other tools
The “Test-OutlookWebServices” cmdlet allows us to test the functionality of the following services:
Autodisocver
Exchange Web Services
Availability Service
Offline Address Book
When we run “Test-OutlookWebServices”, it returns all the web services’ states.
However, some information are useless for some scenarios.
For example:
We just want our Exchange 2010 Server working internally. So it is unnecessary to enable Outlook Anywhere.
However, when we run “Test-OutlookWebServices”, it returns Outlook Anywhere errors because the Outlook Anywhere does not need to been enabled.
In contrast, using “Test E-mail Autodiscover” is more intuitive.
If there is any problems, it will return error code from the test result, like 0x8004010F etc. We can do some research from TechNet articles or MS
KBs.
Although it is difficult to say where the specific problem is just via the error codes, we can combine with IIS logs to perform troubleshooting and
find the root of problem.
2. How to use “Test E-mail AutoConfiguration” Tool
a. Open Outlook, we can find there is an Outlook Icon at the right bottom of System tray. Holding down “Ctrl” button and right click the Outlook Icon, we will see “Test E-mail
AutoConfiguration” option. Please see Figure 01.
Figure 01
b. Click “Test E-mail AutoCofiguration” and input user name, uncheck the “Use Guessmart” and “Secure Guessmart Authentication” checkboxes, then click “Test”. Please see
Figure 02.
Figure 02
c. “Test E-mail AutoConfiguration” result panel and log panel. Please see Figure 03 and Figure 04.
Figure 03
Figure 04
3. How to understand “Test E-mail AutoConfiguration” result
According to the Figure 03, we found there are many URLs in the “Test E-mail AutoConfiguration” result panel. Let us understand the details of these
URLs.
If we these URLs are not the correct ones, we can re-setting or re-creating them via commands.
- Internal OWA URL:
https://vamwan310.vamwan.com/owa/
OWA internal access.
- External OWA URL:
https://mail.vamwan.com/owa/
OWA external access.
- Availability service URL:
https://vamwan310.vamwan.com/EWS/Exchange.asmx
Free/Busy, OOF and meeting suggestions.
- OOF URL:
https://vamwan310.vamwan.com/EWS/Exchange.asmx
Out of Office access.
- OAB URL:
https://vamwan310.vamwan.com/OAB/023ef307-b18a-4911-a52c-de26700f6173/
OAB access.
- Exchange Control Panel URL:
https://vamwan310.vamwan.com/ecp/
ECP access.
4. AutoDiscover Tips
- AutoDiscover Service itself is a web application running on the AutoDiscover virtual directory (not a server service) designed to provide connection information to various
clients.
- The AutoDiscover service is automatically installed and configured when CAS role is added to any Exchange Server.
- AutoDisocver virtual directory is created in IIS within the Default Web Site.
- A Sercive-Connection-Point (SCP) object is created in AD.
- The SCP contains a URL to the AutoDiscover service. This is for intranet clients so they do not have to use DNS to locate the AutoDiscover service.
- In AD this object is located at the following location:
DC=<domain>, CN=Configuration, CN=Services, CN=Microsoft Exchange, CN=First Organization, CN=Administrative Groups, CN=Exchange Administrative
Group, CN=Servers, CN=<CAS Name>, CN=Protocols, CN=AutoDiscover, CN=<CAS Name>
- Setup creates the AutoDiscover URL based on the following structure:
<CASNetbiosName>.domain.com/AutoDiscover/AutoDiscover.xml
If a PKI certificate is not already present, a self-signed certificate is installed on the Default Web Site.
To help allow this certificate pass the Issues to test it is set up with a Subject Alternative Name containing urls.
If a PKI certificate is present, that certificate is utilized and configured for use in IIS.
The Outlook Provider is used to configure separate settings for the Exchange PRC protocol (internal to network), Outlook Anywhere (Exchange HTTP protocol), and WEB:
EXCH, EXPR, WEB
The
EXCH and EXPR setting are vital for the proper configuration of Outlook.
5. AutoDiscover Workflow
General Process flow:
There are various components surrounding the AutoDiscover Service and all are necessary to complete a request. Including IIS, AutoDiscover service
itself, the provider, and AD.
a.
Client constructs service URL and submits Autodiscover Request. First attempt to locate the SCP object in AD. So, DNS is not needed.
b.
IIS Authenticates User.
c.
Is the Autodiscover service in the appropriate forest?
+ If YES.
    1)
Parse/Validate Request
    2)
Is there a provider that can service the Request?
++ If YES
      a)
Config provider processes request and returns config settings.
      b)
Return config setting to client
++ If NO
Inform client we cannot process request
+ If NO.
Redirect client to Autodiscover service in the appropriate forest.
Methods to find Autodiscover services: SCP and DNS
Domain-joined
a. Find SCP first.
The SCP contains the URL to the AutoDiscover service.
URL: https://CAS01.contoso.com(CAS’ FQDN)/AutoDiscover/AutoDiscover.xml
If more than one SCP object is found in AD (it means there are multiple CAS servers in the Exchange organization), Outlook client will choose one of the SCP entries that
are in the same site to obtain the AutoDisocover URL.
b. If we cannot find SCP object, then Outlook client will use DNS to locate AutoDiscover.
Outlook parses out the domain (SMTP suffix) via your EmaiAddress, then attempts to connect to the predetermined order of URLs via the suffix.
For example: If my email address is
[email protected]
Outlook tries POST commands to the following order of URLs:
https://contoso.com/autodiscover/autodiscover.xml
https://autodiscover.contoso.com/autodiscover/autodiscover.xml
NOTE: The URLs above is by design, hardcode
and cannot be changed.
c.
If those fail, Outlook tries a simple redirect to another URLs in IIS:
http://contoso.com/autodiscover/autodiscover.xml
http://autodiscover.contoso.com/autodiscover/autodiscover.xml
If none of these URLs work then DNS is most likely not set up correctly.
We can test that by pinging one of the above URLs.
If that is successful, we must ensure the URLs contoso.com or autodiscover.contoso.com are actually pointing to the CAS server.
If the ping fails then there is a chance that DNS is not set up correctly so be sure to check that the URLs are even registered.
NOTE: If contoso.com is a non-CAS server,
we should add a Host record with just AutoDiscover. And point that entry to your CAS server that is running AutoDiscover.
d.
If still failed, we can use DNS SRV lookup for _autodiscover._tcp.contoso.com, then “CAS01.contoso.com” returned. Outlook will ask permission from the user to continue
with AutoDiscover to post to https://CAS01.contoso.com/autodiscover/autodiscover.xml
Non-Domain-joined
It first tries to locate the Autodiscover service by looking up the SCP object in AD. However the client is unable to contact AD, it tries to locate
the Autodiscover service by using DNS.
Then, same as step b, c, d in
Domain-joined scenario.
6. How to change the AutoDiscover
service location order forcibly?
By default, Outlook client locates AutoDiscover service in that order above.
We can also change the order forcibly.
a.
If we want to locate AutoDiscover service via one of the autodiscover URLs, please running following command in EMS:
Set-ClientAccessServer -identity <servername> -AutodiscoverServiceInternalUri https://autodiscover.contoso.com/autodiscover/autodiscover.xml(URL
that you want)
b. If we want to locate AutoDiscover service via
SRV record, please follows this KB to set up SRV:
http://support.microsoft.com/kb/940881
7. How to check AutoDiscover Healthy
a. We should make sure the AutoDiscover
is healthy before using AutoDiscover to perform troubleshooting.
b.
We can browse following URL in IE explorer:
https://autodiscover.vamwan.com/autodiscover/autodiscover.xml
If it returns “code 600”, that means AutoDiscover is healthy.
Screenshot as below:
c. AutoDiscover itself returns errors to the requesting client if the incoming request does not contain the appropriate information to complete a
request.
The following table explains the possible errors that could be returned.
Error Value
Description
600
Mailbox not found and a referral could not be generated.
601
Address supplied is not a mailbox. The provided email address is not something a client can connect to. It could
be a group or public folder.
602
Active Directory error.
603
Others.
The 600 “Invalid Request” error is returned because a user name was not passed to the service. That is OK for this test because this does confirm
the service is running and accepting requests.
d.
If AutoDiscover service is not working well, I suggest re-building the AutoDiscover Virtual Directory for testing.
Steps as below:
1) Running following command in EMS to remove the AutoDiscover VD (we cannot delete it via EMC):
Remove-AutodiscoverVirtualDirectory -Identity "CAS01\autodiscover(autodiscover.contoso.com)"
Please refer:
http://technet.microsoft.com/en-us/library/bb124113(v=exchg.141).aspx
2)
Running following command in EMS to verify whether we have removed the AutoDisocver VD successfully:
Get-AutodiscoverVirtualDirectory | FL
Please refer:
http://technet.microsoft.com/en-us/library/aa996819(v=exchg.141).aspx
3)
Running following command in EMS to re-creating a new AutoDiscover VD:
New-AutodiscoverVirtualDirectory -Websitename <websitename> -BasicAuthentication:$true -WindowsAuthentication:$true
Please refer:
http://technet.microsoft.com/en-us/library/aa996418(v=exchg.141).aspx
8. Common issues
a. Outlook Disconnection
Issue and Troubleshooting
Issue:
Sometimes the Outlook clients cannot connect to the Exchange server after migrating to a new Exchange server or changing to new CAS. The Outlook clients
always connect to the old CAS server.
Troubleshooting:
To solve this issue, we should change the SCP via following command:
Set-ClientAccessServer -Identity
<var>CAS_Server_Name</var> -AutodiscoverServiceInternalUri
https://mail.contoso.com(newCAS’FQDN)/autodiscover/autodiscover.xml
b. Autodiscover
Certificate issue
Tips on Certificate:
Exchange requires a certificate to run an SSL protocol such as HTTPS. We can use the certificate that supports subject alternate names (SAN) in Exchange.
This is to allow the certificate to support resources that have different names, such as Outlook Anywhere and the Autodisocver Web application.
Issue and Troubleshooting
Issue:
We receiver the Certificate Principal Mismatch error when we use a SAN certificate.
Troubleshooting:
1) Please determine the FQDN that the client
uses to access the resource. Steps as below:
OutlookàToolsàAccount
SettingsàE-mailàclick
the Exchange accountàChangeàMore
SettingsàConnectionàExchange
Proxy Settingsànote the FQND that list in the
Only connect to proxy servers that have this principal name in their certificate box.
2)
Please using EMS to determine the value for the CerPrincipalName attribute: Get-OutlookProvider
This command returns the result for the EXPR name.
3)
Please re-setting the CertPrincipalName attribute to match the FQDN via following command:
Set-OutlookProvider EXPR –CertPrincipalName: “msstd:<FQDN the certificate is issued to>”
9. Resource for reference:
Autodiscover and Exchange 2007
http://technet.microsoft.com/en-us/library/bb232838(v=exchg.80).aspx
White Paper: Understanding the Exchange 2010 Autodiscover Service
http://technet.microsoft.com/en-us/library/jj591328(v=exchg.141).aspx
Certificate Principal Mismatch
http://technet.microsoft.com/en-us/library/aa998424(v=exchg.80).aspx
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

HI,
I get following? when run the test? user is login to Domain A but accessing exchange in Domain B?

Outlook cannot connect after mailbox move from Exchange 2007 to 2013

I am in the middle of migrating an Exchange Server 2007 to 2013. Everything went fine up until I moved the first mailbox. I can access the mailbox via OWA, but not Outlook 2010. When I checked the account settings, the server is incorrect. It shows [email protected]
If I manually enter the name of the Exchange 2007 server, it changes to the Exchange 2013 server, as it should. I save the settings, open Outlook, the connection fails, and the server setting is changed to [email protected]
I then ran the Microsoft Connectivity Analyzer. There are 2 lines which caught my attention:
AutoDiscoverInternalRpcClientServer
[email protected]
AutoDiscoverHomeMdbDn
/o=mydomainMail/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=[email protected]/cn=Microsoft Private MDB
I've checked and rechecked everything and can't seem to locate my error.
Any thoughts? Thanks.

Totally correct!
If you don't plan to maintain Outlook then you plan to fail :(
Additional links etc are in here:
http://blogs.technet.com/b/rmilne/archive/2013/07/18/patching-exchange-don-t-overlook-outlook.aspx
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Outlook 2010 and Exchange 2007. Outlook crashes when user opens it. Event ID 55, 100 and 3036

Hello,
We are running Exchange 2007 on our server and our user clients use Outlook 2010. One of my users is having the following issue. Whenever he opens Outlook 2010, it would crash and show this message: "Microsoft Outlook has stopped working. A problem
caused the program to stop working correctly. Please close the program". I tried recreating his Outlook profile and the issue persisted. I also tried to create his Outlook profile on a different computer and same message shows up. Both computers are domain
joined.
I checked Event Viewer both on his computer and the other computer I tried to set up his Outlook profile on. Both machines showed the same three error logs:
-First error log:
Log Name: Application
Source: Microsoft-Windows-Search
Date: 9/12/2014 12:34:16 PM
Event ID: 3036
Task Category: Gatherer
Level: Warning
Keywords: Classic
User: N/A
Computer: OSD-Assistant10
Description:
The content source <mapi://{S-1-5-21-3579767609-4209606035-2604604182-1235}/> cannot be accessed.
Context: Application, SystemIndex Catalog
Details:
No protocol handler is available. Install a protocol handler that can process this URL type. (HRESULT : 0x80040d37) (0x80040d37)
-Second Error log:
Log Name: Application
Source: Application Error
Date: 9/12/2014 12:34:13 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: OSD-Assistant10
Description:
Faulting application name: OUTLOOK.EXE, version: 14.0.7113.5000, time stamp: 0x527d636c
Faulting module name: OUTLOOK.EXE, version: 14.0.7113.5000, time stamp: 0x527d636c
Exception code: 0xc0000005
Fault offset: 0x00011c8a
Faulting process id: 0x8e0
Faulting application start time: 0x01cfceafa6be0255
Faulting application path: C:\Program Files (x86)\Microsoft Office\Office14\OUTLOOK.EXE
Faulting module path: C:\Program Files (x86)\Microsoft Office\Office14\OUTLOOK.EXE
Report Id: 025ffc35-3aa3-11e4-bb89-001f2937f524
-Third Error log:
Log Name: Application
Source: Outlook
Date: 9/12/2014 12:34:10 PM
Event ID: 55
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: OSD-Assistant10
Description:
Calendar Folder New Download
This leads me to believe the problem has to do with his Exchange User Mailbox account. But I have no clue what could it be. He is the only user experiencing this problem.
Any help is greatly appreciated!! Thanks!

Hi,
Sorry for my delay. Have the issue been resolved?
If there are too many items in the problematic user's mailbox, please delete some and check whether the Outlook can be opened. Please uncheck Use Exchange Cached mode to use Online mode and confirm if the user can access the mailbox for Outlook.
Also try to connect to this user's maibox from your working machine with Outlook. Then check whether it works.
Regards,
Winnie Liang
TechNet Community Support

OWA still redirects to Exchange 2007 (legacy) after mailbox-move to Exchange 2013

Hi,
I am in the process of implementing Exchange 2013 in coex with 2007. I am testing now in a copy of the production environment and have installed the Exchange 2007 SP3 RU11 prior to installing Exchange 2013 using the SP1 media.
We use a wildcard certificate and I prepared the Exchange 2007 internal/external URLs for OWA/OAB/etc to use the legacy.domain.com names and in Exchange 2013 I set them all to email.domain.com. Exchange 2013 has Outlook Anywhere configured.
All tests like autodiscover (internally via SCP) run fine and for a new Exchange 2013 mailbox the Outlook and OWA functionality is as expected. A mailbox still on 2007 also connects fine via Outlook and while connecting to OWA (using the htps://email.domain.com/owa
url) also redirects me to https://legacy.domain.com/owa just fine.
HOWEVER: after a successfull mailbox-move from 2007 to 2013 my OWA logon-request STILL get's redirected to the 2007 legacy URL. When I then logon again on the 2007 OWA I get the message that I should connect to the 2013 URL and end-up in a loop.
Anyone any tips where to search?
Many thanks in advance.
Best regards and many thanks in advance, Eric Vegter

This seems to be an outstanding issue.
We just performed a fresh install of Exchange 2013 on a Windows Server 2012 R2 operating system. We're migrating from our existing Exchange 2007 server. At the moment we have everything properly setup in a co-existence state. All we lack is to complete the
migration of our mailboxes from the 2007 DB to the 2013 DB.
In performing the first mailbox move, to test the migration process and make certain mail flows as expected, we noticed this same problem. Before reading through this thread, I was able to assign Full Access to a delegate user and then perform the "Open
Mailbox" feature from a 2013 user's account. This was successful in opening the mailbox within OWA 2013. However, I still could not access the account by simply logging into the Outlook Web App. It would login, then proxy back to OWA 2007 with the message,
"Use the following link to open this mailbox with optimal performance:
http://mail.domainname.com/"
After reading about cycling the OWA app pool, I immediately tried it as a workaround and it worked. It is a little frustrating going about it in this way. Hoping to see more activity on this thread.
-Lorne

Lync2013 EWS URLs for Exchange 2007/2010 Coexistence

Hi
Last weekend we deployed and activated our new Exchange 2010 CAS. The 'old' Exchange 2007 CAS is still there, using the legacy URL method, since mailboxes are mostly still located on 2007 Mailbox servers.
In other words, clients connect to the Exchange web-services on the 2010 CAS, and depending on where their mailbox is located (2007 or 2010 Mailbox-server) they either stay with the 2010 CAS or get re-directed to the 2007 CAS (legacy.company.com)
Internal and External URL's are the same, for both the primary and the legacy URL's. All is well, no issues with Outlook clients or OWA, EWS, Activesync.
Enter Lync 2013.
Since the change this weekend, we're getting Outlook/Exchange Integration errors. Checking the Lync Configuration Information (CTRL-Click system tray icon), I can see the EWS Internal/External URL's being used by the client. These URL's point to the 2010 CAS.
So why the error ?
Does the 2010 CAS re-direct Lync clients to the legacy URL, just like it does with OWA/Outlook clients ?
Does it even have to, to supply EWS data for mailboxes on 2007 servers ?
Can I change the EWS URL's, and have them point to the legacy URL, but only for Lync clients ? (and change it back later)
Already checked a mailbox on Exchange 2010, it's Lync user does not get the integration error. So the problem is definitely related to mailboxes on 2007, that need the old CAS server during coexistence. Also, before the CAS 2007 server worked fine, providing
EWS to Lync clients.
Eventually, the plan is to move the mailboxes from 2007 to 2010, but this error puts pressure on that plan. It will take at least 2 or 3 weeks, during which time clients continue to get the error until they are moved.
I'm kinda stuck here.

Lync uses DNS to find autodiscover to obtain EWS URL.
Which server did the DNS record Autodiscover point to?
You can run the command Get-AutodiscoverVirtualDirectory to get the EWS internal URL and external URL on the server the Autodiscover pointing to.
2010 CAS can’t redirect Lync client to the legacy URL.
Lisa Zheng
TechNet Community Support

Outlook Users connection issues after Mailbox Migration from 2007 to 2013

Hi,
We have a coexistance between Exchange 2007 SP3 and Exchange 2013 CU7. There is an issue when after migrating the user from exchange 2007 mailbox to exchange 2013, the outlook keeps on prompting for password when it is being launched. Checking the Connection
Status we found that there is a connection to the old 2007 Server and the type is Exchange Public Folder. I have migrated the public folder and checked the Mailbox of the user and found that the DefaultPublicFolderMailbox is set to the 2013 Public Folder Mailbox.
If I check my 2013 MailboxDatabase Properties, It sill shows that PublicFolderDatabase Properties is still pointing to the 2007 Public Folder Database. Any resolution on this?
Another issue is, We set outlook anywhere on the 2013 to use basic authentication, however, when users are migrated to 2013 the Outlook client changes to NTLM. even if we set the outlook to basic to make it work, it still comes back to NTLM after a while.
I did most of the resolutions online to use powershell to make changes to outlook anywhere but no luck. any suggestions is highly appreciated.
Thanks & Regards,
Arthur

Hi,
For the first problem, please check the msExchHomePublicMDB attribute for mailbox database in Exchange 2013, you can check this attribute in ADSIEdit.
If this attribute is pointing to Exchange 2007 public folder database, please set to blank. After that, please restart the information service.
And for the second question, I suggest we open a new case for this issue. In order to avoid confusion and keep track of troubleshooting steps, we usually troubleshoot one
issue per thread in order to find a resolution efficiently.
Thanks for your understanding.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Belinda Ma
TechNet Community Support

Currupted "sent items" folder in Outlook 2007 (on Exchange 2007) causing Outlook to crash.

One user here has a problem when clicking on the "sent items" folder. Outlook hangs for 5 secondes and then crashes. If user logs into OWA, she can
access the "sent items" folder no problem. I thought it was a messege in the folder that was corrupted so I asked the user to move the messages to a temp folder from OWA. She did that, the folder is now empty but Outlook still crashes. Tried cache
mode and uncache.
I tried to delete her sent item folder using MFCMAPI (in the hope the it will recreate a new folder) : right click the folder, selected delete folder, check the
option "hard deletion" and I get
Warning:
Code: MAPI_W_PARTIAL_COMPLETION == 0x00040680
Function lpParentFolder->DeleteFolder(
lpItemEID->cb, (LPENTRYID) lpItemEID->lpb, lpProgress ? (ULONG_PTR)m_hWnd : NULL, lpProgress, ulFlags)
File .\MsgStoreDlg.cpp
Line 991
One more test I did: I copied the sent items folder to a pst, moved the pst to my computer and when I try to open the folder from the PST, my Outlook would freeze
and crash. Isn't interesting?
Am I missing something here? Has someone encounter this problem before? Any other idea on how it could be resolved?
This issue started on Exchange 2003. We are now moving to Exchange 2007. I moved her mailbox to the new server in the hope that any mailbox problem will be filtered
and removed. I still have the issue..
env:
Exchange 2007 running on Win2008
PC:
Windows Vista sp1, outlook 2007 (user was getting same issue under Win2k with Outlook 2003)

Couple steps you may apply...
1. Repair the offline file with a Microsoft utility called SCANOST.exe. I’ve seen this file reside in a number of different locations, mainly within Program
Files. It might be best to search for it with Windows or Google Desktop. SCANPST.exe will also work, though you’ll have to go digging for your outlook.ost, which should be near c:\Documents and Settings\ %profile%\ Local Settings\ Application Data\ Microsoft\
Outlook\ outlook.ost. If your file is significant in size, you’ll save a lot of time with the repair operation by not creating a backup. Because if the repair finishes successfully and Outlook still bombs, you’ll need to.
2. Shutdown Outlook completely, including any runaway outlook.exe processes in the task manager. Open Mail in the Control Panel and before you delete your
profile completely, write down the server settings! There’s no need to worry about backing up your mail as it’s stored on the Exchange server. (Essentially, you’re deleting that outlook.ost when you drop your mail profile.) Now, start Outlook and it will create
a new profile, where you’ll configure the server with the information you wrote down previously.
If steps above doesn’t work or you need to get more variants of .pst restoration, visit...
http://www.filerepairforum.com/forum/microsoft/microsoft-aa/outlook/1503-is-there-any-opportunity-to-recover-huge-pst-file-over-6gb
- multi functional user community where you may discuss methods and cases of .pst corruption
https://www.repairtoolbox.com/how-to-repair-outlook.html
Outlook Repair Toolbox - one of the accessible tools on the market, as a variant in case you can’t recover .pst file via ScanPST or manually solutions

Exchange 2007 - unable to connect to smtp after severall hours

Hi,
We have a Windows SBS 2008 server with Exchange 2007 SP3. After severall hours we are unable to connect to the server with telnet on port 25 from outside. Sometimes a local telnet on the server still works but not always.
The only solution is to restart the server. The transport service can not be stopped.
Even after a fresh reboot the telnet session does not alway show the smtp banner.

Hi Joost,
Is there any related error message left on Exchange server?
I have found a similar thread for your reference:
https://social.technet.microsoft.com/Forums/en-US/5e2b3320-7c97-4b33-bd8e-e27768f51ec0/hub-transport-service-wont-start-and-keep-running-sbs-2008-exchange-2007
More detailed error message without sensitive informaiton is helpful for the further troubleshooting.
Also, SBS 2008 is different from Exchange 2007 on Windows Server, I suggest ask SBS Forum to double confirm this issue.
Thanks
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Mavis Huang
TechNet Community Support

Exchange Server 2010 Outlook Client Stops Responding

Greetings- This issue is with Exchange Server 2010 sp2 using Outlook 2013 clients in AD environment. Single server, single database (80GB) , 60+ users, Windows 8/8.1 workstations.
All of a sudden our users started experiencing issues yesterday. One or two at first, then more.
The issue where Outlook stops responding. This is most noticeable when you try to send and receive. The recipient will get the email before outlook clears it from pending submissions in the outbox.
1. SMTP is fully operational
2. Push clients functions normally
3. Exchange is fully updated and current
4. The mailbox databases are verified and healthy
5. Network traffic to and from the server appears normal according to wire shark
6. Setting Outlook to use no cache connection mitigates the issue partially
7. The issue is global on all deployed OS's
As this is happening on many, maybe all, workstations, my thought is that is has to do with Exchange, not the client.
Thanx
You should never, never doubt what nobody is sure about. -Willy Wonka

Does this happen all day, or at specific times? I'll add that your server appears to be light on CPU, but without knowing its CPU profile (when idle and when under a load), I can't say for sure this is your issue. One additional thing I can
ask - do you have hyperthreading enabled? This can be a bad thing in an Exchange server. See the following:
https://technet.microsoft.com/en-us/library/dd346699%28v=exchg.141%29.aspx?f=255&MSPPError=-2147217396#Hyper and the following:
http://blogs.technet.com/b/exchange/archive/2013/05/06/ask-the-perf-guy-sizing-exchange-2013-deployments.aspx Note that this second note is about Exchange 2013, but it goes into more details on some of the issues that may be adversely affecting your
Exchange 2010 servers.

Exchange 2007 - 2010 Outlook doesn't autodiscover after mailbox move

Similar Messages

Maybe you are looking for