DW SQL 2005 version is 9.0.4053. The error makes me think the minmum SQL version/servicepack/cumulative update hasn't been met.
moter
3 Oct 2011 8:50 PM
3 Oct 2011 8:54 PM
@moter -
I only have SQL 2008R2 running here. Would be very odd if there was something in this report that didnt work on SQL 2005.... I'd bet we will be hearing more about it if that's the case.
moter
3 Oct 2011 9:02 PM
Indeed. Seems to me that most syntax error stuff like what's in the error i posted is usually due to changes between cumulative updates or service packs. 4053 is from a security update in October of 2009. heh, upgrading SQL for scom tough to do?
3 Oct 2011 9:24 PM
Thanks Kevin.
All of our clusters are 2008 R2 Hyper-V clusters. So, with the new cluster discovery feature would we still need the the Windows Cluster MP?
Thanks,
Tom
3 Oct 2011 9:59 PM
@martit01 -
The new MP only discovers and monitors Cluster Share Volumes. The actual Cluster MP does much more - it discovers and monitors entire cluster resources and resource groups. Yes, you'd still need the cluster MP for end-to-end cluster monitoring.
Robb Dilallo
4 Oct 2011 1:19 AM
@moter, I've imported Microsoft.Windows.Server.Reports.mp into 3 different OpsMgr environments, and the only management group that's throwing out the same error as what you're receiving also has SQL 2005 for a DW and SSRS. There's a chance that the reports weren't written for SQL 2005 and / or tested with SQL 2005.
4 Oct 2011 7:51 AM
Hi Kevin
We have a similar error message as it moter describes.
The content of our error message is:
Data Warehouse failed to deploy database component. Failed to deploy Data Warehouse component. The operation will be retried.
Exception 'DeploymentException': Failed to perform Data Warehouse component deployment operation: Install; Component: Script, Id: '8a477b44-6d7b-fef5-beff-b328e34b7400', Management Pack Version-dependent Id: 'b7931af6-807c-4780-9a89-c2543de3ffef'; Target: Database, Server name: 'Server\DB', Database name: 'OperationsManagerDW'. Batch ordinal: 1; Exception: Cannot assign a default value to a local variable.
Must declare the scalar variable "@loop".
Must declare the scalar variable "@loop".
Incorrect syntax near the keyword 'FROM'.
Must declare the scalar variable "@loop".
additional we have the following error message
Data Warehouse failed to deploy database component. Failed to deploy Data Warehouse component. The operation will be retried.
Exception 'DeploymentException': Failed to perform Data Warehouse component deployment operation: Install; Component: Script, Id: '8a477b44-6d7b-fef5-beff-b328e34b7400', Management Pack Version-dependent Id: 'b7931af6-807c-4780-9a89-c2543de3ffef'; Target: Database, Server name: 'Server\DB', Database name: 'OperationsManagerDW'. Batch ordinal: 1; Exception: Cannot assign a default value to a local variable.
Must declare the scalar variable "@loop".
Must declare the scalar variable "@loop".
Incorrect syntax near the keyword 'FROM'.
Must declare the scalar variable "@loop".
Do you have any idea? May you give us some help with it?
Thanks a lot.
4 Oct 2011 8:15 AM
sorry, I have sent 2 times the same error
here is the correct error
Data Warehouse failed to deploy database component. Failed to deploy Data Warehouse component. The operation will be retried.
Exception 'DeploymentException': Failed to perform Data Warehouse component deployment operation: Install; Component: Script, Id: '3a49a530-26a2-c525-35fe-69df5898f150', Management Pack Version-dependent Id: 'f652ee20-fdfd-1cb2-5491-c2cc5fb8daa6'; Target: Database, Server name: 'nvabbst093\SCOMP03', Database name: 'OperationsManagerDW'. Batch ordinal: 1; Exception: Incorrect syntax near the keyword 'with'. If this statement is a common table expression or an xmlnamespaces clause, the previous statement must be terminated with a semicolon.
Incorrect syntax near ','.
Incorrect syntax near ','.
Incorrect syntax near ','.
Incorrect syntax near ','.
Incorrect syntax near the keyword 'ELSE'.
Christopher Keyaert
4 Oct 2011 8:51 AM
Hi Kevin,
I'm also using SQL 2005, and I've got the same error message than Sven and Moter.
Thank you
Regards
Christopher
corwin
4 Oct 2011 8:56 AM
The - Microsoft.Windows.Server.Reports.mp importing without errors. But I can't find new repots in Reporting Panel :(
In what may be the reason ?
Chrizz06
4 Oct 2011 10:26 AM
Hi Kevin,
Same issue here, we are running SQL2005 v 9.0.3042 (SP2 version)
Kind regards
Robb Dilallo
4 Oct 2011 12:48 PM
The new Windows Server Reports that was just released doesn’t seem to work with SQL 2005 Reporting Services. In the header of the report definition in each report, it shows the xmlns of schemas.microsoft.com/.../reportdefinition. It looks as if they were written for SQL 2008 Reporting Services.
4 Oct 2011 1:45 PM
I cannot find the Microsoft.Windows.Server.Reports.mp. I downloaded the msi and extracted but the reports mp isn't in there.. Any ideas?
Kind regards
TiLeCa
4 Oct 2011 5:42 PM
I have the same issue when importing the Microsoft.Windows.Server.Reports.mp
what kind of further investigantions mght help to solve this?
Report Server is running on SQL 2005 EE build 9.0.5057
Robb Dilallo
4 Oct 2011 8:27 PM
@TiLeCa - No further investigation is needed. It doesn't work with SQL 2005 Reporting Services. My recommendation is to post in the OpsMgr Management Pack forum to get some attention on this matter.