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
My guess is that the VM that is being used is a different platform depending on certain conditions. We used to have this issue but it wasn't intermittent at that time. It was very consistent and this was before we upgrading to .NET Core 3.1 and the latest versions of the SDK. Now when it happens, it is super random and we aren't really sure how to handle it since it happens after a number of retries.
Investigative information
Please provide the following:
Timestamp: 2020-05-26T12:42:35.1856794Z
Function App version: NET Core App 3.1 (v3 of runtime)
Function App name: Unable to share this, please message me if you need details.
Function name(s) (as appropriate): Unable to share this, please message me if you need details.
Invocation ID: bdc4b58025f94a67a3b6c64bd16acf45 (Listed as execution ID)
Region: East US 2
Repro steps
Provide the steps required to reproduce the problem:
In the activity function, use EF core to do some form of database access.
Kick off the orchestration function and hope you get (un)-lucky.
Expected behavior
I expect that the activity function will never throw a PlatformNotSupportedException.
Actual behavior
Once in a while, the activity function will throw the PlatformNotSupportedException. It appears to happen through the three retries which makes me think it has something to do with the VM being used. This doesn't happen until about iteration 500-1000, so it doesn't happen in the first activity execution or anything like that.
APIWT
changed the title
Intermittent instances of "Microsoft.Data.SqlClient is not supported on this platform.
Intermittent instances of "Microsoft.Data.SqlClient is not supported on this platform."
May 26, 2020
Any reason why you aren't using the latest version of Microsoft.NET.Sdk.Functions?
Also, you don't seem to be referencing Microsoft.Data.SqlClient - is this correct, and you're thus confused as to why you're getting that error message?
Hey @IanKemp! We are referencing Microsoft.Data.SqlClient transiently through the EF Core SQL Server nuget package in a project reference of the functions project. We updated Microsoft.NET.Sdk.Functions (as per advice in #5950) and I'll close this issue and continue to work with them over there. Thanks!
We have a durable orchestration function that calls an activity function several times. In some cases, the activity function will fail with the exception
Microsoft.Data.SqlClient is not supported on this platform.
. This is an intermittent issue and we have tried to work around it by placing a retry policy on our activity function based on this documentation: https://docs.microsoft.com/en-us/azure/azure-functions/durable/durable-functions-error-handling?tabs=csharp#automatic-retry-on-failureMy guess is that the VM that is being used is a different platform depending on certain conditions. We used to have this issue but it wasn't intermittent at that time. It was very consistent and this was before we upgrading to .NET Core 3.1 and the latest versions of the SDK. Now when it happens, it is super random and we aren't really sure how to handle it since it happens after a number of retries.
Investigative information
Please provide the following:
Repro steps
Provide the steps required to reproduce the problem:
Expected behavior
I expect that the activity function will never throw a
PlatformNotSupportedException
.Actual behavior
Once in a while, the activity function will throw the
PlatformNotSupportedException
. It appears to happen through the three retries which makes me think it has something to do with the VM being used. This doesn't happen until about iteration 500-1000, so it doesn't happen in the first activity execution or anything like that.Known workarounds
This might work, but we have not tried it: Azure/Azure-Functions#1370 (comment)
Related information
This is our CSPROJ:
The text was updated successfully, but these errors were encountered: