Anybody got this working with E2K7 x64, RTM or SP1 beta2? Everytime I run it, I get this below, it's driving me bonkers! 8/27/2007 3:18:28 PM -- This process is required to restart for the changes to take effect.

what last changes you made to server

Ensure that the 4 files (ese.dll, eseperf.dll, eseperf.ini and eseperf.hxx) are copied from the Exchange Server bin directory to the JetStress installation directory. Overwrite the ones that, probably, came from the Exchange CD-ROM.This should work if, of course, Exchange is already installed.

1/7/2009 8:18:28 AM -- Microsoft Exchange Server Jetstress Core Engine (version: 08.02.0060.000) detected.1/7/2009 8:18:28 AM -- Windows Server (R) 2008 Standard Service Pack 1 (6.0.6001.65536) detected.1/7/2009 8:18:28 AM -- Microsoft Exchange Server Database Storage Engine (version: 08.01.0329.000) detected.1/7/2009 8:18:28 AM -- Microsoft Exchange Server Database Storage Engine Performance Library (version: 08.01.0240.003) detected.1/7/2009 8:18:28 AM -- MSExchange Database or MSExchange Database ==> Instances performance counter category is not registered.1/7/2009 8:18:28 AM -- Database Storage Engine Performance Library is successfully registered.1/7/2009 8:18:35 AM -- Database Storage Engine Performance objects and counters are successfully loaded.1/7/2009 8:18:35 AM -- Advanced Database Storage Engine Performance counters are successfully enabled.1/7/2009 8:18:35 AM -- This process is required to restart for the changes to take effect.We are getting the same error. We have:-Windows 2008 SP1 server, 64 bit mode, - JetStress 2007 (08.02.0060) 64 bitversion, downloaded two days ago. - The four files mentioned were copied over from a different Exchange 2007 SP1 RU5 installation.-Exchange 2007 was not installed on this server.- In fact, nothing has been installed on this server except for JetStress and the OS. I tried the 32bit version and got the same results.Has anyone gotten JetStress 2007 to work? Does anyone have any suggestions?

Have you closed Jetstress and start it again and then do you get the same error message?I have worked with it several times.

Yes, I tried that. Going backor closing Jetstress and restarting it just brings us back the same messages. When I run it in the command line it automatically opens a new window, lists out the same error messages, and opens a new window, again and again.

Do you see three MSExchange Database performance counter objects in perfmon.msc? Do you have event viewer entries in the application log from Perflib and Loadperf? Some troubleshooting information is available at http://technet.microsoft.com/es-es/library/bb643106.aspx

Thanks for the debugging hints. We still have the same errors, but here's what I found.When we run windows\system32\perfmon.msc there are no MSExchange Database performance objects.But when werun windows\syswow64\perfmon.mscthe MSExchange Database performance objects do appear.We see the following Loadperf and Perflib entries in the event log every time we run JetstressWin: Loadperf Informational 1000Performance counters for the ESE (ESE) service were loaded successfully. The Record Data in the data section contains the new index values assigned to this service.Loadperf Informational 1002Performance counters for the ESE (ESE) service are already in the registry, no need to reinstall. This only happens when you install the same counter twice. The second time install will generate this event. Perflib Error 1022Windows cannot open the 64-bit extensible counter DLL ASP.NET_64 in a 32-bit environment. Contact the file vendor to obtain a 32-bit version. Alternatively if you are running a 64-bit native environment, you can open the 64-bit extensible counter DLL by using the 64-bit version of Performance Monitor. To use this tool, open the Windows folder, open the System32 folder, and then start Perfmon.exe. Perflib Error 1017Disabled performance counter data collection from the "ASP.NET_64" service because the performance counter library for that service has generated one or more errors. The errors that forced this action have been written to the application event log. Correct the errors before enabling the performance counters for this service.

Did you install the 32 bit Jetstress version on the 64 bit OS?I never did that.Have you tried to unload the counters as described in the TechNet article? Sometimes the performance counters get totally messed up and you have to re-setup the OS. I would try the steps first in a virtual machine. This was what I did to check the topic a few days ago because I havent used Jetstress for some months.

I re-downloaded and installed the 64-bit version a couple of days ago. I did the "unlodctr ese" as described in the article. We are using a virtual machine for this server. Nothing seems to make any difference. I did install the 32-bit version to see if that would work any better but it performed the same. I uninstalled it and reinstalled the 64-bit version.

PROBLEM RESOLVED. I did some looking around and found a manual service named "Performance Counter DLL Host." That service was not started. When I started it Jetstress began to work correctly.Thanks for helping me keep this logical and find a solution.

I confirm. It works;Great job.Thanks Loe.Mustapha

I didn't have that service available in my list to start.Windows Server 2003 SP2Jetstress 2007 with Exchange 2003 dllsAll I had to do to fix the error was open Perfmon prior to running Jetstress.

Here my 50 cents. Do not use the files from an exchange server you already have deployed, but use the files which come from the CD/DVD or ServicePack. Just spend 4 hours with different server installs, .net 2.0 bollocks etc. to finally have it fixed with the original files from the Setup disks. Also, use the 32-bit files from the 32-bit exchange setup for the 32-bit Jetstress 2007 on a 32-bit 2003 server. Same goes for 64-bit files, from the 64-bit exchange setup for the 64-bit Jetstress 2007 on 64-bit 2003 server. Cheers.