Exchange 2013 Attachment Size Issue

Hi everybody,
I'm having some trouble with an Exchange 2013 server.
The users are not able to receive messages with a size bigger than 10MB, i tried with serveral attachments.
I already did te following:
Changed the maximum receive size through the ECP to 60MB (on the default frontend Exchange), and restarted te transport service.
Set the receive size through PowerShell with the following command.
set-transportconfig -maxreceivesize 35MB
when i check the receive size properties, it accepts 35MB messages. (get-transportconfig -property maxreceivesize)
Also restarted serveral Exchange transport services.
Checked the router if there are any special firewall rules, but there are none.
When I send an email with an attachment (PDF about 4 meg), it receives like it should.
Once I send a same email but with an 11meg PDF file, it is not delivered.
When sending this e-mail and attechment, i checked the box to notify me when the message has been deliverd.
I don't get any response, no NDR, nothing...
Tried e-mail tracking but there is no trace of my message.
Am I missing anything?
Kind regards,
Tim

Hi,
Please check the message size limit on receive connector, by default it’s 35MB
Get-ReceiveConnector “connector name”| fl MaxMessageSize
Also check if there are any message size limit in transport rule.
Get-transportrule | fl MessageSizeOver
Message size limits
https://technet.microsoft.com/en-us/library/bb124345(v=exchg.150).aspx
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]
Lynn-Li
TechNet Community Support

Similar Messages

  • Exchange 2013 Mail Size Limits

    I am having an issue with setting the max send and receive size on Exchange 2013.  I keep getting the following error when I attempt to send a 20 meg file server to an internal exchange account OR if I attempt to send a 20 meg file from the exchange
    server to an external account: 
    #550 5.3.4
    ROUTING.SizeLimit; message size exceeds fixed maximum size for route ##
    I have checked the mail sizes and below is the report.  I currently have both send and receive set to 100MB.  Is there some other setting in 2013 that I am not aware of?
    AnonymousSenderToRecipientRatePerHour                       : 1800
    ClearCategories                                            
    : True
    ConvertDisclaimerWrapperToEml                               : False
    DSNConversionMode                                          
    : UseExchangeDSNs
    ExternalDelayDsnEnabled                                     : True
    ExternalDsnDefaultLanguage                                  :
    ExternalDsnLanguageDetectionEnabled                         : True
    ExternalDsnMaxMessageAttachSize                             : 100 MB (104,857,600 bytes)
    ExternalDsnReportingAuthority                               :
    ExternalDsnSendHtml                                        
    : True
    ExternalPostmasterAddress                                   :
    GenerateCopyOfDSNFor                                        :
    HygieneSuite                                               
    : Standard
    InternalDelayDsnEnabled                                     : True
    InternalDsnDefaultLanguage                                  :
    InternalDsnLanguageDetectionEnabled                         : True
    InternalDsnMaxMessageAttachSize                             : 100 MB (104,857,600 bytes)
    InternalDsnReportingAuthority                               :
    InternalDsnSendHtml                                        
    : True
    InternalSMTPServers                                        
    JournalingReportNdrTo                                       : <>
    LegacyJournalingMigrationEnabled                            : False
    LegacyArchiveJournalingEnabled                              : False
    LegacyArchiveLiveJournalingEnabled                          : False
    RedirectUnprovisionedUserMessagesForLegacyArchiveJournaling : False
    RedirectDLMessagesForLegacyArchiveJournaling                : False
    MaxDumpsterSizePerDatabase                                  : 18 MB (18,874,368 bytes)
    MaxDumpsterTime                                            
    : 7.00:00:00
    MaxReceiveSize                                             
    : 100 MB (104,857,600 bytes)
    MaxRecipientEnvelopeLimit                                   : 500
    MaxRetriesForLocalSiteShadow                                : 2
    MaxRetriesForRemoteSiteShadow                               : 4
    MaxSendSize                                                
    : 100 MB (104,857,600 bytes)
    MigrationEnabled                                           
    : False
    OpenDomainRoutingEnabled                                    : False
    RejectMessageOnShadowFailure                                : False
    Rfc2231EncodingEnabled                                      : False
    SafetyNetHoldTime                                          
    : 2.00:00:00
    ShadowHeartbeatFrequency                                    : 00:02:00
    ShadowMessageAutoDiscardInterval                            : 2.00:00:00
    ShadowMessagePreferenceSetting                              : PreferRemote
    ShadowRedundancyEnabled                                     : True
    ShadowResubmitTimeSpan                                      : 03:00:00
    SupervisionTags                                            
    : {Reject, Allow}
    TLSReceiveDomainSecureList                                  : {}
    TLSSendDomainSecureList                                     : {}
    VerifySecureSubmitEnabled                                   : False
    VoicemailJournalingEnabled                                  : True
    HeaderPromotionModeSetting                                  : NoCreate
    Xexch50Enabled                                             
    : True

    Hello Landfish,
    Good Day...
    The output gives the information that Size limit set for Receive and Send is 100 mb, but setting could have changed. So you can follow the below steps to resolve the issue. 
    There are basically three places where you can configure default message size limits on Exchange:
    Organization transport settings
    Send/receive connector settings
    User mailbox settings.
    To check your server’s current limit you can open Exchange Management Shell
    Try the below commands to check the Message quota size limit
    get-transportconfig | ft maxsendsize, maxreceivesize
    get-receiveconnector | ft name, maxmessagesize
    get-sendconnector | ft name, maxmessagesize
    get-mailbox Administrator |ft Name, Maxsendsize, maxreceivesize
    To change the above size limits based on your requirement.
    Set-TransportConfig -MaxSendSize 200MB -MaxReceiveSize 500MB (Size is based on your requirement)
    Attachment size limit
    To set up the rule you can use the below PowerShell cmdlet, as the method is quite simple
    New-TransportRule -Name LargeAttach -AttachmentSizeOver 20MB -RejectMessageReasonText "Message attachment size over 20MB - email rejected."
    For More info
    https://technet.microsoft.com/en-us/library/bb124708(v=exchg.150).aspx
    Remember to 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 Check out my latest blog posts @ Techrid.com

  • Exchange 2013 Mailbox Size Limits

    Are there any hard limits on mailbox sizes in Exchange 2013 (either in terms of mailbox size or item count)?
    Note: I am aware of the public folder mailbox size limits as well as the hard limit of 2TB for mailbox databases.

    I believe the max mailbox size is 100 GB
    http://blogs.technet.com/b/ashwinexchange/archive/2012/12/17/3541150.aspx
    Major changes in Information Store
    Managed Store
    Newly rewritten Information Store processes, Microsoft.Exchange.Store.Service.exe and Microsoft.Exchange.Store.Worker.exe.
    Each database runs under its own process, allowing for isolation of store issues to a single database.
    Tightly integrated with MSExchangeRepl.exe to provide higher availability through improved resiliency.
    Public Folder Database no longer exist.
    Exchange 2013 it supports up to 100 GB of Mailbox size, with OL2013 OST file size can be controlled.
    Exchange 2013 Enterprise Edition can only mount 50 databases on a mailbox server

  • Exchange 2013 Mail Receiving Issues

    Hi everybody,
    Yesterday I configured a new DC and Exchange on Hyper-V (Server 2012 and Exchange 2013)
    All functions and rolls are configured and installed but i am having issues receiving external e-mails.
    Almost all of the external mails are being deliverd a half hour to a hour after being sent.
    To start of on the first level.
    I got a Siemens Fiber modem with an external address connected to the WAN of my Draytek 2995 router.
    Alle the needed ports are forwarded to the Draytek (80,443,25,1723).
    The Draytek DHCP function is set to off.
    192.168.168.2  (DC) -> 80 (HTTP IIS)
    192.168.168.2 (DC) -> 1723 (RRAS)
    192.168.168.3 (Exchange) -> 25 (SMTP)
    192.168.168.3 (Exchange) -> 443 (SSL)
    My Draytek router is connected through LAN1 to a HP switch (unmanaged).
    The physical server has 3 NIC's, all of these are connected to the HP Switch
    I Disabled Hyper-V Queuing on the NIC's because this causes an issue with slow network connections.
    The network has been configured as following.
    I configured the Server 2012 R2 on the hardware(physical server) with only the Hyper-V roll.
    NIC1is setup for the physical server,
    IP Address: 192.168.168.1
    Subnet: 255.255.255.0
    Gateway: 192.168.168.254 (Draytek address)
    DNS: 192.168.168.254 (Draytek address)
    The Server software firewall has been set to a private network through the local security policy.
    I have setup 2 VM's through the Hyper-V roll.
    The first VM is the Server 2012 R2 Domain controller.
    For this VM I created a virtual switch connected to my second NIC(2).
    I unchecked the box where my host can communicate with the NIC(2).
    The DC has been configured as following:
    Hostname: SERVER
    IP Address: 192.168.168.2
    Subnet: 255.255.255.0
    Gateway: 192.168.168.254
    DNS: 127.0.0.1
    I can ping to all the adresses from this server (internal and external).
    The server has been promoted to domain controller with the following rolls.
    ActiveDirectory, Certificate Autohority, DHCP, DNS, RRAS, RDP.
    Alle these rolls have been set and working. (all have been tested)
    DHCP has all options configured (scope, router-192.168.168.254, dns-192.168.168.2)
    A DNS simple and recursive test work fine.
    I did no configuration on the DNS after the DC PROMO.
    So i created users in the AD.
    After that I created a second VM, this one is used for the Exchange.
    I setup a second virtual switch connected to NIC3 and installed Server 2012 R2 with the following config.
    Hostname: SERVER
    IP Address: 192.168.168.3
    Subnet: 255.255.255.0
    Gateway: 192.168.168.254
    DNS: 192.168.168.2 (pointing to the DC)
    I joined this server to the domain, everything is working fine.
    Both servers have internet and network.
    Running portscans on 1723 and 80 all work like a charm.
    No its time to install Exchange.
    I ran all the prerequisits and PowerShell commands (IAcceptLicense. etc.)
    Installed de needed API and filters.
    Installed Frameworks 3.5 on both servers.
    And the Exchange installation was succesfull.
    CU3 is also installed.
    I configured the send connector, accepted domains etc.
    Created all needed certificates (self signed)
    Did a portscan on 433 and 25 and they work.
    All the hosting records are set mail.domain.nl etc. and MX records.
    I created inboxes for the users and was able to connect them to the users in the Active Directory on the DC without any problems.
    Connecting through the internet to OWA works perfect and i can login with users.
    Sending e-mail internally works perfect, the messages are being deliverd in an instant.
    Sending e-mail externally also works perfect, i receive mails in a few seconds on a person email address.
    But when i reply or send e-mail to my new Exchange it can take up to hours to receive the mails!
    I did online SMTP checks and e-mail checks, the all come out like it should.
    One message from MX TOOLBOX on the SMTP:
    SMTP Transaction Time
    8.408 seconds - Not good! on Transaction Time
    I have nog other receive connectors setup, just the standard connectors.
    So i got into the Exchange ECP and under "server" i setup the DNS to listen to 192.168.168.2 (DC).
    I've read that when this is set to all ip addresses it can cause mail delay, but no luck.
    I ran the best practices analyzer and get about 23 errors and 20 warnings.
    A lot of services are unhealt like the "ExchangeTransport).
    I have no idea what is causing the issues and read almost every forum.
    Does anyone have a clue what is going on?
    Did i miss something, is there a misconfiguration?
    Best regards,
    Tim

    The mailserver did not receive any e-mails in this timespan, it was not an issue with the connector to the user mailboxes.
    The internal e-mail also works flawless.
    The entire Exchange server just not received this mail in time.
    I sent an e-mail from my personal accout with the option in my outlook to receive a delivery-reply.
    I got the reply as soon as the mail was deliverd, this took about a half hour to a hour.
    After you asked me about the firewall, i got a hunch..
    It had to be on the incomming connection, so i checked every single firewall on the network and disabled them.
    Still the same problem...
    But there was still one ethernet device that could have a firewall, the internet modem!
    This ATM modem receives multiple external IP's from the ISP, so I figured there was no firewall on this device. (Just like all the cable modems that are deliverd in our area by Ziggo(ISP).
    But I was wrong, there was a firewall enabled on the modem!
    All the ports in the modem had been forwarded but somehow the modem-firewall filtered the traffic,
    creating the issue on the incomming e-mail.
    I disabled the firewall and all the external e-mails are being received in an instant!
    Re-enabled all the software firewalls on the servers and re-enabled the malware filter through powershell, after these steps I did another test, and everything still works like a charm!
    Many thanks for your help Kjartan!

  • Exchange 2007 - Exchange 2013 Mailbox Migration Issues

    Exchange 2013 -  Mail Flow is working.   OWA Access is great.   We have issues connecting Outlook 2010 Clients.  If I create a new user and mailbox Outlook 2010 works fine.   However, if we migrate a user's mailbox to the new Exchange
    2013 server.  Outlook Web (OWA) works and mail flow but "OUTLOOK 2010 can not connect to the new server"  There is something different about a newly created account and a migrated account.  Any help would be great.   I did check
    inheritance in AD and it was on for these accounts.  This occurs with any account migrated to the new server.

    1. Could you double check your Exchange 2007 Internal Autodiscover URI - it should be pointing to Exchange 2013. All clients should be receiving their autodiscover config from the Exchange 2013 server. Based on the client's mailbox location, Exchange 2013
    generates and provides the correct information.
    2. If the autodiscover URI is "autodiscover.yourdomain.com" and you've configured Split-Brain DNS or Pin-Point DNS zones on the local network, make sure the name is resolved to Exchange 2013 internal IP address.
    Step by Step Screencasts and Video Tutorials

  • Exchange 2013 Hybrid Deployment issues.

    Hello.
    i have an issue when configuring Exchange hybrid deployment in my environment.
    when i complete the Exchange hybrid wizard and OAuth is finished our exchange environment will not receive emails from the "internet" as in senders outside the company.
    mail will can be sent out and will flow between internal users.
    when i check the message trace on 365 the emails were failing with the following error.
    Users were also getting a bounce back saying 
    Diagnostic-Code: smtp;550 5.4.1 [[email protected]]: Recipient address rejected: Access denied
    i wondered if it had anything to do with the MX record on our public DNS, i changed this to the one recommended by O365 domain DNS assistant, but this made no odds,
    it looks like it could be a receive connector issue however i am new to exchange so i am still learning.
    the only way to fix the issue was to run Remove-Hybridconfiguration on the Exchange 2013 server, when this finished and few moments had passed mail began being received from the internal again.
    Any Suggestions on what could be caused 
    many thanks

    Hello.
    i have an issue when configuring Exchange hybrid deployment in my environment.
    when i complete the Exchange hybrid wizard and OAuth is finished our exchange environment will not receive emails from the "internet" as in senders outside the company.
    mail will can be sent out and will flow between internal users.
    when i check the message trace on 365 the emails were failing with the following error.
    Users were also getting a bounce back saying 
    Diagnostic-Code: smtp;550 5.4.1 [[email protected]]: Recipient address rejected: Access denied
    i wondered if it had anything to do with the MX record on our public DNS, i changed this to the one recommended by O365 domain DNS assistant, but this made no odds,
    it looks like it could be a receive connector issue however i am new to exchange so i am still learning.
    the only way to fix the issue was to run Remove-Hybridconfiguration on the Exchange 2013 server, when this finished and few moments had passed mail began being received from the internal again.
    Any Suggestions on what could be caused 
    many thanks
    Make sure the accepted SMTP domains in the Office 365 EAC are set to Internal Relay rather then Authoritative.
    Twitter!:
    Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • Exchange 2013 Healthset HubAvailabilityProbe issue

    Hi there
    We are having problem with Exchange 2013 Health probe. We have six on premises Exchange servers in 2 datacenters. Four of them are in DAG cluster and two have CAS role. We also use SCOM 2012 for monitoring. We regularly get alert
    from Exchange HubAvailability probe: 
    Date and Time:
    3/26/2014 8:32:35 PM
    Log Name:
    Microsoft-Exchange-ManagedAvailability/Monitoring
    Source:
    Microsoft-Exchange-ManagedAvailability
    Event Number:
    4
    Level:
    1
    Logging Computer:
    SPBMBS02.nwx.local
    User:
    NT
    AUTHORITY\SYSTEM
    Description:
    The HubAvailabilityProbe has
    failed 5 or more times in 15 minutes.
    Event Data:
    <
    DataItem
    type ="
    System.XmlData "
    time =" 2014-03-26T20:32:35.2416862+04:00
    " sourceHealthServiceId
    =" EF2A415B-F75E-4243-55A2-24292AA4550B
    " >
    <
    UserData
    >
    <
    EventXML
    >
    < HealthSet
    > HubTransport
    </ HealthSet
    >
    < Subject
    > The
    HubAvailabilityProbe has failed 5 or more times in 15 minutes.
    </ Subject
    >
    < Message
    > The
    HubAvailabilityProbe has failed 5 or more times in 15 minutes.
    </ Message
    >
    < Monitor
    > HubAvailabilityMonitor
    </ Monitor
    >
    </ EventXML
    >
    </ UserData
    >
    </ DataItem
    >
    At the same time we don't notice any problem with mail flow. I suggest that some email may stuck in queue but we can't verify which one. What should we do in this situation? Ignore alert or investigate what cause it or may be change probe
    settings?
    I apprecitate for any help and ideas!
    Regards
    John

    Hi,
    OK. To figure out why the probe is failing, you can fist list the configuration details of HubAvailabilityProbe. Make sure the SMTP server is right in the ExtentionAttributes property.
    (Get-WinEvent -LogName Microsoft-Exchange-ActiveMonitoring/ProbeDefinition | % {[XML]$_.toXml()}).event.userData.eventXml | ?{$_.Name -like "HubAvailabilityProbe"}
    If you want to override the thresholds and parameters used by the probes, you can use the Add-GlobalMonitoringOverride command. For more details about the command, you can refer to the following article.
    http://technet.microsoft.com/en-us/library/jj218683(v=exchg.150).aspx
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Exchange 2013 mailbox migration issues

    or I could just restart the 2013 mail server.... *sigh*

    So Exchage 2013 is set up, sending and receiving emails is working, OWA access is working and redirecting to our old 2010 if the mailbox resides there.However after moving a mailbox from 2010 to 2013 there have been a few issues.The mailbox connects ok with Outlook 2013, but will not open the onprem Archive."cannot expand the folder. The set of folders cannot be opened. Microsoft Exchange is not available.."This works ok in OWA.I then deleted the outlook profile, but now Outlook cannot connect to create a profile at all!It detects my name and email ok, then when it gets to "logging on to the mail server" I get the error"Outlook cannot log on. Verify you are connected to the network and are using the proper server and mailbox name. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this...
    This topic first appeared in the Spiceworks Community

  • Exchange 2013 Database Size didn't reduction after user move another DB.

    Hi, I have two Exchange Server Ex01, Ex02 and two database DB1 and DB2. Already we move few user DB1 to DB2 but DB1 database size didn't reduction after move user. 
    Md. Ramin Hossain

    Hi ,
    If you delete or move a mailbox from a database will not create a free space on that database.Instead a white-space will be created on that database during the online defragmentation and that will not make any changes on the physical size of the database
    .Then that white-space will be used when a new mailbox is created on that same database.
    In case if you wanted to convert those white space to free space then you need to do an offline defragmentaion and that will make the physical change in the size of the database
    Note : For offline defragmentation we should have the database to be in a dismounted state.
    Command for offline defragmentation : 
    eseutil /d "path of the edb file"
    But my suggestion would be to move the mailboxes to the newly created database instead of doing the offline defragmentation to attain the free space .Because it would take too much of time for the large databases to get completed.
    Reference link for offline defragmentation : 
    http://exchangeserverpro.com/defrag-exchange-2010-mailbox-database/
    Command to see the white space on the mailbox database :
    ESEUTIL /MS "path of the edb file"
    To execute the above we need the database to be in a dismounted state.
    Reference Link : 
    https://social.technet.microsoft.com/Forums/office/en-US/4059c686-7c02-483b-9b15-891ca55295fe/running-the-eseutil-command-on-each-exchange-database-to-verify-database-whitespace?forum=exchangesvrgeneral
    Please reply me if anything is unclear.
    Thanks & Regards S.Nithyanandham

  • Exchange 2013 CU6 IMAP issue

    Installed CU6 on my EX2013 server on 8/29. Ran fine for a day. Then, for some reason, my IMAP has stopped working.
    There are errors like this:
    Performance counter updating error. Counter name is Time in Resource per second, category name is MSExchange Activity Context Resources. Optional code: 2. Exception: The exception thrown is : System.InvalidOperationException: Instance 'ad-microsoft.exchange.imap4service-microsoft.exchange.imap4service.exe'
    already exists with a lifetime of Process.  It cannot be recreated or reused until it has been removed or until the process using it has exited.
        at System.Diagnostics.SharedPerformanceCounter.FindInstance(Int32 instanceNameHashCode, String instanceName, CategoryEntry* categoryPointer, InstanceEntry** returnInstancePointerReference, Boolean activateUnusedInstances, PerformanceCounterInstanceLifetime
    lifetime, Boolean& foundFreeInstance)
        at System.Diagnostics.SharedPerformanceCounter.GetCounter(String counterName, String instanceName, Boolean enableReuse, PerformanceCounterInstanceLifetime lifetime)
        at System.Diagnostics.SharedPerformanceCounter..ctor(String catName, String counterName, String instanceName, PerformanceCounterInstanceLifetime lifetime)
        at System.Diagnostics.PerformanceCounter.InitializeImpl()
        at System.Diagnostics.PerformanceCounter.get_RawValue()
        at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.get_RawValue()
    Last worker process info : System.ComponentModel.Win32Exception (0x80004005): Access is denied
        at System.Diagnostics.Process.GetProcessHandle(Int32 access, Boolean throwIfExited)
        at System.Diagnostics.Process.get_HasExited()
        at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.GetLastWorkerProcessInfo()
    Processes running while Performance counter failed to update: 
    6104 Microsoft.Exchange.Store.Service
    2556 noderunner
    2108 conhost
    6100 Microsoft.Exchange.Imap4
    3928 MSExchangeThrottling
    572 lsass
    5428 Microsoft.Exchange.Imap4Service
    1948 SMSvcHost
    3128 MSExchangeSubmission
    1748 WmiPrvSE
    564 services
    2936 Microsoft.Exchange.ServiceHost
    756 LogonUI
    952 svchost
    776 svchost
    4888 MSExchangeDagMgmt
    2720 Microsoft.Exchange.RpcClientAccess.Service
    6264 Microsoft.Exchange.Store.Worker
    1336 Microsoft.Exchange.Diagnostics.Service
    5484 Microsoft.Exchange.EdgeSyncSvc
    1728 SFService
    1136 fms
    5272 MSExchangeDelivery
    1528 MSExchangeHMHost
    2512 noderunner
    1916 updateservice
    6364 MSExchangeMailboxReplication
    2504 noderunner
    1408 sftracing
    3092 MSExchangeHMWorker
    1308 inetinfo
    1908 noderunner
    5452 w3wp
    2496 scanningprocess
    1116 svchost
    520 winlogon
    1896 MSOIDSVC
    5832 MSExchangeFrontendTransport
    4452 umservice
    1496 SFService
    5632 Microsoft.Exchange.Search.Service
    4448 Microsoft.Exchange.AntispamUpdateSvc
    4644 w3wp
    3064 msexchangerepl
    1088 spoolsv
    1868 mqsvc
    2060 WMSvc
    680 svchost
    5012 UMWorkerProcess
    3632 rundll32
    4812 Microsoft.Exchange.UM.CallRouter
    280 smss
    476 csrss
    460 svchost
    468 wininit
    4988 SMSvcHost
    860 svchost
    1248 MSOIDSVCM
    5480 Microsoft.Exchange.Imap4
    5580 conhost
    4240 MSExchangeTransportLogSearch
    3212 rundll32
    6560 MSExchangeTransport
    2124 wsbexchange
    844 dwm
    3104 conhost
    2416 MSExchangeMigrationWorkflow
    7124 EdgeTransport
    636 svchost
    7136 conhost
    2800 scanningprocess
    6148 MSExchangeMailboxAssistants
    2404 taskhost
    2400 ForefrontActiveDirectoryConnector
    5156 WmiPrvSE
    3972 scanningprocess
    2196 Microsoft.Exchange.Directory.TopologyService
    1724 svchost
    1208 hostcontrollerservice
    1796 svchost
    808 svchost
    6120 Microsoft.Exchange.Imap4Service
    404 csrss
    4 System
    0 Idle
    Performance Counters Layout information: A process is holding onto a transport performance counter. processId : 7124, counter : time in resource per second Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 7124 StartupTime: 130540706592435178, currentInstance
    : rpca-edgetransport-edgetransport.exe(911B6EB3) RefCount=1 SpinLock=0 Offset=28376, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 7124, counter : time in resource per second Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 7124 StartupTime: 130540706592435178, currentInstance : mb-edgetransport-edgetransport.exe(A5AF4BBC)
    RefCount=1 SpinLock=0 Offset=28048, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 7124, counter : time in resource per second Value=58 SpinLock=0 Lifetime=Type: 1 ProcessId: 7124 StartupTime: 130540706592435178, currentInstance : ad-edgetransport-edgetransport.exe(E79D4A36)
    RefCount=1 SpinLock=0 Offset=27720, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 6264, counter : time in resource per second Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 6264 StartupTime: 130540706609778922, currentInstance : rpca-microsoft.exchange.store.worker-microsoft.exchange.store.worker.exe(ABB009B3)
    RefCount=1 SpinLock=0 Offset=27392, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 6264, counter : time in resource per second Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 6264 StartupTime: 130540706609778922, currentInstance : mb-microsoft.exchange.store.worker-microsoft.exchange.store.worker.exe(38BA31BC)
    RefCount=1 SpinLock=0 Offset=27064, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 6264, counter : time in resource per second Value=4 SpinLock=0 Lifetime=Type: 1 ProcessId: 6264 StartupTime: 130540706609778922, currentInstance : ad-microsoft.exchange.store.worker-microsoft.exchange.store.worker.exe(11106236)
    RefCount=1 SpinLock=0 Offset=26736, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 6120, counter : time in resource per second Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 6120 StartupTime: 130540706478372662, currentInstance : rpca-microsoft.exchange.imap4service-microsoft.exchange.imap4service.exe(128A1B3)
    RefCount=1 SpinLock=0 Offset=26408, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 6120, counter : time in resource per second Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 6120 StartupTime: 130540706478372662, currentInstance : mb-microsoft.exchange.imap4service-microsoft.exchange.imap4service.exe(B4CBDCBC)
    RefCount=1 SpinLock=0 Offset=26080, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 6120, counter : time in resource per second Value=37 SpinLock=0 Lifetime=Type: 1 ProcessId: 6120 StartupTime: 130540706478372662, currentInstance : ad-microsoft.exchange.imap4service-microsoft.exchange.imap4service.exe(F0E98836)
    RefCount=1 SpinLock=0 Offset=25752, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 6560, counter : time in resource per second Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 6560 StartupTime: 130540706541185174, currentInstance : rpca-msexchangetransport-msexchangetransport.exe(24F56C33)
    RefCount=1 SpinLock=0 Offset=25424, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 6560, counter : time in resource per second Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 6560 StartupTime: 130540706541185174, currentInstance : mb-msexchangetransport-msexchangetransport.exe(92FB3D3C)
    RefCount=1 SpinLock=0 Offset=25096, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 6560, counter : time in resource per second Value=9 SpinLock=0 Lifetime=Type: 1 ProcessId: 6560 StartupTime: 130540706541185174, currentInstance : ad-msexchangetransport-msexchangetransport.exe(2447ECB6)
    RefCount=1 SpinLock=0 Offset=24768, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 6364, counter : time in resource per second Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 6364 StartupTime: 130540706526185172, currentInstance : rpca-msexchangemailboxreplication-msexchangemailboxreplication.exe(276F4DB3)
    RefCount=1 SpinLock=0 Offset=24440, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 6364, counter : time in resource per second Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 6364 StartupTime: 130540706526185172, currentInstance : mb-msexchangemailboxreplication-msexchangemailboxreplication.exe(95E41BC)
    RefCount=1 SpinLock=0 Offset=24112, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 6364, counter : time in resource per second Value=77 SpinLock=0 Lifetime=Type: 1 ProcessId: 6364 StartupTime: 130540706526185172, currentInstance : ad-msexchangemailboxreplication-msexchangemailboxreplication.exe(394712B6)
    RefCount=1 SpinLock=0 Offset=23784, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 5480, counter : time in resource per second Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 5480 StartupTime: 130540706497122672, currentInstance : rpca-microsoft.exchange.imap4-microsoft.exchange.imap4.exe(EAAB5DD3)
    RefCount=1 SpinLock=0 Offset=23456, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 5480, counter : time in resource per second Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 5480 StartupTime: 130540706497122672, currentInstance : mb-microsoft.exchange.imap4-microsoft.exchange.imap4.exe(1FC2541C)
    RefCount=1 SpinLock=0 Offset=23128, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 5480, counter : time in resource per second Value=97 SpinLock=0 Lifetime=Type: 1 ProcessId: 5480 StartupTime: 130540706497122672, currentInstance : ad-microsoft.exchange.imap4-microsoft.exchange.imap4.exe(17E0EA16)
    RefCount=1 SpinLock=0 Offset=22800, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 6148, counter : time in resource per second Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 6148 StartupTime: 130540706513997680, currentInstance : rpca-msexchangemailboxassistants-msexchangemailboxassistants.exe(DEAC0933)
    RefCount=1 SpinLock=0 Offset=22472, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 6148, counter : time in resource per second Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 6148 StartupTime: 130540706513997680, currentInstance : mb-msexchangemailboxassistants-msexchangemailboxassistants.exe(A754293C)
    RefCount=1 SpinLock=0 Offset=22144, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 6148, counter : time in resource per second Value=20 SpinLock=0 Lifetime=Type: 1 ProcessId: 6148 StartupTime: 130540706513997680, currentInstance : ad-msexchangemailboxassistants-msexchangemailboxassistants.exe(EE890EB6)
    RefCount=1 SpinLock=0 Offset=21816, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 6104, counter : time in resource per second Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 6104 StartupTime: 130540706510560188, currentInstance : rpca-microsoft.exchange.store.service-microsoft.exchange.store.service.exe(A07BD4F3)
    RefCount=1 SpinLock=0 Offset=21488, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 6104, counter : time in resource per second Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 6104 StartupTime: 130540706510560188, currentInstance : mb-microsoft.exchange.store.service-microsoft.exchange.store.service.exe(4519AFC)
    RefCount=1 SpinLock=0 Offset=21160, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 6104, counter : time in resource per second Value=60 SpinLock=0 Lifetime=Type: 1 ProcessId: 6104 StartupTime: 130540706510560188, currentInstance : ad-microsoft.exchange.store.service-microsoft.exchange.store.service.exe(6B0DD0F6)
    RefCount=1 SpinLock=0 Offset=20832, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 5452, counter : time in resource per second Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 5452 StartupTime: 130540706426185171, currentInstance : rpca-w3wp-msexchangeservicesapppool(E8BBF810)
    RefCount=1 SpinLock=0 Offset=20504, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 5452, counter : time in resource per second Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 5452 StartupTime: 130540706426185171, currentInstance : mb-w3wp-msexchangeservicesapppool(10FE94BF)
    RefCount=1 SpinLock=0 Offset=20176, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 5452, counter : time in resource per second Value=13 SpinLock=0 Lifetime=Type: 1 ProcessId: 5452 StartupTime: 130540706426185171, currentInstance : ad-w3wp-msexchangeservicesapppool(E0DE475)
    RefCount=1 SpinLock=0 Offset=19848, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 5832, counter : time in resource per second Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 5832 StartupTime: 130540706450716432, currentInstance : rpca-msexchangefrontendtransport-msexchangefrontendtransport.exe(935D2AB3)
    RefCount=1 SpinLock=0 Offset=19520, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 5832, counter : time in resource per second Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 5832 StartupTime: 130540706450716432, currentInstance : mb-msexchangefrontendtransport-msexchangefrontendtransport.exe(52FB38BC)
    RefCount=1 SpinLock=0 Offset=19192, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 5832, counter : time in resource per second Value=61 SpinLock=0 Lifetime=Type: 1 ProcessId: 5832 StartupTime: 130540706450716432, currentInstance : ad-msexchangefrontendtransport-msexchangefrontendtransport.exe(409CE636)
    RefCount=1 SpinLock=0 Offset=18864, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 5632, counter : time in resource per second Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 5632 StartupTime: 130540706435247685, currentInstance : rpca-microsoft.exchange.search.service-microsoft.exchange.search.service.exe(3A401CB3)
    RefCount=1 SpinLock=0 Offset=18536, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 5632, counter : time in resource per second Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 5632 StartupTime: 130540706435247685, currentInstance : mb-microsoft.exchange.search.service-microsoft.exchange.search.service.exe(C67EE73C)
    RefCount=1 SpinLock=0 Offset=18208, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 5632, counter : time in resource per second Value=22 SpinLock=0 Lifetime=Type: 1 ProcessId: 5632 StartupTime: 130540706435247685, currentInstance : ad-microsoft.exchange.search.service-microsoft.exchange.search.service.exe(FFDEB6B6)
    RefCount=1 SpinLock=0 Offset=17880, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 5484, counter : time in resource per second Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 5484 StartupTime: 130540706428060178, currentInstance : rpca-microsoft.exchange.edgesyncsvc-microsoft.exchange.edgesyncsvc.exe(5590F433)
    RefCount=1 SpinLock=0 Offset=17552, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 5484, counter : time in resource per second Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 5484 StartupTime: 130540706428060178, currentInstance : mb-microsoft.exchange.edgesyncsvc-microsoft.exchange.edgesyncsvc.exe(AC0B4E3C)
    RefCount=1 SpinLock=0 Offset=17224, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 5484, counter : time in resource per second Value=300 SpinLock=0 Lifetime=Type: 1 ProcessId: 5484 StartupTime: 130540706428060178, currentInstance : ad-microsoft.exchange.edgesyncsvc-microsoft.exchange.edgesyncsvc.exe(7321B36)
    RefCount=1 SpinLock=0 Offset=16896, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 4888, counter : time in resource per second Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 4888 StartupTime: 130540706368372679, currentInstance : rpca-msexchangedagmgmt-msexchangedagmgmt.exe(AEDE63B3)
    RefCount=1 SpinLock=0 Offset=16568, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 4888, counter : time in resource per second Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 4888 StartupTime: 130540706368372679, currentInstance : mb-msexchangedagmgmt-msexchangedagmgmt.exe(55FA86BC)
    RefCount=1 SpinLock=0 Offset=16240, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 4888, counter : time in resource per second Value=23 SpinLock=0 Lifetime=Type: 1 ProcessId: 4888 StartupTime: 130540706368372679, currentInstance : ad-msexchangedagmgmt-msexchangedagmgmt.exe(CC1DA236)
    RefCount=1 SpinLock=0 Offset=15912, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 4644, counter : time in resource per second Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 4644 StartupTime: 130540706359622658, currentInstance : rpca-w3wp-msexchangeautodiscoverapppool(6DABF262)
    RefCount=1 SpinLock=0 Offset=15584, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 4644, counter : time in resource per second Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 4644 StartupTime: 130540706359622658, currentInstance : mb-w3wp-msexchangeautodiscoverapppool(D1C6EF4D)
    RefCount=1 SpinLock=0 Offset=15256, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 4644, counter : time in resource per second Value=68 SpinLock=0 Lifetime=Type: 1 ProcessId: 4644 StartupTime: 130540706359622658, currentInstance : ad-w3wp-msexchangeautodiscoverapppool(FD072087)
    RefCount=1 SpinLock=0 Offset=14928, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 5272, counter : time in resource per second Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 5272 StartupTime: 130540706406810182, currentInstance : rpca-msexchangedelivery-msexchangedelivery.exe(9051FBB3)
    RefCount=1 SpinLock=0 Offset=14600, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 5272, counter : time in resource per second Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 5272 StartupTime: 130540706406810182, currentInstance : mb-msexchangedelivery-msexchangedelivery.exe(60C77F3C)
    RefCount=1 SpinLock=0 Offset=14272, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 5272, counter : time in resource per second Value=114 SpinLock=0 Lifetime=Type: 1 ProcessId: 5272 StartupTime: 130540706406810182, currentInstance : ad-msexchangedelivery-msexchangedelivery.exe(820B5E36)
    RefCount=1 SpinLock=0 Offset=13944, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 5012, counter : time in resource per second Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 5012 StartupTime: 130540706330872711, currentInstance : rpca-umworkerprocess-umworkerprocess.exe(970CCE33)
    RefCount=1 SpinLock=0 Offset=13616, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 5012, counter : time in resource per second Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 5012 StartupTime: 130540706330872711, currentInstance : mb-umworkerprocess-umworkerprocess.exe(8A7F8A3C)
    RefCount=1 SpinLock=0 Offset=13288, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 5012, counter : time in resource per second Value=34 SpinLock=0 Lifetime=Type: 1 ProcessId: 5012 StartupTime: 130540706330872711, currentInstance : ad-umworkerprocess-umworkerprocess.exe(95818B6)
    RefCount=1 SpinLock=0 Offset=12960, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 4812, counter : time in resource per second Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 4812 StartupTime: 130540706293060177, currentInstance : rpca-microsoft.exchange.um.callrouter-microsoft.exchange.um.callrouter.exe(E8475353)
    RefCount=1 SpinLock=0 Offset=12632, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 4812, counter : time in resource per second Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 4812 StartupTime: 130540706293060177, currentInstance : mb-microsoft.exchange.um.callrouter-microsoft.exchange.um.callrouter.exe(8F65881C)
    RefCount=1 SpinLock=0 Offset=12304, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 4812, counter : time in resource per second Value=116 SpinLock=0 Lifetime=Type: 1 ProcessId: 4812 StartupTime: 130540706293060177, currentInstance : ad-microsoft.exchange.um.callrouter-microsoft.exchange.um.callrouter.exe(78F52196)
    RefCount=1 SpinLock=0 Offset=11976, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 4452, counter : time in resource per second Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 4452 StartupTime: 130540706231497667, currentInstance : rpca-umservice-umservice.exe(E39A1133)
    RefCount=1 SpinLock=0 Offset=11648, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 4452, counter : time in resource per second Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 4452 StartupTime: 130540706231497667, currentInstance : mb-umservice-umservice.exe(FFBB273C) RefCount=1
    SpinLock=0 Offset=11320, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 4452, counter : time in resource per second Value=127 SpinLock=0 Lifetime=Type: 1 ProcessId: 4452 StartupTime: 130540706231497667, currentInstance : ad-umservice-umservice.exe(9A8AC6B6)
    RefCount=1 SpinLock=0 Offset=10992, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 4240, counter : time in resource per second Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 4240 StartupTime: 130540706209778932, currentInstance : rpca-msexchangetransportlogsearch-msexchangetransportlogsearch.exe(EF66F2D3)
    RefCount=1 SpinLock=0 Offset=10664, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 4240, counter : time in resource per second Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 4240 StartupTime: 130540706209778932, currentInstance : mb-msexchangetransportlogsearch-msexchangetransportlogsearch.exe(B020391C)
    RefCount=1 SpinLock=0 Offset=10336, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 4240, counter : time in resource per second Value=13 SpinLock=0 Lifetime=Type: 1 ProcessId: 4240 StartupTime: 130540706209778932, currentInstance : ad-msexchangetransportlogsearch-msexchangetransportlogsearch.exe(20578116)
    RefCount=1 SpinLock=0 Offset=10008, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 3928, counter : time in resource per second Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 3928 StartupTime: 130540706198372672, currentInstance : rpca-msexchangethrottling-msexchangethrottling.exe(8C1DA893)
    RefCount=1 SpinLock=0 Offset=9680, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 3928, counter : time in resource per second Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 3928 StartupTime: 130540706198372672, currentInstance : mb-msexchangethrottling-msexchangethrottling.exe(AB2BADDC)
    RefCount=1 SpinLock=0 Offset=9352, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 3928, counter : time in resource per second Value=10 SpinLock=0 Lifetime=Type: 1 ProcessId: 3928 StartupTime: 130540706198372672, currentInstance : ad-msexchangethrottling-msexchangethrottling.exe(8962F4D6)
    RefCount=1 SpinLock=0 Offset=9024, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 3128, counter : time in resource per second Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 3128 StartupTime: 130540705949466422, currentInstance : rpca-msexchangesubmission-msexchangesubmission.exe(60747EB3)
    RefCount=1 SpinLock=0 Offset=8696, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 3128, counter : time in resource per second Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 3128 StartupTime: 130540705949466422, currentInstance : mb-msexchangesubmission-msexchangesubmission.exe(67B4173C)
    RefCount=1 SpinLock=0 Offset=8368, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 3128, counter : time in resource per second Value=53 SpinLock=0 Lifetime=Type: 1 ProcessId: 3128 StartupTime: 130540705949466422, currentInstance : ad-msexchangesubmission-msexchangesubmission.exe(85200236)
    RefCount=1 SpinLock=0 Offset=8040, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 3092, counter : time in resource per second Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 3092 StartupTime: 130540705946653923, currentInstance : rpca-msexchangehmworker-msexchangehmworker.exe(39325ED3)
    RefCount=1 SpinLock=0 Offset=7712, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 3092, counter : time in resource per second Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 3092 StartupTime: 130540705946653923, currentInstance : mb-msexchangehmworker-msexchangehmworker.exe(6177C09C)
    RefCount=1 SpinLock=0 Offset=7384, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 3092, counter : time in resource per second Value=732 SpinLock=0 Lifetime=Type: 1 ProcessId: 3092 StartupTime: 130540705946653923, currentInstance : ad-msexchangehmworker-msexchangehmworker.exe(712B0516)
    RefCount=1 SpinLock=0 Offset=7056, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 2936, counter : time in resource per second Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 2936 StartupTime: 130540705918060169, currentInstance : rpca-microsoft.exchange.servicehost-microsoft.exchange.servicehost.exe(39C8D53)
    RefCount=1 SpinLock=0 Offset=6728, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 2936, counter : time in resource per second Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 2936 StartupTime: 130540705918060169, currentInstance : mb-microsoft.exchange.servicehost-microsoft.exchange.servicehost.exe(E7963A1C)
    RefCount=1 SpinLock=0 Offset=6400, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 2936, counter : time in resource per second Value=265 SpinLock=0 Lifetime=Type: 1 ProcessId: 2936 StartupTime: 130540705918060169, currentInstance : ad-microsoft.exchange.servicehost-microsoft.exchange.servicehost.exe(10E8B196)
    RefCount=1 SpinLock=0 Offset=6072, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 2720, counter : time in resource per second Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 2720 StartupTime: 130540705888841424, currentInstance : rpca-microsoft.exchange.rpcclientaccess.service-microsoft.exchange.rpcclientaccess.service.exe(E4305E13)
    RefCount=1 SpinLock=0 Offset=5744, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 2720, counter : time in resource per second Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 2720 StartupTime: 130540705888841424, currentInstance : mb-microsoft.exchange.rpcclientaccess.service-microsoft.exchange.rpcclientaccess.service.exe(BBA60BDC)
    RefCount=1 SpinLock=0 Offset=5416, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 2720, counter : time in resource per second Value=275 SpinLock=0 Lifetime=Type: 1 ProcessId: 2720 StartupTime: 130540705888841424, currentInstance : ad-microsoft.exchange.rpcclientaccess.service-microsoft.exchange.rpcclientaccess.service.exe(B6581E56)
    RefCount=1 SpinLock=0 Offset=5088, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 2400, counter : time in resource per second Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 2400 StartupTime: 130540705938997675, currentInstance : rpca-forefrontactivedirectoryconnector-defaultdomain(A627DA57)
    RefCount=1 SpinLock=0 Offset=4760, categoryName: MSExchange Activity Context Resources 
    A process is holding onto a transport performance counter. processId : 2400, counter : time in resource per second Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 2400 StartupTime: 130540705938997675, currentInstance : mb-forefrontactivedirectoryconnector-defaul...
    I've reset all the perfom counters, as that's fixed issues like this in the past. But it didn't work this time.
    Any thoughts?
    Eric               
    Eric Gunderson

    I found this via web search. While the subject of the error for this person was POP, I used what he did for IMAP4 and it fixed my issue too. Like him, I'd like to understand the WHY, but I'm just happy its working for me again.
    Eric
    The issue was that the “State” of the PopProxy component was set to Inactive:
    [PS] D:\>Get-ServerComponentstate -Identity SRVDENEX01
    Server Component State
    SRVDENEX01.company.com ServerWideOffline Active
    SRVDENEX01.company.com HubTransport Active
    SRVDENEX01.company.com FrontendTransport Active
    SRVDENEX01.company.com Monitoring Active
    SRVDENEX01.company.com RecoveryActionsEnabled Active
    SRVDENEX01.company.com AutoDiscoverProxy Active
    SRVDENEX01.company.com ActiveSyncProxy Active
    SRVDENEX01.company.com EcpProxy Active
    SRVDENEX01.company.com EwsProxy Active
    SRVDENEX01.company.com ImapProxy Active
    SRVDENEX01.company.com OabProxy Active
    SRVDENEX01.company.com OwaProxy Active
    SRVDENEX01.company.com PopProxy Inactive
    SRVDENEX01.company.com PushNotificationsProxy Active
    SRVDENEX01.company.com RpsProxy Active
    SRVDENEX01.company.com RwsProxy Active
    SRVDENEX01.company.com RpcProxy Active
    SRVDENEX01.company.com UMCallRouter Active
    SRVDENEX01.company.com XropProxy Active
    SRVDENEX01.company.com HttpProxyAvailabilityGroup Active
    SRVDENEX01.company.com ForwardSyncDaemon Active
    SRVDENEX01.company.com ProvisioningRps Active
    SRVDENEX01.company.com MapiProxy Active
    SRVDENEX01.company.com EdgeTransport Active
    SRVDENEX01.company.com HighAvailability Active
    SRVDENEX01.company.com SharedCache Active
    A quick call to Set-ServerComponentState to mark this component Active fixed the issue:
    Set-ServerComponentState -Identity SRVDENEX01 -Component PopProxy -Requester HealthAPI -State Active
    After doing this POP started responding as expected, using any valid hostname or IP address.
    Like the user who posted to TechNet, I would also like to know why the health check failed and marked the PopProxy as inactive.
    I will research this further and if I find anything I will update this post.
    Eric Gunderson

  • Mail, Exchange Server, attachment size

    Hi all - I encounter problems while sending mail messages with attachments larger than 10 MB from Mountain Lion Mail (Version 6.3) via Exchange Server (Version 8.1.240.0).
    Using OWA light this works fine...
    Receiving mails with larger attachments also works fine...
    Colleagues using their Windows PC also do not encounter any problems
    What is going wrong?

    Hi ,
    In addition to winnie suggestions , please have a look in to the following things.
    1.On the error message , Just check about the generating server .Is that the server which is generated that error message is residing on your end else it is the server on the recipient end.
    2.We can also check what is the maximum size of message which can be received by the server on the recipient end.
    http://www.samlogic.net/articles/smtp-commands-reference.htm
    telnet destination server ip 25
    ehlo localhost
    Then you will get some ouputs for the above command.On the output please check the below mentioned part.
    250-SIZE
    Along with the verb 250-SIZE you can also came to know the maximum size of message that can be received by the destination server.
    Thanks & Regards S.Nithyanandham

  • Exchange 2013 - 453 4.3.1 Insufficient system resources".

    Hi,
    I have 2 virtualized exchange 2013 servers. Other mail systems are reporting that emails are taking a long time to get processed by our Exchange server due to "453 4.3.1 Insufficient
    system resources”."
    Our database has plenty of space to grow so I cant see where the problem is...Thanks for your ideas

    Hi,
    From the error description, I would like to clarify the following thing:
    Please adjust the configuration file attached to the transport hub to ensure that it either doesn't monitor system resources, or that it has a higher tolerance for when the physical server resources drops below a specified limit.
    What's more, here is a helpful blog for your reference.
    4.3.1 Insufficient System Resources in Exchange Server 2007 (Note: Though it is Exchange 2007, it also applies to Exchange 2013 for this issue)
    http://blogs.msdn.com/b/echarran/archive/2007/04/30/4-3-1-insufficient-system-resources-in-exchange-server-2007.aspx
    Hope it helps.
    Best regards,
    Amy Wang
    TechNet Community Support

  • Unable to access public folders on Exchange 2007 when user mailbox is on Exchange 2013

    Hi
    I have coexistence with Exchange 2007 and Exchange 2013. I've moved a mailbox to Exchange 2013 and now cannot view the public folders on Exchange 2007. The error message I get is "could not connect to the public folder server. microsoft exchange is
    not available. either there are network problems or the exchange server is down for maintenance."
    Mailboxes on Exchange 2007 do not have any problems viewing public folders. I can't migrate users to Exchange 2013 until this issue is resolved.
    The IIS permissions to the Public virtual directory on Exchange 2007 is set to Intergrated Windows and Basic authentication.

    Hi northerly,
    I recommend you follow the steps below for troubleshooting:
    1. Please run the Get-OutlookAnywhere cmdlet to verify the Outlook Anywhere settings on Exchange Server 2013 Client Access servers.
    2. If "ExternalHostName" is set, and "ExternalClientAuthenticationMethod" is Negotiate, change "ExternalClientAuthenticationMethod" to something other than Negotiate.
    3. If "InternaClientlAuthenticationMethod" is set to Negotiate, and "InternalRequireSSL" is True, change "InternalClientAuthenticationMethod" to something other than Negotiate, or change "InternalRequireSSL" to False.
    What's more, here is a helpful KB for your reference.
    Users of Exchange Server 2013 or Exchange Online can't open public folders or shared mailboxes on an Exchange 2010 or Exchange 2007 server
    http://support.microsoft.com/kb/2834139/en-us
    Hope my clarification is helpful.
    If there are any problems, please feel free to let me know.
    Best regards,
    Amy
    Amy Wang
    TechNet Community Support

  • ACE 4710 and Exchange 2013

    Greetings everyone.  
    I am curious if anyone has any experiences with Exchange 2013 and ACE SLB functions.  I know they changed to RPC over HTTPS on exch side and few other items changed as well.   I do not forsee any issues just looking to see if anyone has any feedback from a production deployment.   
    Thanks
    Joel

    Joel, I checked internally and only located one case raised against ACE and Exchange 2013. The issue was resolved via defect CSCuc98599 "ACE randomly resets POST requests with SSL offloading". Use A5.2.2 or apply workaround (increase maxparselen to 65k). Matthew

  • Exchange 2013 - Client Access Servers - Disk Space C:\ Running Low Space

    Currently having an issue with both of our client access servers with exchange 2013.
    The issue is that the C:\ drive will run low on disk space on one of the cas server and the other one will be fine.  We have cleaned up all the logs etc to free space on the cas server that is running low on space but its not sufficient enough
    as it keeps on running low on space, then what we do the free up the space is to reboot the cas server that runs low on space, and it free the space up after it has been restarted, then the other cas server starts running low on space.
    has anyone seen this before?

    Hi,
    If it is possible, I suggest re-installing Exchange Server on another path instead of C:\.
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support

Maybe you are looking for

  • Can I use Acrobat 11to download pdf that only allows me to read, enter data, and print?

    I need to complete gov. forms available online as pdf.  I can review, enter data and print, but I cannot save to my computer or anywhere else.  I need to be able to save so I can return to the form and enter information as I access it.  Can this be d

  • AdapterModule Development using NWDI

    Hi all, could you please be so kind and tell me, how i can devlop an adaptermodule for PI 7.1 using NWDI (for central build + transport) I know how to develop an adapter module using netweaver developer studio, but the problem with this approach is,

  • C5180 Ink System Failure hp 0xc19a0024

    Hello Everybody, Recently I moved from one city to another. After one week of that I run my HP C5180 printer. Unfortunately I have until today an error: "Ink system has failed. Refer to printer documentation. Error: 0xc19a0024. Turn power off then on

  • Certificate of Completion

    Is there a way to add a Certificate of Completion at the end of a course - to be generated when the learner has satisfactorily completed the course? I am using Captivate 3 with Windows XP.

  • Itunes file naming format

    Hey all just wondering if anyone can answer a question for as I can't seem to find a definate answer. I used to store my music in the format of: Artist\Album\CD1\track name-artist.ext taking out a folder step as neccessary. Now I've decided to let it