Bug: "Dynamic MDX Queries" don't work as described
Mark Landry
I’ve lifted the sample code directly, tried to run it, and it fails.
It’s documented at http://msdn.microsoft.com/en-us/library/ms172589(SQL.90).aspx
The “Analysis Services Event Provider” queries a SQL table, generates
XML output, passes it through an XSLT style sheet, and generates an
MDX query dynamically. Using the documented example, no MDX is created
as seen in the event log error below: (The “MDX Query String” is
blank).
Event Type: Error
Event Source: NotificationServices
Event Category: None
Event ID: 2976
Date: 3/26/2009
Time: 6:59:10 PM
User: N/A
Computer: MyServer
Description:
Description: The AnalysisServicesProvider event provider failed while
running an MDX query. The provider will be terminated.
EventParameters:
Provider Name: TerminalEventNsEventProvider
MDX Query String:
Description: ExecuteReader: CommandText property has not been
initialized
InstanceName: IodNS
ApplicationName: DashboardNotifications
Component: Event collection
Thread: 10
I’ve tried countless variations and “pass-through” XSLT and I can’t
get anything past this point.
Can someone at MS redirect to the SSNS support group?
Mark Landry
Provider’ component of Notification Services 2005.
Bug #1 The documentation describes the following XML :
<rows>
<row Employee="Ken J Snchez" />
<row Employee="Laura F Norman" />
<row Employee="Terry Lee Duffy" />
<row Employee="Gordon L Hee" />
</rows>
<slicers>
<slicer Calendar Time="2002"/>
</slicers>
This is non-standard XML as it doesn’t have a root node. Therefore,
XSLT translations using this code will always fail producing an empty
MDX query.
Bug#2: If the SlicerQuery argument is present (as shown below), even
if it’s value is empty, the Event Provider will add an empty
<slicers></slicers> tag to the xml rendering the result unparse-able
as described above.
<HostedProvider>
<ProviderName>DynamicASEventProvider</ProviderName>
...
<Argument>
<Name>SlicerQuery</Name>
<Value></Value>
</Argument>
...
</Arguments>
</HostedProvider>