Microsoft KB Archive/914824

= The MSSLogToDatabase tool does not recognize a SQL Server 2005 Reporting Services host in Microsoft Speech Server 2004 =

Article ID: 914824

Article Last Modified on 5/5/2006

-

APPLIES TO


 * Microsoft Speech Server 2004 Standard Edition
 * Microsoft Speech Server 2004 R2 Standard Edition
 * Microsoft Speech Server 2004 Enterprise Edition
 * Microsoft Speech Server 2004 R2 Enterprise Edition

-





SYMPTOMS
When you use the MSSLogToDatabase tool (MSSLogToDatabase.exe) to import Microsoft Speech Server (MSS) 2004 log data into a reporting database, the MSSLogToDatabase tool does not recognize a Microsoft SQL Server 2005 Reporting Services host.



CAUSE
This problem occurs because the Microsoft Windows Management Instrumentation (WMI) interface for SQL Server 2005 Reporting Services differs from the WMI interface for SQL Server 2000 Reporting Services. The MSSLogToDatabase tool examines the VirtualRoot property of the Reporting Services host WMI interface. Therefore, you cannot use the MSSLogToDatabase tool together with a SQL Server 2005 Reporting Services host unless you follow the steps in the &quot;Workaround&quot; section.



WORKAROUND
To work around this problem, create a static instance of the SQL Server 2000 Reporting Services WMI namespace on the computer that is running SQL Server 2005 Reporting Services.

Note This workaround does not affect the SQL Server 2005 Reporting Services installation.

To do this, follow these steps:   On the computer that is running SQL Server 2005 Reporting Services, create a text file that contains the following code.
 * 1) pragma namespace(&quot;\\\\.\\root\\Microsoft&quot;)

instance of __Namespace {   Name = &quot;SqlServer&quot;; };


 * 1) pragma namespace(&quot;\\\\.\\root\\Microsoft\\SqlServer&quot;)

instance of __Namespace {   Name = &quot;ReportingServices&quot;; };


 * 1) pragma namespace(&quot;\\\\.\\root\\Microsoft\\SqlServer\\ReportingServices&quot;)

instance of __Namespace {   Name = &quot;v8&quot;; };


 * 1) pragma namespace(&quot;\\\\.\\root\\Microsoft\\SqlServer\\ReportingServices\\v8&quot;)

class MSReportServer_ConfigurationSetting {   [key] string VirtualRoot; };

instance of MSReportServer_ConfigurationSetting {   VirtualRoot = &quot;http://localhost/reportserver&quot;; };  Save this file as the C:\CreateSql2000RS.mof file. Click Start, click Run, type the following command, and then click OK:

Mofcomp C:\CreateSql2000RS.mof

Note The MSSLogToDatabase tool works as expected.

Removal
When you no longer want to use the MSSLogToDatabase tool to import MSS 2004 log data, you may want to delete the instance of the WMI namespace that you created in this workaround. To do this, follow these steps on the computer that is running SQL Server 2005 Reporting Services:   Create a text file that contains the following code. Save this file as the C:\DeleteSql2000RS.mof file. Click Start, click Run, type the following command, and then click OK:
 * 1) pragma namespace(&quot;\\\\.\\root\\Microsoft\\SqlServer\\ReportingServices&quot;)
 * 2) pragma deleteinstance(&quot;__Namespace='V8'&quot;, NOFAIL) </li>

Mofcomp C:\DeleteSql2000RS.mof

</li></ol>

Note Do not follow these steps if a valid instance of SQL Server 2000 Reporting Services is present on the computer.

<div class="moreinformation_section">

MORE INFORMATION
This problem or similar problems do not occur when you migrate a MSS 2004 Data Transformation Services (DTS) package to SQL Server 2005. Additionally, the MSSLogToDatabase tool can create the Call Viewer database on a server that is running SQL Server 2005 without encountering this problem or similar problems.

Keywords: kbprb KB914824

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.