Exchange 2013 - Event ID 4999 MS Exchange Common - Watson report about to be sent for process id: 5816

Hi,
We have a single Exchange 2013 server and are getting this error many times in a day.  I haven't been able to find a solution and was wondering if anyone came across this error or have any suggestions.
Edition             : Standard
AdminDisplayVersion : Version 15.0 (Build 913.22)
Watson report about to be sent for process id: 5816, with parameters: E12IIS, c-RTL-AMD64, 15.00.0913.022, M.Exchange.Imap4, M.Exchange.Net, M.E.N.NetworkConnection.BeginNegotiateTlsAsClient, System.InvalidOperationException, 99a4, 15.00.0913.007.
ErrorReportingEnabled: True 
Thanks
Amit

We have exchange 2013 cu6 mailbox server and we keep getting the below event error message
Log Name:      Application
Source:        MSExchange Common
Date:          10/2/2014 1:06:25 PM
Event ID:      4999
Task Category: General
Level:         Error
Keywords:      Classic
User:          N/A
Computer:     
Description:
Watson report about to be sent for process id: 30632, with parameters: E12, c-RTL-AMD64, 15.00.0995.029, M.E.RpcClientAccess.Service, M.E.Data.ApplicationLogic, M.E.D.A.U.HttpPhotoRequestBuilder.Build, System.NotSupportedException, 4e29, 15.00.0995.027.
ErrorReportingEnabled: True
Event Xml:
< Event xmlns="">
  <System>
    <Provider Name="MSExchange Common" />
    <EventID Qualifiers="16388">4999</EventID>
    <Level>2</Level>
    <Task>1</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-10-02T20:06:25.000000000Z" />
    <EventRecordID>7826297</EventRecordID>
    <Channel>Application</Channel>
    <Computer></Computer>
    <Security />
  </System>
  <EventData>
    <Data>30632</Data>
    <Data>E12</Data>
    <Data>c-RTL-AMD64</Data>
    <Data>15.00.0995.029</Data>
    <Data>M.E.RpcClientAccess.Service</Data>
    <Data>M.E.Data.ApplicationLogic</Data>
    <Data>M.E.D.A.U.HttpPhotoRequestBuilder.Build</Data>
    <Data>System.NotSupportedException</Data>
    <Data>4e29</Data>
    <Data>15.00.0995.027</Data>
    <Data>True</Data>
    <Data>False</Data>
    <Data>Microsoft.Exchange.RpcClientAccess.Service</Data>
    <Data>
    </Data>
  </EventData>
< /Event>
Services seem to be fine (Via test-servicehealth), but i do have a group of users that complain that their outlook 2013 email clients will go non-responsive a few times a days. Wondering if this is related. Also this error is appearing every few minutes.
Anyone else experiencing this?

Similar Messages

  • Event 4999 - Watson report about to be sent for process id: 27244 on Mailbox Server every five minutes

    On one of my DAG enabled Exchange 2013 mailbox servers, I get this error in event viewer every five minutes:
    Log Name:      Application
    Source:        MSExchange Common
    Date:          6/25/2014 10:49:46 AM
    Event ID:      4999
    Task Category: General
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:    mailboxserver  
    Description:
    Watson report about to be sent for process id: 27244, with parameters: E12IIS, c-RTL-AMD64, 15.00.0913.022, M.E.RpcClientAccess.Service, unknown, M.E.R.S.U.DatabaseInfo..ctor, System.NullReferenceException, aba8, unknown.
    ErrorReportingEnabled: True 
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MSExchange Common" />
        <EventID Qualifiers="16388">4999</EventID>
        <Level>2</Level>
        <Task>1</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-06-25T17:49:46.000000000Z" />
        <EventRecordID>687360</EventRecordID>
        <Channel>Application</Channel>
        <Computer>mailboxserver</Computer>
        <Security />
      </System>
      <EventData>
        <Data>27244</Data>
        <Data>E12IIS</Data>
        <Data>c-RTL-AMD64</Data>
        <Data>15.00.0913.022</Data>
        <Data>M.E.RpcClientAccess.Service</Data>
        <Data>unknown</Data>
        <Data>M.E.R.S.U.DatabaseInfo..ctor</Data>
        <Data>System.NullReferenceException</Data>
        <Data>aba8</Data>
        <Data>unknown</Data>
        <Data>True</Data>
        <Data>False</Data>
        <Data>Microsoft.Exchange.RpcClientAccess.Service</Data>
        <Data>
        </Data>
      </EventData>
    </Event>
    Everything is working ok, but I'm concerning that I"m seeing this.  
    ST

    Amit,
    I don't see the same type of 4999 error every five minutes anymore.  It only get the 4999 error about 3 times a day.  I get one with the same ID and other completely different process ID.  The error is below:
    Log Name:      Application
    Source:        MSExchange Common
    Date:          7/2/2014 6:01:36 AM
    Event ID:      4999
    Task Category: General
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:     computer
    Description:
    Watson report about to be sent for process id: 13152, with parameters: E12, c-RTL-AMD64, 15.00.0913.022, w3wp#MSExchangeOWAAppPool, M.E.Data.ApplicationLogic, M.E.D.S.GccUtils.GetClientIPEndpointsFromHttpRequest, System.NullReferenceException, 868, 15.00.0913.017.
    ErrorReportingEnabled: True 
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MSExchange Common" />
        <EventID Qualifiers="16388">4999</EventID>
        <Level>2</Level>
        <Task>1</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-07-02T13:01:36.000000000Z" />
        <EventRecordID>825358</EventRecordID>
        <Channel>Application</Channel>
        <Computer>computer</Computer>
        <Security />
      </System>
      <EventData>
        <Data>13152</Data>
        <Data>E12</Data>
        <Data>c-RTL-AMD64</Data>
        <Data>15.00.0913.022</Data>
        <Data>w3wp#MSExchangeOWAAppPool</Data>
        <Data>M.E.Data.ApplicationLogic</Data>
        <Data>M.E.D.S.GccUtils.GetClientIPEndpointsFromHttpRequest</Data>
        <Data>System.NullReferenceException</Data>
        <Data>868</Data>
        <Data>15.00.0913.017</Data>
        <Data>True</Data>
        <Data>False</Data>
        <Data>w3wp#MSExchangeOWAAppPool</Data>
        <Data>
        </Data>
      </EventData>
    </Event>
    Going to keep an eye on it, but its not causing any issues. 
    ST

  • Exchange 2013 Event ID 4999

    Hello,
    I have two exchange servers 2013 both running MB and CAS roles. I also have a DAG on my servers. On one of my servers almost every 7-8 minutes I receive the following error event. Could you please assist me with this?
    Event 4999, MSExchange Common
    Watson report about to be sent for process id: 17084, with parameters: E12IIS, c-RTL-AMD64, 15.00.0995.029, MSExchangeMigrationWorkflow, unknown, M.E.M.L.L.<>c__DisplayClass11.<GetLocalServerData>b__10, System.NullReferenceException, 49af, unknown.
    ErrorReportingEnabled: False 
    Thanks a lot.
    Pooriya Aghaalitari

    Hi,
    DAG Network Automatic configuration may cause the Misconfigured Network sometimes. I recommend you to configure DAG Network manually to solve this problem.
    Please refer to the “DAG Networks” section in the following link.
    http://technet.microsoft.com/en-us/library/dd298065(v=exchg.150).aspx#Dat
    Similar thread for reference.
    https://social.technet.microsoft.com/Forums/exchange/en-US/e0496d08-c82b-4e8d-ae70-f64c69dc3913/add-dag-member-event-4999-msexchange-common?forum=exchangesvravailabilityandisasterrecovery
    Hope this will be helpful for you.
    Best Regards.

  • Exchange 2013 CU6 Event ID 4999

    After installing CU6 on the exchange 2013 mailbox server we keep getting the below event error message
    Log Name:      Application
    Source:        MSExchange Common
    Date:          10/2/2014 1:06:25 PM
    Event ID:      4999
    Task Category: General
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:     
    Description:
    Watson report about to be sent for process id: 30632, with parameters: E12, c-RTL-AMD64, 15.00.0995.029, M.E.RpcClientAccess.Service, M.E.Data.ApplicationLogic, M.E.D.A.U.HttpPhotoRequestBuilder.Build, System.NotSupportedException, 4e29, 15.00.0995.027.
    ErrorReportingEnabled: True
    Event Xml:
    <Event xmlns="">
      <System>
        <Provider Name="MSExchange Common" />
        <EventID Qualifiers="16388">4999</EventID>
        <Level>2</Level>
        <Task>1</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-10-02T20:06:25.000000000Z" />
        <EventRecordID>7826297</EventRecordID>
        <Channel>Application</Channel>
        <Computer></Computer>
        <Security />
      </System>
      <EventData>
        <Data>30632</Data>
        <Data>E12</Data>
        <Data>c-RTL-AMD64</Data>
        <Data>15.00.0995.029</Data>
        <Data>M.E.RpcClientAccess.Service</Data>
        <Data>M.E.Data.ApplicationLogic</Data>
        <Data>M.E.D.A.U.HttpPhotoRequestBuilder.Build</Data>
        <Data>System.NotSupportedException</Data>
        <Data>4e29</Data>
        <Data>15.00.0995.027</Data>
        <Data>True</Data>
        <Data>False</Data>
        <Data>Microsoft.Exchange.RpcClientAccess.Service</Data>
        <Data>
        </Data>
      </EventData>
    </Event>
    Services seem to be fine but i do have a group of users that complain that their outlook 2013 email clients will go non-responsive a few times a days. Wondering if this is related. Also this error is appearing every few minutes. Anyone else experiencing
    this?

    Hi,
    I would like to add some information to this, in case others are facing the same circumstance. I too received the same errors on my Exchange 2013 CU5 and CU6 servers mentioned above. I ended up calling Microsoft Premiere support because there was a very
    large impact in our environment as we had Outlook 2010 clients that were having Exchange 2013 connectivity issues. Long story short, since Outlook 2010 was trying to use RPC to connect to the Exchange 2013 servers and in the Event Viewer we were seeing the
    4999 Event ID multiple times per minute, RPC was crashing on the Exchange servers resulting in client connectivity issues.
    Microsoft ran a ProcDump on the PID for RPC crash and basically came back with nothing only saying that it was a result of someone uploading a picture via Lync that was either corrupt or too large cause the photo store to crash the RPC Service. They also
    were firm in saying that this should have no impact. I was not convinced because this happened after installing CU5 and the client connectivity issues also appeared in conjunction with these 4999 RPC errors. In my mind that is a bug and I asked that something
    be published to address this as it seems silly that one user uploading a Lync profile picture could cripple our environment.
    You would need to navigate to the following location to see this Photo Store. (D:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\photos) Change the path to point to your local Exchange install instance. Most of the files in my location are 0K but
    there are a few that are 4K so it seems they are not large enough to affect anything. We have 4 CAS+MBX servers so I looked at all 4 servers.
    What I ended up doing to resolve the 4999 event ID which actually ended up fixing my client connectivity issues also was to edit the following file. "D:\Program Files\Microsoft\Exchange Server\V15\Bin\Microsoft.Exchange.RpcClientAccess.Service.exe.config"
    Back the above file up and when you open it scroll about 3/4 to 7/8 of the way down and find the following lines:
        <!-- Enables retrieval of the HD photo in DOMT. -->
        <add key="HDPhotoEnabled" value="true" />
    Set the line to "false" like so:
        <!-- Enables retrieval of the HD photo in DOMT. -->
        <add key="HDPhotoEnabled" value="false" />
    Then restart the Microsoft Exchange RPC Client Access service and refresh the Event Viewer and the 4999 errors should stop and client connectivity should be restored.
    I noticed this error with CU5 and then subsequently after I installed CU6, so I had to perform this change after I installed CU6 and probably do the same once CU7 comes out. I do not know the adverse effects of making this change as Microsoft really could
    not explain more than what I wrote above, but I had to get Outlook connectivity restored and this was my only option. It appears that Lync 2010 photos and Outlook 2010 photos stayed intact so no users were complaining that their self-uploaded profile pictures
    were gone. We never had this problem with Outlook 2013 SP1 as we have MAPI enabled and the crashing RPC service would not have effected those clients. OWA was also working just fine.
    Hopefully Microsoft can offer me more of an explanation as I ended up fixing my own issue but I raised concern with how this happened. I hope this helps someone else as it helped me.
    Thanks.
    Alan

  • Event ID: 4999 - MSExchange Common - Exchange 2010 SP3

    Hi all,
    I have Exchange 2010 SP3 RU4 and since yesterday without reason (I didn´t patch anything, configure etc.) following error randomly appears in app eventlog:
    Watson report about to be sent for process id: 6000, with parameters: E12, c-RTL-AMD64, 14.03.0151.000, AirSync, MSExchange ActiveSync, Microsoft.Exchange.Data.Storage.GlobalObjectId.IsForeignUid, UnexpectedCondition:NullReferenceException, 54b1,
    14.03.0151.000.
    ErrorReportingEnabled: True
    I´ve tried to find some info but no luck.
    Does anybody know how to fix this?
    Thanks in advance, O.

    Resolved..
    A few days ago I hid some testing resource mailboxes (rooms) in GAL, which were used in Cisco TMSXE (Videoconferencing SW). Then, when I restarted the IIS, these errors appeared, because of Cisco TMSXE couldn´t find the room mailboxes. So I unhide
    them and errors are gone..

  • Exchange 2010 SP3 RU 5 - Event id 4999

    We have Exchange 2010 SP3 RU5 with four CAS/HT and five mailbox servers. We get tons of event 4999 on the four CAS/HT during the last weeks:
    Watson report about to be sent for process id: 6456, with parameters: E12, c-RTL-AMD64, 14.03.0178.000, AirSync, MSExchange ActiveSync, Microsoft.Exchange.Data.Storage.GlobalObjectId.IsForeignUid, UnexpectedCondition:NullReferenceException, 54b1, 14.03.0178.000.
    ErrorReportingEnabled: False
    We have 10000+ mailboxes and no problem with activesync has been reported. I increased diagnostic logging of activesync to "expert" without getting more details about this. I have also restarted all four CAS/HT servers but event 4999 is
    still there.
    Any ideas?

    Thanks for your reply Willard Martin
    This event is also from MSExchange Common and the process id 6456 referred to in the event text is w3wp.exe.
    I also checked both your links but they are not similar to my problem. The first of your links is about  "System.IndexOutOfRangeException" and doesn't seem to have anything to do with ActiveSync. The second is about ActiveSync but with another kind
    of error: "UnexpectedCondition:ArgumentNullException". 
    My error text is "UnexpectedCondition:NullReferenceException"

  • Exchange 2010 SP3 upgrade - Event ID 4999 - Address Book Crash

    0
    I just upgraded an Exchange 2010 SP1 CAS server to SP3 - since then anytime an outlook client connects to the CAS server, the Address Book service crash's and event 4999 is logged in App log.  I can reproduce the issue by attempting to create a new
    outlook profile and checking the name against the CAS server.  This crash's the service and the client recieves an error message.  The contents of event ID 4999 is below.  I've tried re-installing the CAS role, re-applying the schema extension
    for SP3.  I've installed all windows updates, enabled logging but I'm not getting anywhere.  If anyone can help with this issue, I would greatly appreicate it.
    Watson report about to be sent for process id: 10168, with parameters: E12, c-RTL-AMD64, 14.03.0123.004, M.E.AddressBook.Service, M.Exchange.Rpc, M.E.R.R.RfriRpcOperationBase.Complete, System.ArgumentException, a3e, 14.03.0123.002.
    ErrorReportingEnabled: True
    That error is followed by a message that the Address Book service has sucessfully started

    Hello,
    For exchange 2010 sp3, there is no article to explain the issue.
    I suggest you run EXBPA aganist your exchange server health check.
    Cara Chen
    TechNet Community Support

  • MSExchange Common event-id 4999

    I'm having errors (2 of them every 5 minutes) on a HT/CAS/Mailbox server:
    MSExchange Common 4999
    Watson report about to be sent for process id: 7960, with parameters: E12, c-RTL-AMD64, 14.03.0224.001, AirSync, MSExchange ActiveSync, Microsoft.Exchange.Data.Storage.GlobalObjectId.IsForeignUid, UnexpectedCondition:NullReferenceException, 54b1, 14.03.0224.001.
    ErrorReportingEnabled: False
    Any ideas?
    PS
    It's not kb2665115, no ( ) : in database names.
    Dario Palermo

    Hi Dario, 
    Thank you for your question.
    There are some reasons which caused event id 4999, for example hid resource mailboxes, the corrupt calendar item.
    We could refer to the following steps to troubleshoot:
    If there are some resource mailboxes which are hid, we could unhidden unhide them, then we could restart IIS and check if there are event id 4999 
    We could refer to the following link to check if there are any the corrupt calendar item via
    Calcheck, we could remove or repair the corrupt calendar item: http://blogs.msdn.com/b/webdav_101/archive/2012/02/28/how-to-check-for-calendar-corruption.aspx
    If the event id persist, I suggest we could update Exchange 2010 to CU8 v2 by the following link, because Exchange 2010 CU8 v1 has been recalled:
     http://www.microsoft.com/en-us/download/details.aspx?id=45225 
    If there are any questions regarding this issue, please be free to let me know. 
    Best Regard,
    Jim

  • Installing Exchange 2013 SP1 - Errors MSExchange ADAccess & MSExchange Common

    The topology first:
    AD-server + Exchange-server
    What I am trying to do is just install a full version of Exchange 2013 sp1.
    But the problem is that install wizard freezes on the "initializing setup" page. Also eventviewer gives 2 different error messages, MSExchange ADAccess & MSExchange Common.
    MSExchange ADAccess:
    The description for Event ID 4027 from source MSExchange ADAccess cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local
    computer.
    If the event originated on another computer, the display information had to be saved with the event.
    The following information was included with the event:
    ExSetup.exe
    2964
    Get Servers for mydomain.com
    TopologyClientTcpEndpoint (localhost)
    3
    System.ServiceModel.EndpointNotFoundException: Could not connect to net.tcp://localhost:890/Microsoft.Exchange.Directory.TopologyService. The connection attempt lasted for a time span of 00:00:01.9984949. TCP error code 10061: No connection could be made because
    the target machine actively refused it 127.0.0.1:890.  ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:890
       at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
       at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
       at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
       --- End of inner exception stack trace ---
    Server stack trace:
       at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
       at System.ServiceModel.Channels.BufferedConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
       at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)
       at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout)
       at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
       at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)
       at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
    Exception rethrown at [0]:
       at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
       at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
       at System.ServiceModel.ICommunicationObject.Open()
       at Microsoft.Exchange.Net.ServiceProxyPool`1.GetClient(Boolean useCache)
       at Microsoft.Exchange.Net.ServiceProxyPool`1.TryCallServiceWithRetry(Action`1 action, String debugMessage, WCFConnectionStateTuple proxyToUse, Int32 numberOfRetries, Boolean doNotReturnProxyOnSuccess, Exception& exception)
    the message resource is present but the message is not found in the string/message table
    MSExchange Common:
    The description for Event ID 106 from source MSExchange Common cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
    If the event originated on another computer, the display information had to be saved with the event.
    The following information was included with the event:
    2
    Time in Resource per second
    MSExchange Activity Context Resources
    The exception thrown is : System.InvalidOperationException: The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly.
       at System.Diagnostics.PerformanceCounter.InitializeImpl()
       at System.Diagnostics.PerformanceCounter.get_RawValue()
       at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.get_RawValue()
    Last worker process info : Last worker process info not available!
    Processes running while Performance counter failed to update:
    1044 VSSVC
    1064 spoolsv
    4032 notepad
    1416 svchost
    700 dwm
    3100 SMSvcHost
    3616 msdtc
    2564 csrss
    336 csrss
    424 winlogon
    244 smss
    688 LogonUI
    2556 Taskmgr
    596 svchost
    1124 inetinfo
    1920 svchost
    1652 SMSvcHost
    1400 svchost
    2916 taskhostex
    492 lsass
    2688 dwm
    396 wininit
    484 services
    1104 svchost
    388 csrss
    384 svchost
    1896 svchost
    3052 svchost
    744 svchost
    1180 mmc
    3404 conhost
    1800 explorer
    3668 Setup
    552 svchost
    712 svchost
    2864 svchost
    2964 ExSetup
    2948 rdpclip
    2592 winlogon
    900 svchost
    808 svchost
    4 System
    1164 mqsvc
    0 Idle
    Performance Counters Layout information: FileMappingNotFoundException for category MSExchange Activity Context Resources : Microsoft.Exchange.Diagnostics.FileMappingNotFoundException: Cound not open File mapping for name Global\netfxcustomperfcounters.1.0msexchange
    activity context resources. Error Details: 2
       at Microsoft.Exchange.Diagnostics.FileMapping..ctor(String name, Boolean writable)
       at Microsoft.Exchange.Diagnostics.PerformanceCounterMemoryMappedFile.Initialize(String fileMappingName, Boolean writable)
       at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.GetAllInstancesLayout(String categoryName)
    the message resource is present but the message is not found in the string/message table

    I solved this problem or at least managed to get a workaround for it.
    I tried to install Exchange using rdp connection and the installation media was mapped on my local computer. After I copied it to server itself, everything started to work and now I am able to send emails.

  • Exchange 2013 event ID 36888 SChannel error 12 and 1203

    I am running Windows Server 2012 STD with Exchange 2013 installed on the same server. I know that Microsoft doesnt recommend to do this, but I had no choice. Errors are follow:
    A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 10. The Windows SChannel error state is 12.
    A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 10. The Windows SChannel error state is 1203.
    - System
    - Provider
    [ Name] Schannel
    [ Guid] {1F678132-5938-4686-9FDC-C8FF68F15C85}
    EventID 36888
    Version 0
    Level 2
    Task 0
    Opcode 0
    Keywords 0x8000000000000000
    - TimeCreated
    [ SystemTime] 2014-11-25T23:30:34.120233400Z
    EventRecordID 121125
    Correlation
    - Execution
    [ ProcessID] 1064
    [ ThreadID] 20184
    Channel System
    Computer server
    - Security
    [ UserID] S-1-5-18
    - EventData
    AlertDesc 10
    ErrorState 12
    System
    - Provider
    [ Name] Schannel
    [ Guid] {1F678132-5938-4686-9FDC-C8FF68F15C85}
    EventID 36888
    Version 0
    Level 2
    Task 0
    Opcode 0
    Keywords 0x8000000000000000
    - TimeCreated
    [ SystemTime] 2014-11-26T05:45:22.650086300Z
    EventRecordID 121230
    Correlation
    - Execution
    [ ProcessID] 1064
    [ ThreadID] 45336
    Channel System
    Computer SERVER
    - Security
    [ UserID] S-1-5-18
    - EventData
    AlertDesc 10
    ErrorState 1203
    Process ID 1064 is Isass.exe
    I found somewhere that error 1203 could be ignored, but nothing about error 12. 
    Server is running with selfsigned SAN certificate, hosted 2 exchange domains (10 mailboxes, 5 local, 5 linked for remote domain connected via external 2 way non transitive domain trust).
    Thank you very much for any advise.
    Regards,
    Jan
    Šerý

    Hi Jan,
    Based on my research for the Event 36888, the issue may be caused by not standard or corrupted behavior of web browsers or users, such as user use HTTP protocol to access Exchange service which is a SSL site on port 443.
    Please check whether there is a HTTP redirect configured in your IIS Manager of Exchange server. Also reset web browsers to have a try. Here are some similar thread for this issue:
    https://social.technet.microsoft.com/Forums/forefront/en-US/92c63737-c2a3-41f7-8878-3b0cf5ee95ff/new-install-event-log-schannel-event-id-36888?forum=Forefrontedgegeneral
    http://ficility.net/2013/10/21/exchange-2013-exchange-2010-windows-server-2012-schannel-event-id36888-1203-tlsssl-error-the-root-cause/
    Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make
    sure that you completely understand the risk before retrieving any suggestions from the above link.
    Regards,
    Winnie Liang
    TechNet Community Support

  • Exchange 2010 "This message could not be sent. Try sending the message again later, or contact your network administrator. Error is [0x80004005-00000000-00000000].

    Exchange 2010 "This message could not be sent. Try sending the message again later, or contact your network administrator.  Error is [0x80004005-00000000-00000000].
    In a mixed client environment, mostly Outlook 2010 & 2013 clients. Only Outlook 2013 clients (about only 4 mailboxes) are receiving this error immediately after sending an email. My temp band-aid at the
    moment is to: from the client, go into the "address book" & select a different address book like "Contacts" & then select the address again & select the Global Address List, which is the default. (it will have the users email
    + at the beginning of the field, it reads, Global Address List - (email of the user), then I close Outlook & open it back up, & the problem is solved. But on some mailboxes, not all, the issue comes back. From my research, I know that our individual
    mailboxes do not send out over 500 emails in one day. Most users will send out maybe 20 or 30 in one day, so I don't think it's that. 
    But I'm not sure if this is related, but I have noticed that the log files for the Exchange 2010 seems to only hold logs with date stamps of only a couple of days. It used to hold log files indefinitely until they were archived, deleted, etc. So, this is
    a new, unusual issue I have seen as well. 
    We have 2 .edb's, one active: 78 GB's and one disabled at 7 GB's. Exchange 2010 is running on Windows Server 2008 r2, Enterprise Ed. We have had Exchange 2010 running now for about almost 2 years now and this is the first time this particular issue has come
    up.
    Thanks.

    Hi,
    You can refer to the following steps to rebuild an Offline Address Book.
    1. Open EMS. Update OAB using the Update-OfflineAddressbook "offline address book" cmdlet. Restart Background Intelligent Transfer Service on the Mailbox server.
    2. Initiate OAB replication from mail box server to CAS server. Execute for each CAS server using the Update-FileDistributionService "CASServerName" cmdlet.
    3. Start Outlook and download OAB.
    What's more, here is an article for your reference.
    How to Quickly Rebuild an Exchange 2010 Offline Address Book
    http://social.technet.microsoft.com/wiki/contents/articles/7725.how-to-quickly-rebuild-an-exchange-2010-offline-address-book.aspx
    Hope this can be helpful to you.
    Best regards,
    Amy Wang
    TechNet Community Support

  • Exchange 2003 SMTP resolves to incorrect MX record for Outbound emails

    Starting October 2007, we have encountered numerous incidents where users complaint that they can not send emails to randomly with Relayed Denied error. 
    First we thought the problem is with the receipient servers, but after reviewing the SMTP log intensively, I have noticed that the SMTP service on Exchange Server 2003 SP2 tries to send out emails to wrong IP Addresses (instead of sending out to listed IP of MX record, it tries to send to primary domain IP address).
    To test further, we have changed the DNS server of the Exchange Server to public DNS service provided by the ISPs and still received same result.
    If the user tries to send the email again (from the bounced back message), it some times goes through.
    Has anyone know what the problem is?
    Have checked the server configuration, DNS configuration, ran all updates, and yet still same result.  Is one of the Microsoft Updates causing this issue?

    Here is the official explanation i got from MS, sounds like it is doing what they expect it to do.
    Problem Description
    When Exchange 2003 sends e-mail to the Internet using DNS to resolve external domain names a DNS query is done for the remote domain's MX records. In the event that the initial MX query returns a "server failure", Exchange 2003 will fall back to a DNS A record query. If this query is, in turn, successful and there is an A record for the domain in question that happens to be listening on port 25, Exchange will make a connection to that server. However, if this server does not relay, or accept e-mail for the intended domain a NDR will be generated with a 5.7.1, or
    5.5.0 error message.
    There are several domains that have A records that point to IP addresses that accept connections on port 25, but do not relay for the same name space:
    Eg: Mindspring.com; Earthlink.net
    Resolution
    Resolve the DNS resolution problems that are causing occasional MX record failures.
    Examples:
    1. The Exchange server has multiple default gateways set on a multi-homed server.
    This is not a recommended configuration and can cause a number of unexpected network problems. If the internal DNS server the internal NIC points to cannot resolve external DNS queries, this problem can occur.
    Action: remove the default gateway from one of the NICs.
    This doesn’t applies to us, as we don’t use Internal DNS
    2. If the Exchange server points to multiple DNS servers on TCP/IP properties, or on the SMTP Virtual Server properties, verify that each of these DNS servers will return MX records properly. If one of the DNS servers does not return DNS records consistently, rectify this problem.
    Action: remove this DNS server from the external DNS tab.
    Workaround:
    Bypass DNS by creating a SMTP connector with address space of <domain.com> and forward to smart host as the IP address the MX/A points to.
    Exchange Query Explained
    1. If Exchange finds the MX record(s) for a remote domain (through DNS query) it will not fall back to an A record query in the event the MX record (more precisely, the A record the MX record points to) is temporarily not responding on port 25. Instead, Exchange will try another MX record if one exists. If no other MX records exist and none are responding on port 25, the queue will go into a retry state for this remote domain. When that retry state has expired, Exchange will again attempt to resolve MX records for this domain, and so on.
    2. Exchange will fall back to an A record query for the remote domain in the event that no MX record can be found. This is not to say that the MX record does not exist - only that when Exchange issued a DNS query for the remote domain the DNS response was "server failure", which basically means no MX was found. So, the MX record may indeed exist, but Exchange simply could not find it through DNS resolution.
    3. Exchange then queries the A record and this happens to return a result. If the A record is listening on port 25, but does not accept mail for <domain.com> then we will get the NDR with 550 5.7.1 unable to relay (or some variation of this NDR error code) when Exchange connects and attempts to send the e-mail.
    So, the intermittent nature of the problem is caused by a failure to find the MX record and a success in finding A record. This can happen for a variety of reasons, but it boils down to flakey DNS resolution.
    For example:
    a. A bad DNS server listed as a forwader on the DNS server.
    b. A bad DNS server on the TCP/IP properties.
    c. A bad DNS server on the SMTP VS (external DNS servers)
    d. Multiple default gateways on Exchange (ie. multiple NICs on different networks, each NIC having a default GW)
    A netmon on Exchange will show the failed MX lookup and successful A record lookup; however, it may not be conclusive unless the "bad" DNS server is listed in the netmon trace. For example, if Exchange points to internal DNS server(s) for name resolution and these DNS servers service these DNS queries by Exchange, you may need a netmon on the DNS server(s) as well to determine which DNS server/Forwarder/etc is at fault.
    Regards,
    Shahul Hameed Dasthagir
    Support Engineer | Enterprise Communications Support 

  • Looking for help with respect to configuring MS Exchange server to handle attachments over 10 MB for forwarding to Salesforce (Email-to-case).

    Looking for help with respect to configuring MS Exchange server to handle attachments over 10 MB for forwarding to Salesforce (Email-to-case).
    Problem - SFDC does not create cases from emails that have more than 10 MB of attachments. Our clients will not go-live if their clients cannot send in emails with attachments over 10 MBs
    Potential resolution - Configure MS exchange to strip off the attachments(if over 10 MB) and store it in a public folder, forward the email to Salesforce (so the case gets created or the email
    is associated to an existing case), the client should have some way to know if the attachments were stripped off and should be able to dlownload the attachments and continue with case resolution.
    Any help is appreicated!
    Thanks

    Hi,
    From your description, you want to achieve the following goal:
    Configure Exchange to filter the attachments if the size is over 10 MB and store it in a public folder, and then forward the email to Salesforce.
    Based on my knowledge, I'm afraid that it can't be achieved. Exchange can filter messages with attachments, but it couldn't store these attachments on public folder automatically. Also, I don't see any transport rule can do it.
    Hope my clarification is helpful.
    Best regards,
    Amy Wang
    TechNet Community Support

  • Can i exchange my appe ipod touch cable and headphone for new one

    can i exchange my appe ipod touch cable and headphone for new one

    Only if they are in warranty and have factory defects.

  • Hello, My iCal don't synchronize older events than two or three month ago. How can I do to synchronize all my schedule? In iTunes it's all right in Calendars. I don't put a cross in "synchronize event older than ....... days". Thanks for answer.

    Hello, My iCal don't synchronize older events than two or three month ago. How can I do to synchronize all my schedule? In iTunes it's all right in Calendars. I don't put a cross in "synchronize event older than ....... days". Thanks for answer.

    Just saw your post. Better late than never. You may want to
    consider GameBrix.com, where you can create Flash based, casual
    games using your web browser. No downloads are required. You can
    create a game from scratch using a library of images, sounds and
    game mechanics. You can also upload your own. The online script
    editor will allow you to view and edit the ActionScripts associated
    with each game mechanic. In short, a great way to ramp up on game
    design and build your own game without investing a lot of $
    upfront.
    BTW I am associated with GameBrix so any feedback is
    appreciated.

Maybe you are looking for