Outlook 2007-2013 doesn't connect in non-cached mode to Exchange 2013.

Hello!
I have organization Exchange 2010 + Exchange 2013 in one AD site (hybrid organization)
Mailboxes based on Exchange 2010 servers work fine. But after moving one of mailboxes to
Exchange 2013 database, Outlook doesn't connect to mailbox in
non-cached mode. If I turn on cached mode this mailbox is connecting perfectly (OAB, Folders, PublicFolders, Addresslists).
I cleaned parameter "PublicFolderDatabase" for Exchange 2013 database, but the problem didn't solve.
In CAS
RpcHttp
log:
2015-01-22T12:08:12.720Z,MBXDB13,RpcHttp,S:Stage=BeginRequest;S:AuthType=Negotiate;S:HttpVerb=RPC_IN_DATA;S:UriQueryString=?MBXDB13.DOMAIN.local:6001;S:RpcHttpUserName=DOMAIN\USER;S:ServerTarget=[email protected];S:RequestId=267b0bf2-4361-4efb-9865-7f8d664b6e00;S:ClientIp=10.10.10.111
2015-01-22T12:08:12.720Z,MBXDB13,RpcHttp,S:Stage=PostAuthorizeRequest;S:UserName=DOMAIN\MBXDB13.domain.local:6001;S:RpcHttpUserName=DOMAIN\USER;S:ServerTarget=[email protected];S:RequestId=267b0bf2-4361-4efb-9865-7f8d664b6e00;S:ClientIp=10.10.10.111
Exchange Server 2013 Cumulative Update 7 (CU7)
are installed.

Hi Allen!
Thank you for reply!
Outlook cannot connect to all mailboxes on Exchange 2013 server.
>Get-OutlookAnywhere | FL Name,*auth*,*host*Name : Rpc (Default Web Site)
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods : {Basic}
ExternalHostname : exchange2010.contoso.com
InternalHostname :
Name : Rpc (Default Web Site)
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods : {Basic}
ExternalHostname : exchange2010.contoso.com
InternalHostname :
Name : Rpc (Default Web Site)
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods : {Basic}
ExternalHostname : exchange2013.contoso.com
InternalHostname : cas1302.domain.local
Name : Rpc (Default Web Site)
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods : {Basic}
ExternalHostname : exchange2013.contoso.com
InternalHostname : cas1301.domain.local
Outlook error message:
"Cannot start Microsoft Outlook. Cannot open the Outlook window. The set of folders cannot be opened. The attempt log on to Microsoft Exchange has failed."
This error reproduced even in new profile. Repair does not help.

Similar Messages

Outlook 2007 disconnects and restore immediatley within every 20 minutes in exchange 2013

Hi all,After upgrading from 2003 to exchange 2013 we are facing outlook disconnects and immediately restores but this happens after every 20 minutes. Outlook client is outlook 2007 sp3. There is no issues in the networks. Is there is outlook version issue
or network issue. I will check again in the network if u all say it. Please help me in this. Thanks

hello, you can try to install this hotfix:
http://support.microsoft.com/kb/2596598/en-us
Described in this blog:
http://blogs.technet.com/b/jribeiro/archive/2012/09/25/exchange-2013-preview-supported-outlook-clients.aspx
Regards,
Flynn

Exchange 2010 all mail clients with internal cached and internal non-cached mode users having connection status issues, login prompt -- external is fine either way

