Event Id 9040
A report will be sent for the following exception: Microsoft.Exchange.Assistants.AIGrayException ---> Microsoft.Exchange.Common.GrayException ---> Microsoft.Mapi.MapiExceptionPartialCompletion: MapiExceptionPartialCompletion: Unable to save watermarks. (hr=0x40680, ec=0) Diagnostic context: Lid: 1494 ---- Remote Context An exception has been handled on behalf of an assistant. All have users on them that work, this is a test lab, the 2010 and 2007 servers are working fine, but the CCR node is not. Mine went away with a reboot.. 0 LVL 1 Overall: Level 1 Exchange 1 Message Author Closing Comment by:BBQSTEAK ID: 372305392011-11-28 Fixed it myself 0 Message Expert Comment by:rgibson1969 Check This Out
The winsock subsystem returned the error:[0x2746]. Go to Solution 5 3 3 Participants BBQSTEAK(5 comments) LVL 1 Exchange1 rgibson1969(3 comments) Amit LVL 41 Exchange38 9 Comments LVL 41 Overall: Level 41 Exchange 38 Message Active today Yes: My problem was resolved. The target > Domain > Controller or the network or a client might be down. http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Exchange&ProdVer=8.0&EvtID=9040&EvtSrc=MSExchangeSA&LCID=1033
Join our community for more solutions or to ask questions. WindowSecurity.com Network Security & Information Security resource for IT administrators. Exchange server software Mobility & Wireless Outlook Addons OWA Addons POP3 Downloaders PST Management Reporting Security & Encryption SMS & Paging Tips & Tricks Webinars White Papers Featured Products Featured Book The winsock subsystem returned the error:[0x%1].
Log Name: Application Source: MSExchange Assistants Date: 3/15/2011 Event ID: 9040 Task Category: Assistants Level: Information If you are experiencing a similar issue, please ask a related question Suggested Solutions Title # Comments Views Activity OS X Mail will not connect to Microsoft Hosted Exchange 7 35 However, if this event is logged repeatedly, then further investigation would be needed". My problem is, on the MS KB it says the problem is on a certain user.
Privacy statement © 2017 Microsoft. his comment is here Particularly the GC servers? That server is working fine, only the CCR nodes arent. Copyright © 2014 TechGenix Ltd.
Private comment: Subscribers only. The winsock subsystem returned the error:[
This problem may be a transient one. Either way test lab simple fix, production would had been a pain. Event Xml:
TheEventId.Net for Splunk Add-onassumes thatSplunkis collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
As per Microsoft: "This event indicates that the NSPI interface of the Exchange server encountered a problem when communicating with a global catalog server. read more... The winsock subsystem returned the error:. Article by: Michael ADCs have gained traction within the last decade, largely due to increased demand for legacy load balancing appliances to handle more advanced application delivery requirements and improve application
Comments: Peter Van Gils This event is logged when you're running Exchange Server 2007 and HKLM\System\CurrentControlSet\Services\TCPIP\Parameters\MaxUserPort is set lower than 60000. Return to Jump to: Select a forum ------------------ Adiscon Support MonitorWare Product Line MonitorWare Agent MonitorWare Console EventReporter WinSyslog Database However, if this event is logged repeatedly, then further investigation would be needed". navigate here The target Domain Controller or the network or a client might be down.
This article provides an overview of main Internet speed challenges and reveals backup best practices. Not sure why moving the mailbox back and forth fixed it, but it did clear up something that was an issue. Join & Ask a Question Need Help in Real-Time? Keep in touch with Experts ExchangeTech news and trends delivered to your inbox every month Membership How it Works Gigs Live Careers Plans and Pricing For Business Become an Expert Resource
The circuit that received this error is being closed. See ME912062 for additional information about this event. The circuit that received this error is being closed. The winsock subsystem returned the error:.
Log into Exchange Admin Center.: Navigate to the Recipients >>Resources tab.: "Recipients" is our default selection … Exchange Email Servers Advertise Here 658 members asked questions and received personalized solutions in The event repository was initially provided as a tool for parser creation but has since evolved. The target Domain Controller or the network or a client might be down. Thanks Post #: 1 Featured Links* Page:  << Older Topic Newer Topic >> All Forums >> [Microsoft Exchange 2000] >> General >> Event ID: 9040 Page: 
All users are showing the correct legacy dn. 0 NAS Cloud Backup Strategies Promoted by Alexander Negrash This article explains backup scenarios when using network storage. Things to look for would be as follows: Check the cabling on the network card of the Exchange server. See example of private comment Links: ME912062, MaxUserPort Key is Missing or Non-default, MSEX2K3DB Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links... Login here!
Marked as answer by VAs Hachi Roku Friday, April 23, 2010 5:32 PM Friday, April 23, 2010 5:32 PM Reply | Quote Microsoft is conducting an online survey to understand your See MSEX2K3DB for details on this event. This problem may be a transient one. Continue reading Question has a verified solution.
However, if this event is logged repeatedly, then further investigation would be needed. The circuit that received this error is being closed.Event InformationExplanation : This event indicates that the NSPI interface of the Exchange server encountered a problem when communicating with a Global Catalog Peter Bruzzese Andy Grogan Nuno Mota Henrik Walther Neil Hobson Anderson Patricio Jaap Wesselius Markus Klein Rui Silva Ilse Van Criekinge Books Hardware Mail Archiving Load Balancing Message Boards Migration Section However, if this is happening frequently, check network related factors in the environment.