FIX: After Upgrade to OLAP SP2 Reconnection to Server May Cause "Cannot save object in DSO" Error Message

Article translations Article translations
Article ID: 274701 - View products that this article applies to.
This article was previously published under Q274701
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 8300 (PLATO_7x)
Expand all | Collapse all


After you upgrade to Microsoft OLAP Service Pack 2 (SP2) and you attempt to connect to the server, the following error message may occur:
Cannot save object in DSO.


To make the repository locale independent, during the installation process OLAP opens all objects such as cubes and dimensions and saves them back to the repository. However, in OLAP Service Pack 2 (SP2), if the save fails an error message does not occur. Thus, it appears that everything was saved properly when it was not. Consequently, OLAP SP2 leaves the repository in an inconsistent state.


To work around this bug, open all the cubes and partitions, and then save them.


Microsoft has confirmed this to be a problem in SQL Server OLAP Services version 7.0. This problem has been corrected in U.S. Service Pack 3 for Microsoft SQL Server OLAP Services version 7.0. For information about how to download and install the latest SQL Server OLAP Services Service Pack, see the following Microsoft Web site:
For more information, contact your primary support provider.


This bug is fixed in Microsoft OLAP Service Pack 3 (SP3).


Article ID: 274701 - Last Review: February 28, 2014 - Revision: 4.1
  • Microsoft SQL Server OLAP Services
kbnosurvey kbarchive kbbug kbfix kbolap700sp3fix KB274701

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from