October 22, 2009 at 11:47 am
After much configuration (and a small edit in the dbo.spri_cpu procedure to default @Name), we are able to get SQLH2.exe to work... but if we try to run it from the Windows Task manager, nothing happens. Removed the task and made it a SQL Server 2008 job... no dice.
Anyone have suggestions as to the task method? Why would it not work?
October 22, 2009 at 12:47 pm
Only thing I can think about is permission. Does the SQL Server service user have sufficient rights?
-Roy
October 22, 2009 at 12:55 pm
Figured it out... running the exe from a job was not picking up the config file... added the /C<config file> and it worked 🙂 Task might have needed that as well.
Thanks!
any idea why i had to edit the dbo.spri_cpu stored procedure to default the @Name parameter to make it work? This was the error I was getting:
10/21/2009 4:40:01 PM Status: Opening Unit 1 (OS/CS)
10/21/2009 4:40:01 PM Status: Collecting Win32_OperatingSystem
10/21/2009 4:40:02 PM Status: Collecting Win32_ComputerSystem
10/21/2009 4:40:02 PM Status: Collecting Win32_Processor
10/21/2009 4:40:04 PM ERROR: Procedure or function 'spri_CPU' expects parameter '@Name', which was not supplied.
10/21/2009 4:40:04 PM Status: Closing Unit 1
10/21/2009 4:40:04 PM ERROR: dbo.spri_CPU
10/21/2009 4:40:04 PM WARNING: WMI Collector encountered critical error. Abandoning Collector.
10/21/2009 4:40:04 PM ERROR: dbo.spri_CPU
10/21/2009 4:40:04 PM ERROR: HOSTINGDB02: Collection failed; Error:StorSyntaxErrorNonQuery; Provider Error: 201
10/21/2009 4:40:04 PM ERROR: Critical Repository Failure
10/21/2009 4:40:04 PM SQLH2 is shutting down
10/21/2009 4:40:04 PM Closing Log
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply