A member-level permission that includes identity-driven values might cause an abend of the SAS Metadata Server when resolved. This problem might occur if the resolved permission condition exceeds 512 characters. Following is an example of a permission condition that exceeds 512 characters:

Filter([Org].[Org].[Company].members, [Org].[Org].currentmember.name = "SUB::SAS.PersonName")
+
Filter([Org].[Org].[Company].members, [Org].[Org].currentmember.name = "SUB::SAS.PersonName")

Filter([Org].[Personnel].[Company].members, [Org].[Personnel].currentmember.name = "SUB::SAS.PersonName")
+
Filter([Org].[Personnel].[Company].members, [Org].[Personnel].currentmember.name = "SUB::SAS.PersonName")
+
Filter([Org].[Personnel].[Company].members, [Org].[Personnel].currentmember.name = "SUB::SAS.PersonName")

Symptoms of this problem include unresponsive connections through your SAS client applications and error traces in the SAS Metadata Server log. Restarting the SAS Metadata Server and dependent SAS processes is the only resolution.

To avoid the problem, decrease the length of the condition so that the resolved version does not exceed 512 characters.

Click the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

A fix for this issue for Base SAS 9.21_M1 is available at:

A fix for this issue for Base SAS 9.21_M3 is available at: