Outlook 2003 clients cannot connect to shared diaries on Exchange 2010

Having recently upgraded to Exchange 2010 from 2003, I am now receiving calls from users regarding the above.
I am due to move to Office 2013 later this year but there are some third party app incompatibilities I need to get resolved first.
So I came across the following article
https://support.microsoft.com/en-us/kb/2299468?wa=wsignin1.0
and have changed the default RCAMaxConcurrency from 20 to a very high value of 214783647 and have restarted the Throttling services.
However, my Outlook 2003 users are still having issues when they have less then 16 calendars open.
I have ran Get-ThrottlingPolicy to confirm my changes which is correct.
As another approach, I have got users to run the /resetnavpane switch when lauching Outlook to clear down any orphaned references.
Can anyone suggest what else I could try?

Hi,
As per the information and details provided by you, to solve this issue, please follow these steps: -
To resolve this problem, create a custom throttling policy by using an increased value for
RCAMaxConcurrency. Then, associate this custom throttling policy to the mailboxes that require Outlook 2003 clients to open multiple shared calendars.
After you make this change, wait for the
Active Directory replication to finish. By default, the throttling policy should be applied after
15 minutes. To apply it immediately, restart the Microsoft Exchange RPC Client Access service on the
Client Access Server (CAS).
Note: - An
RCAMaxConcurrency value of 100 is suffient in typical cases in which Outlook 2003 has to open
29 shared calendars. This value may have to be increased, depending on which
Outlook add-ins is installed.
Important: - The original release of Exchange Server 2010
allows a maximum parameters value for RCAMaxConcurrency of 100. Exchange server 2010 service pack 1 increase the maximum value for
RCAMaxConcurrency to 2147483647.
I hope this information will be helpful for you.
Thanks and regards
Shweta@G 

Similar Messages

  • Exchange 2010 - Setting up Users Calendar with Free /Busy Details share permssion, Outlook 2007 client cannot open

    Setting up Users Calendar with Free /Busy Details share permssion, Outlook 2007 client cannot open the user shared folder but if we use OWA 2010 or Outlook 2010 client no issue opening the user shared calendar with Free/Busy Details setting.
    The follwowig error is reported
     You do not have sufficient permission to open the calendar folder. you don't have appropriate permission to perform this operation.
    thanks,
    Hussain

    Setting up Users Calendar with Free /Busy Details share permssion, Outlook 2007 client cannot open the user shared folder but if we use OWA 2010 or Outlook 2010 client no issue opening the user shared calendar with Free/Busy Details setting.
    The follwowig error is reported
     You do not have sufficient permission to open the calendar folder. you don't have appropriate permission to perform this operation.
    thanks,
    Hussain
    I built this little command from the "CalendarProcessing" commandlet...  it cleared up my issues ...
    Set-CalendarProcessing -Identity joeuser -AddNewRequestsTentatively $false -AddOrganizerToSubject $true -AllBookInPolicy $true -AllowConflicts $true -AllowRecurringMeetings $true  -AutomateProcessing AutoUpdate -BookingWindowInDays 0 -ConflictPercentageAllowed
    50 -DeleteAttachments $false -DeleteComments $false -DeleteNonCalendarItems $false -DeleteSubject $false -EnableResponseDetails $true -EnforceSchedulingHorizon $true -ForwardRequestsToDelegates $false -MaximumConflictInstances 100 -MaximumDurationInMinutes
    0 -OrganizerInfo $true -ProcessExternalMeetingMessages $true -RemoveForwardedMeetingNotifications $true -RemoveOldMeetingMessages $true -RemovePrivateProperty $false -ScheduleOnlyDuringWorkHours $false -TentativePendingApproval $false -WhatIf
    Look at those settings in technet article dd335046
    good luck
    JLH

  • New-Pssession client cannot connect to the destination specified

    I've used the following cmdlets to connect powershell to our tenant for months and now I cannot open a possession with the same commands.
    I've searched on some of the error text show below without any great progress. We have a pair of Hybrid servers and we get the same result on either.
    Any suggestions are appreciated.
    Bruce
    Import-module msonline
    $O365Cred = Get-Credential
    $O365Session = New-PSSession –ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell -Credential $O365Cred -Authentication Basic -AllowRedirection
    Import-PSSession $O365Session
    Connect-MsolService –Credential $O365Cred
    [email protected]
    working password at the MicrosoftOnline Portal
    $O365Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell -Credential $O365Cred -Authentication Basic –AllowRedirection
    WARNING: Your connection has been redirected to the following URI:
    https://pod51038psh.outlook.com/powershell-liveid?PSVersion=4.0
    New-PSSession : [pod51038psh.outlook.com] Connecting to remote server pod51038psh.outlook.com failed with the following error message : The client cannot connect to the destination specified
    in the request. Verify that the service on the destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service,
    run the following command on the destination to analyze and configure the WinRM service: "winrm quickconfig". For more information, see the about_Remote_Troubleshooting Help topic.
    + $O365Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUr ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotingTransportException + FullyQualifiedErrorId : CannotConnect,PSSessionOpenFailed
    Import-PSSession $O365Session
    Import-PSSession : Cannot validate argument on parameter 'Session'. The argument is null. Provide a valid value for the argument, and then try running the command again.
    At line:1 char:18
    + Import-PSSession $O365Session
    +                 
    ~~~~~~~~~~~~
    + CategoryInfo         
    : InvalidData: (:) [Import-PSSession], ParameterBindingValidationException
    + FullyQualifiedErrorId : ParameterArgumentValidationError,Microsoft.PowerShell.Commands.ImportPSSessionCommand
    Connect-MsolService -Credential $O365Cred

    You are using the outdated URI string, which is known to cause problems. Should be: https://outlook.office365.com/powershell-liveid/
    Just follow the instructions in the TechNet article:
    https://technet.microsoft.com/en-us/library/jj984289(v=exchg.150).aspx

  • Clients cannot connect using afp running lion 10.7.1, worked ok before upgrade from 10.7 to 10.7.1

    I am running a macminiserver on ahome newtwork.  Original running snow leopard and then upgraded to 10.7 lion on all machine and everything was working fine.  Clients coul connected to shared drives on the server using afp.  However, after upgrading to 10.7.1 on the server and client machines, they can no lnger connect to the drives using afp, however you can connect using smb.
    I ahve tried stopping and starting the afp server, rebuilding permissions on the server - still cannot connect using afp.
    Any ideas?

    Be sure the correct Lion afp port is open on your router, even if you are using an Airport (port 548 tcp). Just do a search on "Mac OS X Lion ports".
    Also, if this is outside of the network, use the full server name in the Finder's Connect to Server, afp://server.com; when it prompts for a username, enter your first name and last name (not your short name) and then you also need to enter your password. If you don't have a fqdn, then you can use the static ip for "server.com"
    It should work, working for me inside and outside of the network. Admittedly, I don't think you need the port on the router for internal use, but you can test both ways.
    When working outside of the network a vpn is not required.

  • 8.8 Client cannot connect to Windows Server 2008 error -1102

    SAP Business On 8.8 on PL 18
    This is not the first time I have had this issue with Windows Server 2008.
    however everytime the resolution was diffrent. Now this site is causing trouble.
    The issue is the client cannot connect. We have the log on window, can see the company list. type on the password and we get a -1102 error.
    The client on the Server itself can log on. It is the cleints that cannot.
    I checked these below.
    1 SQL Native client is installed and ok.
    2. Licence server is configured and ok
    3. The user has admin access to locl PC
    4. The SAP user name and password are correct ( client on server can connect fine )
    5. The ports 1433, 30000 and 30001 are open on the server.
    6. Through SQL server configuration the named pipes and TCP are enabled.
    7. SQL server browser is running
    The only things I have not tried are
    The Firewall is running on the server and I have not yet stopped it. Will try that tomorrow.
    Do you have any other ideas please ?

    I have got this working but I am not confidant of the outcome  - yet  - I really need your expert advise here.
    This is what I did. In that order.
    1.     As Owen suggested I checked if there was a specified Port for the instance.  What I found was TCP Dynamic  ports were enabled (  SQL server config manager | network configuration | tcp properties ) and there was no TCP port specified.  Assuming ( ai may be wrong) that the system assigns a dynamic port to this instance  I set it up so the Dynamic port does not happen and manually specified the Port  1433. Restarted the SQL Service. ( still having the Port 1433 open in the firewall). This did not solve the issue.
    2.     With the above setting still on, switched off the firewall. Went to the PC client and SAP can log on now.  Now keeping the SAP client running, switched on the Firewall on the server. Log off SAP on PC client and log back in ( with firewall off ). SAP now can log on.
    3.     I had to do the above step for all PCs to get them working.
    4. Currently the firewall is on and clients can connect
    So what could be happening? I have no clue. It is apparent there is some setting that gets saved within the PCs ( may be user profile) after the first log on with the Firewall off  - to say its safe ?
    However I have no idea what will happen if the server is restarted u2013 this server we cannot restart any time we want as itu2019s a critical server and runs other things. 
    I would still like to get to the bottom of this to understand what is happening.
    I have a SAP message running too and will ask them this same question.

  • ODI Client cannot connect the datebase after the datebase IP changed

    ODI Client cannot connect the datebase after the datebase IP changed.
    1,the datebase on mac A,the mac changed ip
    2,on the client, tnsping db is ok.
    3,use pl/sql ,can connect on the db
    4,with odi,changed the repostry URL to the new db IP,throw the exception below
    java.sql.SQLException: Io Exception: The Network Adapter could not establish the connection
         at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:125)
         at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:162)
         at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:274)
         at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:328)
         at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:361)
         at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:151)
         at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:32)
         at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:595)
         at com.sunopsis.sql.SnpsConnection.u(SnpsConnection.java)
         at com.sunopsis.sql.SnpsConnection.c(SnpsConnection.java)
         at com.sunopsis.sql.h.run(h.java)
    Is anything we need to config after change db machine IP?

    yeah,I got it.Everything is ok now.
    After change IP,we must open TopologyManager:change the JDBC connection of workrepository which must chose in Designer.
    when we open the Designer ,it will connect to db.then coonect to workrepository with original IP.So,we must rechange workrepository's JDBC first!

  • The client cannot connect to the server

    we just installed the boe but found that the client cannot connect to the server.
    server: windows server 2008
                 boe xi3
    client:    window xp sp3
    the server and client are in same dns
    all components are work in server but client.
    any idea on this?
    ps: i can ping the server name successful.
    thanks
    ada
    Edited by: Ada_Wei on Oct 29, 2010 10:12 AM

    Can you please try to stop and disable the Windows firewall service on your client machine?
    WHich client do you use and which error message do you get exactly?
    Regards,
    Stratos

  • My macbook air cannot sync with my office microsoft exchange 2010 mail server

    My macbook air cannot sync with my office microsoft exchange 2010 mail server.
    It used to work perfectly, and then I lost connection and was never able to establish one. I re-istalled my e-mail account several times, no success.

    I am sure all of you got your email issues sorted out by now but i was having trouble settings up exchange email on my Iphone 5S, and the problem i found was to go to settings, icloud, then log into icloud with your apple id first (before setting up the exchange email).  Once i logged into my icloud account on my Phone 5S, the exchange server email starting working and synching right away.
    to confirm this worked, i even deleted my email account and deleted my Icloud accounts both from my iphone was able to simulated the same exact problem (exchange server would not sync with my Iphone 5S) until i logged back into my Icloud account on my 5S.
    Again once i logged into Icloud, the exchange server issues went completely away.
    Just wanted to post this so anyone else having the issue could see.

  • My win 7 home premium cannot connect the sharing printer (EPSON L1100) in Windows server 2003 it say "Windows cannot connect to the printer. Accses denied"

    in My office there is a win server 2003 R2 computer, i install a printer Epson L1100 in that computer, and it successfull, and i can print using that printer from that computer..
    I already share this printer, but when i try to connect the printer from my laptop using OS Win 7 Home Premium.. it has error
    "Windows cannot connect to the printer. Accses denied"...
    and then i try connect using other computer but same OS (win 7 Home premium) it still has same error...
    i usually connect to the server computer using //(the ip of computer) , for example
    //52.30.20.66 .. that is my IP server..
    and than i right click in shared printer which appears in windows explorer, and i choose
    Connect...  but it contain error "Windows cannot connect to the printer. Accses denied"..
    anyone know the solution from this error???
    i`m sorry if my english is bad.. i`m from indonesia

    Got a local password/username on your Win7 ? Create the same on the 2003R2 as you seem in workgroup
    net user /add useraccountname mypassword
    net localgroup users useraccountname /add  (I think it's users the name, you can validate to be sure) or
    net localgroup administrators useraccountname /add in worst case.
    nb, or add the user guess in the printer share security
    Regards, Philippe

  • Outlook 2003 Client connections fail after a while, requiring reboot

    I have Windows 2003 Server terminal servers in several sites, with Outlook 2003 as email clients.  Server is Exchange 2010, located in my main site.  The remote site terminal servers are connected through WAN links that are 5 Mbps connections,
    with generally very low usage compared to capacity.
    Outlook works properly for 2 - 3 days for the remote site users, but then, their connections start to drop, and they see "Outlook is trying to connect the the exchange server ..." systray messages, and they lose their email.  Can't see their
    inbox contents,  though sometimes the tree gets populated.  The only fix is to reboot the terminal server. 
    Similar terminal servers at the main site do not experience this.
    The backstory is that I recently migrated users from Exchange2003 to Exchange2010.  On exchange 2003 we never had this problem.
    What is going on here?

    Hi,
    From your description, I would like to clarify the following things:
    1. Make sure that these problematic users use Microsoft Office Outlook 2003 Service Pack 2 or later version.
    2. The default Exchange Server 2010 RTM configuration requires RPC encryption. However, Microsoft Office Outlook 2003 does not use RPC encryption by default. You need to update an existing Outlook 2003 profile manually so that it uses RPC encryption with
    Exchange 2010.
    For more information about it, here is a helpful KB for your reference.
    Outlook connection issues with Exchange 2010 mailboxes because of the RPC encryption requirement
    https://support.microsoft.com/kb/2006508?wa=wsignin1.0
    Hope this can be helpful to you.
    Best regards,
    Amy Wang
    TechNet Community Support

  • Windows VNC clients cannot connect to Snow Leopard Server native VNC server

    I am resurfacing the following related comment made in another post that discusses the same issue I am having with VNC on Snow Leopard. This is still an issue and I cannot connect to our Xserve's Snow Leopard Server with a VNC client on Windows.
    I don't want to install another third party VNC server onto our SL Server, and am looking for a VNC client for windows that will connect to our SL Server.
    Does anyone have any solutions?
    == QUOTED TEXT BELOW ==
    Re: Newbie: Connect Windows -> OSX Server
    Posted: Nov 4, 2009 9:26 AM in response to: Antonio Rocco
    I would politely disagree. Yes, definitely, the Mac 'Screen Sharing' app works a treat, and Apple Remote Desktop.app works as well, but I am coming from a Window's PeeCee.
    For me, connecting to my 10.5(.8) Server via tightvnc gives 'Server did not offer supported security type!". Using RealVNC to this machine states "No matching security types Do you wish to reconnect to ... ?" a telnet to this AppleVNCServer service (port 5900), shows RFB 003.889 *, or Remote Frame Buffer Major 3, minor 889.
    Also, connecting to multiple 10.6(.1) Clients with Tightvnc correctly asks for a password but then hangs at "Status: Security type requested". Using RealVNC opens, connects, asks for authentication, and exits. Telneting to this AppleVNCServer service (port 5900), also shows RFB 003.889 *.
    The Current Version of the protocol is supposed to be 3.8, that is Major version 3, minor version 8. Not 80 or 800 but Eight). http://www.realvnc.com/docs/rfbproto.pdf and I believe that tightvnc only supports up to version 3.7.
    On each station I have installed the 'old' OSXVnc.app as a service (to a unique port). OSXVnc utilizes protocol 3.3 and I can control them successfully, but that is of my own doing because of this issue.
    Now JollysFastVNC works a treat to any machine I have EVER tried to connect to. I have not tried COTVNC or any of the others (too slow for me, when they wer e around)
    Also, I just noticed that RealVNC states that their free and personal version will not connect to Mac OSX (x86 and PPC) but the Enterprise one will. I just Dl'ed the Enterprise Viewer and it gave essentially the same thing ('protocol is not valid' message, even after it asks for a password). Anyway, I am not here to hijack this thread, just trying to keep the info flowing and open.
    Maybe I am the only one with these problems but the bottom line is I cannot use Real or Tight, or UltraVNC to administer my server or clients as long as AppleVNCServer gives out the 003.889 protocol version.
    Peter
    * The ProtocolVersion message consists of 12 bytes interpreted as a string of ASCII characters in the format "RFB xxx.yyy\n" where xxx and yyy are the major and
    minor version numbers, padded with zeros.

    Searching on the net brought me to the same solution that Mr. Hoffman found as well, I was a bit skeptical at first but since he recommended it, and all my other attempts failed, it was a last resort and I have some additional notes of my own for a successful solution. Read the two links below first before doing anything, as they contribute to the solution in tandem.
    http://forums.macrumors.com/showpost.php?p=7221295&postcount=20
    http://forums.macrumors.com/showpost.php?p=9081641&postcount=28
    I should probably just create an entirely new post with all of the steps that worked for me, but it's rather straightforward nonetheless.

  • External Clients cannot connect to Exchange Server

    Hello all:
    My external clients using outlook cannot connect to Exchange Server 2013.  We have on-presmise version updated to Cu3 and after the Cu3 update we lost connectivity with Outlook clients.  Many of the settings in IIS were changed after the Cu3 update,
    I noticed after my http->https redirect was not applied anymore to the default website.  Here is my Get-OutlookAnywhere results:
    RunspaceId                         : 6379fab1-f692-484f-8118-99e48330d4c4
    ServerName                         : EXCHSERV
    SSLOffloading                      : True
    ExternalHostname                   : mail.domain.com
    InternalHostname                   : mail.domain.com
    ExternalClientAuthenticationMethod : Negotiate
    InternalClientAuthenticationMethod : Ntlm
    IISAuthenticationMethods           : {Basic}
    XropUrl                            :
    ExternalClientsRequireSsl          : True
    InternalClientsRequireSsl          : True
    MetabasePath                       : IIS://EXCHSERV.domain.com/W3SVC/1/ROOT/Rpc
    Path                               : D:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\rpc
    ExtendedProtectionTokenChecking    : None
    ExtendedProtectionFlags            : {}
    ExtendedProtectionSPNList          : {}
    AdminDisplayVersion                : Version 15.0 (Build 775.38)
    Server                             : EXCHSERV
    AdminDisplayName                   :
    ExchangeVersion                    : 0.20 (15.0.0.0)
    Name                               : Rpc (Default Web Site)
    DistinguishedName                  : CN=Rpc (Default Web
                                         Site),CN=HTTP,CN=Protocols,CN=EXCHSERV,CN=Servers,CN=Exchange Administrative
                                         Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=domain,CN=Microsoft
                                         Exchange,CN=Services,CN=Configuration,DC=domain,DC=com
    Identity                           : EXCHSERV\Rpc (Default Web Site)
    Guid                               : 596ed7a1-ceec-4a36-9cbc-617ac5214463
    ObjectCategory                     : domain.com/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
    ObjectClass                        : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
    WhenChanged                        : 12/23/2013 2:20:41 AM
    WhenCreated                        : 11/25/2013 2:51:36 PM
    WhenChangedUTC                     : 12/23/2013 7:20:41 AM
    WhenCreatedUTC                     : 11/25/2013 7:51:36 PM
    OrganizationId                     :
    OriginatingServer                  : DOMAINCONTROLLER.domain.com
    IsValid                            : True
    ObjectState                        : Changed
    Thanks in advance

    Hi,
    According to your description, users cannot connect to Exchange server 2013 both internal and external.
    Please run Test E-mail AutoConfiguration in Outlook to check your autodiscover service. Also
    reset your Exchange virtual directory to connect correctly. If the issue still continues after all configurations are setting properly, collect some Event logs would be helpful.
    If there is any question, please post the results here for further analysis.
    Thanks,
    Winnie Liang
    TechNet Community Support

  • Outlook 2007 Clients Cannot Access Free/Busy Calendar info. for Exchange 2010 Mailbox

    Hi:
    I have Outlook 2007 clients that cannot access Free/Busy Calendar info. for Exchange 2010 mailboxes.  They receive error like "...you do not have appropriate permissions..."
    If those same users logon to a machine running Outlook 2010 then they can view the free/busy info. of the other user's mailbox, so I believe the permissions are set correctly on the mailbox to allow the viewing.
    Any insights are greatly appreciated!
    Thank you!
    Bob Herman IT Tropolis

    Hi Herman,
    As you said, it seems users have proper permissions on mailbox.
    Please make sure users has Reviewer permission on Outlook 2007.
    Please try to run Outlook 2007 under safe mode or re-create profile.
    Also try to turn Outlook 2007 to Exchange Online mode from Cached mode.
    Thanks
    Mavis Huang
    TechNet Community Support

  • Outlook 2003 won't connect with gmail

    I use Outlook 2003 SP3 on my Windows 7 laptop and it will not always pull my gmail down using the Verizon hotspot. My AT&T hotspot works fine, and a direct wifi connection works fine.
    I get the server not available message.
    However, in the Options setup, I can test and receive the gmail just fine, including the test message.
    Some research indicates this might be an issue with IPv6 verses IPv4.
    Other than updating to Outlook 2010 which does not appear to have the same issue, any suggestions?

        Hey there skyking4ar.  That certainly is odd. If you're able to get gmail sometimes you certainly should be able to all of the time, especially if a competitors device is always able to bring it up.
    Do you have any issues with any other websites? Which mobile hotspot device do you have? Are the server settings set up correctly?
    Please provide additional details skyking4ar and we will continue to troubleshoot. I am confident we can resolve the issue.
    NickB_VZW
    VZWSupport
    Follow us on Twitter @VZWSupport

  • Win XP Client Cannot Connect to Mac OS X 10.4.4 Server but Win 2000 Can

    Anyone run into this problem? Just basic Apple/Windows stand alone, no domain or interaction with other Windows Servers. User can log on fine with Windows 2000 client, but same user cannot connect with Windows XP client on same network.
    Any workarounds out there?
    Mac G4 MDD, 1GB RAM, 80MB main drive, 400GB data Mac OS X (10.4.4)

    I had trouble with a WinXP client a while back, and
    only vaguely rememeber things I did to fix it. I'm
    thinking it's the Win system, not the Mac. On the win
    machine, try deselecting the box "Enable IEEE 802.1x
    authen. for this network" in the Properties >
    Authentication tab for your network
    interface.
    Thank you for the suggestion. It worked!

Maybe you are looking for