BlueCielo Meridian Enterprise 2012 Administrator's Guide | BlueCielo ECM Solutions

You are here: BlueCielo Meridian Enterprise Administrator's Guide > Troubleshooting server performance and stability > About system status reporting > Creating a system status report

Creating a system status report

AMRepU is a command-line tool that can be run on a Meridian application server or client computer to gather configuration and status information useful for troubleshooting. Running this executable is completely safe and typically can be done during production hours because it does not interact or interfere with any Meridian components that might also be running.

AMRepU accepts several parameters that are described in the following table. The command-line syntax is:

AMRepU <OutputFolder> [/ds] [/bu]

The output file will be named AMReport_<ComputerName>_<Date>.cab where <ComputerName> is the name of the computer where AMRepU is being run and <date> is the current date, for example, AMReport_MyServer_10042009.CAB.

AMRepU command-line parameters
Parameter Description

<OutputFolder>

The folder in which to store the output file. The DOS shorthand characters “.” (current folder) and “..” (parent folder) are accepted. This parameter is required.

/ds

Includes all vault databases (excluding stream files) in the output file. This can cause the output file to become very large. Optional.

Warning    AMRepU will temporarily stop the Meridian services in order to do this. Therefore, do not use this option while the server is in use! Do not use this option unless specifically asked to do so by a technical support representative.

/bu

Includes the Backup folders of all vault databases (excluding stream files) in the output file. The Meridian services will not be stopped if this switch is used. This can cause the output file to become very large. Optional.

Warning    Although AMRepU doesn’t stop any services when this switch is used, it can temporarily put a heavy load on the server, which will result in decreased performance. Do not use this option unless specifically asked to do so by a technical support representative.

/ext

Includes the contents of the extensions share in the output file. By default, these are located at C:\BC-Meridian Extensions.

/ch:<Drive>

Runs CHKDSK on the specified drive and includes the results in the output file.

To create a system status report:

  1. Open a command-prompt window on the computer where you want to run the program.
  2. Change the current folder to the Meridian program folder, by default, at C:\Program Files\BC-Meridian\Program.
  3. Type the program name, specify the necessary parameters, and press Type. The following example will produce a basic report file in the current folder:

C:\Program Files\BC-Meridian\Program>AMRepU

  1. As AMRepU runs, progress messages are shown in the command-prompt window. Completion can take several minutes.
  2. When AMRepU is finished, you can open the resulting CAB file to review the results.

An AMRepU output file (.CAB) contains the files described in the following table.

CAB file contents
File Name Description

*.dat

Symantec Norton AntiVirus configuration files (files > 10 KB in size are skipped)

*.hdb

Hypertrieve database file (requires /ds parameter)

*.log

Hypertrieve database log file (requires /ds parameter)

*.log

Backup of Hypertrieve database log file (requires /bu parameter)

*.snb

Hypertrieve database snapshot backup (requires /ds parameter)

*.snp

Hypertrieve database snapshot (requires /ds parameter). Not added if *.snb exists

*.snp

Backup of Hypertrieve database snapshot (requires /bu parameter)

*_ALLOC.CSV

Hypertrieve allocation information

amfs.log

AMFS service log file

AMM_Installed
DataStores.txt

A listing of vaults and the amount of disk space used

AMM_Installed
DataStores.txt.dir

Directory listings for each vault folder

AMMamacad.ini

AutoCAD application link settings

AMM-Setup-
NetViewer.log

NetViewer setup log

AMRepFiles.csv

A listing of all files included in the CAB file

Application
Events.csv

An export of the Windows Application Event log

BLUESCRN.TXT

Dump of BlueSave

boot.ini

Windows boot configuration file.

CacheLoader.ini

Cache loader settings

CU_Cyco.txt

An export of Meridian-related registry settings under HKEY_CURRENTUSER

DataStore.ini

Settings of installed datastores

Drivers.txt

A listing of Windows drivers

HyperCache.evt

HyperCache event log

HyperTrieve.evt

Hypertrieve event log

ICME<Version>-
Setup<Build>.log

Setup log files where <Version> is the installed Meridian version number and <Build> is the build number

BC-Setup-
AdvancedViewer.log

Advanced Viewer setup log

iFilters.txt

Information about installed Indexing Service content filters

LM_Classes_AppID.txt

An export of registry settings related to class AppIDs

LM_Cyco.txt

An export of Meridian-related registry settings under HKEY_LOCALMACHINE

LM_HotFix.txt

An export of registry settings related to Windows hot fixes

LM_McAfee.txt

An export of registry settings related to McAfee software

LM_MsOle.txt

An export of registry settings related to OLE

LM_MSSQLServer.txt

An export of registry settings related to SQL Server

LM_Services.txt

An export of registry settings related to installed services

LM_Symantec.txt

An export of registry settings related to Symantec software

LM_Uninstall.txt

An export of registry settings related to uninstall information

LM-Autodesk.txt

An export of registry settings related to Autodesk software

Scheduled Jobs.txt

An export of jobs in Windows Task Scheduler

Security Events.csv

An export of the Windows Security log

SetupLog.csv

A listing of files installed by Meridian

System Events.csv

An export of the Windows Events log

System Information.txt

System information

USERS_*_Intl.txt

An export of registry settings related to the current international region from the Default, LocalService, LocalSystem, and NetworkService registry sections

Related concepts

About system status reporting

Understanding the event logs

Related tasks

Reviewing the server configuration information

Reviewing the System event log

Reviewing the Application event log


Copyright © 2000-2012 BlueCielo ECM Solutions

www.bluecieloecm.com