Chat now with support
Chat with Support

Stat 6.2 - User Guide

Introduction to Stat Connecting to Stat Change/Service Requests Stat Consoles Tasks and Time Entries Stat Projects Search Engines Reports and Graphs Personal Rules Object Tools and Wizards Change Management for PeopleSoft
Object Management (PeopleSoft) Object Archives (PeopleSoft) Object Migrations (PeopleSoft)
Change Management for Oracle Applications
Object Management (Oracle Applications) Patch Management Object Archives (Oracle Applications) Object Migrations (Oracle Applications)
Change Management for Generic Applications
Object Management (Generic Applications) Object Archives (Generic Applications) Object Migrations (Generic Applications)
Appendix: Troubleshooting Chart Appendix: Migration Options Appendix: User-Specific Parameters Appendix: Supported PeopleSoft Proprietary Objects Appendix: Stat Reports

Login/Connection

 
Problem
Explanation/Solution

Receive the following error message when logging in:

“Unable to complete ‘First Pass’ login.... Invalid username/password.”

Verify that the login ID field in the Stat.ini is correct. Normally, this is “STATLOGIN.”

Verify that the STATLOGIN account is defined at the environment level.

Receive the following error message when logging in:

“Unable to complete ‘First Pass’ login.... DBMS (073/MSS) is not supported on your current installation.”

Re-install Quest® Stat®, making sure that you install the appropriate native environment connectivity drivers.

Verify that the appropriate environment client software is installed on the workstation (i.e., SQL*Net or SQL Server® client).

In the case of Oracle®, verify that the oracle/bin directory is part of the workstation’s path.

Receive the following error message when logging in:

“TNS: Could not resolve service name.”

Verify that the Server Name field in the Stat.ini file matches a valid TNSnames.ora entry

Receive the following error message when logging in:

“Unable to complete ‘Second Pass’ login.... Invalid user name/password....”

This error indicates that the LOGINID and/or LOGINPWD fields in the STAT_LOGIN table do not match those of the environment owner. Check the password in the Stat.ini file.

CSRs

 
Problem
Explanation/Solution

CTRL+F Usage:

The CTRL+F keystroke that advances the user to the next entry field in the Description tab of the CSR is not functioning.

This is caused when a space is inserted between the adjoining greater than/less than <> brackets in the Application/CSR Template. Access the template which is failing, and verify that no spaces exist between the two brackets.

Deleting CSRs:

Is there a way to delete CSRs from the environment?

With proper security rights, you can use the CSR Purge Wizard to permanently delete CSRs from the Quest® Stat® Repository.

Before deleting a CSR, however, it is recommended that you first use the wizard to export the CSR to a file for backup purposes.

Deleting Objects and Archive Sets from CSRs:

How do I delete objects and archive sets from existing CSRs?

Please contact Quest Software Support for instructions on how to proceed.

CSR Locks:

After logging in to Stat, I opened an existing CSR and received the following message: “This message has been locked by...”

This warning message indicates that the CSR is locked by the user noted in the message. You will also receive this error message when a user closes Stat and fails to close the CSR first. Ensure that all CSRs are closed prior to closing Stat. Not doing so will not remove the lock status in the environment and will cause this warning message to appear when another user tries to access the CSR.

Stat Web

 
Problem
Explanation/Solution

For users running the Quest® Stat® Central Agent on Unix®, graphical workflow diagrams do not display properly in Stat Web.

This problem may occur when either:

•
The machine hosting the Stat Central Agent doesn’t have a windowing system installed in the operating system, as specified in the Stat system requirements
•
You are connecting to the Stat Central Agent using a telnet session that doesn’t have graphical display capability

The solution to the second case is to start the Stat Central Agent in a background mode through the telnet session. To do this, execute the following command:

./run.sh &

Archiving and Migrating

 
Problem
Explanation/Solution

Base Archive Sets:

Base archive set status remains stuck in In Process.

First, verify that the objects in the Base archive set are from the Base Object Source (Base Final). Also, verify that you selected the All on Migration Path radio button in the Lock in Environment box on the Objects tab in the PeopleSoft® Change Management window.

A base archive set may remain in process if:

Any objects are locked in another CSR (for example, you have a reservation for an object in the Base database)

The Quest® Stat® Central Agent lost connectivity to the environment and/or the network

There are no objects that can be archived for the base environment on the CSR.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating