|
Actual Interval too different from Capture Interval
|
File was captured later than expected, i.e., this file does not
follow on from the previous file processed. This is usually caused
by the Acquire service being started and stopped or the machine
being turned off for a period of time.
|
|
|
ControlCenter WinParser has caught an unexpected Exception*.
Contact Action Line for support.
|
Unexpected errors in the data.
|
|
|
An Exception* occurred
|
Unexpected errors in the data.
|
|
|
Athene Exception* 1001, There is no performance text map
available.
|
No First File processed/corrupt First File or corruption of
PTnnnnnnnn.dat
|
Force the Windows Acquire to start a new measurement period by
stopping capture for at least two capture intervals
|
|
Athene Exception* 1005, The version number in the PerfText file is
incorrect
|
Corruption of PTnnnnnnnn.dat or changes on the OS.
|
Force the Windows Acquire to start a new measurement period by
stopping capture for at least two capture intervals
|
|
Athene Exception* 1006, The capture year is earlier than
1991
|
Old Acquire or corrupt counters.
|
Upgrade the Acquire and/or fix the performance
counters
|
|
Athene Exception* 1007, This interval has been skipped. Key
performance data is missing (service started after
Acquire?
|
-
No data in the files
-
Valid data in the files
|
-
Acquire must be started after the SQL Server, including when
the SQL server is ‘bounced’.
-
The instance name of the SQL server, check and correct the
instance name in System Manager
|
|
Two processes have the same PID
|
Processes should not have the same PID, therefore if this error is
seen there is likely to be a corruption of the data
files.
|
|
|
An attempt has been made to evaluate a non-snapshot counter in a
snapshot profile
|
The format of the data file is not as expected.
|
|
|
The performance text map is corrupt
|
|
Confirm Virus scans, Indexing and Backups are turned off/excluded
for the Syncsort™ Capacity Management …\work directory and
subdirectories and the …\Logs directory
If Virus scans are not
causing the issue then delete the PTnnnnnnnn.DAT and force the
Windows Acquire to start a new measurement period by stopping
capture for at least two capture intervals
|
|
The SQL Server instance name in the data does not match the
instance name in the target definition. Correct the SQL Server
instance name using System Manager.
|
The SQL Server instance name within System Manager has been
defined incorrectly.
|
Check System Manager has the appropriate Instance Name
defined.
|