Gateway error updating data source

[Anonymous]

Hi,

I have an user getting the following error when trying to update the data-source of a report that is being shared trhought the "On-premises data gateway".



We already tried changing the Spooling folder from %APPDATA% to a folder in the drive giving permissions to the service and restarting the service but unfortanly nothing seems to work.

Is there anyone that already had this type of issue and is able to help me?

Note: this is only happening with one user.

Thank you for your attention!

[arvindsingh802]

Use a service account rather than default account and provide the service account Adminstrator previledge on gateway server.

[siva506]

Hi,

I need help with the issue below.

Please help me.working fine on the desktop but problem in service only.

Last refresh failed: 11/24/2022, 10:11:55 PM
There was an error when processing the data in the dataset.Hide details

Data source error:	{"error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","pbi.error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","parameters":{},"details":[{"code":"DM_ErrorDetailNameCode_UnderlyingErrorCode","detail":{"type":1,"value":"-2147467259"}},{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"AnalysisServices: The connection either timed out or was lost."}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.ValueError.DataSourceKind","detail":{"type":1,"value":"AnalysisServices"}},{"code":"Microsoft.Data.Mashup.ValueError.DataSourcePath","detail":{"type":1,"value":"canatec1v4621.na.loreal.intra\\boost;Boost_Local"}},{"code":"Microsoft.Data.Mashup.ValueError.Reason","detail":{"type":1,"value":"DataSource.Error"}}],"exceptionCulprit":1}}} Table: UPC ASP.
Cluster URI:	WABI-NORTH-EUROPE-D-PRIMARY-redirect.analysis.windows.net
Activity ID:	434c9d45-659b-4d24-91e2-a2deae519e83
Request ID:	4dac45b1-9228-ab6c-0f6c-c2ee30aa473d
Time:	2022-11-24 16:41:55Z

[Anonymous]

Hi, thank you for your response!

We tried that but unfortanly there are no changes in the previous behavior.
I also forgot to mention something that might help, when the user that is experiencing this issue publish his work again this issue stops.