March 16, 2005 at 8:53 am
I have errors while running SQLH2 tool for remote servers. On local servers it runs fine. When the same server monitored remotely - I have this errors. SQLH2 is patched - current version 2.0.24.0. WMI provider for SQL intalled on this servers. Any ideas?
3/16/2005 8:27:00 AM Status: Initializing Target: SQL-1-SRV
3/16/2005 8:27:00 AM Status: registering Server
3/16/2005 8:27:00 AM INFO: srv_id = 3; signature = dad3c401-077d-4ab8-8c21-2876d7833bb0
3/16/2005 8:27:00 AM Status: Scanning Registry on SQL-1-SRV
3/16/2005 8:27:00 AM Status: registering instance SQL-1-SRV
3/16/2005 8:27:00 AM INFO: inst_id = 1
3/16/2005 8:27:00 AM INFO: version: 8.00.818
3/16/2005 8:27:00 AM Status: RUN
3/16/2005 8:27:00 AM Status: Initializing collector: WMI
3/16/2005 8:27:00 AM Status: Running WMI collector
3/16/2005 8:27:00 AM Status: Opening Unit 1 (OS/CS)
3/16/2005 8:27:00 AM Status: Collecting Win32_OperatingSystem
3/16/2005 8:27:00 AM Status: Collecting Win32_ComputerSystem
3/16/2005 8:27:00 AM Status: Collecting Win32_Processor
3/16/2005 8:27:04 AM Status: Closing Unit 1
3/16/2005 8:27:04 AM Status: Opening Unit 2 (NIC)
3/16/2005 8:27:04 AM Status: Collecting Win32_NetworkAdapter
3/16/2005 8:27:05 AM Status: Collecting Win32_NetworkAdapterConfiguration
3/16/2005 8:27:05 AM Status: Closing Unit 2
3/16/2005 8:27:05 AM Status: Opening Unit 3 (Disk)
3/16/2005 8:27:05 AM Status: Collecting Win32_DiskDrive
3/16/2005 8:27:05 AM Status: Closing Unit 3
3/16/2005 8:27:05 AM Status: Opening Unit 4 (QFEs)
3/16/2005 8:27:05 AM Status: Collecting QFE registry
3/16/2005 8:27:05 AM ERROR: String or binary data would be truncated.
The statement has been terminated.
3/16/2005 8:27:05 AM ERROR: Exec dbo.spri_qfe @run_id=2, @srv_id=3, @component='Shavlik', @rkey='Shavlik\17389252c89901ea08ec5d1f859e9fa74018c7245aaf273dd1b876093fd0d8881b8b1f7b3f189a66', @HotFixID='bf4ab4da0978f3b7f96e9b0f5f9c0704826be8fc4d764f8d3c8aeaeb17516be0a646a9fb68ed5db792434ccc28245772fe362a858a90be3d', @ServicePack='17389252c89901ea08ec5d1f859e9fa74018c7245aaf273dd1b876093fd0d8881b8b1f7b3f189a66'
3/16/2005 8:27:05 AM WARNING: WMI Collector encountered critical error. Abandoning Collector.
3/16/2005 8:27:05 AM ERROR: Exec dbo.spri_qfe @run_id=2, @srv_id=3, @component='Shavlik', @rkey='Shavlik\17389252c89901ea08ec5d1f859e9fa74018c7245aaf273dd1b876093fd0d8881b8b1f7b3f189a66', @HotFixID='bf4ab4da0978f3b7f96e9b0f5f9c0704826be8fc4d764f8d3c8aeaeb17516be0a646a9fb68ed5db792434ccc28245772fe362a858a90be3d', @ServicePack='17389252c89901ea08ec5d1f859e9fa74018c7245aaf273dd1b876093fd0d8881b8b1f7b3f189a66'
3/16/2005 8:27:05 AM ERROR: SQL-1-SRV: Collection failed; Error:104; Provider Error: 8152
3/16/2005 8:27:05 AM ERROR: Critical Repository Failure
3/16/2005 8:27:05 AM SQLH2 is shutting down
3/16/2005 8:27:05 AM Closing Log
March 16, 2005 at 3:31 pm
Is "SQL-1-SRV" the name of your server? Could be part of the problem, I've heard of people having problems with different tools when they have "-" in the server name.
Other than that, send an email to sqlh2@microsoft.com
--------------------
Colt 45 - the original point and click interface
March 16, 2005 at 5:46 pm
Yes, this is server name. But this does not look like error's source. It runs withour errors localy on the same server. I guess, error is because of this procedure (may be this component 'Shavlik'):
Exec dbo.spri_qfe @run_id=2, @srv_id=3, @component='Shavlik' ...
I'll send my question to sqlh2@microsoft.com . Thank you.
March 18, 2005 at 5:13 pm
This is known issue
Please run the following script against your Repository DB
ALTER table dc_qfe ALTER COLUMN HotFixID nvarchar(128)
March 18, 2005 at 5:36 pm
Thanks Grigory
Will a new version of SQLH@ be getting released before the SQL Server 2005 release?
--------------------
Colt 45 - the original point and click interface
March 21, 2005 at 11:33 am
I can't really answer that question.
There are discussions going on regarding our plans. I think it will get clearer within a month or two.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply