Article ID: 816480 - Last Review: November 21, 2006 - Revision: 2.3 FIX: Cannot Use User-Defined Functions in Dimension Security Definitions Bug #: 13905 (Plato7x) On This PageSYMPTOMSYou try to use a user-defined function as part
of an MDX expression in the Allowed Members or Denied Members entry for
dimension security in an Analysis Services role. However, when you try to close the Manage Roles dialog box, you may receive the following error message: Some of the cubes could not be updated. Errors: Unable to update role in cube cubename. Error occurred during update of Cube 'cube' on the server: 'Error occurred while processing security for cube 'cube'(Error in the definition of the dimension security for the dimension 'dimension' and role 'role'. Cannot evaluate the expression 'MDX Expression' RESOLUTIONService pack informationTo resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:290211
(http://support.microsoft.com/kb/290211/
)
How to obtain the latest SQL Server 2000 service pack Hotfix informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.Date Time Version Size File name ------------------------------------------------------------ 20-Feb-2003 00:08 8.0.772.0 217,668 Msmdcb80.dll 12-Feb-2003 02:49 8.0.767.0 1,024,576 Msmdgd80.dll 27-Jan-2003 07:47 8.0.0.761 9,638,464 Msmdsgn80.dll 21-Feb-2003 01:36 8.0.773.0 1,827,396 Msmdsrv.exe 17-Feb-2003 21:35 8.0.770.0 2,069,072 Msolap80.dll STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.This problem was first corrected in Microsoft SQL Server 2000 Service Pack 4.
| Article Translations
|
Back to the top
