Hi all, I have a problem with the runmetersumm.exe tool. Here is the background: I have an SCCM SP2 R2 server on SERVER1, and SQL 2008 on SERVER2 (standalone box). Both server OS's are Windows 2008 R2 (but I don't think that should matter). I have successfully enabled the software metering client agent, I have enabled a software metering rule, and I can see on my client that it has received the updated policy, and the mtrmgr.log is monitoring usage of my metered application. I can also see in the swmtrreportgen.log that software metering data has been sent to the server. On the SERVER2 (the SQL box), I have created a folder, and I have placed the baseobj.dll, basesql.dll, basesvr.dll, baseutil.dll and runmetersumm.exe. I have opened a command prompt (as administrator) and I have executed the following command: runmetersumm SMS_ABC (where ABC is obviously my site code). I then get the following error.... *** [08001][17][Microsoft][ODBC SQL Server Driver][Shared Memory]SQL Server does not exist or access denied. $$<SMS_SQL_MONITOR><Mon Nov 29 16:08:16.268 2010 E . Australia Standard Time><thread=3152 (0xC50)> *** [01000][2][Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionOpen ( Connect()). $$<SMS_SQL_MONITOR><Mon Nov 29 16:08:16.268 2010 E. Australia Stand ard Time><thread=3152 (0xC50)> *** Failed to connect to the SQL Server. $$<SMS_SQL_MONITOR><Mon Nov 29 16:08:1 6.269 2010 E. Australia Standard Time><thread=3152 (0xC50)> Error: Could not get a SQL connection to database: SMS_ABC Now here's the kicker... my SQL server is running a named instance, and on a non-standard port. So my first question is... does anybody know, or has anybody seen that error before? Everything else in SCCM is working, and reports are working fine. It's only when I try to force a software metering summarization that I encounter an issue. Second question is... would it be possible that my SQL setup is beyond the capability of the tool itself? runmetersumm.exe can't connect to a named instance/non-default SQL port? Thanks in advance guys! Noel.http://www.dreamension.net

Ok - looks like we got it working. To do runmetersumm on a named instance, you need to specify the named instance and then the database name. So the command to get it to work was: runmetersumm.exe instancename\sms_abc However this brings me to the next question. It worked for us this time because it's a standalone SQL box, but when we move the SCCM environment into the next phase, SQL will be clustered. I noticed the same question asked in this post, but it wasn't answered: http://social.technet.microsoft.com/Forums/en-US/configmgrgeneral/thread/490e8617-7891-4b68-be66-881d6458e534/ Does anybody know if runmetersumm will work on an SQL cluster, with a named instance? http://www.dreamension.net