Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.

Error refreshing from PBI service (Cancellation occurred when sending or receiving a request)

Hi,

 

I have a bunch of reports that started to fail with this error: Cancellation occurred when sending or receiving a request

 

These reports use a mix of SQL server and web connections to get their data (Web is generally files on Office 365).

 

It was all working fine until a few days/weeks ago - since we've had to refresh on PBI Desktop and re-publish which is a pain.

 

Because they are connecting to web datasources that require impresonation (Web on Sharepoint 365), we can't use the entreprise gateway that doesn't support this yet...

 

I've re-installed the personal gateway on several different machines, with no luck.

 

The logs from the gateway show the following:

 

GatewayPipelineErrorCode=DM_GWPipeline_Gateway_SignatureNotMatchCredentialError --->
Inner exception chain: System.FormatException
<pi>System.FormatException: InvalidCredentialFormat - Signature does not match
   at Microsoft.PowerBI.DataMovement.CommonUtilities.SymmetricKeyEncryptionHelper.Decrypt(SymmetricKeyEncryptedResultDataContract encryptedData, SymmetricKeyContractBase key)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayDataAccess.CredentialUtils.DecryptSymmetricKey(SymmetricKeyEncryptedResultDataContract encryptedData, SymmetricKeyContractBase key)</pi>
   --- End of inner exception stack trace ---
  ([0]Microsoft.PowerBI.DataMovement.Pipeline.Diagnostics.InvalidCredentialDueToSignatureNotMatchException.StackTrace:)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayDataAccess.CredentialUtils.DecryptSymmetricKey(SymmetricKeyEncryptedResultDataContract encryptedData, SymmetricKeyContractBase key)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayDataAccess.CredentialUtils.DecryptCredential(CredentialDetails credentialDetails, IGatewayCredentialStore credentialStore)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayDataAccess.DbConnectionProviderBase.DecryptCredential(CredentialDetails credentialDetails)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayDataAccess.MashupConnectionProviderBase.DecryptAndPrepareMashupCredential(DataSourceGatewayDetails datasource)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayDataAccess.MashupOleDbConnectionProvider.<TestConnectionAsync>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.ConnectionStrings.AdoNetDbFullConnectionString.<TestConnectionAsync>d__19.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.ConnectionStrings.DbFullConnectionString.<TestConnectionAsync>d__23.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.GatewayProcessor.<>c__DisplayClass4_0.<<TestDataSourceConnection>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.PowerBI.DataMovement.Pipeline.Common.Diagnostics.PipelineTelemetryService.<ExecuteInActivity>d__7`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.GatewayProcessor.<TestDataSourceConnection>d__4.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.GatewayProcessorDispatcher.<DispatchImpl>d__1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.GatewayProcessorDispatcher.<Dispatch>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.Serialization.GatewayDeserializer.<DeserializeImpl>d__9.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.Serialization.GatewayDeserializer.<>c__DisplayClass8_0.<<Deserialize>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.PowerBI.DataMovement.Pipeline.Common.Diagnostics.PipelineTelemetryService.<ExecuteInActivity>d__7`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.Serialization.GatewayDeserializer.<Deserialize>d__8.MoveNext()

According to this thread, there was an issue on the PBI Service related to web.page(), but despite the awareness item being removed from the list, this is still a problem for me.

 

Any advice? 

 

Damien.

Status: New
Comments
v-qiuyu-msft
Community Support

Hi @Anonymous,

 

After you update the on-premise data gateway to the latest version, please go to the dataset settings page for the dataset on Power BI service, ensure the dataset use this gateway and both SQL and web data sources credentials are fine. Then manually refresh the dataset again. 

 

Best Regards,
Qiuyun Yu 

Anonymous
Not applicable

Hi Qiuyun,

 

I've been running the latest gateway on all machines where I've tried.

The dataset does use this gateway, credentials are fine (actually if they weren't the error would be different right?).

 

Damien

v-qiuyu-msft
Community Support

Hi @Anonymous,

 

As you mentioned the dataset gets data from "SQL server and web connections to get their data (Web is generally files on Office 365)", which file to you use web data source to get data from and do you use OAuth2 authentication for this web data source? Do you perform merge or append query for tables use these two data sources? 

 

Please backup the pbix file for the report. Then remove the web data source and leave the SQL data source only, save as a new report, publish to service and set with the gateway, to see if it can be refreshed successfully. Open the report in desktop, remove SQL data source and leave we data source only, then publish to service and set with the gateway, to see if it can be refreshed successfully. 

 

Best Regards,
Qiuyun Yu