All TagsCOM input format (RSS)
Sorry, but there are no more tags available to filter with.
  • RE: Scripted COM Input

    [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...
    Posted to Forum by LogParser User : StanL on 01-22-2007, 3:37 PM
  • RE: Scripted COM Input

    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.
    Posted to Forum by LogParser User : DEinspanjer on 01-22-2007, 1:33 PM
  • RE: Scripted COM Input

    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
    Posted to Forum by LogParser User : StanL on 01-22-2007, 10:04 AM
  • Scripted COM Input

    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")...
    Posted to Forum by LogParser User : StanL on 01-22-2007, 8:52 AM
  • Registering logparser.dll in COM+

    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
    Posted to Forum by LogParser User : BigBadger on 10-13-2006, 12:38 PM
  • RE: LP_Toolkit.WMIQuery question

    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?
    Posted to Forum by LogParser User : DEinspanjer on 10-10-2006, 1:59 PM
  • RE: LP_Toolkit.WMIQuery question

    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...
    Posted to Forum by LogParser User : GregVM on 10-10-2006, 11:05 AM
  • RE: LP_Toolkit.WMIQuery question

    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" ...
    Posted to Forum by LogParser User : DEinspanjer on 10-09-2006, 5:03 PM
  • LP_Toolkit.WMIQuery question

    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...
    Posted to Forum by LogParser User : GregVM on 10-09-2006, 4:49 PM
  • RE: Invalid parameter

    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.
    Posted to Forum by LogParser User : Vijai Kalyan on 09-07-2006, 9:32 PM
Page 1 of 5 (42 items) 1 2 3 4 5 Next >
Microsoft Communities