looked through the rsreportserver.config files, and they did indeed
include the SQL extension as this points out:
http://blogs.msdn.com/selvar/archive/20 ... erver.aspx
So that wasn't it, yet my test system had always worked. Upon closer
inspection, I noticed that my (non-working) production system had this line
under the SemanticQuery section:
Type="Microsoft.ReportingServices.SemanticQueryEngine.Sql.SqlSQCommand,Microsoft.ReportingServices.SemanticQueryEngine" />
Yet my test system (working) had this line:
Type="Microsoft.ReportingServices.SemanticQueryEngine.Sql.MSSQL.MSSqlSQCommand,Microsoft.ReportingServices.SemanticQueryEngine/">
Note the small differences between the two. It's correct on the blgo entry
above, but incorrect in my file! Since these were not hand-edited, I've no
idea why one is different. My only guess is that the test system was SQL 2005
SP2, then upgraded to SP3. Whereas I had installed SP3 on the production
system before installing SCOM...
Anyway, changing the line to the one that included the "MSSQL.MSSql" seems
to have fixed the problem.
Thnaks you
http://graycloud.com/operations-manager/audit-reports-not-running-odd-entry-rsreportserver-confi-t31479.html
No comments:
Post a Comment