Forum Discussion

AnthonyMCUBI's avatar
AnthonyMCUBI
Frequent Visitor
6 years ago
Solved

Nondescript error in Power BI service for dataflow refresh

Hi everyone,   I'm having trouble debugging my powerbi dataflows, and would appreciate some guidance. When I try to refresh them I'm given a nondescript error that lists a Request ID, an Activity I...
Dataflow
Need Help
  • AnthonyMCUBI's avatar
    AnthonyMCUBI
    6 years ago

    Sorry for the late reply, I figured out the issue.

     

    Power BI recently, apparently had an update to how it connects to SQL CLR databases.  0-length passwords used to be allowed but now are not. I had to change my password from nothing to something in SSMS and then update my password in power bi connection settings. Everything worked fine after that.

     

    I should note that there was no error with my nothing-password until I erased it and put nothing as my password again, which was not allowed and I was asked to input a password. That's why it took awhile to track down.

v-lionel-msft's avatar
v-lionel-msft
Community Support
6 years ago

Hi AnthonyMCUBI ,

 

Click on the warning message and you will see more tips.

   

If the problem is still not solved, please post your M code(You can copy the code in "Advanced editor".)

 

Best regards,
Lionel Chen

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

 

  • AnthonyMCUBI's avatar
    AnthonyMCUBI
    Frequent Visitor
    6 years ago

    Thanks for the response.

     

    Below is the popup text box that appears after I clicked the error description mentioned in your response. 

     

     

    Since the popup doesn't give me extra information, I've also added the M code (in a picture, and then pasted):

     

     

    let
      Source = Sql.Database("localhost", "Test"),
      dbo_Locations = Source{[Schema = "bi", Item = "LocationCLRDim"]}[Data],
      #"Converted to Table" = Table.SplitColumn(dbo_Locations, "RowData", Splitter.SplitTextByDelimiter("#(tab)", QuoteStyle.None), {"ActiveBusinessDays", "AllowTransfers", "BranchCode", "Description", "LocationCode", "LocationId", "PrinterCode"}),
      #"Renamed Columns" = Table.RenameColumns(#"Converted to Table", {{"ActiveBusinessDays", "Active Business Days"}, {"AllowTransfers", "Allows Transfers"}, {"BranchCode", "Branch Code"}, {"Description", "Location Description"}, {"LocationCode", "Location Code"}, {"LocationId", "Location ID"}, {"PrinterCode", "Printer Code"}}),
      #"Fixed Types" = Table.TransformColumnTypes(#"Renamed Columns", {{"Active Business Days", type text}, {"Allows Transfers", type logical}, {"Branch Code", type text}, {"Location Description", type text}, {"Location Code", type text}, {"Location ID", type text}, {"Printer Code", type text}})
    in
      #"Fixed Types"
    • v-lionel-msft's avatar
      v-lionel-msft
      Community Support
      6 years ago

      AnthonyMCUBI ,

       

      This is very strange, I checked your code carefully and found no errors.

      What is your data source? SQL Server?

       

      Best regards,
      Lionel Chen

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

      • AnthonyMCUBI's avatar
        AnthonyMCUBI
        Frequent Visitor
        6 years ago

        Sorry for the late reply, I figured out the issue.

         

        Power BI recently, apparently had an update to how it connects to SQL CLR databases.  0-length passwords used to be allowed but now are not. I had to change my password from nothing to something in SSMS and then update my password in power bi connection settings. Everything worked fine after that.

         

        I should note that there was no error with my nothing-password until I erased it and put nothing as my password again, which was not allowed and I was asked to input a password. That's why it took awhile to track down.