Search results matching tag 'COM input format'

RE: Scripted COM Input

LogParser User : StanL — Mon, 22 Jan 2007 20:37:00 GMT

[QUOTE User="LogParser User : StanL"]Quote: You don't have an INTO clause specified in your query, so I imagine the output format is trying to get a handle to STDOUT and failing. Try changing your query to "SELECT * INTO foo.xml FROM ." and th...[/QUOTE]
My bad, I tried SELECT * FROM . INTO and got an error. Just had my SQL parms out of place. Thank You. Stan

RE: Scripted COM Input

LogParser User : DEinspanjer — Mon, 22 Jan 2007 18:33:00 GMT

You don't have an INTO clause specified in your query, so I imagine the output format is trying to get a handle to STDOUT and failing.

Try changing your query to "SELECT * INTO foo.xml FROM ." and then see if your ExecuteBatch works.

RE: Scripted COM Input

LogParser User : StanL — Mon, 22 Jan 2007 15:04:00 GMT

Oh, BTW if I simply script

oRS = oLog.Execute cSQL, oInput

I can query the recordset object using GetColumnCount(), GetColumnName() and toNativeString( "," ) to concatenate a .csv file... but the question remains, why doesn't it accept an output format? Stan

Scripted COM Input

LogParser User : StanL — Mon, 22 Jan 2007 13:52:00 GMT

I registered the QBF.wsc and executed the command line logparser "SELECT * FROM ." -i:COM -iprogid:MSUtil.LogQuery.Sample.QFE and it worked. I wanted to 'script' the .wsc and so set up

cSQL = 'SELECT * FROM .'

oLog = CreateObject("MSUtil.LogQuery")

oInput = CreateObject("MSUtil.LogQuery.Sample.QFE")

oOut = CreateObject("MSUtil.LogQuery.XMLOutputFormat")

oLog.ExecuteBatch cSQL, oInput, oOut

but get this error which I do not inderstand.

Stan

Registering logparser.dll in COM+

LogParser User : BigBadger — Fri, 13 Oct 2006 16:38:00 GMT

Hi,

I've had runtime problems when I refer LogParser's COM Objects after registering the DLL in COM+. After removing it from COM+ and registering it using regsvr32 the code executes fine.

Does anyone else use COM+ or do you know if LogParser works with it?

Thanks,

Richard

RE: LP_Toolkit.WMIQuery question

LogParser User : DEinspanjer — Tue, 10 Oct 2006 17:59:00 GMT

So that Column Name is not an integer error is coming from the Chart3D. It seems to want the first column to be a number.
Did you try a different chart out?

RE: LP_Toolkit.WMIQuery question

LogParser User : GregVM — Tue, 10 Oct 2006 15:05:00 GMT

Daniel,

Thanks for the reply. I tried that this morning:

logparser "SELECT Name, Capacity, MUL(PROPSUM(FreeSpace), 100) AS Percent

INTO VolSpace.gif FROM Win32_Volume

WHERE Name LIKE '%PSSTATIC%'

GROUP BY Name,Capacity

ORDER BY Percent DESC"

-i:COM -iProgID:LP_ToolKit.WMIQuery -iCOMParams:ComputerName=PHPSVFS01 -charttype:Column3D

-View -ChartTitle:"Volume Space" -categories:off

And received this result:

Task aborted.
Column Name is not an INTEGER nor a REAL

Statistics:
-----------
Elements processed: 0
Elements output: 0
Execution time: 13.70 seconds

I tried running it again with a -h flag but received an error that field names can be retrieved only from input files SOOO I instead had it write to CSV just to make sure I was connecting to the server:

logparser "SELECT Name, Capacity, FreeSpace

INTO c:\temp\VolSpace.csv

FROM Win32_Volume

WHERE Name LIKE '%PSSTATIC%'"

-i:COM -iProgID:LP_ToolKit.WMIQuery -iCOMParams:ComputerName=PHPSVFS01

Statistics:
-----------
Elements processed: 58
Elements output: 38
Execution time: 14.59 seconds

It worked beautifully and gave me the expected results so at least now I know that the parameter is working properly. Now I'll work on getting the original requested output COLUMN3D to work properly.

Thx!

-G

RE: LP_Toolkit.WMIQuery question

LogParser User : DEinspanjer — Mon, 09 Oct 2006 21:03:00 GMT

I'm not really familiar with the toolkit WMIQuery, but given the information you've provided, it seems like this would work:

-i:COM -iProgID:LP_ToolKit.WMIQuery -iCOMParams:"ComputerName=myremoteserver" ...

LP_Toolkit.WMIQuery question

LogParser User : GregVM — Mon, 09 Oct 2006 20:49:00 GMT

Good day all,

I use a WMI script to retrieve Win32_Volume properties from a remote MS Cluster server, write the results to CSV and email to dept managers. I prefer the output options with Logparser and want to convert the script to the LP_Toolkit COM input but ran into a problem - how do I point this at a remote server??

logparser "SELECT Name,Capacity,MUL(PROPSUM(FreeSpace), 100) AS Percent

INTO VolSpace.gif

FROM Win32_Volume

WHERE Name LIKE '%PSSTATIC%'

GROUP BY Name" -i:COM -iProgID:LP_ToolKit.WMIQuery -charttype:Column3D -View -ChartTitle:"Volume Space" -categories:off

Seeing that there is a "iCOMParams" parameter available I opened the VBP file with VisStudio2005 looking for a COMPUTER property to call to but didn't see one. I'm no VB programmer by any means but did see this string:

Public Property ComputerName() As String
Get
ComputerName = mvarComputerName
End Get
Set(ByVal Value As String)
mvarComputerName = Value
End Set
End Property

Then further down:

m_sFromEntity = FromEntity

sComputer = mvarComputerName

oWMIService = GetObject("winmgmts:\\" & sComputer & "\root\cimv2")

oClass = oWMIService.Get(m_sFromEntity)

I need to manage the oWMIService string above. Any suggestions? Has anyone else used this class to query remote WMI properties? I thougt about giving this a stab myself and creating another VB function within the project, but when I opened it with VisStudio2005 there were many conversion errors so I think that path is screwed.

TIA!

-Greg

RE: Invalid parameter

LogParser User : Vijai Kalyan — Fri, 08 Sep 2006 01:32:00 GMT

Hi Daniel,

Thanks for the help. I looked around on the forums and resources pages and found an explanation of how the custom properties structure behaves. I fixed that and things work now!

Thanks a lot for pointing me along.

regards,

-vijai.