September 8, 2006 at 4:27 am
Hello, i am using windows 2003 (x64) ,SQL 2005 (x64) and try to use SQlH2 for monitoring. In the sqlh2 log I get the following error : No SQL Server instances registered on the box
Part of the log:
9/8/2006 12:05:18 PM
9/8/2006 12:05:18 PM Opening Log
9/8/2006 12:05:18 PM SQLH2 ver. V2 2.0.027.0 10/17/05 16:25
9/8/2006 12:05:18 PM Status: Init
9/8/2006 12:05:18 PM WARNING: There are no PerfProviders in the config file
9/8/2006 12:05:18 PM Status: Initializing repository: hol01sic311\WhatsUp
9/8/2006 12:05:18 PM Status: Repository Database: SQLH2Repository
9/8/2006 12:05:18 PM INFO: host_id = 1
9/8/2006 12:05:18 PM Status: Starting RUN
9/8/2006 12:05:18 PM Status: Registering Run
9/8/2006 12:05:18 PM INFO: run_id = 2
9/8/2006 12:05:18 PM Status: Starting Targets processing
9/8/2006 12:05:18 PM Status: Initializing Target: HOL01SIC311
9/8/2006 12:05:18 PM Status: registering Server
9/8/2006 12:05:18 PM INFO: srv_id = 1; signature = c823555b-df4b-47d4-8363-cdaffb1f4576
9/8/2006 12:05:18 PM Status: Scanning Registry on HOL01SIC311
9/8/2006 12:05:18 PM WARNING: No SQL Server instances registered on the box
9/8/2006 12:05:18 PM Status: RUN
9/8/2006 12:05:18 PM Status: Initializing collector: WMI
9/8/2006 12:05:18 PM Status: Running WMI collector
Has someone encounterd this problem and can help me.
rgds Henk Schilders
email henk.schilders@nl.fujitsu.com
September 11, 2006 at 8:00 am
This was removed by the editor as SPAM
September 11, 2006 at 1:53 pm
Sorry I don't have an answer for this but we've had the same issue (so you aren't the only one). H2 works with 64-bit 2005 SQL, it's the PerfCollector service that doesn't seem to work with it. It scans the registry but can't find SQL ("No SQL Server instances registered on the box").
We're using ver. 2.0.2 of SQLH2PerfCollector.exe.
March 27, 2007 at 10:31 am
In my shop none of our SQL 2005 64-bit servers are reporting to our repository:
3/27/2007 8:54:28 AM
3/27/2007 8:54:28 AM Opening Log
3/27/2007 8:54:28 AM SQLH2 ver. V2 2.0.027.0 10/17/05 16:25
3/27/2007 8:54:28 AM Status: Init
3/27/2007 8:54:29 AM WARNING: There are no PerfProviders in the config file
3/27/2007 8:54:29 AM Status: Initializing repository: dbs90008
3/27/2007 8:54:29 AM Status: Repository Database: SQLH2Repository
3/27/2007 8:54:29 AM INFO: host_id = 114
3/27/2007 8:54:29 AM Status: Starting RUN
3/27/2007 8:54:29 AM Status: Registering Run
3/27/2007 8:54:29 AM INFO: run_id = 4897
3/27/2007 8:54:29 AM Status: Starting Targets processing
3/27/2007 8:54:29 AM Status: Initializing Target: DBSW8020
3/27/2007 8:54:29 AM Status: registering Server
3/27/2007 8:54:29 AM INFO: srv_id = 296; signature = 7f54ab6c-951f-4d1f-877b-c3e8e6d299d4
3/27/2007 8:54:29 AM Status: Scanning Registry on DBSW8020
3/27/2007 8:54:29 AM WARNING: No SQL Server instances registered on the box
3/27/2007 8:54:29 AM Status: RUN
3/27/2007 8:54:29 AM Status: Initializing collector: WMI
3/27/2007 8:54:29 AM Status: Running WMI collector
3/27/2007 8:54:29 AM Status: Opening Unit 1 (OS/CS)
3/27/2007 8:54:29 AM Status: Collecting Win32_OperatingSystem
3/27/2007 8:54:30 AM Status: Collecting Win32_ComputerSystem
3/27/2007 8:54:30 AM Status: Collecting Win32_Processor
3/27/2007 8:54:34 AM Status: Closing Unit 1
3/27/2007 8:54:34 AM Status: Opening Unit 2 (NIC)
3/27/2007 8:54:34 AM Status: Collecting Win32_NetworkAdapter
3/27/2007 8:54:35 AM Status: Collecting Win32_NetworkAdapterConfiguration
Yet a signifcant amount of data is collected (I can see the files while the collector is running), it just doesn't seem to post to our repository. All our SQL 2000 boxes are working properly.
May 24, 2007 at 5:57 am
The only thing that I have found is that if you run the SQL H2 scans from a 32 bit box, it sometimes works.
September 13, 2007 at 9:49 am
I am also having this problem.
Windows 2003 (64-bit)
SQL Server Enterprise (64-bit)
SQLH2 V2 2.0.027.0 10/17/05 16:25
9/12/2007 4:41:53 PM Status: Scanning Registry on AFNSQLENTTST
9/12/2007 4:41:53 PM WARNING: No SQL Server instances registered on the box
I can open reports in Reporting Services and most of them are empty.
If I had to venture a guess, SQL 2005 64-bit keys are in a different Registry Location than 32-bit keys on a 64-bit OS. But, this is a very preliminary guess, and I have been working on this for a few days now. I will let you know if I get more information.
November 1, 2007 at 9:13 am
Hi all,
I do have the same problem with X64 systems. I wrote a mail to MS and got the answer that it is a known problem and it will be fixed.
Regards,
Rene
November 2, 2007 at 3:52 am
I have not checked this out, but your problem sounds like the KB 941823 issue. Check that the SQLH2 service account has the permissions to the SQL service that are described in 941823.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
March 13, 2008 at 7:39 am
I wonder if anyone has solved this issue.
KB 941823 is not the solution in my case.
SQLH2 is run under the SQL Server service account. Same for the SQLH2PerfCollector service.
The registry location is the same for x86 and x64, so I would think this is not the problem.
[font="Verdana"]Markus Bohse[/font]
March 13, 2008 at 7:58 am
I'd post this as a bug on Connect, ask for some votes (post the URL here) and see if you can get a good answer from MS. Or have someone call MS PSS and get a resolution.
Follow me on Twitter: http://www.twitter.com/way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
May 8, 2008 at 2:38 pm
I have a way of finding these posts late...
anyway, here's an entry on Connect that is related, although it doesn't mention x64 explicitly.
https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=293792
October 15, 2008 at 2:40 pm
SQLH2 is now published on CodePlex
November 21, 2008 at 8:14 am
I'd be interested to see if anyone found the resolution to this problem. I'm having it too.
November 21, 2008 at 9:31 am
Well, I was playing with this sourcecode earlier this week. I took my config file & copied it into my bin\debug folder and it appears to be pulling data from x64 servers just fine. So I guess this was resolved when the code was cleaned up for public release.
I did run into a bit of code that was throwing an unhandled exception.. that was caused by the WMI Product query where a product name was NULL. This was actually from my own workstation as this class isn't normally registered on servers. But it was causing the stored proc that does the insert/update to fail. I guess I'll publish my fix back to Codeplex once I figure out how to do that 😀
(added a WHERE Name IS NOT NULL to the Product WMI query)
December 8, 2008 at 9:53 am
I've got the latest build from codeplex and am running sp2 with cumulative update 7 on most of my servers. All my servers are x64 windows 2003 and running SQL Server 2005 x64. I still seem to be having the issue.
I haven't yet run the debug on it to see why this is happening but I did look at the source code that does the registry scan, and its pretty straight-forward. It doesn't seem like it would cause any kind of problem at all.
I am wondering if the issue described in kb941823 applies here. I do know that there are several lockdown procedures run on the production machines so the likelihood that the issue described in this kb applies. However I do find it odd that the problem only seems to manifest itself on machines in which SP2 is installed. SP1 and RTM register just fine.
I really would like to get this issue resolved because we're simply not in the position to go to SQL 2008 just yet. 2008 has the performance warehouse and although its impressive, it requires yet another license running somewhere. Its kinda nice to have a free open-source tool like SQL H2 to do basically the same thing. In addition, the database design of H2 is actually quite good and I find it incredibly easy to write custom reports based from the "canned" H2 reports that are actually quite good. I'd hate to have to re-write some of them.
Viewing 15 posts - 1 through 15 (of 16 total)
You must be logged in to reply to this topic. Login to reply