Outlook 2010 gets disconnected with Exchange 2010

Hi
We are facing a strange issue that some Outlook users are getting disconnected and it reconnects after 1 or 2 hours or after changing the IP of the system. During the Outlook disconnection period we can't even telnet on port 433 to the CAS BLB name or IP
(same time we can able to ping CAS name). The security and network team is checking the same, is there any thing to be checked with Exchange servers regarding this issue?
Thanks in Advance
LMS

Also I found a similar article "http://social.technet.microsoft.com/Forums/exchange/en-US/06f4d721-a778-4437-b43a-9ad6ca70344b/outlook-clients-randomly-disconnected-from-cas-array?forum=exchange2010"
which almost explains the same issue - users are getting disconnected and even unable to telnet teh cluster IP and getting connected after a few minutes.
So we will go ahead and re configure the NLB. We plan to keep the existing NLB on one server and remove and add second node and do the same for the other. What do you think?
LMS

Similar Messages

  • Outlook 2013 not connect with Exchange server 2013 in internal network

    Hello All,
    I Have two Exchange server 2013 in our environment. Both server install mailbox and CAS role. After configure exchange server 2013, Outlook 2013 not connect in internal network. I have configure outlook manually. i tried by using the suggestion from blog
    but not work. Outlook show that Server cannot connect/ server name could not be resolved. in outlook setting i also put exchange proxy setting. In exchange admin center i have changed the OWA, OAB, Auto discover name. But still not work.
    I know that outlook can be connect from external by using ssl certificate and publish outlook anywhere but i did my configure from internal network. 
    Can you please suggest as soon as possible.
    Thanks,
    Parvez

    Hi,
    Firstly, I’d like to explain, same with external users, internal users use Outlook Anywhere to connect with Exchange server and use Autodiscover get all settings.
    Thus, let’s try the following resolutions:
    1. run the following command: get-clientaccessservice |fl autodiscoverserviceinternaluri
    2. check if the host name in the above URL is in the DNS server and there is a DNS entry about the host name points to the proper IP address.
    3. Check if the above host name is in your certificate.
    Thanks,
    Angela
    Angela Shi
    TechNet Community Support

  • Calls Getting disconnected with reason code 26

    Hi,
    Few of my calls are getting disconnected with reason code 26. on agent screen it just flash and disconnect.as per RCD its showing Error code 0( fine) and finally its ending at Skill Group Node. talk time is 1 or 2 seconds. agents having auto answer setting as well as IP Phone set auto ans with headset.
    my setup is IPIVR based UCCE setup.
    Please help
    Regards-
    PK

    Hi PK,
    CD 26 normally indicates Resource Not available in CUCM side. please check the Jtapi gateway process logs for the failed calls. you should be able to see something similar to below
    19:08:37:896 PG1A-jgw1 Trace: ConnFailedEv CID: 27224748 Addr: 80002985 CiscoCause: CAUSE_RESOURCESNAVAIL Cause: CAUSE_RESOURCES_NOT_AVAILABLE.
    if that is the case , please check from CUCM perspective as well.
    Regards,
    Sasikumar.

  • KB953804 for delegatesentitemsstyle in Outlook 2003 in combination with Exchange Server 2010 SP1 not working.

    KB953804 Full  title  "Hotfix for An e-mail message does not appear in a user's mailbox if the e-mail message was sent on behalf of the user by a delegate in Outlook 2003." 
    We have this working for ok Outlook 2003 SP3 in combination with Exchange Server 2003 SP2.  Now for mailboxes that are moved to our new Exchange 2010 environment the hotfix stopped working. The sent items get stuck in the outbox of the delegate instead
    of moving to the user in whose name the mail was sent. It does not matter if the user mailbox is on 2003 or 2010 as long as the delegated user is on Exchange 2010 SP1 it fails. We use Outlook 2003 SP3 in online mode.  Does anyone know how to fix this
    or maybe someone knows an alternative way to move the mails to the sent items with Exchange2010 SP1.

    Hi,
    I'd like to know how did you set "send on behalf",from outlook give delegation permission or from Exchange Server give "send as" right?
    Please try to use get-adpermission to verify if the user has "send as" right.
    Manage Send As Permissions for a Mailbox
    http://technet.microsoft.com/en-us/library/bb676368.aspx
    Note: After you grant send as right, please try to restart Microsoft Information Store.
    By the way, do you receive any NDR or error information when you send on behalf of others?
    Xiu

  • Outlook can't connect with Exchange 2013 after migration from Exchange 2007

    <style type="text/css">P { margin-bottom: 0.21cm; }</style>
    Hello,
    recently we've done a Exchange 2007 sp3 to 2013 sp1. Users can conect perfectly with OWA and with his iphone clients.
    But the problem is they can't connect from his Outlook clients (2010, 2013), both internaly and externaly. Always fails with the message: The Connection to Exchange it is not avaliable.... Can't resolve the name of Exchange server.
    To try to resolve it we've done:
    - Check Outlook anywhere configuration en EAC: it is configure with and external url mail.company.com and internal server.domain.local. The security is the default Negociation, but we've tried all.
    - Check the internal dns, there are records for mail.company.com and exchangeserverdomain.local pointing to the exchange local ip. Also there is a public zone company.com with the record mail.caompany.com pointing to the exchange local ip. Also we've made
    records autodiscover.company.com and autodiscover.domain.local pointing to the exchange local ip.
    - In the public dns from our domain there is the record A and MX pointing our public ip. There aren't any record Autodiscover but we think that the manial conection should work.
    Check certificates: we've made a new self-signed certificate including all this internal and external domains and for all services.
    - Check Outlook Anywhere block: we've cheked.
    Currently server state:
    - Old Exchange 07 server can't start, it was in very bad state and we achieved migrate the mailbox to the new server, after that we tried to uninstall, but it crashes with a public folder replication error. We got uninstall all the roles
    unless the mailbox. After a restart it can't start.
    -The new Exchange 2013 looks great, there isn't any trail of the old server, or we haven't seen anything in the EAC or shell.
    I paste below the result of Microsoft Remote conectivity analaizer, with Outlook anywhere test. It is clear that there is a problem with that.
    Sorry because the test is in spanish and I translated it with google, from here I only can access the tool in spanish.
    We continue to try to resolve the problem.
    Thanks to all in advance!
    Testing RPC / HTTP connectivity.
    Error in testing RPC / HTTP.
    additional Details
    Elapsed time: 24295 ms.
    Test steps
    Connectivity Analyzer Microsoft is trying to test Autodiscover for [email protected] .
    Error in automatic detection test .
    additional Details
    Elapsed time: 24294 ms.
    Test steps
    Attempting each method of contacting the Autodiscover service .
    Failed to properly contact the Autodiscover service using all methods.
    additional Details
    Elapsed time: 24294 ms.
    Test steps
    Trying to prove possible Autodiscover URL https://empresa.com/AutoDiscover/AutoDiscover.xml
    Error in testing this potential Autodiscover URL .
    additional Details
    Elapsed time: 1509 ms.
    Test steps
    Attempting to resolve the host name in DNS empresa.com .
    The host name is resolved correctly .
    additional Details
    IP addresses returned : 80.36.252.194
    Elapsed time: 507 ms.
    Testing TCP port 443 on the host to ensure empresa.com listening or is open.
    The port was opened successfully.
    additional Details
    Elapsed time: 464 ms.
    Testing the SSL certificate to make sure it is valid.
    The SSL certificate is not exceeded one or more certificate validation checks .
    additional Details
    Elapsed time: 537 ms.
    Test steps
    Connectivity Analyzer Microsoft is attempting to obtain the SSL certificate from remote server on port 443 empresa.com .
    Connectivity Analyzer Microsoft successfully obtained the remote SSL certificate.
    additional Details
    Remote Certificate Subject : CN = mail.empresa.com , issuer : CN = mail.empresa.com .
    Elapsed time: 454 ms.
    Validating the certificate name .
    The certificate name was validated successfully .
    additional Details
    Hostname empresa.com was found at the entrance of the alternative subject name of the certificate.
    Elapsed time: 1 ms.
    Is validating the trusted certificate .
    Validation Error trusted certificate.
    Test steps
    Connectivity Analyzer Microsoft is trying to build certificate chains for certificate CN = ​​mail.empresa.com .
    Could not build a certificate chain for the certificate.
    Tell me more about this issue and how to resolve
    additional Details
    The certificate chain did not end in a trusted root . Root = CN = mail.empresa.com
    Elapsed time: 31 ms.
    Trying to prove possible Autodiscover URL https://autodiscover.empresa.com/AutoDiscover/AutoDiscover.xml
    Error in testing this potential Autodiscover URL .
    additional Details
    Elapsed time: 21723 ms.
    Test steps
    Attempting to resolve the host name in DNS autodiscover.empresa.com .
    The host name is resolved correctly .
    additional Details
    IP addresses returned : 46.16.56.40
    Elapsed time: 498 ms.
    Testing TCP port 443 on the host to ensure autodiscover.empresa.com listening or is open.
    The specified port is blocked , not listening or does not generate the expected response .
    Tell me more about this issue and how to resolve
    additional Details
    Network Error communicating with the remote host.
    Elapsed time: 21224 ms.
    Attempting to contact the Autodiscover service with the HTTP redirect method .
    Error when trying to contact the Autodiscover HTTP redirect method .
    additional Details
    Elapsed time: 606 ms.
    Test steps
    Attempting to resolve the host name in DNS autodiscover.empresa.com .
    The host name is resolved correctly .
    additional Details
    IP addresses returned : 46.16.56.40
    Elapsed time: 14 ms .
    Testing TCP port 80 on the host to ensure autodiscover.empresa.com listening or is open.
    The port was opened successfully.
    additional Details
    Elapsed time: 202 ms.
    Connectivity Analyzer Microsoft is checking the automatic detection of host empresa.com for an HTTP redirect to the Autodiscover service.
    Connectivity Analyzer Microsoft could not get a HTTP redirect response for Autodiscover .
    additional Details
    Web exception occurred because an HTTP 404 response was received - Unknown NotFound . Headers received: Connection : close Content- Length: 1209 Content- Type: text / html Date: Wed, 12 Mar 2014 15:27:58 GMT Server : Apache/2.2.9 (Debian ) PHP/5.2.6-1 +
    lenny3 with Suhosin -Patch X -Powered -By : PHP/5.2.6-1 + lenny3 HTTP Response Headers : Connection : close Content- Length: 1209 Content- Type: text / html Date: Wed, 12 Mar 2014 15:27: 58 GMT Server : Apache/2.2.9 (Debian ) PHP/5.2.6-1 + lenny3 with
    Suhosin -Patch X -Powered -By : PHP/5.2.6-1 + lenny3
    Elapsed time: 388 ms.
    Attempting to contact the Autodiscover service using the method of DNS SRV redirect server.
    Connectivity Analyzer Microsoft could not contact the Autodiscover service using the DNS SRV redirect method .
    additional Details
    Elapsed time: 186 ms.
    Test steps
    Trying to find the SRV record in DNS _autodiscover._tcp.empresa.com .
    Not the Autodiscover SRV record in DNS found .
    Tell me more about this issue and how to resolve
    additional Details
    Elapsed time: 186 ms.
    Checking for a CNAME record for Autodiscover in DNS for your domain " empresa.com " to Office 365.
    Could not validate the Autodiscover CNAME record in DNS. If your mailbox is not in Office 365 , you can ignore this warning.
    Tell me more about this issue and how to resolve
    additional Details
    No Autodiscover CNAME record for your domain ' empresa.com ' .
    Elapsed time: 268 ms.
    jspt

    Hello,
    We have the Self-signed certificate that comes with Exchange, and we've created a new self-signed including all our domains mail.company.com, domain.local, exchange13.domain.local, autodiscover.company.com, autodiscover.domain.local.
    below I print you the result os the comand Get-ClientAccesServer | fl . Now we've configured a SPC objetct folow the instructions of Wizard
    Exchange Server Deployment from Microsoft. We've executed the commands in our new Exchange 13, but can't did it in the old Exchange:
    $AutodiscoverHostName = "autodiscover.contoso.com"Get-ExchangeServer | Where {($_.AdminDisplayVersion -Like "Version 8*") -And ($_.ServerRole -Like "*ClientAccess*")} | Set-ClientAccessServer -AutoDiscoverServiceInternalUri https://$AutodiscoverHostName/Autodiscover/Autodiscover.xmlThis is the result of
    RunspaceId                           : 89c86f8e-d156-4480-b31d-59215976879b
    Name                                 : EXCHANGE13
    Fqdn                                 : EXCHANGE13.domain.local
    ClientAccessArray                    :
    OutlookAnywhereEnabled               : True
    AutoDiscoverServiceCN                : EXCHANGE13
    AutoDiscoverServiceClassName         : ms-Exchange-AutoDiscover-Service
    AutoDiscoverServiceInternalUri       : https://autodiscover.company.com/Autodiscover/Autodiscover.xml
    AutoDiscoverServiceGuid              : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
    AutoDiscoverSiteScope                : {Nombre-predeterminado-primer-sitio}
    AlternateServiceAccountConfiguration :
    IsOutOfService                       : False
    WorkloadManagementPolicy             : DefaultWorkloadManagementPolicy_15.0.825.0
    Identity                             : EXCHANGE13
    IsValid                              : True
    ExchangeVersion                      : 0.1 (8.0.535.0)
    DistinguishedName                    : CN=EXCHANGE13,CN=Servers,CN=Exchange Administrative Group
                                           (FYDIBOHF23SPDLT),CN=Administrative
    Groups,CN=First Organization,CN=Microsoft
                                           Exchange,CN=Services,CN=Configuration,DC=domain,DC=local
    Guid                                 : e83055fe-217b-4ed6-9cd0-7711097baf99
    ObjectCategory                       : domain.local/Configuration/Schema/ms-Exch-Exchange-Server
    ObjectClass                          : {top, server, msExchExchangeServer}
    WhenChanged                          : 09/03/2014 12:46:07
    WhenCreated                          : 08/03/2014 19:15:54
    WhenChangedUTC                       : 09/03/2014 11:46:07
    WhenCreatedUTC                       : 08/03/2014 18:15:54
    OrganizationId                       :
    OriginatingServer                    : severdc.domain.local
    ObjectState                          : Unchanged
    I hope this stuff can help you.
    Thanks!!
    jspt

  • Outlook 2013 connection issue with exchange 2013

    my exchange 2013 was upgrade from exchange 2010. after the upgrade (migration), i using outlook 2013 connect to exchange 2013. some very
    weird issues happened.
    when i using auto discovery to create profile and connect to exchange will success. but when i manually create the profilewill failed. the following pic for your reference. (same account, same PC)
    please help, thanks lots!!!!

    This is what changed in Exchange 2013. It uses RPC or HTTPs (Outlook Anywhere) and uses Server GUID to connect...
    "As a result of these architectural changes, there have been some changes to client connectivity. First, RPC is no longer a supported direct access protocol. This means that all Outlook connectivity must take place using RPC over HTTP (also known as
    Outlook Anywhere). At first glance, this may seem like a limitation, but it actually has some added benefits. The most obvious benefit is that there is no need to have the RPC client access service on the Client Access server. This results in the reduction
    of two namespaces that would normally be required for a site-resilient solution. In addition, there is no longer any requirement to provide affinity for the RPC client access service.
    Second, Outlook clients no longer connect to a server FQDN as they have done in all previous versions of Exchange. Outlook uses Autodiscover to create a new connection point comprised of mailbox GUID, @ symbol, and the domain portion of the user’s primary
    SMTP address. This simple change results in a near elimination of the unwelcome message of “Your administrator has made a change to your mailbox. Please restart.” Only Outlook 2007 and higher versions are supported with Exchange 2013."
    From : What's New in Exchange 2013-
    http://technet.microsoft.com/library/jj150540%28EXCHG.150%29.aspx#BKMK_arch
    Blog |
    Get Your Exchange Powershell Tip of the Day from here

  • Outlook save/update error with Exchange 2013 public folder used as Contact Items

    Hello Everybody.
    This problem is driving me crazy.
    In Exchange 2013 i have created a public folder with several subfolders used as Contact Items.
    I've reviewed all settings several times and all is ok.
    Outlook 2010/2013 users several times receive the message:
    "The item cannot be saved to this folder. The folder was deleted or moved, or you do not have permission. Do you want to save a copy of it in the default folder for the item?"
    when try save an existing contact after modification.
    I can assure you that user permissions, server configurations are ok; please, help me.

    Did you make the subfolder the correct type, i.e., a contacts-type folder?
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • Outlook 2013 not compatible with Exchange 2003

    Hello
    Some of my customers bought SBS 2003 R2 just before SBS 2008 was released so they have systems which are only 4+ years old. SBS 2003 came with Exchange 2003 pre-installed. Outlook 2013 does not support Exchange 2003. So they cannot upgrade their Outlook
    clients to 2013 version.
    Microsoft, is this correct?!

    If this post is hard to read, it's because of Dragonsoft!!  (sometimes it is like auto-correct on the phone - "I said WHAT!??")
    Overall I think this is the most interesting thread that I have ever read on Microsoft.com.
    As a computer for professional for over 30 years, I've always followed the context that software products are designed for a three to five-year term, to have more is a luxury.
    When I was first in the industry (1983), Microsoft had a tendency to change the software versions every year to two years. As we approached the era of Windows XP there was an expected lifetime use of three years. Every two years a new product would appear.
    So, when windows XP lasted well beyond the three-year term, it was pretty exciting to not have to spend money on new product, and we all enjoyed the decade of Windows XP.
    The new generation of IT professionals has somehow believe that software products should live more than five years, and it just blows my mind!
    The reason that I make this post, is because I've used SBS ever since Back Office Server 4.5, and the versions of small business server (now called Small Business Server) have always appeared on the market 1 to 3 years after the primary versions of
    Windows for which they are named.  So I always felt that there was a disadvantage to using small business server in that the products appearing inside of SBS had been on the market for a few years before being incorporated into the SBS package. It
    made me feel, at first, that Microsoft was waiting on the level of maturity within the product before creating the SBS package. Now that I look back on the whole process it made me think that the SBS team had some difficulty merging the products into a install
    package which could handle the intricacies of the licensing limitations on the SBS system.
    SBS 2003 was a great tool when it came out, but I found that it was riddled with security holes. To say the least some of my first SBS 2003 servers had their exchange system hacked by outside influences. (These were external facing servers who had websites
    and exchange server running with public domain names, even though there were firewalls!) After a few patches, DNS modifications, reverse DNS entries, and some changes in the exchange system, I was finally able to make the system secure and solid.
    My first real nightmare with SBS was when upgrading to SBS 2003 R2, which, yes, appeared around 2005. You cannot simply upgrade a machine from SBS to a new version.  You must purchase a new server, install the new SBS version, and migrate your
    entire installation to this new host. (While running SBS 2003 for several years and making backups on a tape, I realized that the new hardware on the market would not support a restore from my tape backup!)  The whole process is rather daunting as not
    all of the detailed steps to upgrade work as expected. I had to call, and pay, Microsoft to complete the process because exchange had trouble during the migration.
    So off we went with our new installation of SBS 2003 R2.  Then along came SBS 2008!  I went through the same steps again... new hardware, new software, and, yes, paid Microsoft, again, for support to migrate.
    When SBS 2011 appeared on the scene I was willing to upgrade again. Having gone through this, twice now, I  fully prepared the client to purchase a new system and to purchase the new software. But because I was faced with the whole entire
    nightmare of new hardware, migration, and having to call Microsoft to complete the process, I decided on a new approach. This time we were going to buy server which would run VMware.  (I was not going to get stuck in a hardware box that I could not replace
    if I ever needed to restore the operating system due to a massive failure.)  So off I went, purchasing a new box, installing VMware, and installing my favorite operating system, Microsoft SBS!
    Well, to say the least, it wasn't exactly as exciting as I had expected. Had some trouble getting VMware to settle into the new hardware, as there seemed to be some compatibility issues, but was able to work it out. Eventually, I was able to get started
    on the migration. Things went well up until the point that I got to the exchange migration, and ran into a similar problem as before! A call to Microsoft revealed that it was even a little daunting for the support personnel, but as I documented the things
    that they modified, and even performed a little cleanup, after they performed their cleanup!  I can happily say that I'm no longer worried about hardware issues, when it comes to restoring my SBS server in case of a failure!
    Overall I'm pleased with having used Microsoft SBS solutions over the past 10 years, but I would never expect, nor would I lead my customer to expect, that a product should last 10 years!
    Previous comments have indicated that server should last seven years because they can be depreciated that way, I believe that to be entirely false!  I live in Texas, and the state of Texas DIR program has adopted standards which state that
    you should replace your hardware every five years! State agencies have this as a requirement, and it is not optional!  Many state agencies have gone to leasing their equipment, which is a three-year term. (Where do you think off-lease equipment comes
    from, anyway?)
    One of my primary clients looked at me one day, and directly ask, "Okay, if we spend the $10,000 on the new server and software, how long should it last?"
    Obviously, I wanted to say, "Forever!" But, remembering something that my mother had said (always plan for the worst and you always come out on top!), I said back to them, "I believe we should plan for a three-year lifespan, and if we get
    any more than that, it will be a luxury." Needless to say, there have been some upgrades which lasted well more than three years, but there have been some which have been spot on.
    The SBS server is a huge savings over purchasing the individual products separately. But there have always been some drawbacks during the upgrade process which makes the entire feasibility of the installation top-heavy when it comes to support costs. 
    I have noticed is that the SBS servers require more labor to keep them running smooth, especially with backup procedures and backup software, as SBS always requires a third-party product to make a "real" (restorable) backup.
    A client's expectations should be that you are taking care of their business without them having to worry about what takes place in the tech room. They understand, and realize, that they can pay you a specific amount of money for your support without necessarily
    having to purchase new hardware. But a good, healthy relationship with your client means that they should always be willing to upgrade, whether it is a workstation or server.
    If you allow a client to be painted in a corner, then it's not their fault, it's your fault!  Because, they have no idea what the new technology can do, and don't realize what's on the market. It's your job to keep up with what's current and to deliver
    expectations which make them realize that each year has a dollar value attached to it, whether it is spent, or not.
    If you have a client is unwilling to spend money to upgrade their equipment, then there's something else wrong with their business, and you should probably consider that they may not be in business for very long. So don't make it your problem when
    they are unwilling to spend money.  You don't work for free.
    One last, quick example of the conversation that I had with a client who was unwilling to upgrade because things seem to be working so well.  I put it like this, "You pay me to make certain that your business operates in good times and in
    bad. Right now, everything is fine. If your building were to burn, and the only thing we had were the backups, I cannot go out and purchase new hardware and restore your system successfully.  The equipment that we have operating here is no longer
    available on the market.  If I were to find the equipment, it would be out-of-date, and most likely, used, and I cannot guarantee its compatibility or functionality. So, if I can't restore your system to an operational status, then what would you do?
    I don't believe there are any number of man-hours you can use to recover the information lost. You would probably have to go out of business! If your business becomes my business, then I would try to move to a position where my data is safe and my business
    can continue in the case of catastrophe. The only way I can do this, is to purchase new hardware, new software, and put you back in a position of compatibility with the market. One of the things I always try to do is keep your business operations at a point
    where if I die, someone else can come in and take my place. The whole idea here is to keep your business going."
    It didn't take them long to come back and surprise me, "Make a list of what you need. Don't give us a list of what we need to get by, tell us what we need to be productive for several years.  We don't want to patch this together
    and always have problems."
    And just as a note, your customer can write off $10,000+ per year for new equipment purchases.  I think the number may be higher now. I had one customer who purchased a $15,000 system in December and wrote off $10,000 in one year and the other $5000,
    a month later, in the next year!

  • Client getting disconnected with CTISVR

    Hello Everyone,
    I am using ICM 8.5(2).Recording servers which are communicating with ctisvr are getting disconnected continuously.
    While observing the logs ,found the below mentioned termination reason.
    14:19:16:421 cg1B-ctisvr Transmit queue limit of 15000 messages exceeded by client PGUser (session 223).
    14:19:18:499 cg1B-ctisvr SESSION 223: Terminating client PGUser at (172.19.241.16:3440), E_CTI_UNSPECIFIED_FAILURE
    14:19:18:499 cg1B-ctisvr Trace: CTILockObject::Unlock - WARNING: - Long Lock Warning on Global\Session Lock, Thread 4500 held lock for 2078 ms, exceeded threshold 500 ms
    14:19:18:499 cg1B-ctisvr Trace: TransportProtocol::QueueMSG - PGUser (SessionID 224) , Message queued:  (11517 msgs in the queue, max:15000)
    14:19:18:499 cg1B-ctisvr Trace: TransportProtocol::QueueMSG - Verint (SessionID 226) , Message queued:  (13639 msgs in the queue, max:15000)
    14:19:18:499 cg1B-ctisvr Trace: CTILockObject::Unlock - WARNING: - Long Lock Warning on Global\Master Session Lock, Thread 4500 held lock for 2078 ms, exceeded threshold 500 ms
    14:19:18:499 cg1B-ctisvr Trace: TransportProtocol::UnQueueMSG - PGUser (SessionID 224) , Message unqueued:  (11516 msgs in the queue, max:15000)
    14:19:16:421 cg1B-ctisvr Transmit queue limit of 15000 messages exceeded by client PGUser (session 223).
    14:19:18:499 cg1B-ctisvr SESSION 223: Terminating client PGUser at (172.19.241.16:3440), E_CTI_UNSPECIFIED_FAILURE
    14:19:18:499 cg1B-ctisvr Trace: CTILockObject::Unlock - WARNING: - Long Lock Warning on Global\Session Lock, Thread 4500 held lock for 2078 ms, exceeded threshold 500 ms
    14:19:18:499 cg1B-ctisvr Trace: TransportProtocol::QueueMSG - PGUser (SessionID 224) , Message queued:  (11517 msgs in the queue, max:15000)
    14:19:18:499 cg1B-ctisvr Trace: TransportProtocol::QueueMSG - Verint (SessionID 226) , Message queued:  (13639 msgs in the queue, max:15000)
    14:19:18:499 cg1B-ctisvr Trace: CTILockObject::Unlock - WARNING: - Long Lock Warning on Global\Master Session Lock, Thread 4500 held lock for 2078 ms, exceeded threshold 500 ms
    14:19:18:499 cg1B-ctisvr Trace: TransportProtocol::UnQueueMSG - PGUser (SessionID 224) , Message unqueued:  (11516 msgs in the queue, max:15000)
    Is the termination reason is due to exceeding transmit queue limit of 15000 messages or not???
    If yes kindly suggest the resolution of the same.
    It would be a great help to me.
    Thanks in Advance.
    Regards,
    Arpit Arora

    hi,
    what about the manual?
    http://download.oracle.com/docs/cd/E11882_01/network.112/e10746/toc.htm
    Also some startup information can be found in docid 76629.1 Overview and Configuration of ASO Encryption
    Also if they are interested in encrypting data with TDE I found the following on OTN:
    TDE column encryption Implementation Guide and Script for PeopleSoft :
    http://www.oracle.com/technetwork/database/security/tde-comp-tool-160389.zip
    greetings,
    Harm

  • Sessions get disconnected with a STATUS 26

    I'm running Solaris 10 x86 update 5 will all patches that smpatch said were available and Sunray Software 4.0 with patch 127554.-03. All this is running on an X4150 within ESX 3.5. The DTUs seem to run fine after anywhere between 4 hours to 3 days and then they goto a STATUS 26. I utswitch'd over to this new sunray server so power cycling my DTU only brings me back to my original sunray server that runs fine (solaris 10 x86 update 2, sunray software 4.0 no patches). When i attempt to utswitch back to the new sunray server, i get stuck with the status 26 again. The only way i can log back into the new sunray server is to do a utrestart -c on the new sunray server. Something to note is I only have 2 sunray2 FS DTUs connecting to this new sunray server and they both DON'T get status 26s at the same time.

    We have a set of 7 servers (heterogeneous hardware) all running Solaris 10 on a patch level not older than three month.
    Three of them seem to cause no problems at all (classic UltraSPARC platforms).
    Another also seems not involved though it's differetn hardware (SunFire X4100, AMD Opteron)
    Two occasionally cause this 26D problem (T1 processors)
    And the last one immediately and always "hijacks" all DTUs and then lets them starve. (T6320 blade module, T2 processor)
    Even after putting raysrv7 to offline and stopping the ray services there are still a couple of Xnewt processes occupying DTUs.
    When I do a pstack to one of them it does not look sound with respect to the arguments of pollsys or WaitForSomething.
    We did not yet apply patch 127554-05, but as far as what I'm reading here it does not really sound promising to do so.
    root@raysrv7 1# ps -ef|grep Xnew
    root 13448 13371 0 15:23:06 ? 0:01 /opt/SUNWut/lib/Xnewt :34 -nobanner -auth /var/dt/A:34-gJayhA +bs
    root 22379 22359 0 15:42:48 pts/3 0:00 grep Xnew
    root 13824 13371 0 15:23:07 ? 0:01 /opt/SUNWut/lib/Xnewt :25 -nobanner -auth /var/dt/A:25-pJayhA +bs
    root 13638 13371 0 15:23:07 ? 0:01 /opt/SUNWut/lib/Xnewt :28 -nobanner -auth /var/dt/A:28-mJayhA +bs
    root 14116 13371 0 15:23:08 ? 0:01 /opt/SUNWut/lib/Xnewt :22 -nobanner -auth /var/dt/A:22-sJayhA +bs
    root 13549 13371 0 15:23:07 ? 0:01 /opt/SUNWut/lib/Xnewt :30 -nobanner -auth /var/dt/A:30-kJayhA +bs
    root 15244 13371 0 15:23:10 ? 0:01 /opt/SUNWut/lib/Xnewt :7 -nobanner -auth /var/dt/A:7-BJayhA +bs
    root 13381 13371 0 15:23:06 ? 0:02 /opt/SUNWut/lib/Xnewt :39 -nobanner -auth /var/dt/A:39-bJayhA +bs
    root 14833 13371 0 15:23:09 ? 0:01 /opt/SUNWut/lib/Xnewt :16 -nobanner -auth /var/dt/A:16-yJayhA +bs
    root@raysrv7 2# pstack 13448
    13448: /opt/SUNWut/lib/Xnewt :34 -nobanner -auth /var/dt/A:34-gJayhA +bs
    ffffffff7e2d9c2c pollsys (ffffffff7fff69c0, a, ffffffff7fff7280, 0)
    ffffffff7e273bf0 pselect (a, ffffffff7fff69c0, ffffffff7e444710, ffffffff7e444710, ffffffff7fff7280, 0) + 1f0
    ffffffff7e273f94 select (ff, 10043df08, 0, 0, ffffffff7fffd390, 1005f4d58) + a0
    000000010009e308 WaitForSomething (ffffffff7ffff450, 1, 1005df480, 1003baa00, 1003b1600, 1003baa00) + 5d0
    00000001000d9d0c Dispatch (4800, 1, 1004d6978, 0, 10043ffa8, 4800) + 33c
    00000001001055b8 main (5308, 1003bb874, 1004d6630, 1003b1600, 1005f3cb8, 1005f3cb0) + 930
    000000010003c2bc _start (0, 0, 0, 0, 0, 0) + 17c
    Any suggestions? Any help? Or is this a dead thread?
    Regards
    Karl

  • Outlook keep getting disconnected and Queues in remote hub servers.

    Hi
    We have 3 servers ( Say ServernameA,ServernameB,Server nameC) and databases shared equally and we have 4 farms with same mutli role . Off late, We are getting complaints stating Outlook is frozen for few. Since all the 3 servers are multirole with 12 servers.
    It is hard to see, Which server is causing an issue. Do we have any tools to isolate the exact servers.

    Hi,
    From your description, Outlook is frozen for few users. I recommend you check the database these mailboxes are mounted, and then try to move these problematic mailboxes to another database and check the result.
    Hope this can be helpful to you.
    Best regards,
    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]
    Amy Wang
    TechNet Community Support

  • Outlook 2010 Exchange Server pop-up box keeps popping up

    I just upgraded to Exchange 2010 from Exchange 2003. I have 2 e-mail ***.k12.mi.us and ***schools.org. The new exchange server is ***svr01.***.k12.mi.us. Everything seemed to transfer over ok. The only problem we are having and it's more annoying then
    anything is when anyone opens up outlook they get the  Microsoft Exchange pop-up box. I setup a UCC Cert and I have it setup for both domains, but I can't figure out why this box keeps popping up. I am attaching a screenshot. Thanks for the help with
    this!

    make sure that you setup Exchange webservices correctly. specially
    internal autodiscover and Webservices internal names
    check my article
    http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/A_3002-Exchange-2007-2010-Web-services-and-Autodiscover-Ultimate-Troubleshooting-Guide.html
    Regards, Mahmoud Magdy Watch Arabic Level 300 Videos about Exchange 2010 here: http://vimeo.com/user3271816 follow my blog: http://autodiscover.wordpress.com , Follow me on twitter http://www.twitter.com/_busbar and if you Liked my post please mark it
    as helpful and accept it as an answer

  • Outlook 2010 - server unavailable - clicking Retry works

    I'm just installing Office 2010 on a Win2k8 R2 server with Remote Desktop Services (Exchange server is 2010).  When I start Outlook I get the message "exchange server unavailable", click Retry.  So I click Retry and after a minute Outlook launches. 
    The whole process takes longer than it should I'm sure, but it's consistent: every time at Outlook launch; wait, click Retry, wait, success.  Any ideas what I should check?
    Thanks
    Mark 

    Hi,
    Try to test the problem in Windows Safe mode with networking to check if the problem is caused by the
    background
    programs. If the issue persists, reinstall outlook 2010 and see if the issue persists.
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Thanks Gen Lin-MSFT

  • Outlook 2013 can't communicate with Exchange 2013

    we're just finishing migration to Exchange 2013 and found some Outlook 2013 clients (migrated from Exchange 2010) can't communicate with Exchange 2013. even if i recreate the Outlook profile.
    what worked is to reinstall Office 2013.  just want to get ideas why a reinstall fixed the problem.
    same outlook proxy is there in the account settings.

    Hi,
    What was the symptom that Outlook couldn't communicate with Exchange 2013? Could you please detail this a bit?
    If the Account Settings are completely same before and after the reinstallation, we can say the cause is not on the Exchange side. While I can't guarantee the root cause based
    on the provided information. A reinstallation fixes the corrupted or missing components/files in Office, but it's hard to say what has been fixed during the reinstallation.
    If you still have some Office 2013 clients that have not been reinstalled, try to run Microsoft Office Configuration Analyzer Tool to quickly identify problematic configurations in Outlook:
    https://www.microsoft.com/en-us/download/details.aspx?id=36852
    Regards,
    Melon Chen
    Forum Support
    Come back and mark the replies as answers if they help and unmark them if they provide no help.
    If you have any feedback on our support, please click
    here.

  • Can we connect Outlook with Exchange 2013 with the default Self-signed certificate?

    Hi,
    the question is very simple, but after several days searching in this forums and in the web I have not been able to find a definitive answer YES or NOT. I know that Self-signed certificates are not for a production enviroment and only for labs and we must
    purchase a third party certificate or get one from a internal CA.
    Anyone can answer this question with no doubt?
    Thanks in advance!
    jspt

    Hi Abhi,
    I wrote this question because in a recent migration to 2013 from 2007 we've found with this problem: you can view it in the post http://social.technet.microsoft.com/Forums/exchange/en-US/1ddd1e81-1061-4461-95dd-13de653ef8fe/outlook-cant-connect-with-exchange-2013-after-migration-from-exchange-2007?forum=exchangesvrdeploy.
    Also I have installed a new exchange 2013 in a lab enviroment and I also have unabled to connect from a Outlook 2013. The problem is the same Outlook is unable to detect the exchange server. Many people in this forums told me that have to be a certificate
    problem and for that I posted this question. Honestly, I don't know how to do for Outlook can be connect with Exchange 2013. I don't know what I'm doing wrong.
    Anyway thanks for your answer.
    jspt

Maybe you are looking for