Get Free Trial
Get Free Trial

Error during DiscoverDimensions step, no info, completely unable to troubleshoot

Answered
Jeramy Couts asked on September 26, 2019

We are currently using the Flexmonster Accelerator as a DLL on our server. Although everything had been working fine for some time, suddenly we are getting a nondescript error during the request to /DiscoverDimensions. Handshaking works fine and nothing is visible in the server logs.
 
The error simply says:
MessageAn error has occurred.
 
Since we cannot override the DiscoverDimensions step, and there is no additional information, I’m completely unsure of where to go from here. We are using Analysis Services and I have verified that everything is working fine with our cube. It’s accessible from every other source. How can we continue to debug this issue?
 
Thanks,
Jeramy

5 answers

Public
Ian Sadovy Flexmonster September 27, 2019

Hello Jeramy,
 
Thank you for the question.
In case it was working well before, we can assume that your project is configured properly.
We recommend checking the following:

  • Access to SSAS is open for your back-end project
  • Credentials for connection are valid (not expired, have permissions, etc.)

Also, is there any additional error information if you run the project in debug mode?
 
Regards,
Ian

Public
Jeramy Couts November 19, 2019

Hi Ian,
 
Thanks for getting back to me so quickly. After encountering this error, we shifted our priorities and decided to focus on supporting other services first. Now that we have support for those services in place we’re back around to considering Flexmonster and I’ll be much more responsive on my end as we try to get this resolved.
I can verify that access to SSAS is open and the credentials are valid. Unfortunately, running the project in debug mode doesn’t give any extra info at all. I currently have all Common Language Runtime Exceptions and all Win32 Exceptions enabled for breaking if they are encountered.
What can we try next?
 
Thanks,
Jeramy

Public
Ian Sadovy Flexmonster November 20, 2019

Hello Jeramy,
 
Thank you for the details.
My best guess is that the issue is connected to the project dependencies.
Since you are using Flexmonster.Accelerator DLL, the required dependencies should be added to your project and match appropriate versions.
At first, we recommend cloning the sample project from https://github.com/flexmonster/pivot-accelerator-dll, setting your connection string in the App_Start/FlexmonsterConfig and checking that it works.
Then, you need to check the NuGet dependencies and their versions in your project. 
Please pay attention to the following dependencies:

  • id=”Flexmonster.Accelerator” version=”2.7.19″
  • id=”Microsoft.AnalysisServices.AdomdClient.retail.amd64″ version=”18.2.3″
  • id=”Microsoft.AnalysisServices.retail.amd64″ version=”18.2.3″
  • id=”Newtonsoft.Json” version=”12.0.1″

Please let us know the results to move forward.
 
Regards,
Ian

Public
Jeramy Couts November 20, 2019

Hi Ian,
 
Thanks for this. It pointed me in the right direction and I managed to figure out what was going wrong. Turns out we had a problem in our security setup that was preventing NuGet from updating properly. It thought it had the latest version of everything due to being unable to reach out to everywhere that it needed to.
Flexmonster.Accelerator was at version 2.7.19, though, which was actually the cause of all of this trouble. We were forced to update due to an error that said our current Accelerator version was “incompatible”. After the update, everything silently broke, with no complaints about versions or dependencies from Flexmonster. Just the “An error has occurred” message. Is there anything I missed during debugging? A way that I could have known that dependencies were the issue? I’m worried that we’ll end up in a situation again in the future where we get a generic error message like this and have our clients waiting for multiple days while we get it sorted out.
 
Thanks,
Jeramy

Public
Ian Sadovy Flexmonster November 22, 2019

Hello Jeramy,
 
We are glad to hear that you managed to figure out what was the cause of the issue.
As for the possible steps to prevent similar issues from happening, it seems we can explicitly set the dependencies and their version inside the Flexmonster.Accelerator NuGet packages. We need some time to research that further, so we will update you about the results after the next minor release (ETA Dec 16).
I hope it helps.
 
Regards,
Ian

Please login or Register to Submit Answer