Topic Last Modified: 2007-07-13
The following are some specific issues that can occur when you run Jetstress, their possible causes, and the recommended solutions.
Consider the following information to help you resolve issues that may be preventing you from attaching or creating a database.
Event log error that may display: Error -1023
Possible cause: The path of the database or log files is incorrect.
Solution: Ensure that the paths and file names are correct.
Event log error that may display: Error -1032
Possible cause: Permissions are insufficient to access the .edb file or the log files.
Solution: Verify that permissions are sufficient for the account under which Jetstress is running. Jetstress requires read/write permission to the directories it is using.
Event log error that may display: Error -550 (0)
Possible cause: The last time Jetstress was run, it was ended uncleanly. This caused the log files to become unsynchronized with the database.
Solution: Delete the Jetstress database (*.edb), log files (*.log), and check file (*.chk), and re-create the Jetstress database. You can also use Eseutil.exe with the /r switch to resynchronize the logs and database.
Event log error that may display: Error -1022
Possible cause: The failure is caused by circular logging by Jetstress.
Solution: Check the log drive for the log file name that is identified in the event log. Delete that log file and all the log files that have a higher number in the file name. Then, run Eseutil.exe /r to recover Jetstress.edb. When the database is in a good state, delete all the log files in the log directory, and rerun Jetstress.
JetstressWin.exe relies on performance counters to monitor the system and specifically requires the ESE database counters to be installed. When the counters are not loaded correctly, you may see exception errors related to performance counters. To reload the counters:
Exit from the JetstressWin.exe application.
Locate the directory where JetstressWin.exe was installed and verify that eseperf.dll, eseperf.hxx, and eseperf.ini files exist in the directory.
In a command shell window, type the command unlodctr ESE and then click Enter. This will unregister the ESE Database performance counters.
Start JetstressWin.exe and allow it to reload the performance counters.
In certain cases when Exchange Server was installed before Jetstress, uninstalling Jetstress could result in unstable Database Performance counters. To restore access to Database Counters after Jetstress has been removed, do the following:
At a command prompt, change the directory to the Exchange installation directory (exchsrvr\bin).
Run the command unlodctr ESE to ensure that the Database Performance counter registration information has been completely removed from the registry.
Run the command lodctr esperf.ini, which should correctly register the Database counters.
The Database Performance counters will be available the next time that you start System Monitor.
This error indicates that Jetstress could not find appropriate parameters that could be used to run a performance or stress test at the desired level of I/O load. This can be caused by several factors. The most common reason is that the storage subsystem has multiple hosts attached to it, and those hosts are competing for common resources during the tuning process. When you are running in a scenario such as this, you can run Jetstress on a single host with tuning enabled to generate the appropriate load parameters, and then rerun the test on the other hosts with the Suppress Tuning option enabled and the tuning parameters entered manually from the results of the first test.