Microsoft KB Archive/304593

= FIX: Application Center 2000 Replication May Fail with Event ID 5064, Status 0x8007274C =

Article ID: 304593

Article Last Modified on 9/23/2005

-

APPLIES TO


 * Microsoft Application Center 2000 Standard Edition

-



This article was previously published under Q304593



SYMPTOMS
On extremely high-latency networks, Application Center 2000 file replication may fail and you may see the Event ID error 5064 in the Event Viewer log. The full contents of the log resemble the following:

Event Type: Error Event Source:  Application Center Event Category: Replication Event ID:  5064 Date:      ... Time:      ... User:      N/A Computer:  ... Description: __CLASS: MicrosoftAC_Replication_Session_DriverEvents_ActionListTransfer_SendFileFailed_Event __SERVER: ... ServerGUID: ... DriverID: FS EventId: 5064 GUID: {AE61F00C-E4FF-4769-B32D-11630C1752DD} Path: ... RemoteServer: ... ReplicationID: ... ReplicationJobID: ... Status: 0x8007274c StatusMessage: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. TimeGenerated: ... Type: 1 DisplayName: Replication Session DriverEvents ActionListTransfer SendFileFailed



CAUSE
The Application Center 2000 replication service uses the Windows Sockets TransmitFile function for high-performance file data transfers over sockets. However, in extremely high latency networks, the TransmitFile function may fail with the 0x8007274c (WSAETIMEDOUT) error because of TCP/IP connection timeouts. The replication service does not treat WSAETIMEDOUT as a recoverable error and fails replication if this error condition occurs.



RESOLUTION
To resolve this problem, upgrade to Application Center 2000 Service Pack (SP) 1. For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

309384 INFO: How to Obtain the Latest Application Center 2000 Service Pack



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

This problem was corrected in Application Center 2000 Service Pack 1.

Keywords: kbbug kbfix kbqfe kbhotfixserver KB304593

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.