Parameter query failed
Updated: 21 May 2010 | 6 comments
This issue has been solved. See solution.
When I try to run microsoft compliance and vulnerability reports I get an error saying: parameter query failed. Other reports work in patch management but not these. We are running patch management 6.2.3644
discussion Filed Under:
Comments
Just making sure you have loaded the updated stored procedures listed here: https://kb.altiris.com/article.asp?article=34527&p=1
Jim Harings
HP Enterprise Services
1st Rule of Connect Club: Mark the post that helped you the most as a 'solution'. 2nd Rule of Connect Club:You must talk about Connect club.
Yes I had run the compliance and vulnerability by computer script and it didn't fix it. I just ran the other two and it still isn't working after restarting the services.
Try running the following against your Altiris database (in Query Analyzer or whatever the tool is in SQL 2005). These are the parameter queries that the C&V report runs to generate the drop-down menus:
exec spPMWindows_MicrosoftSeverityNames @pCulture = 'en-US'
exec spPMCore_CustomSeverityNames @pCulture = 'en-US'
Actually both of these substitute the browser's reported regional settings, so if you have an alternate language set as default in IE, it might fail if the @pCulture variable isn't matching up with one that is recognized. You can modify these in Tools > Internet Options > Languages in IE. What is the top item in your list (if not [en-us])?
Thanks,
Kyle
Symantec Trusted Advisor
For Forum threads, please click "Mark as Solution" if answered.
For all content, please give a thumbs up if you agree with or support the post.
That didn't do it but as I did some searching through the queries that the reports run I found that there are several stored procedures missing. Has anybody else run into this problem before? These reports used to run fine. I wish I could say at what point they stopped but I can't. We did update patch a while ago but I am not sure if that is when the problem started or not. At some point either stored procedures were deleted or the queries were changed to include stored procedures that never existed.
A failed or problematic upgrade would do it. Try starting here:https://kb.altiris.com/article.asp?article=31628&p=1
Also make sure you are either logged onto the server, or at the very least using a Session 0 console session, preferably with the Application ID (Altiris) account.
Jim Harings
HP Enterprise Services
1st Rule of Connect Club: Mark the post that helped you the most as a 'solution'. 2nd Rule of Connect Club:You must talk about Connect club.
Running a repair on the reports patch solved the problem. Thanks!
Would you like to reply?
Login or Register to post your comment.