Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
9 years ago
Solved

Couldn't load the schema for the database model

Hi,

 

I have a Dashboard under the client administrator account. This works with no problemems. With the Enterprise gateway the data is refreshed from a on-demand SQL Server.

This dashboard i have shared with a lot of people, also outside the organisation. So am i.

 

A few people outside the organisation have the next message:

"Can't load modelschema that is connected to your report. Check the serverconnection and try aggain"

 

The strange thing is that not everybody have this error

 

 

 

Can someone help me whit this?

 

With kind regard, Norbertus

  • Hi Anonymous,

     

    Did the error throw out when free or pro trail users out side of the organization access the dashboard? If that is a case, we have reported the same issue internally. Normally, the free users should get the 'Pro License Required' dialog instead of the error message. I will keep an eye on this issue and update to you if I get any feedback.

     

    Best Regards,
    Qiuyun Yu

4 Replies

  • Phil_Seamark's avatar
    Phil_Seamark
    Icon for Microsoft Employee rankMicrosoft Employee

    Does your model import all the data, or does it use Direct query.

     

    If Direct Query, do all your users have permissions to the onpremise datasource?

    • Anonymous's avatar
      Anonymous
      Not applicable

      the data doesn't load from a direct query.

  • v-qiuyu-msft's avatar
    v-qiuyu-msft
    Icon for Community Support rankCommunity Support

    Hi Anonymous,

     

    Did the error throw out when free or pro trail users out side of the organization access the dashboard? If that is a case, we have reported the same issue internally. Normally, the free users should get the 'Pro License Required' dialog instead of the error message. I will keep an eye on this issue and update to you if I get any feedback.

     

    Best Regards,
    Qiuyun Yu

    • Anonymous's avatar
      Anonymous
      Not applicable

      The issue had still to do with the license type. The user didn't have the pro-license.