Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
8 years ago
Solved

November(2017) update cannot connect to data model

Hi,   Since updating desktop to the latest version as of 11/9/2017 I tried to switch data source of one my reports to a test version of the same model. This process has worked well before. However ...
Need Help
  • Anonymous's avatar
    Anonymous
    8 years ago

    Hello,

     

    I have also experienced this issue when changing data connections after installing the November update. I copied the error and it is very ambiguous

     

    Error Details:
    An exception of type System.InvalidOperationException occured.

     

    It broke every visual in the desktop file. Interestingly enough, when I published the file with the broken visuals to the service it worked perfectly in the service. I then saved the broken file and reopened it and my visuals started working again.

     

    Hopefully the above is helpful in troubleshooting your issue.

     

    Thanks,

    James

Anonymous's avatar
Anonymous
Not applicable
8 years ago

Hello,

 

I have also experienced this issue when changing data connections after installing the November update. I copied the error and it is very ambiguous

 

Error Details:
An exception of type System.InvalidOperationException occured.

 

It broke every visual in the desktop file. Interestingly enough, when I published the file with the broken visuals to the service it worked perfectly in the service. I then saved the broken file and reopened it and my visuals started working again.

 

Hopefully the above is helpful in troubleshooting your issue.

 

Thanks,

James

  • parry2k's avatar
    parry2k
    Super User
    8 years ago

    I had the same issue when updated SSAS data source , but once I saved the file and reopened it, worked fine. 

  • Anonymous's avatar
    Anonymous
    Not applicable
    8 years ago

    Thanks for the replies guys, that trick with saving and reopening is a useful workaround I'll give it a go. :)

     

    I feel like this issue is a bug of sorts and MS need to be informed but I don't know the proper channels, where's the correct place to raise this issue?

     

    Thanks again,

     

    Will

    • Anonymous's avatar
      Anonymous
      Not applicable
      8 years ago

      Hey Anonymous,

       

      I posted this on the issue forum and linked back to this post. The mods over there are usually pretty good at responding and getting fixes. Microsoft will also tell you to log a support ticket, in my past experience the support ticket team will do everything possible to say the issue is "by design" or that the developer is doing something wrong so that they don't have to work it. If you want to try that path I hope you get a better experience.

       

      James

      • Anonymous's avatar
        Anonymous
        Not applicable
        8 years ago

        Great, thank you very much James. I'll heed your warning and do my best to avoid the classic support circle.

         

        Thanks again,

         

        Will