Merge pull request #293004 from Lucky-Wang16/0114-Update_TSG_link

JamesJBarnett · web-flow · commit 3b600ca710fa · 2025-02-08T16:42:17.000-07:00
[Doc update] Update TSG overview section name
diff --git a/articles/data-factory/connector-troubleshoot-guide.md b/articles/data-factory/connector-troubleshoot-guide.md
@@ -5,7 +5,7 @@ description: Learn how to troubleshoot connector issues in Azure Data Factory an
 author: jianleishen
 ms.subservice: data-movement
 ms.topic: troubleshooting
-ms.date: 09/25/2024
+ms.date: 01/14/2025
 ms.author: jianleishen
 ms.custom: synapse
 ai-usage: ai-assisted
@@ -44,8 +44,7 @@ You can refer to the troubleshooting pages for each connector to see problems sp
 
 The following errors are general to the copy activity and could occur with any connector.
 
-<a name="error-code-usererrorodbcoperationFailed"></a>
-#### Error code: 2200 - UserErrorOdbcOperationFailed
+#### <a name="error-code-usererrorodbcoperationfailed"></a> Error code: 2200 - UserErrorOdbcOperationFailed
 
 - **Message**: `The underlying connection was closed: An unexpected error occurred on a send.`
 
@@ -56,25 +55,23 @@ The following errors are general to the copy activity and could occur with any c
   - Check the authentication method used for the connection.
   - Review firewall configuration settings for Azure Cosmos DB to ensure they allow the necessary traffic.
 
-<a name="error-code-jrenotfound"></a>
-#### Error code: 20000 - JreNotFound
+#### <a name="error-code-jrenotfound"></a> Error code: 20000 - JreNotFound
 
 - **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.`
 
 - **Cause**: The self-hosted IR can't find Java Runtime. Java Runtime is required for reading particular sources.
 
 - **Recommendation**:  Check your integration runtime environment, see [Use Self-hosted Integration Runtime](./format-parquet.md#using-self-hosted-integration-runtime).
 
-#### Error code: 20002
+#### <a name="error-code-jniexception"></a> Error code: 20002 - JniException
 
 - **Message**: `An error occurred when invoking Java Native Interface.`
 
 - **Cause**: If the error message contains "Can't create JVM: JNI return code [-6][JNI call failed: Invalid arguments.]," the possible cause is that JVM can't be created because some illegal (global) arguments are set.
 
 - **Recommendation**: Sign in to the machine that hosts *each node* of your self-hosted integration runtime. Check to ensure that the system variable is set correctly, as follows: `_JAVA_OPTIONS "-Xms256m -Xmx16g" with memory bigger than 8G`. Restart all the integration runtime nodes, and then rerun the pipeline.
 
-<a name="error-code-wildcardpathsinknotsupported"></a>
-#### Error code: 20020 - WildcardPathSinkNotSupported
+#### <a name="error-code-wildcardpathsinknotsupported"></a> Error code: 20020 - WildcardPathSinkNotSupported
 
 - **Message**: `Wildcard in path is not supported in sink dataset. Fix the path: '%setting;'.`
 
@@ -101,51 +98,45 @@ The following errors are general to the copy activity and could occur with any c
 
     3. Save the file, and then restart the Self-hosted IR machine.
 
-<a name="error-code-jniexception"></a>
-#### Error code: 20150 - JniException
+#### <a name="error-code-getoauth2accesstokenerrorresponse"></a> Error code: 20150 - GetOAuth2AccessTokenErrorResponse
 
 - **Message**: `Failed to get access token from your token endpoint. Error returned from your authorization server: %errorResponse;.`
 
 - **Cause**: Your client ID or client secret is invalid, and the authentication failed in your authorization server.
 
 - **Recommendation**: Correct all OAuth2 client credential flow settings of your authorization server.
 
-<a name="error-code-failedtogetoauth2accesstoken"></a>
-#### Error code: 20151 - FailedToGetOAuth2AccessToken
+#### <a name="error-code-failedtogetoauth2accesstoken"></a> Error code: 20151 - FailedToGetOAuth2AccessToken
 
 - **Message**: `Failed to get access token from your token endpoint. Error message: %errorMessage;.`
 
 - **Cause**: OAuth2 client credential flow settings are invalid.
 
 - **Recommendation**: Correct all OAuth2 client credential flow settings of your authorization server.
 
-<a name="error-code-<a name="error-code-oauth2accesstokentypenotsupported"></a>
-#### Error code: 20152 - OAuth2AccessTokenTypeNotSupported
+#### <a name="error-code-oauth2accesstokentypenotsupported"></a> Error code: 20152 - OAuth2AccessTokenTypeNotSupported
 
 - **Message**: `The token type '%tokenType;' from your authorization server is not supported, supported types: '%tokenTypes;'.`
 
 - **Cause**: Your authorization server isn't supported.
 
 - **Recommendation**: Use an authorization server that can return tokens with supported token types.
-- 
-<a name="error-code-<a name="error-code-oauth2clientidcolonnotallowed"></a>
-#### Error code: 20153 - OAuth2ClientIdColonNotAllowed
+
+#### <a name="error-code-oauth2clientidcolonnotallowed"></a> Error code: 20153 - OAuth2ClientIdColonNotAllowed
 
 - **Message**: `The character colon(:) is not allowed in clientId for OAuth2ClientCredential authentication.`
 
 - **Cause**: Your client ID includes the invalid character colon (`:`).
 
 - **Recommendation**: Use a valid client ID.
 
-<a name="error-code-ManagedIdentityCredentialObjectNotSupported"></a>
-#### Error code: 20523 - ManagedIdentityCredentialObjectNotSupported
+#### <a name="error-code-managedidentitycredentialobjectnotsupported"></a> Error code: 20523 - ManagedIdentityCredentialObjectNotSupported
 
 - **Message**: `Managed identity credential is not supported in this version ('%version;') of Self Hosted Integration Runtime.`
 
 - **Recommendation**: Check the supported version and upgrade the integration runtime to a higher version.
 
-<a name="error-code-QueryMissingFormatSettingsInDataset"></a>
-#### Error code: 20551 - QueryMissingFormatSettingsInDataset
+#### <a name="error-code-querymissingformatsettingsindataset"></a> Error code: 20551 - QueryMissingFormatSettingsInDataset
 
 - **Message**: `The format settings are missing in dataset %dataSetName;.`
 
@@ -157,115 +148,99 @@ The following errors are general to the copy activity and could occur with any c
 
 - **Recommendation**: Deselect the "Binary copy" in the dataset, and set correct format settings.
 
-<a name="error-code-QueryUnsupportedCommandBehavior"></a>
-#### Error code: 20552 - QueryUnsupportedCommandBehavior
+#### <a name="error-code-queryunsupportedcommandbehavior"></a> Error code: 20552 - QueryUnsupportedCommandBehavior
 
 - **Message**: `The command behavior "%behavior;" is not supported.`
 
 - **Recommendation**: Don't add the command behavior as a parameter for preview or GetSchema API request URL.
 
-<a name="error-code-DataConsistencyFailedToGetSourceFileMetadata"></a>
-#### Error code: 20701 - DataConsistencyFailedToGetSourceFileMetadata
+#### <a name="error-code-dataconsistencyfailedtogetsourcefilemetadata"></a> Error code: 20701 - DataConsistencyFailedToGetSourceFileMetadata
 
 - **Message**: `Failed to retrieve source file ('%name;') metadata to validate data consistency.`
 
 - **Cause**: There's a transient issue on the sink data store, or retrieving metadata from the sink data store isn't allowed.
 
-<a name="error-code-DataConsistencyFailedToGetSinkFileMetadata"></a>
-#### Error code: 20703 - DataConsistencyFailedToGetSinkFileMetadata
+#### <a name="error-code-dataconsistencyfailedtogetsinkfilemetadata"></a> Error code: 20703 - DataConsistencyFailedToGetSinkFileMetadata
 
 - **Message**: `Failed to retrieve sink file ('%name;') metadata to validate data consistency.`
 
 - **Cause**: There's a transient issue on the sink data store, or retrieving metadata from the sink data store isn't allowed.
 
-<a name="error-code-DataConsistencyValidationNotSupportedForNonDirectBinaryCopy"></a>
-#### Error code: 20704 - DataConsistencyValidationNotSupportedForNonDirectBinaryCopy
+#### <a name="error-code-dataconsistencyvalidationnotsupportedfornondirectbinarycopy"></a> Error code: 20704 - DataConsistencyValidationNotSupportedForNonDirectBinaryCopy
 
 - **Message**: `Data consistency validation is not supported in current copy activity settings.`
 
 - **Cause**: The data consistency validation is only supported in the direct binary copy scenario.
 
 - **Recommendation**: Remove the 'validateDataConsistency' property in the copy activity payload.
 
-<a name="error-code-DataConsistencyValidationNotSupportedForLowVersionSelfHostedIntegrationRuntime"></a>
-#### Error code: 20705 - DataConsistencyValidationNotSupportedForLowVersionSelfHostedIntegrationRuntime
+#### <a name="error-code-dataconsistencyvalidationnotsupportedforlowversionselfhostedintegrationruntime"></a> Error code: 20705 - DataConsistencyValidationNotSupportedForLowVersionSelfHostedIntegrationRuntime
 
 - **Message**: `'validateDataConsistency' is not supported in this version ('%version;') of Self Hosted Integration Runtime.`
 
 - **Recommendation**: Check the supported integration runtime version and upgrade it to a higher version, or remove the 'validateDataConsistency' property from copy activities.
 
-<a name="error-code-SkipMissingFileNotSupportedForNonDirectBinaryCopy"></a>
-#### Error code: 20741 - SkipMissingFileNotSupportedForNonDirectBinaryCopy
+#### <a name="error-code-skipmissingfilenotsupportedfornondirectbinarycopy"></a> Error code: 20741 - SkipMissingFileNotSupportedForNonDirectBinaryCopy
 
 - **Message**: `Skip missing file is not supported in current copy activity settings, it's only supported with direct binary copy with folder.`
 
 - **Recommendation**: Remove 'fileMissing' of the skipErrorFile setting in the copy activity payload.
 
