Viewing Log Files

Access the View Logs form.

Server Build Log - Client Log

Select this option to view client-side processing.

The SvrPkgBuild.log is located directly under the <package name> directory.

Server Build Log - Server(s) Log(s)

Select this option to view server-side processing.

The <server name>_SvrPkgBuild.log files are located in the <package name>\serverlogs\<server name> directory.

Server(s) .sts logs (30+ logs)

These are the status files for all of the dlls that were built on the enterprise server.

The <dll name>.sts files are located under the <package name>\serverlogs\<server name> directory.

Client Build Log

The client package build log lists the steps completed in building the client package, as well as any errors that occurred during the process. This log is created for a client-only or client/server package.

The ClientPkgBuild.log file is located in the <package name> directory on the deployment server.

Client Package Statistics

This report contains the size of the directories on the client, number of files in each directory, and the size of the local package database.

The BuildReport.txt file is located under the <package name>\work directory.

Client Business Function Errors

Select this option to view any errors that occurred during the business function build for this package. Both errors and warnings display in this report. A summary appears at the end of the report that indicates how many errors and warnings occurred for each dll. Use this information to determine if a rebuild is necessary.

Business functions that appear on this report might be business functions that are still in development and have not yet been checked in. Business functions that have never been checked in do not have source, and therefore, are listed in the missing business function source errors log.

The BuildLog.txt file is located under the <package name>\work directory.

Missing Business Function Source

Select this option to see a list of all .c files that were missing when the business function was created. The program attempted to find these members because each had a record in the F9860 table. However, a matching source could not be found in the source directory. To resolve these errors, either delete the Object Librarian record or provide a source member.

The NoSource.txt file is located under the <package name>\work directory.

Business Services Build Log

Select this option to be able to view the results of the business services build for this package.

These logs are located under the <package name>\work\sbf directory.