Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
5 years ago
Solved

Strange error while refreshing a Dataflow

This morning I have experienced multiple Dataflow refresh errors. The error is the same in all Dataflows and it is repeatable upon manual refresh.:

 

Error: Can't convert 9 to proper M credential Type

 

The dataflows all connect to the same on-prem SQL server using Windows AD authentication.

 

The On Prem gateway shows all OK:

 

Also I can edit the dataflow and sucessfully add new queries to it. The fault only occurs on refresh of the dataflow.

 

No changes have been made to these dataflows since the last successful refresh and the password for the user account has not changed.

 

Any ideas what could be causing this? The error message has 0 results in Google.

Dataflow
Need Help
  • Anonymous's avatar
    Anonymous
    5 years ago

    Folks, the only seems to affect SQL based sources (ours are MS SQL) . This is what we did .... I don't like it, but as a workaround it may be OK:

    1. upgrade to the latest version of (May 2021) of the gateway
    2. Get a Gateway Administrator to take over the dataflows and refresh them. It did work for us; OR
    3. Add the dataflow owners as Gateway Admins and refresh the dataflows

    Neither of these options is ideal, if you have  a lot of dataflows , getting an admin to take them over is a lot of work. Similarly, adding dataflow owners as Gateway Admins may be exposing you from a security perspective etc.

     

    However, to get your dataflows up and running again and keeping your users happy, it is a suitable workaround short term.

     

    I was told by Microsoft Support Team (Mindtree in India) that this is expected behaviour (dataflow owner has to be gateway admin to refresh). I challenged them on this statement as I am not aware of any changes in this area ! 

16 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable
    5 years ago

    I've raised a ticket with Microsoft, will provide any updates here

  • Anonymous's avatar
    Anonymous
    Not applicable
    5 years ago

    I worked with Microsoft support and installed the May 2021 on premise gateway.  I was running the November 2020 version.  All my sql data flows are now running.

  • Anonymous's avatar
    Anonymous
    Not applicable
    5 years ago

    I have the exact same error since this night. All my flows connecting to a SQL DB are failing with this error. BUt I am able to edit them without any errors.

  • Anonymous's avatar
    Anonymous
    Not applicable
    5 years ago

    Yeah - we're having the same issue !!

  • Anonymous's avatar
    Anonymous
    Not applicable
    5 years ago

    I'm getting the same error as well and the flows are connecting to a SQL DB as well. I get the error about 36 seconds into the refresh.

  • Anonymous's avatar
    Anonymous
    Not applicable
    5 years ago

    Same thing here.  I have tried creating a new data source in the gateway and creating a brand new dataflow.  Both attempts did not address the issue.

    • Anonymous's avatar
      Anonymous
      Not applicable
      5 years ago

      Folks, the only seems to affect SQL based sources (ours are MS SQL) . This is what we did .... I don't like it, but as a workaround it may be OK:

      1. upgrade to the latest version of (May 2021) of the gateway
      2. Get a Gateway Administrator to take over the dataflows and refresh them. It did work for us; OR
      3. Add the dataflow owners as Gateway Admins and refresh the dataflows

      Neither of these options is ideal, if you have  a lot of dataflows , getting an admin to take them over is a lot of work. Similarly, adding dataflow owners as Gateway Admins may be exposing you from a security perspective etc.

       

      However, to get your dataflows up and running again and keeping your users happy, it is a suitable workaround short term.

       

      I was told by Microsoft Support Team (Mindtree in India) that this is expected behaviour (dataflow owner has to be gateway admin to refresh). I challenged them on this statement as I am not aware of any changes in this area ! 

      • csmith_enpro's avatar
        csmith_enpro
        Advocate I
        5 years ago

        Thank you for the response, so they weren't able to tell you the actual source of this problem?

  • csmith_enpro's avatar
    csmith_enpro
    Advocate I
    5 years ago

    Encountering this error as well, just started occurring this morning. I'm also able to create new dataflows, but can't refresh anything.

  • Sina's avatar
    Sina
    Frequent Visitor
    5 years ago

    The same error is happening for all our Data Flows as well, we have connections to ORACLE and SAP instances. 

    Any solutions from Microsoft team or anyone else who has solved the issue?

     

  • Anonymous's avatar
    Anonymous
    Not applicable
    5 years ago

    I also solved the problem by upgrading the gateway from November 2020 version to the last one.

  • ViniNaegele's avatar
    ViniNaegele
    Frequent Visitor
    5 years ago

    Samething from here, I can edit entities but cant refresh.

    Error: Can't convert 9 to proper M credential Type