Forum Discussion
November(2017) update cannot connect to data model
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
I'd already popped in a support request before seeing this thread and responses so far have been to suggest the workaround identified above, so it would appear that news of this issue has propagated through various channels.
I'm personally finding this workaround a bit hit and miss, depending on the workspace my data models are deployed to - sometimes I can re-point/save/exit/reload without prolems and on some occassions it's managed to completely corrupt my report, although I can sometimes salvage thi sis I publish my model to a different workspace and repeat the workaround. I need to do a little more testing around this scenario and see if I can identify a bit more.
With the Nov update not being particularly eventful in terms of changes I need and this particular issue being quite prominent in and dirsuptive to our workflow, I'm planning to downgrade to the Oct release once I've provided some more info to my assigned support person and I'm hoping that this one doesn't hang around for too long...
The admins over on the issues forum have confirmed this as an issue and have logged it internally with Microsoft. Hopefully a fix comes soon.