Skip to content

Commit 3bbc55f

Browse files
committed
clear mc
2 parents 105aa98 + 04893cb commit 3bbc55f

14 files changed

+47
-35
lines changed

articles/data-factory/ci-cd-github-troubleshoot-guide.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -372,6 +372,9 @@ For more help with troubleshooting, try the following resources:
372372

373373
* [Data Factory blog](https://techcommunity.microsoft.com/t5/azure-data-factory-blog/bg-p/AzureDataFactoryBlog)
374374
* [Data Factory feature requests](/answers/topics/azure-data-factory.html)
375+
<<<<<<< HEAD
375376
* [Azure videos](/shows/data-exposed/?products=azure&terms=data-factory)
377+
=======
378+
>>>>>>> 04893cb4a0795a90dee76e382e96e606f7d51205
376379
* [Stack overflow forum for Data Factory](https://stackoverflow.com/questions/tagged/azure-data-factory)
377380
* [X information about Data Factory](https://x.com/hashtag/DataFactory)

articles/data-factory/connector-troubleshoot-dynamics-dataverse.md

Lines changed: 7 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ This article provides suggestions to troubleshoot common problems with the Dynam
3131

3232
- **Cause**: This issue is by design, because Data Factory and Synapse pipelines are unable to show columns that contain no values in the first 10 records. Make sure that the columns you've added are in the correct format.
3333

34-
- **Recommendation**: Manually add the columns in the mapping tab. For more details, refer to [Explicit mapping](copy-activity-schema-and-type-mapping.md#explicit-mapping).
34+
- **Recommendation**: Manually add the columns in the mapping tab. For more information, see [Explicit mapping](copy-activity-schema-and-type-mapping.md#explicit-mapping).
3535

3636

3737
## Error code: DynamicsMissingTargetForMultiTargetLookupField
@@ -80,9 +80,9 @@ This article provides suggestions to troubleshoot common problems with the Dynam
8080

8181
| Cause analysis | Recommendation |
8282
| :----------------------------------------------------------- | :----------------------------------------------------------- |
83-
| You are seeing `ERROR REQUESTING ORGS FROM THE DISCOVERY SERVERFCB 'EnableRegionalDisco' is disabled.` or otherwise `Unable to Login to Dynamics CRM, message:ERROR REQUESTING Token FROM THE Authentication context - USER intervention required but not permitted by prompt behavior AADSTS50079: Due to a configuration change made by your administrator, or because you moved to a new location, you must enroll in multi-factor authentication to access '00000007-0000-0000-c000-000000000000'` If your use case meets **all** of the following three conditions: <li>You are connecting to Dynamics 365, Common Data Service, or Dynamics CRM.</li><li>You are using Office365 Authentication.</li><li>Your tenant and user is configured in Microsoft Entra ID for [conditional access](../active-directory/conditional-access/overview.md) and/or Multi-Factor Authentication is required (see this [link](/powerapps/developer/data-platform/authenticate-office365-deprecation) to Dataverse doc).</li> Under these circumstances, the connection used to succeed before 6/8/2021. Starting 6/9/2021 connection will start to fail because of the deprecation of regional Discovery Service (see this [link](/power-platform/important-changes-coming#regional-discovery-service-is-deprecated)).| If your tenant and user is configured in Microsoft Entra ID for [conditional access](../active-directory/conditional-access/overview.md) and/or Multi-Factor Authentication is required, you must use 'Microsoft Entra service principal' to authenticate after 6/8/2021. Refer this [link](./connector-dynamics-crm-office-365.md#prerequisites) for detailed steps.|
83+
| You're seeing `ERROR REQUESTING ORGS FROM THE DISCOVERY SERVERFCB 'EnableRegionalDisco' is disabled.` or otherwise `Unable to Login to Dynamics CRM, message:ERROR REQUESTING Token FROM THE Authentication context - USER intervention required but not permitted by prompt behavior AADSTS50079: Due to a configuration change made by your administrator, or because you moved to a new location, you must enroll in multi-factor authentication to access '00000007-0000-0000-c000-000000000000'` If your use case meets **all** of the following three conditions: <li>You're connecting to Dynamics 365, Common Data Service, or Dynamics CRM.</li><li>You're using Office365 Authentication.</li><li>Your tenant and user is configured in Microsoft Entra ID for [conditional access](../active-directory/conditional-access/overview.md) and/or multifactor authentication is required (see this [link](/powerapps/developer/data-platform/authenticate-office365-deprecation) to Dataverse doc).</li> Under these circumstances, the connection used to succeed before 6/8/2021. Starting 6/9/2021, connection will start to fail because of the deprecation of regional Discovery Service (see this [link](/power-platform/important-changes-coming#regional-discovery-service-is-deprecated)).| If your tenant and user is configured in Microsoft Entra ID for [conditional access](../active-directory/conditional-access/overview.md) and/or multifactor authentication is required, you must use 'Microsoft Entra service principal' to authenticate after 6/8/2021. Refer this [link](./connector-dynamics-crm-office-365.md#prerequisites) for detailed steps.|
8484
|If you see `Office 365 auth with OAuth failed` in the error message, it means that your server might have some configurations not compatible with OAuth.| <li>Contact Dynamics support team with the detailed error message for help.</li><li>Use the service principal authentication, and you can refer to this article: [Example: Dynamics online using Microsoft Entra service principal and certificate authentication](./connector-dynamics-crm-office-365.md#example-dynamics-online-using-azure-ad-service-principal-and-certificate-authentication).</li>
85-
|If you see `Unable to retrieve authentication parameters from the serviceUri` in the error message, it means that either you input the wrong Dynamics service URL or proxy/firewall to intercept the traffic. |<li>Make sure you have put the correct service URI in the linked service.</li><li>If you use the Self Hosted IR, make sure that the firewall/proxy does not intercept the requests to the Dynamics server.</li> |
85+
|If you see `Unable to retrieve authentication parameters from the serviceUri` in the error message, it means that either you input the wrong Dynamics service URL or proxy/firewall to intercept the traffic. |<li>Make sure you have put the correct service URI in the linked service.</li><li>If you use the Self Hosted IR, make sure that the firewall/proxy doesn't intercept the requests to the Dynamics server.</li> |
8686
|If you see `An unsecured or incorrectly secured fault was received from the other party` in the error message, it means that unexpected responses were gotten from the server side. | <li>Make sure your username and password are correct if you use the Office 365 authentication. </li><li> Make sure you have input the correct service URI.</li><li>If you use regional CRM URL (URL has a number after 'crm'), make sure you use the correct regional identifier.</li><li>Contact the Dynamics support team for help.</li>|
8787
|If you see `No Organizations Found` in the error message, it means that either your organization name is wrong or you used a wrong CRM region identifier in the service URL.|<li>Make sure you have input the correct service URI.</li><li>If you use the regional CRM URL (URL has a number after 'crm'), make sure that you use the correct regional identifier.</li><li>Contact the Dynamics support team for help.</li>|
8888
| If you see `401 Unauthorized` and Microsoft Entra related error message, it means that there's an issue with the service principal. |Follow the guidance in the error message to fix the service principal issue. |
@@ -101,7 +101,7 @@ This article provides suggestions to troubleshoot common problems with the Dynam
101101

102102
- **Message**: `The Fetch Xml query specified is invalid.`
103103

104-
- **Cause**: There is an error existed in the fetch XML.
104+
- **Cause**: There's an error existed in the fetch XML.
105105

106106
- **Recommendation**: Fix the error in the fetch XML.
107107

@@ -110,7 +110,7 @@ This article provides suggestions to troubleshoot common problems with the Dynam
110110

111111
- **Message**: `Input DataSet must contain keycolumn(s) in Upsert/Update scenario. Missing key column(s): %column;`
112112

113-
- **Cause**: The source data does not contain the key column for the sink entity.
113+
- **Cause**: The source data doesn't contain the key column for the sink entity.
114114

115115
- **Recommendation**: Confirm that key columns are in the source data or map a source column to the key column on the sink entity.
116116

@@ -119,7 +119,7 @@ This article provides suggestions to troubleshoot common problems with the Dynam
119119

120120
- **Message**: `The primary key attribute '%attribute;' must be of type guid.`
121121

122-
- **Cause**: The type of the primary key column is not 'Guid'.
122+
- **Cause**: The type of the primary key column isn't 'Guid'.
123123

124124
- **Recommendation**: Make sure that the primary key column in the source data is of 'Guid' type.
125125

@@ -128,7 +128,7 @@ This article provides suggestions to troubleshoot common problems with the Dynam
128128

129129
- **Message**: `Cannot retrieve key information of alternate key '%key;' for entity '%entity;'.`
130130

131-
- **Cause**: The provided alternate key does not exist, which may be caused by wrong key names or insufficient permissions.
131+
- **Cause**: The provided alternate key doesn't exist, which could be caused by wrong key names or insufficient permissions.
132132

133133
- **Recommendation**: <br/>
134134
- Fix typos in the key name.<br/>
@@ -166,7 +166,6 @@ This article provides suggestions to troubleshoot common problems with the Dynam
166166
- **Cause**: The virtual column is not supported now.
167167

168168
- **Recommendation**: For the Option Set value, follow the options below to get it:
169-
- You can get the object type code by referring to [How to Find the Object Type Code for Any Entity](https://powerobjects.com/tips-and-tricks/find-object-type-code-entity/).
170169
- You can link the StringMap entity to your target entity and get the associated values.
171170

172171
## The parallel copy in a Dynamics CRM data store

articles/data-factory/connector-troubleshoot-file-system.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -20,9 +20,9 @@ This article provides suggestions to troubleshoot common problems with the file
2020

2121
- **Message**: `Access to '%path;' is not allowed.`
2222

23-
- **Cause**: Copying files from local machine is not supported under Azure Integration Runtime. For Self-hosted Integration Runtime (versions >= 5.22.8297.1) , Azure Data Factory is introducing a new security control to allow or disallow local SHIR file system access through the connector. By default, it's disabled.
23+
- **Cause**: Copying files from local machine isn't supported under Azure Integration Runtime. For Self-hosted Integration Runtime (versions >= 5.22.8297.1), Azure Data Factory is introducing a new security control to allow or disallow local SHIR file system access through the connector. It's disabled by default.
2424

25-
- **Recommendation**: Using command line from [Set up an existing self-hosted IR via local PowerShell](create-self-hosted-integration-runtime.md#set-up-an-existing-self-hosted-ir-via-local-powershell) , you could allow or disallow local SHIR file system access.
25+
- **Recommendation**: Using command line from [Set up an existing self-hosted IR via local PowerShell](create-self-hosted-integration-runtime.md#set-up-an-existing-self-hosted-ir-via-local-powershell), you could allow or disallow local SHIR file system access.
2626

2727

2828
## Related content

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ This article provides suggestions to troubleshoot common problems with the ORC f
1919
## Error code: OrcJavaInvocationException
2020

2121
- **Message**: `An error occurred when invoking Java, message: %javaException;.`
22-
- **Causes and recommendations**: Different causes may lead to this error. Check below list for possible cause analysis and related recommendation.
22+
- **Causes and recommendations**: Different causes could lead to this error. Check this list for possible cause analysis and related recommendation.
2323

2424
| Cause analysis | Recommendation |
2525
| :----------------------------------------------------------- | :----------------------------------------------------------- |
@@ -33,7 +33,7 @@ This article provides suggestions to troubleshoot common problems with the ORC f
3333

3434
- **Message**: `The Ticks value '%ticks;' for the datetime column must be between valid datetime ticks range -621355968000000000 and 2534022144000000000.`
3535

36-
- **Cause**: If the datetime value is '0001-01-01 00:00:00', it could be caused by the differences between the [Julian calendar and the Gregorian calendar](https://en.wikipedia.org/wiki/Proleptic_Gregorian_calendar#Difference_between_Julian_and_proleptic_Gregorian_calendar_dates).
36+
- **Cause**: If the datetime value is '0001-01-01 00:00:00', it could be differences between the [Julian calendar and the Gregorian calendar](https://en.wikipedia.org/wiki/Proleptic_Gregorian_calendar#Difference_between_Julian_and_proleptic_Gregorian_calendar_dates).
3737

3838
- **Recommendation**: Check the ticks value and avoid using the datetime value '0001-01-01 00:00:00'.
3939

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

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -20,11 +20,11 @@ This article provides suggestions to troubleshoot common problems with the Parqu
2020

2121
- **Message**: `An error occurred when invoking java, message: %javaException;.`
2222

23-
- **Causes and recommendations**: Different causes may lead to this error. Check below list for possible cause analysis and related recommendation.
23+
- **Causes and recommendations**: Different causes could lead to this error. Check this list for possible cause analysis and related recommendation.
2424

2525
| Cause analysis | Recommendation |
2626
| :----------------------------------------------------------- | :----------------------------------------------------------- |
27-
| When the error message contains the strings "java.lang.OutOfMemory", "Java heap space", and "doubleCapacity", it's usually a memory management issue in an old version of Integration Runtime. | If you are using Self-hosted IR and the version is earlier than 3.20.7159.1, we recommend that you upgrade to the latest version. |
27+
| When the error message contains the strings "java.lang.OutOfMemory", "Java heap space", and "doubleCapacity", it's usually a memory management issue in an old version of Integration Runtime. | If you're using Self-hosted IR and the version is earlier than 3.20.7159.1, we recommend that you upgrade to the latest version. |
2828
| When the error message contains the string "java.lang.OutOfMemory", the integration runtime doesn't have enough resources to process the files. | Limit the concurrent runs on the integration runtime. For Self-hosted IR, scale up to a powerful machine with memory that's equal to or greater than 8 GB. |
2929
| When the error message contains the string "NullPointerReference", it might be a transient error. | Retry the operation. If the problem persists, contact support. |
3030

@@ -40,7 +40,7 @@ This article provides suggestions to troubleshoot common problems with the Parqu
4040

4141
- **Message**: `Unsupported Parquet type. PrimitiveType: %primitiveType; OriginalType: %originalType;.`
4242

43-
- **Cause**: The Parquet format is not supported in Azure Data Factory and Synapse pipelines.
43+
- **Cause**: The Parquet format isn't supported in Azure Data Factory and Synapse pipelines.
4444

4545
- **Recommendation**: Double-check the source data by going to [Supported file formats and compression codecs by copy activity](./supported-file-formats-and-compression-codecs.md).
4646

@@ -106,7 +106,7 @@ This article provides suggestions to troubleshoot common problems with the Parqu
106106

107107
- **Cause**: This scenario isn't supported.
108108

109-
- **Recommendation**: 'ParquetInterpretFor' should not be 'sparkSql'.
109+
- **Recommendation**: 'ParquetInterpretFor' shouldn't be 'sparkSql'.
110110

111111
## Error code: ParquetUnsupportFileLevelCompressionOption
112112

@@ -122,7 +122,7 @@ This article provides suggestions to troubleshoot common problems with the Parqu
122122

123123
- **Cause**: A Java Virtual Machine (JVM) can't be created because some illegal (global) arguments are set.
124124

125-
- **Recommendation**: Log in to the machine that hosts *each node* of your self-hosted IR. Check to ensure that the system variable is set correctly, as follows: `_JAVA_OPTIONS "-Xms256m -Xmx16g" with memory bigger than 8 G`. Restart all the IR nodes, and then rerun the pipeline.
125+
- **Recommendation**: Sign in to the machine that hosts *each node* of your self-hosted IR. Check to ensure that the system variable is set correctly, as follows: `_JAVA_OPTIONS "-Xms256m -Xmx16g" with memory bigger than 8 G`. Restart all the IR nodes, and then rerun the pipeline.
126126

127127
## Arithmetic overflow
128128

@@ -140,7 +140,7 @@ This article provides suggestions to troubleshoot common problems with the Parqu
140140

141141
The issue could be caused by white spaces or unsupported special characters (such as,;{}()\n\t=) in the column name, because Parquet doesn't support such a format.
142142

143-
For example, a column name such as *contoso(test)* will parse the type in brackets from [code](https://github.com/apache/parquet-mr/blob/master/parquet-column/src/main/java/org/apache/parquet/schema/MessageTypeParser.java) `Tokenizer st = new Tokenizer(schemaString, " ;{}()\n\t");`. The error is thrown because there is no such "test" type.
143+
For example, a column name such as *contoso(test)* will parse the type in brackets from [code](https://github.com/apache/parquet-mr/blob/master/parquet-column/src/main/java/org/apache/parquet/schema/MessageTypeParser.java) `Tokenizer st = new Tokenizer(schemaString, " ;{}()\n\t");`. The error is thrown because there's no such "test" type.
144144

145145
To check supported types, go to the GitHub [apache/parquet-mr site](https://github.com/apache/parquet-mr/blob/master/parquet-column/src/main/java/org/apache/parquet/schema/OriginalType.java).
146146

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

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1189,5 +1189,4 @@ For more troubleshooting help, try these resources:
11891189
* [Data Factory feature requests](/answers/topics/azure-data-factory.html)
11901190
* [Stack Overflow forum for Data Factory](https://stackoverflow.com/questions/tagged/azure-data-factory)
11911191
* [X information about Data Factory](https://x.com/hashtag/DataFactory)
1192-
* [Azure videos](https://azure.microsoft.com/resources/videos/index/)
11931192
* [Microsoft Q&A question page](/answers/topics/azure-data-factory.html)

0 commit comments

Comments
 (0)