-<a name="error-code-SkipInconsistencyDataNotSupportedForNonDirectBinaryCopy"></a>
-#### Error code: 20742 - SkipInconsistencyDataNotSupportedForNonDirectBinaryCopy
+#### <a name="error-code-skipinconsistencydatanotsupportedfornondirectbinarycopy"></a> Error code: 20742 - SkipInconsistencyDataNotSupportedForNonDirectBinaryCopy
 
 - **Message**: `Skip inconsistency is not supported in current copy activity settings, it's only supported with direct binary copy when validateDataConsistency is true.`
 
 - **Recommendation**: Remove 'dataInconsistency' of the skipErrorFile setting in the copy activity payload.
 
-<a name="error-code-SkipForbiddenFileNotSupportedForNonDirectBinaryCopy"></a>
-#### Error code: 20743 - SkipForbiddenFileNotSupportedForNonDirectBinaryCopy
+#### <a name="error-code-skipforbiddenfilenotsupportedfornondirectbinarycopy"></a> Error code: 20743 - SkipForbiddenFileNotSupportedForNonDirectBinaryCopy
 
 - **Message**: `Skip forbidden file is not supported in current copy activity settings, it's only supported with direct binary copy with folder.`
 
 - **Recommendation**: Remove 'fileForbidden' of the skipErrorFile setting in the copy activity payload.
 
-<a name="error-code-SkipForbiddenFileNotSupportedForThisConnector"></a>
-#### Error code: 20744 - SkipForbiddenFileNotSupportedForThisConnector
+#### <a name="error-code-skipforbiddenfilenotsupportedforthisconnector"></a> Error code: 20744 - SkipForbiddenFileNotSupportedForThisConnector
 
 - **Message**: `Skip forbidden file is not supported for this connector: ('%connectorName;').`
 
 - **Recommendation**: Remove 'fileForbidden' of the skipErrorFile setting in the copy activity payload.
 
-<a name="error-code-SkipInvalidFileNameNotSupportedForNonDirectBinaryCopy"></a>
-#### Error code: 20745 - SkipInvalidFileNameNotSupportedForNonDirectBinaryCopy
+#### <a name="error-code-skipinvalidfilenamenotsupportedfornondirectbinarycopy"></a> Error code: 20745 - SkipInvalidFileNameNotSupportedForNonDirectBinaryCopy
 
 - **Message**: `Skip invalid file name is not supported in current copy activity settings, it's only supported with direct binary copy with folder.`
 
 - **Recommendation**: Remove 'invalidFileName' of the skipErrorFile setting in the copy activity payload.
 
-<a name="error-code-SkipInvalidFileNameNotSupportedForSource"></a>
-#### Error code: 20746 - SkipInvalidFileNameNotSupportedForSource
+#### <a name="error-code-skipinvalidfilenamenotsupportedforsource"></a> Error code: 20746 - SkipInvalidFileNameNotSupportedForSource
 
 - **Message**: `Skip invalid file name is not supported for '%connectorName;' source.`
 
 - **Recommendation**: Remove 'invalidFileName' of the skipErrorFile setting in the copy activity payload.
 
-<a name="error-code-SkipInvalidFileNameNotSupportedForSink"></a>
-#### Error code: 20747 - SkipInvalidFileNameNotSupportedForSink
+#### <a name="error-code-skipinvalidfilenamenotsupportedforsink"></a> Error code: 20747 - SkipInvalidFileNameNotSupportedForSink
 
 - **Message**: `Skip invalid file name is not supported for '%connectorName;' sink.`
 
 - **Recommendation**: Remove 'invalidFileName' of the skipErrorFile setting in the copy activity payload.
 
-<a name="error-code-SkipAllErrorFileNotSupportedForNonBinaryCopy"></a>
-#### Error code: 20748 - SkipAllErrorFileNotSupportedForNonBinaryCopy
+#### <a name="error-code-skipallerrorfilenotsupportedfornonbinarycopy"></a> Error code: 20748 - SkipAllErrorFileNotSupportedForNonBinaryCopy
 
 - **Message**: `Skip all error file is not supported in current copy activity settings, it's only supported with binary copy with folder.`
 
 - **Recommendation**: Remove 'allErrorFile' in the skipErrorFile setting in the copy activity payload.
 