Hello,
I'm seeing an issue that started this past Monday with no recent change to our environment.
External Outlook Anywhere users and Mobile users, OWA users are unaffected.
Internal Users are affected when using Outlook of any version, 2010 or 2013.
-Internal Users normally log into their workstation with their ad credentials, domain joined machines. Outlook opens without credentials prompting ideally.
1 . Using Cached Mode:
a. Login Prompts, slowness - Since Monday, users are getting prompted to login. The prompt goes away after logging in at startup. It is also causing high CPU
on the workstations.
b. Free/Busy, Out of Office doesn't work. I can, however complete auto-setup for a new user, so autodiscover is not completely down for internal users.
c. Checking Connection Status shows connecting status on highlighted entry below without ever establishing connection (just goes away).
The outlook icon in the system tray says "Outlook is requesting data from the server":
2. Using Non-cached mode
a. No Login Prompt at startup, business as usual
b. Free/Busy, Out of Office works fine. Autodiscover is fine.
c. Checking Connection Status shows normal except, it has "casarray URL, then status is referral" it seams to flicker this constantly then go away intermittently.
d. Main issue in non-cached mode is, sometimes a user will log into windows, open outlook and it will not open and says "server is unavailable. Retry, work offline, or cancel" I can try re-opening, same message.
Only after logging out of windows, logging back in, I can get back into outlook. This is not every time, or consistent with specific users, but random.
3. Lync Pop up for credentials often, though entering the password.
URLs are correct. Autodiscover, EWS, etc.
Already tried bypassing our loadmaster load balancer with host files on clients. same issue regardless of casarray node.
Not sure what is going on.
Josh

You have a hybrid configuration with Office 365, right? You didn't provide this valuable piece of information.
In Exchange Online PowerShell run this command:
Get-OrganizationConfig | FL PublicFoldersEnabled
If the value is "Remote" then users with Exchange Online mailboxes are looking to on-premises public folders. Be sure that you have legacy pubic folder interoperability properly configured.
http://technet.microsoft.com/en-us/library/dn249373(v=exchg.150).aspx
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Nokia N70 connected in non compatible mode

First here are some facts: Im Using Pc Suite v6.83 on Windows XPsp2. Im using USB cable to connect to my N70.
Now here's the problem: The first time I used PC Suite after Installation, it worked fine. When I used it again the second time, it acted strangely. It didn't detect my phone correctly. It detected the N70 alright, but a baloon popped up from the PC suite Icon on the system tray saying "nokia n70 connected in non compatible mode". Then when I went to the Get Connected wizard, a warning popped up which says "Your phone is in file transfer mode and connot be used with PC suite. quit file transfer mode from the phone if you want to use PC suite". I wonder how could this be since I know that the N70 has no file transfer mode.
Then after finally having my phone detected correctly after diconnecting then connecting the USb cable, my system detected the phone as a digital camera imaging device and as a mass storage device, showing up in windows explorer aside from showing up in the Nokia Phone browser. I Don't think this is a normal bahaviour.
Then the third time I tried to use PC suite, it detected the phone as bing in in non compatible mode again. Yhis time disconnecting and reconnecting the USb cable didn't help.
I found some strange things in the windows device manager too. I found out that under portable device, the N70 was there but disabled and labled as not properly working.
Have you guys encounterd this prblem before? If you did maybe you can help me resolve it. Thanks in advance!

08-Jul-2007 05:32 PM
pmguanco wrote:
First here are some facts: Im Using Pc Suite v6.83 on Windows XPsp2. Im using USB cable to connect to my N70.
Now here's the problem: The first time I used PC Suite after Installation, it worked fine. When I used it again the second time, it acted strangely. It didn't detect my phone correctly. It detected the N70 alright, but a baloon popped up from the PC suite Icon on the system tray saying "nokia n70 connected in non compatible mode". Then when I went to the Get Connected wizard, a warning popped up which says "Your phone is in file transfer mode and connot be used with PC suite. quit file transfer mode from the phone if you want to use PC suite". I wonder how could this be since I know that the N70 has no file transfer mode.
Then after finally having my phone detected correctly after diconnecting then connecting the USb cable, my system detected the phone as a digital camera imaging device and as a mass storage device, showing up in windows explorer aside from showing up in the Nokia Phone browser. I Don't think this is a normal bahaviour.
Then the third time I tried to use PC suite, it detected the phone as bing in in non compatible mode again. Yhis time disconnecting and reconnecting the USb cable didn't help.
I found some strange things in the windows device manager too. I found out that under portable device, the N70 was there but disabled and labled as not properly working.
Have you guys encounterd this prblem before? If you did maybe you can help me resolve it. Thanks in advance!
Message Edited by geronimo on 10-Jan-2008 07:59 AM

E71x Connected in non-compatible mode

