You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/data-factory/connector-troubleshoot-guide.md
+11Lines changed: 11 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -43,6 +43,17 @@ You can refer to the troubleshooting pages for each connector to see problems sp
43
43
44
44
The following errors are general to the copy activity and could occur with any connector.
45
45
46
+
#### Error code: 2200
47
+
48
+
-**Message**: `The underlying connection was closed: An unexpected error occurred on a send.`
49
+
50
+
-**Cause**: This typically indicates an authentication failure during data transfer operations. This can occur when the remote party closes the transport stream.
51
+
52
+
-**Reccomendation**:
53
+
- Verify the source connection and test it to ensure it is functioning correctly.
54
+
- Check the authentication method used for the connection.
55
+
- Review firewall configuration settings for Azure Cosmos DB to ensure they allow the necessary traffic.
56
+
46
57
#### Error code: 20000
47
58
48
59
-**Message**: `Java Runtime Environment cannot be found on the Self-hosted Integration Runtime machine. It is required for parsing or writing to Parquet/ORC files. Make sure Java Runtime Environment has been installed on the Self-hosted Integration Runtime machine.`
0 commit comments