-<a name="error-code-DeleteFilesAfterCompletionNotSupportedForNonDirectBinaryCopy"></a>
-#### Error code: 20771 - DeleteFilesAfterCompletionNotSupportedForNonDirectBinaryCopy
+#### <a name="error-code-deletefilesaftercompletionnotsupportedfornondirectbinarycopy"></a> Error code: 20771 - DeleteFilesAfterCompletionNotSupportedForNonDirectBinaryCopy
 
 - **Message**: `'deleteFilesAfterCompletion' is not support in current copy activity settings, it's only supported with direct binary copy.`
 
 - **Recommendation**: Remove the 'deleteFilesAfterCompletion' setting or use direct binary copy.
 
-<a name="error-code-DeleteFilesAfterCompletionNotSupportedForThisConnector"></a>
-#### Error code: 20772 - DeleteFilesAfterCompletionNotSupportedForThisConnector
+#### <a name="error-code-deletefilesaftercompletionnotsupportedforthisconnector"></a> Error code: 20772 - DeleteFilesAfterCompletionNotSupportedForThisConnector
 
 - **Message**: `'deleteFilesAfterCompletion' is not supported for this connector: ('%connectorName;').`
 
 - **Recommendation**: Remove the 'deleteFilesAfterCompletion' setting in the copy activity payload.
 
-<a name="error-code-FailedToDownloadCustomPlugins"></a>
-#### Error code: 27002 - FailedToDownloadCustomPlugins
+#### <a name="error-code-failedtodownloadcustomplugins"></a> Error code: 27002 - FailedToDownloadCustomPlugins
 
 - **Message**: `Failed to download custom plugins.`
 
@@ -275,17 +250,15 @@ The following errors are general to the copy activity and could occur with any c
 
 ## General connector errors
 
-<a name="error-code-UserErrorOdbcInvalidQueryString"></a>
-#### Error code: 9611 - UserErrorOdbcInvalidQueryString
+#### <a name="error-code-usererrorodbcinvalidquerystring"></a> Error code: 9611 - UserErrorOdbcInvalidQueryString
 
 - **Message**: `The following ODBC Query is not valid: '%'.`
  
 - **Cause**: You provide a wrong or invalid query to fetch the data/schemas.
 
 - **Recommendation**: Verify your query is valid and can return data/schemas. Use [Script activity](transform-data-using-script.md) if you want to execute nonquery scripts and your data store is supported. Alternatively, consider to use stored procedure that returns a dummy result to execute your nonquery scripts.
 
-<a name="error-code-FailToResolveParametersInExploratoryController"></a>
-#### Error code: 11775 - FailToResolveParametersInExploratoryController
+#### Error code: 11775
 
 - **Message**: `Failed to connect to your instance of Azure Database for PostgreSQL flexible server. '%'`
  
diff --git a/articles/data-factory/connector-troubleshoot-postgresql.md b/articles/data-factory/connector-troubleshoot-postgresql.md
@@ -5,7 +5,7 @@ description: Learn how to troubleshoot issues with the Azure Database for Postgr
 author: jianleishen
 ms.subservice: data-movement
 ms.topic: troubleshooting
-ms.date: 10/20/2023
+ms.date: 01/16/2025
 ms.author: jianleishen
 ms.custom: has-adal-ref, synapse
 ---
@@ -16,15 +16,13 @@ ms.custom: has-adal-ref, synapse
 
 This article provides suggestions to troubleshoot common problems with the Azure Database for PostgreSQL connector in Azure Data Factory and Azure Synapse.
 
-<a name="error-code-AzurePostgreSqlNpgsqlDataTypeNotSupported"></a>
-## Error code: 23704 - AzurePostgreSqlNpgsqlDataTypeNotSupported
+## <a name="error-code-azurepostgresqlnpgsqlpartitioncolumnnamenotprovided"></a> Error code: 23704 - AzurePostgreSqlNpgsqlPartitionColumnNameNotProvided
 
 - **Message**: `Partition column name must be specified.`
 
 - **Cause**: No partition column name is provided, and it couldn't be decided automatically.
 
-<a name="error-code-AzurePostgreSqlNpgsqlPartitionColumnNameNotProvided"></a>
-## Error code: 23705 - AzurePostgreSqlNpgsqlPartitionColumnNameNotProvided
+## <a name="error-code-azurepostgresqlnpgsqldatatypenotsupported"></a> Error code: 23705 - AzurePostgreSqlNpgsqlDataTypeNotSupported
 
 - **Message**: `The data type of the chosen Partition Column, '%partitionColumn;', is '%dataType;' and this data type is not supported for partitioning.`
 