Brand new E71x
Vista - 4GB RAM, 250GB HDD, 512MB Video
Nokia PC Suite 7.1.26.0
Connected cable to PC USB 2.0 port
and other end to E71x
In PC Suite main window see "Connected in non-compatible mode". What now?

OK I found the solution on the Asia forums. It's a setting within the phone that dictates what the phone does on a USB cable connection.
Menu>Settings>Config>Data Cable.
Change from Media Transfer to PC Suite and all is well.

Nokia 6500 Slide Connected In Non-Compatible Mode

Hi,I've cracked my screen and unable to access anything! I transferred my SIM (3 network) to another phone. Although the phone works all my contacts and messages have disappeared. I am quite positive they were saved to SIM. Anyway tried connecting using broken phone with SIM using USB and get message Connected in non-compatible mode and I still cannot access contacts or messages. I'm getting extremely frustrated can anyone help?
Many thanks
Solved!
Go to Solution.

You have a S40 phone, Another thing you can try is, when you are sure the keypad is unlocked, connect the phone and after a few second press the right selection key(the one you usually use to step back or disagree or cancel) which should be cancel. If your phone is anything like my 5200 that will send it straight to connect via PC suite. I think even pressing the red button will do this(Not sure about the red button though but the right selection I'm certain about)
Show your appreciation. Hit that kudos button real hard

E61i- USB connected in non compatible mode.

My E61i is not getting recognised by the PC. I get the error "USB connected in non compatible mode."

Check under the connectivity menu then USB, that the mode is set to ask which connection you want when connected to a PC. If it is set to mass storage mode it will continue to connect in that mode until you either change it to PC Suite mode or if you set it to ask you always.
Best to set it to always ask then you can select the mode you need at different times.
When connecting o the PC select PC Suite mode
iPhone 5 32GB
MacBook Pro Retina 15" Mac OS X Mountain Lion 10.8.4

Outlook non cached mode

Good day,
I have been tasked to see if there is a way to enable outlook to alternate between cached on non cached mode. This must be based on whether the user is logging onto his primary device for cached mode, and whether he is logging onto a temp device for
non-cached mode.
Can this be done using group policy? I know we can determine a primary device using SCCM, but not how to enable GPO to read from SCCM and then apply the correct setting.
Windows 7 SP1 x 32
SCCM 2012 SP1
Server 2008.
Any info on how this can be achieved?
Regards
VB Knowledge = 0%

Hi Carlo,
Before going further, to use group policy to manage Office, we need to download administrative templates files for Office from Microsoft download center.
>>This must be based on whether the user is logging onto his primary device for cached mode, and whether he is logging onto a temp device for non-cached mode.
For the Outlook setting we want is under User Configuration in GPO, we can create a new GPO, enable Loopback Merge processing mode in the GPO, configure the Outlook setting in the GPO, and then utilize Security
Filtering to just apply the GPO to the user’s primary device account.
Regarding Loopback processing, the following article can be referred to for more information.
User Group Policy loopback processing mode
http://technet.microsoft.com/en-us/library/cc978513.aspx
Windows Server: Understand “User Group Policy Loopback Processing Mode”
http://social.technet.microsoft.com/wiki/contents/articles/2548.windows-server-understand-user-group-policy-loopback-processing-mode.aspx
Regarding security filtering, the following article can be referred to for more information.
Security filtering using GPMC
http://technet.microsoft.com/en-us/library/cc781988(v=WS.10).aspx
Best regards,
Frank Shen

Failled Exchange 2007 to SP3 how can I continue to upgrade to Exchange 2013

I have domain with 2 - 2003 (32bit) DC, 1 - 2008 (64bit) DC (not a good candidate for Exchange 2007) and 1-2008(64bit) DC with Exchange 2007. The Exchange server has ran out of hard drive space and the equipment needs upgrading. Several
attempts were made to update to SP3 but it failed.
The option to move the Exchange 2007 to another server is null. Will Exchange 2013 read 2007 mailboxes? Is there a way to move the Exchange 2007 Mailboxes to Exchange 2013 thru a co-existence scenario?
PraxisHousing

Hi Praxis,
Thank you for your question.
By my understanding, if we didn’t update Exchange 2007 to SP3, we will not install Exchange 2013 in organization. We didn’t upgrade to Exchange 2013.
We could expand hard drive space. If the failed error is concerned about drive space, we could move mailbox databases to other drive or other things in order to shrink drive space to update to SP3. As you said, we could move Exchange 2007 to a new
server.
If the error is about others, we suggest you post error to
[email protected] for our troubleshooting. We could refer to the following link:
https://social.technet.microsoft.com/Forums/en-US/04449b40-9911-4e73-8ae7-810627f94112/exchange-2007-sp2-upgrade-to-sp3
We could refer to the following steps to migrate Exchange 2007 to Exchange 2013:
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim
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]
Jim Xu
TechNet Community Support

