JetStress does not go further than Checking Test System

sammeh · Joined: 10 Feb 2008 Posts: 1

Hi,

JetStress will install, but will not go beyond "Checking Test System". This
same behavior was observed on all installs of JetStress (08.01.0177.000) on
Win 2003 SE SP2 and Win 2003 EE SP2, both operating systems are 32bit.

Microsoft Exchnage Server 2007 is not installed (nor has it been installed )
on any of the machines.

VERSIONS:
JetStress 08.01.0177.000
OS: WIN 2003 XP 2 (plus all the Service Packs as of 02/09/2008)
FROM Exchange Server 2007 CD::
ESE.DLL (12/03/2006)
ESEPERF.DLL (12/03/2006)
ESEPERF.HXX (11/09/2006)
ESEPERF.INI (11/09/2006)

OUTPUT FROM JETSTRESS:

2/10/2008 10:52:27 AM -- Microsoft Exchange Server Jetstress Core Engine
(version: 08.01.0177.000) detected.
2/10/2008 10:52:27 AM -- Microsoft Windows Server 2003 R2 Service Pack 2
(5.2.3790.131072) detected.
2/10/2008 10:52:27 AM -- Microsoft Exchange Server Database Storage Engine
(version: 08.00.0685.024) detected.
2/10/2008 10:52:27 AM -- Microsoft Exchange Server Database Storage Engine
Performance Library (version: 08.00.0685.024) detected.
2/10/2008 10:52:28 AM -- Database or Database ==> Instances performance
counter category is not registered.
2/10/2008 10:52:28 AM -- Database Storage Engine Performance Library is
successfully registered.
2/10/2008 10:52:28 AM -- Database Storage Engine Performance objects and
counters are successfully loaded.
2/10/2008 10:52:28 AM -- Advanced Database Storage Engine Performance
counters are successfully enabled.
2/10/2008 10:52:28 AM -- This process is required to restart for the changes
to take effect.

The output is the same whether .NET 3.0 is on the machine or not. .NET 2.0
is installed on all machines with the .NET service packs.

These are standard stand-alone installs, no roles installed on servers and
they are not members of any domain. All the Microsoft updates have been
installed. Also, this version of JetStress does not have a "Fix button". The
only options after running the JetStress test are "Back" and "Exit". The
command line version produces the identical outpt as the windows version.

Thanks for any assistance,
Sammeh
Thanks for any insight.

Archived from group: microsoft>public>exchange>tools

loadsim and jetstress I added another server to my production enviroment. It currently does not have any mailboxes on it. Is it safe to run jetstress and loadsim? Or does it have to be on a non production AD?

Checking Outlook based delegtes Sorry as I think this is a cross post but got no answer in the Outlook area. We have Exchange 2003 and 2007 and many users who put delegates into Outlook. Of course when a mailbox is deleted the delagte still remains in Outlook and causes meeting requests

JetStress Exchange 2007 Hi All can anyone tell me what you should set the following test parameter to for Exchange 2007 Jetstress testing? Supress Tuning and use thread count = n Im confused at what this actually means and how it will relate to my test results Thanks AJ

Connecting an Exchange 2000 system to a 2003 system... I run Windows 2000 SP4 with Exchange 2000SP3 using AD 2000. I might be required to connect my Free/busy info with the free/busy info on a Windows 2003 with exchange 2003 system on another network. My Network is abc.123.com and their network is 123.com.

TEST TEST1