More on Exchange ActiveSync Reporting with Log Parser - COM object available

re: More on Exchange ActiveSync Reporting with Log Parser - COM object available

Robert Spilman — Wed, 08 Mar 2006 19:09:06 GMT

This is great stuff! Can we get more?

re: More on Exchange ActiveSync Reporting with Log Parser - COM object available

Joachim Farla — Wed, 08 Mar 2006 19:51:11 GMT

What can i do when i get the following message in my system log:

Generate Activation Context failed for c:\Program Files\Log Parser 2.2\lpeas.dll. Reference error message: The referenced assembly is not installed on your system.

re: More on Exchange ActiveSync Reporting with Log Parser - COM object available

David Ruth — Wed, 08 Mar 2006 21:22:43 GMT

I've been using the earlier Logparser scripts with great success. Thanks...
When I try and register lpeas.dll on my XPsp2 or W2K3sp1 systems I get "LoadLibrary(lpeas.dll)Failed-The application failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem."

What next?

re: More on Exchange ActiveSync Reporting with Log Parser - COM object available

Erik Jans — Thu, 09 Mar 2006 17:37:46 GMT

Thanks for great work!
I unfortunately get the same error as David Ruth. "LoadLibrary(lpeas.dll) failed - This application has failed to start because the application configuration is incorrect. ..."
Running XP SP2 fully patched, and I installed LogParser 2.2 a few minutes ago. :)

re: More on Exchange ActiveSync Reporting with Log Parser - COM object available

Simon — Fri, 10 Mar 2006 00:18:45 GMT

Im getting the same error, im runing on Windows Server 2003 SP1, Exchange Server 2003 SP2.

re: More on Exchange ActiveSync Reporting with Log Parser - COM object available

mhigashi — Fri, 10 Mar 2006 04:59:14 GMT

The problem may be associated with your machine not having the correct version of the MSVCR80.dll (or not having it at all).

We have update the EAS_Logparser_COM_Obj.zip file to include an executable which will install the MSVCR80.dll on your machine.

Please try this out and let me know if that resolves your problem.

--Mike

re: More on Exchange ActiveSync Reporting with Log Parser - COM object available

Tony Eversole — Fri, 10 Mar 2006 06:57:11 GMT

I would really like to see something like this for Exchange IMF data. We have the ability to see the SCL totals, etc within perfmon, but how could we use something like this to give us data on the IMF counters?

re: More on Exchange ActiveSync Reporting with Log Parser - COM object available

MaxDamage — Fri, 10 Mar 2006 17:30:43 GMT

I'm a fan of your work guys. Excelent Job. I sort of missed the boat and started reading this blog a bit late. I have been doing this in VBScript for a while. So if its okay with you I'll try to plagerise this bit too LOL.

Cheers

Max

re: More on Exchange ActiveSync Reporting with Log Parser - COM object available

David Ruth — Sat, 11 Mar 2006 06:29:32 GMT

Thanks, the MSVCR80.dll fixed my issue.

re: More on Exchange ActiveSync Reporting with Log Parser - COM object available

Thomas — Fri, 17 Mar 2006 08:59:46 GMT

I'm getting a very different error no matter where I run the command from or how I set up my SQL file:

Error: Error calling Input Context plugin method "OpenInput": The filename, dire
ctory name, or volume label syntax is incorrect.

This is on a Win2k3SP1 server with the updated com object redist installed...thoughts?

re: More on Exchange ActiveSync Reporting with Log Parser - COM object available

Chris W — Fri, 17 Mar 2006 15:10:45 GMT

This is great, but what about using Log Parser on Message tracking to the same end? I have been playing with it, and all thought I can read thru the log's I'm having problems finding resources telling me what I'm looking for. And once I find it, what doies it mean.

Any suggestions?

re: More on Exchange ActiveSync Reporting with Log Parser - COM object available

Simon — Tue, 21 Mar 2006 03:30:08 GMT

That did the trick, now for some fun!

re: More on Exchange ActiveSync Reporting with Log Parser - COM object available

mhigashi — Wed, 29 Mar 2006 22:28:14 GMT

Thomas,

Can you provide the following:

- the complete syntax that you typed into the command-line?
- the contents of the script that you were executing

This should me understand where the problem may be coming from.

Thanks!

--Michael