A kind of hosting mode in Exchange 2013?

Hi @ all,
I have a Windwos Server 2012 as DC with AD, DNS, DHCP. Also I have a Windows Server 2012 with Exchange 2013.
In the Active Directory I have different OUs for different groups of users. Every OU has it's own Administrator. And now I want, that the Admin only can create/see/edit/delete Mailboxes and Users out of his own OU. (like hosting mode in Exchange 2010)
I used RBAC and different scopes. Now each Administrator can only manage his own OU, but sees all.
I uses this example for my scope:
New-ManagementScope -Name "Executive Mailboxes" -RecipientRoot "contoso.com/Executives" -RecipientRestrictionFilter {RecipientType -eq "UserMailbox"}
(of cours with the my attributes ;) )
But it didn't work.
In summary, I want to realise a "hosting mode" in Exchange 2013.
I've tried an long time different ways, but nothing worked.
Can anybody help me?
dechecker
Sorry for my english, it's not the best. :)

Hello,
You can refer to the following thread:
http://social.technet.microsoft.com/Forums/nb-NO/exchangeserverpreview/thread/dfe648db-4d41-4bcd-ba4f-c2e1b4ec9435
Thanks,
Simon Wu
TechNet Community Support

Outlook 2007 SP3 can't connect to Exchange 2013

Outlok 2007 with latest hotfixes
Freshly migrated mailboxes
Gives the error
Can't open outlook-The set of folders cannot be opened
Cert has internal FQDN name. Encryption is disabled
Any pointers?

Does the certificate have the server name?
That was apparently the solution here:
http://social.technet.microsoft.com/Forums/exchange/en-US/1ae67f48-d1ba-44b5-a3c7-4e9a5e955f3e/outlook-2007-cannot-connect-to-exchange-2013?forum=exchangesvrclients
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.

Outlook Connectivity Problem on 2003 Term Server - Exchange 2013

I am working on deploying a new 2013 Exchange server. The Exchange is installed on a 2012 Server OS. I have three windows terminal servers (or remote desktop services) at three separate locations that have users working on them via thin-client - (RDP). The
users run Outlook 2010 from the three servers. Two of the terminal servers are Windows 2008 R2 and one is 2003 R2 Standard. I am able to get the Outlook clients to connect to Exchange from the two 2008 servers but the Outlook clients on the 2003 server are
so far unable to connect to the Exchange server.
When I try to add the mail profile from the control panel - signed on as each user - it auto detects the user profile and looks like it connects but then it prompts for a password. I can try to input the password but it will not accept it. Ultimately it
fails with a message indicating Outlook cannot log on etc., etc.
These three servers are at three different locations but connect back to the location where the Exchange server resides via MPLS. Connectivity between locations is solid.
Odd thing is I have an old 2003 server at the same location where the Exchange box is and I fired it up and tried to connect an Outlook client from it and it does not work either.
Does anyone know of any documented problems with connecting to 2013 Exchange from a 2003 server OS? Or, conversely, has anyone successfully deployed Exchange to Outlook clients on a 2003 server?

Hi there,
What version Outlook is install on the problematic Windows server 2003? Note that Outlook 2007 SP3 with July 2012 Cumulative Update or higher version can be supported; other earlier version is NOT supported.
Refer to:
http://blogs.technet.com/b/jribeiro/archive/2012/09/25/exchange-2013-preview-supported-outlook-clients.aspx
Besides, is the certificate installed on Exchange 2013 trusted by the problematic Windows 2003 server? Please test the proxy url from server 2003 and also run the online test from
https://www.testexchangeconnectivity.com/
Hope it is helpful.
Fiona Liao
TechNet Community Support

