Excel 多成员mdx查询返回错误（访问指定成员的权限）

我想说的是，我是SSAS和MDX的新手

在过去的几天里，我一直在处理一个excel生成的查询，结果出错了

问题在于，当试图从联机多维数据集数据源读取数据时，excel会生成查询，从而阻止对该多维数据集的其他读取。查询是针对AZURE多维数据集执行的，我设法对其进行分析并获得以下查询：

with set __XLUniqueNames as {[Stores].[Chain].[Chain].&[SuperBrugsen], [Stores].[Chain].[Chain].&[Salling], [Stores].[Chain].[Chain].&[SuperBrugsen] } 
set __XLDrilledUp as 
Generate(__XLUniqueNames, 
{ IIF([Stores].[Chain].currentmember.LEVEL_NUMBER <= 2147483647, 
    [Stores].[Chain].currentmember, 
    Ancestor([Stores].[Chain].currentmember, 
            [Stores].[Chain].currentmember.LEVEL_NUMBER - 2147483647)) } ) 
member [Measures].__XLPath as 
Generate( 
    Ascendants([Stores].[Chain].currentmember), 
                [Stores].[Chain].currentmember.unique_name, 
                "__XLPSEP") 
select { [Measures].__XLPath } on 0, 
__XLDrilledUp on 1 
from [SomeCube] 
cell properties value

将uuxluniquenames设置为{[Stores].[Chain].[Chain].&[SuperBrugsen]，[Stores].[Chain].[Chain].[Salling]，[Stores].[Chain].[SuperBrugsen]}
将uuu XLDrilledUp设置为
生成（uuxluniquenames，
{IIF（[Stores].[Chain].currentmember.LEVEL_NUMBER问题似乎自行解决。很可能是某个更新解决了此问题。请参阅azure更新日志页面：
Excel用于查找多维数据集的连接字符串中是否有任何线索？这可能会施加安全限制，或设置其他干扰的首选项。@MagnusSmith I研究了连接字符串并尝试在没有任何运气的情况下修改参数。下面是一个示例：
Provider=MSOLAP.8；Persist Security Info=True；Initial Catalog=SomeCatalog；Data Source=AddressToServer；MDX Compatibility=1；Safety Options=1；MDX Missing Member Mode=Error；Update Isolation Level=2
我在该c中看不到任何关于“角色”的信息连接字符串，所以它应该是好的。对不起，我没有其他想法。
<PropertyList xmlns="urn:schemas-microsoft-com:xml-analysis">
        <Catalog>SomeCatalog</Catalog>
        <ShowHiddenCubes>true</ShowHiddenCubes>
        <SspropInitAppName>Microsoft SQL Server Management Studio</SspropInitAppName>
        <Timeout>3600</Timeout>
        <LocaleIdentifier>1033</LocaleIdentifier>
        <ClientProcessID>24400</ClientProcessID>
        <DataSourceInfo/>
        <Format>Tabular</Format>
        <Content>Schema</Content>
        <DbpropMsmdFlattened2>true</DbpropMsmdFlattened2>
        <ReturnCellProperties>true</ReturnCellProperties>
        <DbpropMsmdActivityID>2309dfa2-3607-41b2-9446-8ece2f5ababa</DbpropMsmdActivityID>
        <DbpropMsmdCurrentActivityID>2309dfa2-3607-41b2-9446-8ece2f5ababa</DbpropMsmdCurrentActivityID>
        <DbpropMsmdRequestID>d3dbd079-5ca7-496c-ab55-afea71889238</DbpropMsmdRequestID>
</PropertyList>

<PropertyList xmlns="urn:schemas-microsoft-com:xml-analysis">
        <Catalog>SomeCatalog</Catalog>
        <SspropInitAppName>Microsoft SQL Server Management Studio - Query</SspropInitAppName>
        <LocaleIdentifier>1033</LocaleIdentifier>
        <ClientProcessID>24400</ClientProcessID>
        <DataSourceInfo/>
        <Format>Native</Format>
        <AxisFormat>TupleFormat</AxisFormat>
        <Content>SchemaData</Content>
        <Timeout>0</Timeout>
        <DbpropMsmdActivityID>e5e75ad6-8fca-4f25-abba-047f86198602</DbpropMsmdActivityID>
        <DbpropMsmdCurrentActivityID>e5e75ad6-8fca-4f25-abba-047f86198602</DbpropMsmdCurrentActivityID>
        <DbpropMsmdRequestID>8901787f-15a7-48a0-86eb-18ff0b92bdc4</DbpropMsmdRequestID>
</PropertyList>

<PropertyList xmlns="urn:schemas-microsoft-com:xml-analysis" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
    <Catalog>SomeCatalog</Catalog>
    <Timeout>0</Timeout>
    <Format>Native</Format>
    <DbpropMsmdFlattened2>false</DbpropMsmdFlattened2>
    <SafetyOptions>2</SafetyOptions>
    <Dialect>MDX</Dialect>
    <MdxMissingMemberMode>Error</MdxMissingMemberMode>
    <DbpropMsmdOptimizeResponse>9</DbpropMsmdOptimizeResponse>
    <DbpropMsmdActivityID>9D69640F-553A-4970-BD4E-7234F1CD928C</DbpropMsmdActivityID>
    <DbpropMsmdRequestID>B5E10FF0-EF2F-409E-83BF-CD2DBA20C2BE</DbpropMsmdRequestID>
    <LocaleIdentifier>1030</LocaleIdentifier>
    <DbpropMsmdMDXCompatibility>1</DbpropMsmdMDXCompatibility>
</PropertyList>