Hello,I am using version 12.1.20121.2002 of the WPF DV controls.I have a pivot grid and data selector attached to an XMLADataSource with MSMDPump.DLL. I use credentials to establish the connection to an SSAS. The connection returns databases/cubes based on the credentials. Some of the cubes contain 150 dimensions or more (referred to as large cube). I monitor all the XMLADataSource “Completed” events such as “LoadSchemaCompleted”, “LoadCubesCompleted”, etc. Once the connection is established, the databases are always correctly returned and made available for selection in the data selector. Then, selecting a database always correctly returns its cubes and displays them in the data selector correctly as well.Now, and this happens sporadically, selecting a large cube then will not always load its measure groups and dimensions. The last event I can monitor is the”LoadMeasuresCompleted” event. Its “AsyncCompletedEventArgs” does not contain any errors. The data source does not raise any further “PropertyChange” notifications in its “Processing” property. I have to go back to the data selector and select another cube, and then, loading of measures/measure groups/dimensions usually works. After an initial successful loading of the data, it seems that the problem does not reoccur. Selecting back the original cube then correctly loads its data.
I also need to mention does this happens with large cubes only. If I initially load a small cube, things work. Switching to a large cube then, things work as well.It seems related to a strange timing issue. I really need your help to track this down.Thanks,Frank
Hello Frank,
I have been looking into your description and as detailed as it is we haven’t seem to have encountered a similar behavior. This does sound like a timing issue of some sort however in order to investigate it and look for a solution we would need to reproduce it on our side. This would probably require a your data source. Before that though we can check your environment and see if there is anything we haven’t tested against. Please describe in more details what are you using and also if you can think of anything else that is specific for your project please let us know.
Looking forward to hearing from you.
Hi Petar,thanks a lot for your response. It definitely is a difficult one to track down, I still have no idea how I could narrow down the problem. I have meanwhile installed the SSAS databases and cubes on a local server located in our LAN. Even connecting to large cubes then will not generate the problem.I also created a standalone, simple solution by just putting the naked DataSelector to a window, and connecting it to the remote server. The problem is back and I still don't see why. After connecting the DataSelector the databases are correctly loaded. I select a database with a large cube, the cubes are correctly loaded. Then I select a large cube and nothing happens, the dimensions are not returned, the call gets lost in outer space. Is there anything I could to actively trigger an update of the data source, once a cube got selected? Btw, I use a server URI like this: http://www.server.com:8090/olap/msmdpump.dll. Could there be an issue with the port configuration?I will ask my customer if I am allowed to grant you access to the server. I agree that this is the only way for you to be able to investigate the problem. Since I am definitely not allowed to share any information or data via a forum, I would like to kindly ask you to send me a contact where I could supply the information necessary.Thanks, Frank
Hi Frank,
Could you get LoadDimensionsCompleted event notifications of the data source and check the state of AsyncCompletedEventArgs.Error property. This event is fired when we have all of the information about the dimensions, hierarchies and levels loaded or when we have an error during retrieving of that information. I guess the Error property will contain some exception details that can give a hint what's wrong.
Thanks.Plamen.
Hi Plamen
As I previously wrote the last event occurring is the LoadMeasuresEvent and this one does not contain any errors. The LoadDimensionsEvent is not fired at all, including the LoadMeasureGroupsCompleted event.
Frank
I have been looking into this and usually if there is some issue with our request/response logic there should be an exception to verify that. I can suggest checking out your project to see if there is something to shut out such an error. If this isn’t the case I can suggest using Fiddler or another equivalent tool to see if it can shed some light on the origin of this behavior.