Outlook 2007 intermitent loss of connection at remote VPN Site

We have some remote sites connected by IPSEC site-to-site VPN. Users run Outlook 2007 connected to Exchange 2007 at the main site.
It is common for Outlook to go through periods of losing and regaining connections: Outlook displays constantly connection messages. The error occurs on an intermittent basis and does not effect all users at the remote site, the problem usually
disappears after a day. Users can get access to e-mails through OWA and this does not have the same outage errors.
Not sure if it is related to other traffic running over VPN link but I cannot find any obvious cause.

Hi,
The intermittent Outlook connection issue can be caused by the following factors:
1. Network issue.
2. Exchange Server performance issue.
3. Outlook client side issues.
What’s your Exchange environment? How many Exchange servers and Server Roles?
In Exchange 2007, Outlook directly connect to Mailbox Server. So, if you have multiple Mailbox Servers, please confirm whether the problematic users are all on the same Mailbox Server.
You can take a performance monitor to check whether the RPC request is too high:
http://blogs.technet.com/b/mikelag/archive/2008/05/02/perfwiz-replacement-for-exchange-2007.aspx
Thanks,
Simon Wu
TechNet Community Support

Outlook 2007 not working, internet connection is fine

I installed an airport extreme yesterday and my internet connection is up and running on all PC's and an IMac. However, I can't seem to get my Outlook 2007 connected to my ISP. All my ISP incoming and outgoing server names are correct. Should I change the advanced settings for server port numbers? They are 110 (incoming) and 25 (outgoing)?
As you all know, being w/o email is a bxxxh.

Lyle,
Ok, so we know the issue is not related to the base station, but the email account.
I know it sounds silly, but make sure you are on YOUR wireless network (click Airport icon in menu bar and make sure your network name is selected). If you are on another network, RoadRunner may block you from using their SMTP (outgoing) mail server.
Once you're sure on your network, re-create the account with settings you get from your ISP. Find out if the 'username' they want for the incoming server is your full email address or just the part before the @ symbol (e.g. bobsmith or [email protected]), whether they use SSL encryption and odd port numbers. Ports 110 and 25 are common settings for POP & SMTP servers, respectively.
Perry

Outlook 2007 Calendar doesn't sync!

Hi, can't sync Outlook 2007 calendar with my 120gb. Contacts-sync is OK but no calendar!!?? Tried to disable Add-Ins, but still the same. Any help??? Thx

This problem probably exists because you're using work Outlook connected to an Exchange server. In that case contacts sync but for whatever reason your calendar won't.
Here's the Apple Support fine-print on that....
This sure seems like something Apple should make a lot clearer on their mobile me marketing materials....
Symptoms
In the MobileMe Control Panel for Windows' Sync tab, you may not be able to select calendars to sync with MobileMe (the Calendars selection appears dimmed, or "grayed out").
Products Affected
MobileMe
Resolution
This can occur if:
* Microsoft Outlook is not installed: Calendar syncing is only supported for Outlook 2003 or Outlook 2007. If you do not have either of these installed in Windows, Calendar syncing with MobileMe is not available.
* *Outlook is installed but connected to a Microsoft Exchange Server, and MobileMe Control Panel 1.2 or later is installed. If Outlook is connected to Exchange, Calendar syncing with MobileMe is not available. For more information about MobileMe and Exchange syncing, see this article.*
If Outlook is installed and is not connected to an Exchange Server, but Calendars is still dimmed:
1. Close the MobileMe Control Panel
2. Open Outlook
3. Quit Outlook
4. Open the MobileMe Control Panel and try again
If the above steps do not resolve the issue, restart your PC, and Calendars should then be selectable from the MobileMe Control Panel.
null

Outlook 2007-2013 doesn't connect in non-cached mode to Exchange 2013.

Similar Messages

Maybe you are looking for