Error -2147467259 al intentar actualizar origen de datos SQL en Power BI

[adolfomartinez]

Microsoft SQL: La conexión ha devuelto el código de error -2147467259.

{
"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": "Microsoft SQL: La conexión ha devuelto el código de error -2147467259."
}
},
{
"code": "DM_ErrorDetailNameCode_UnderlyingHResult",
"detail": {
"type": 1,
"value": "-2147467259"
}
},
{
"code": "Microsoft.Data.Mashup.ValueError.DataSourceKind",
"detail": {
"type": 1,
"value": "SQL"
}
},
{
"code": "Microsoft.Data.Mashup.ValueError.DataSourcePath",
"detail": {
"type": 1,
"value": "<ip>MyIP</ip>;MyDB"
}
},
{
"code": "Microsoft.Data.Mashup.ValueError.ErrorCode",
"detail": {
"type": 1,
"value": "-2147467259"
}
},
{
"code": "Microsoft.Data.Mashup.ValueError.Message",
"detail": {
"type": 1,
"value": "La conexión ha devuelto el código de error -2147467259."
}
},
{
"code": "Microsoft.Data.Mashup.ValueError.Reason",
"detail": {
"type": 1,
"value": "DataSource.Error"
}
}
],
"exceptionCulprit": 1
}
}
} Table: Sabana TP 18 Meses.

[Anonymous]

Hi @adolfomartinez ,

Has your problem been solved? If the problem has been solved you can mark the reply for the standard answer to help the other members find it more quickly. If not, please point it out. Thanks in advance.

Best Regards,

Neeko Tang

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly. 

[Anonymous]

Hi @adolfomartinez ,

Please try  :

1. Set the Privacy Level setting for all your data sources to "Public" .

2.Clear all data source permissions (File-->Options and Settings --> Data Source Settings --> clear each data source permission).

3.Make sure that you've set the correct user with sufficient premission in the data source of your gateway. If the user is correct, try to delete and re-create the data source. If it still doesn't work, try to save your pbix in another name and publish it as a new report.

Best Regards,

Neeko Tang

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.