Merge pull request #280823 from nachoalonsoportillo/add-adf-pg-error

Add entry for 11775 and replace enum names with codes (users never see enum names)

Author: v-ccolin

articles/data-factory/connector-troubleshoot-guide.md

@@ -44,7 +44,7 @@ You can refer to the troubleshooting pages for each connector to see problems sp
 
 The errors below are general to the copy activity and could occur with any connector.
 
-#### Error code: JreNotFound
+#### Error code: 20000
 
 - **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.`
 
@@ -53,7 +53,15 @@ The errors below are general to the copy activity and could occur with any conne
 - **Recommendation**:  Check your integration runtime environment, see [Use Self-hosted Integration Runtime](./format-parquet.md#using-self-hosted-integration-runtime).
 
 
-#### Error code: WildcardPathSinkNotSupported
+#### Error code: 20002
+
+- **Message**: `An error occurred when invoking Java Native Interface.`
+
+- **Cause**: If the error message contains "Cannot 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**: Log 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.
+
+#### Error code: 20020
 
 - **Message**: `Wildcard in path is not supported in sink dataset. Fix the path: '%setting;'.`
 
@@ -80,53 +88,45 @@ The errors below are general to the copy activity and could occur with any conne
 
     3. Save the file, and then restart the Self-hosted IR machine.
 
-#### Error code: JniException
-
-- **Message**: `An error occurred when invoking Java Native Interface.`
-
-- **Cause**: If the error message contains "Cannot 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**: Log 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.
-
-#### Error code: GetOAuth2AccessTokenErrorResponse
+#### Error code: 20150
 
 - **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.
 
-#### Error code: FailedToGetOAuth2AccessToken
+#### Error code: 20151
 
 - **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.
 
-#### Error code: OAuth2AccessTokenTypeNotSupported
+#### Error code: 20152
 
 - **Message**: `The toke type '%tokenType;' from your authorization server is not supported, supported types: '%tokenTypes;'.`
 
 - **Cause**: Your authorization server is not supported.
 
 - **Recommendation**: Use an authorization server that can return tokens with supported token types.
 
-#### Error code: OAuth2ClientIdColonNotAllowed
+#### Error code: 20153
 
 - **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.
 
-#### Error code: ManagedIdentityCredentialObjectNotSupported
+#### Error code: 20523
 
 - **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.
 
-#### Error code: QueryMissingFormatSettingsInDataset
+#### Error code: 20551
 
 - **Message**: `The format settings are missing in dataset %dataSetName;.`
 
@@ -138,99 +138,99 @@ The errors below are general to the copy activity and could occur with any conne
 
 - **Recommendation**: Deselect the "Binary copy" in the dataset, and set correct format settings.
 
-#### Error code: QueryUnsupportedCommandBehavior
+#### Error code: 20552
 
 - **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.
 
-#### Error code: DataConsistencyFailedToGetSourceFileMetadata
+#### Error code: 20701
 
 - **Message**: `Failed to retrieve source file ('%name;') metadata to validate data consistency.`
 
 - **Cause**: There is a transient issue on the sink data store, or retrieving metadata from the sink data store is not allowed.
 
-#### Error code: DataConsistencyFailedToGetSinkFileMetadata
+#### Error code: 20703
 
 - **Message**: `Failed to retrieve sink file ('%name;') metadata to validate data consistency.`
 
 - **Cause**: There is a transient issue on the sink data store, or retrieving metadata from the sink data store is not allowed.
 
-#### Error code: DataConsistencyValidationNotSupportedForNonDirectBinaryCopy
+#### Error code: 20704
 
 - **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.
 
-#### Error code: DataConsistencyValidationNotSupportedForLowVersionSelfHostedIntegrationRuntime
+#### Error code: 20705
 
 - **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.
 
-#### Error code: SkipMissingFileNotSupportedForNonDirectBinaryCopy
+#### Error code: 20741
 
 - **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.
 
-#### Error code: SkipInconsistencyDataNotSupportedForNonDirectBinaryCopy
+#### Error code: 20742
 
 - **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.
 
-#### Error code: SkipForbiddenFileNotSupportedForNonDirectBinaryCopy
+#### Error code: 20743
 
 - **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.
 
-#### Error code: SkipForbiddenFileNotSupportedForThisConnector
+#### Error code: 20744
 
 - **Message**: `Skip forbidden file is not supported for this connector: ('%connectorName;').`
 
 - **Recommendation**: Remove 'fileForbidden' of the skipErrorFile setting in the copy activity payload.
 
-#### Error code: SkipInvalidFileNameNotSupportedForNonDirectBinaryCopy
+#### Error code: 20745
 
 - **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.
 
-#### Error code: SkipInvalidFileNameNotSupportedForSource
+#### Error code: 20746
 
 - **Message**: `Skip invalid file name is not supported for '%connectorName;' source.`
 
 - **Recommendation**: Remove 'invalidFileName' of the skipErrorFile setting in the copy activity payload.
 
-#### Error code: SkipInvalidFileNameNotSupportedForSink
+#### Error code: 20747
 
 - **Message**: `Skip invalid file name is not supported for '%connectorName;' sink.`
 
 - **Recommendation**: Remove 'invalidFileName' of the skipErrorFile setting in the copy activity payload.
 
-#### Error code: SkipAllErrorFileNotSupportedForNonBinaryCopy
+#### Error code: 20748
 
 - **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.
 
-#### Error code: DeleteFilesAfterCompletionNotSupportedForNonDirectBinaryCopy
+#### Error code: 20771
 
 - **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.
 
-#### Error code: DeleteFilesAfterCompletionNotSupportedForThisConnector
+#### Error code: 20772
 
 - **Message**: `'deleteFilesAfterCompletion' is not supported for this connector: ('%connectorName;').`
 
 - **Recommendation**: Remove the 'deleteFilesAfterCompletion' setting in the copy activity payload.
 
-#### Error code: FailedToDownloadCustomPlugins
+#### Error code: 27002
 
 - **Message**: `Failed to download custom plugins.`
 
@@ -240,21 +240,21 @@ The errors below are general to the copy activity and could occur with any conne
 
 ## General connector errors
 
-#### Error code: UserErrorOdbcInvalidQueryString
+#### Error code: 9611
 
 - **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 non-query scripts and your data store is supported. Alternatively, consider to use stored procedure that returns a dummy result to execute your non-query scripts.
 
-#### Error code: FailToResolveParametersInExploratoryController 
+#### Error code: 11775
 
-- **Message**: `The parameters and expression cannot be resolved for schema operations. …The template function 'linkedService' is not defined or not valid.`
+- **Message**: `Failed to connect to your instance of Azure Database for PostgreSQL flexible server.`
 
-- **Cause**: The service has limitation to support the linked service which references another linked service with parameters for test connection or preview data. For example, passing a parameter from a Key Vault to a linked service may occur the issue. 
+- **Cause**: User or password provided are incorrect. The encryption method selected is not compatible with the configuration of the server. The network connectivity method configured for your instance doesn't allow connections from the Integration Runtime selected.
 
-- **Recommendation**: Remove the parameters in the referred linked service to eliminate the error. Otherwise, run the pipeline without testing connection or previewing data. 
+- **Recommendation**: Confirm that the user provided exists in your instance of PostgreSQL and that the password corresponds to the one currently assigned to that user. Make sure that the encryption method selected is accepted by your instance of PostgreSQL, based on its current configuration. If the network connectivity method of your instance is configured for Private access (VNet integration), use a Self-Hosted Integration Runtime (IR) to connect to it. If it is configured for Public access (allowed IP addresses), it is recommended to use an Azure IR with managed virtual network and deploy a managed private endpoint to connect to your instance. When it is configured for Public access (allowed IP addresses) a less recommended alternative consists in creating firewall rules in your instance to allow traffic originating on the IP addresses used by the Azure IR you're using.
 
 ## Related content
 

articles/data-factory/connector-troubleshoot-postgresql.md

@@ -17,18 +17,18 @@ 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.
 
-## Error code: AzurePostgreSqlNpgsqlDataTypeNotSupported
-
-- **Message**: `The data type of the chosen Partition Column, '%partitionColumn;', is '%dataType;' and this data type is not supported for partitioning.`
-
-- **Recommendation**: Pick a partition column with int, bigint, smallint, serial, bigserial, smallserial, timestamp with or without time zone, time without time zone or date data type.
-
-## Error code: AzurePostgreSqlNpgsqlPartitionColumnNameNotProvided
+## Error code: 23704
 
 - **Message**: `Partition column name must be specified.`
 
 - **Cause**: No partition column name is provided, and it couldn't be decided automatically.
 
+## Error code: 23705
+
+- **Message**: `The data type of the chosen Partition Column, '%partitionColumn;', is '%dataType;' and this data type is not supported for partitioning.`
+
+- **Recommendation**: Pick a partition column with int, bigint, smallint, serial, bigserial, smallserial, timestamp with or without time zone, time without time zone or date data type.
+
 ## Related content
 
 For more troubleshooting help, try these resources: