We're attempting to stablise some WebStandard users, who've created their own views in "My Views". The reports have dimensional specific picks, which can disappear over time. When this happens, of course the reports break and have to run through the Missing Data Wizard.

Sets on the other hand, don't track the individual picks to the same degree. Ideally, the set would simply be submitted, and MSAS 2005 would simply ignore the missing items (default behavior).

However, it seems like ProClarity forces the connectionm to <MdxMissingmemberMode>Error</MdxMissingmemberMode>. Most likely, this is to force a compatibility mode back to MSAS 2000.

This setting causes the MDX to "break" (issue an error), when what I really need is for it to simply leave the default alone.

Does anyone know how to change the connection information for ProClarity, so that it doesn't set this value?

You are correct, this setting is enforced to maintain compatibility with AS 2000.

Here's a thread on how to set connection string properties in ProClarity.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2248945&SiteID=1

Let us know if you continue to run into problems.

Ben,

I am currently using the connection string Timeout property to set the query timeout value and that works well.

I created a new string registry item for the MdxMissingMemberMode:

Entry Type: Sting Value

Value Name:MdxMissingMemberMode

Value Data: Ignore

Unfortunately the query stillsets the value to Error (<MdxMissingMemberMode>Error</MdxMissingMemberMode>)

ShouldI have to restart the server or should an IIS reset be sufficient?I am testing this using Proclarity Professional.

Just to be clear, you're making the registry changes on your client machine and then testing with the ProClarity Pro on that same machine, correct? I want to be sure you aren't making the registry changes on the machine hosting PAS if you're using a Pro client, as that client will initiate the connection to the cube directly from your client machine.

Once you're sure you're making the change on the correct machine, this entry should do it for you.

[HKEY_LOCAL_MACHINE\SOFTWARE\ProClarity Corporation\Server\Properties]
"MDX Missing Member Mode"="Ignore"

Thanks Ben. That worked. It required spaces. "MDX Missing Member Mode"="Ignore" not "MDXMissingMemberMode"="Ignore"

Thanks for the fix, four years later and it still comes handy. I have encountered the "MDX Missing Member" issue today using "ProClarity Desktop Professional". Please note the entry does not exist in the registry, which may be a bit confusing at the first; but once added works like a dream. 

Thanks again,