Export - Import fails after server reboot or SharePlex Services Restart in Windows (4286272)

Return

Feedback Submitted

Did this article solve an issue for you?

Select Rating

Title

Export - Import fails after server reboot or SharePlex Services Restart in Windows
Description

The connection between export and import can be established when starting a new replication, but after a server reboot or the restart of the SharePlex services on either of the machines causes the connection to fail with the following messages:
Source:
Export: Couldn't write data to socket - too many EINTR retries (exporting to $TARGET_HOSTNAME queue QUEUE) [module xpt]
Export: Failed to send message mid 529556 to sp_mport (exporting to $TARGET_HOSTNAME queue QUEUE) [module xpt]
Export: Send_queuedata failed to send message to import - exiting (exporting to $TARGET_HOSTNAME queue QUEUE) [module xpt]
Target:
Import: Error 0 - read from port (importing from $SOURCE_HOSTNAME queue QUEUE) [module imp]
Import exited with code=1, pid = 4852 (importing from $SOURCE_HOSTNAME queue QUEUE)
Cause

Incorrect MTU size on source server causes connectivity issues when sending larger packages between Source and Target.
Executing "netsh interface ipv4 show interfaces" on CMD on source server shows a number larger than 1500 and ping using MTU size - 28 fails
C:\>netsh interface ipv4 show interfaces
Idx Met MTU State Name
--- ---------- ---------- ------------ ---------------------------
1 4294967295 1 0 32887 Loopback Pseudo-Interface 1
15 1514 1 1849431082 11737903881 Local Area Connection
Verify by using ping that the MTU size - 28 bytes of the header is able or unable to communicate with the other server.
MTU - Header = 1514 -28 = 1486
C:\>ping -l 1486 -f targethostname
Pinging targethostname [IP ADDRESS] with 1486 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Resolution

Resolution:
Please work with network administrator to change MTU as needed.
Example:
From an CMD prompt started as an Administrator, reset the MTU to the default of 1500 bytes as below:
netsh interface ipv4 set subinterface IDX mtu=1500 store=persistent
netsh interface ipv6 set subinterface IDX mtu=1500 store=persistent
IDX Is the first value obtain through "netsh interface ipv4 show interfaces". In the example above it would be 15
If the error of connection persists after setting the MTU to 1500 bytes, please contact SharePlex Support
Additional Information

https://blogs.technet.microsoft.com/askpfeplat/2014/12/01/psa-incorrect-mtu-size-causes-connectivity-issues-with-windows-server-2012-and-windows-server-2012-r2/

Feedback Submitted

Did this article solve an issue for you?

Select Rating

Request a KB Article

Export - Import fails after server reboot or SharePlex Services Restart in Windows (4286272)

Title

Description

Cause

Resolution

Additional Information

Leave a Comment