Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
7 years ago
Solved

Unexpected error occured in streaming dataset

Hello, since monday we are experiencing issues with streaming datasets in one of our workspaces. We got two workspaces, each contains ~10 streaming datasets and all of the datasets and reports based on are working in one workspace and they fail in the other workspace. 

 

When I try to load report containing those datasources, it looks like that: 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Error message below: 

Activity ID bb810cd5-a13f-414b-8d1c-2889899f39bf
Request ID f715e61f-5fdf-48f1-f317-6324152d144d
Correlation ID bb7bf330-5b42-e233-8a06-bcbaa56e4f12
Time Fri Nov 23 2018 10:49:59 GMT+0100 (Central European Standard Time)
Version 13.0.7382.168
Cluster URI https://wabi-north-europe-redirect.analysis.windows.net
 
 
Powershell scripts that are used to push data into Power BI are failing from time to time - usually we get Internal Server Error 500 in response or it's just timeouting. I havent managed to load even a single tile that's using streaming dataset from this particular workspace since day before yesterday. 
 
Need Help
  • v-jiascu-msft's avatar
    v-jiascu-msft
    7 years ago

    Hi Anonymous,

     

    The best solution for such unexpected error could be filing a support ticket here.

    What I can find from the log database is that something related to storage doesn't exist. So the workaround could be rebuilding them.

    create-ATicket

     

     

    Best Regards,
    Dale

2 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable
    7 years ago

    Anonymous I would post this to the issues section, or submit a support ticket.

    issues.powerbi.com for the issues.

  • v-jiascu-msft's avatar
    v-jiascu-msft
    Icon for Microsoft Employee rankMicrosoft Employee
    7 years ago

    Hi Anonymous,

     

    The best solution for such unexpected error could be filing a support ticket here.

    What I can find from the log database is that something related to storage doesn't exist. So the workaround could be rebuilding them.

    create-ATicket

     

     

    Best Regards,
    Dale