Issue when using XMLA endpoint for my dataset

[GeorgeVepkhvadz]

I have problem when I try to connect to analysis service throught xmla endpoint for my workspace. 

It connects and I can see the list of datasets, I can even check tables in there, but if I want to open specific partition of table, or even proceess anything, this is the error I am given: 

TITLE: Microsoft SQL Server Management Studio
------------------------------

The operation failed on Model because the model couldn't be found. Try refreshing the entire database or server instead. (Microsoft.AnalysisServices.NodeContextServices)

------------------------------
ADDITIONAL INFORMATION:

Object reference not set to an instance of an object. (Microsoft.AnalysisServices.NodeContextServices)

------------------------------
BUTTONS:

OK
------------------------------

[Anonymous]

hi, @GeorgeVepkhvadz 

I'm happy to answer your questions. I'm sorry to hear that you're encountering an error message while trying to open a specific partition of a table in Microsoft SQL Server Management Studio. Is there a button as shown in the screenshot below on the error page:

Click it to view more detailed error information.

You can also check whether there are errors in the semantic model from the following aspects, causing the model couldn't be found error.

1. Check whether you have permission to access the semantic model
2. Try to republish the semantic model to this workspace and connect it again to see if the same error will still be reported.
3. Check whether other models in the same workspace have this error, to determine whether it is a problem in the workspace.

How to Get Your Question Answered Quickly

If it does not help, please provide more details with your desired output and pbix file without privacy information (or some sample data) .

Best Regards

Jianpeng Li

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

[GeorgeVepkhvadz]

This is the message, I tried to republish it, and same error persists, I think it is dataset issue, as I didn't receive similar message for other dataset on same workspace. 

[Anonymous]

Hi, @GeorgeVepkhvadz 

I submitted a solution in the post, and I’m wondering if it was helpful to you. Could you please provide some feedback on my solution?

[Anonymous]

Hi, @GeorgeVepkhvadz 

Thank you very much for your reply. According to the error message, I noticed two points:

1.The operation failed on Model because the model couldn't be found.

2.Object reference not set to an instance of an object

These two error messages state:

1. Model not found. This may be caused by an incorrect model name, or a model being moved or deleted.
2. The object reference is not set to an object instance. This indicates that when you are trying to access or operate a partition or model, the related object or component was not initialized successfully.

You can try the following steps to resolve the issue:

1. Check the model’s name and the names of any tables in the model to ensure that the model you are trying to connect to, and its related information exist in Power BI.
2. Refresh the entire database. Try refreshing all data related to the model as well as the database. This ensures that all models, partitions, and other components are up to date.
3. Check the connection string. Make sure your XMLA connection string is correct and that you have sufficient permissions to access and manipulate the dataset.
4. Try to check the relationship between models in Power BI Desktop. In the case of backup, try to delete the relationship between models and then publish it to the Service. This way you can check whether there is an error in the table relationship.

Hope the above suggestions can help you.

How to Get Your Question Answered Quickly

If it does not help, please provide more details with your desired output and pbix file without privacy information (or some sample data) .

Best Regards

Jianpeng Li

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

[GeorgeVepkhvadz]

Thanks for the reply:
1. Name of model and tables matches.
2. I tried refresh, it is not solving my issue.
3. connection string is fine, as I can actually see the model and all tables, I just can't process them or check the partitions.
4. Do you mean relationship in model between tables? This one I have not tried yet. Will check and let you know. (It should be fine, if I do the changes via ALM toolkit, instead of republishing and refreshing whole model right? As it is over 30gb

[GeorgeVepkhvadz]

Hi, Thanks for the reply. I have read write function enabled, in fact in the past I was able to do open it up.
Then when I used dynamic formatting I think there was compatability issues, so I would get read of dynamic formatting to refresh the partitions and then would add them back on. 

But now the error message is different. My dataset got quite complex, and I have issue that Power BI premium is throttiling the refresh. So I want to refresh partitions. 

[TomMartens]

Hey @GeorgeVepkhvadz ,

I assume that the workspace you are connecting to is assigned to a capacity that support the XMLA endpoint.

Check if the XMLA feature is enabled for Read/Write operations as in the one below (Premium Per User workloads in the Admin Portal):

For all others capacity types you will find this setting in the Capacity settings in the Admin portal.

Hopefully, this helps to tackle your challenge.

Regards,

Tom