While running SYSPRO, error conditions can be detected by the operating system, the runtime system, or the SYSPRO program itself.
Some of these error messages can occur in various programs and situations. The causes and solutions listed are not absolute and merely serve as a basis for troubleshooting these errors.
Check the Release Notes section on the SYSPRO InfoZone for possible program corrections.
When an error occurs, you can press Ctrl+F1 to view documentation about that specific error.
Group | General Explanation |
---|---|
User validation errors | These errors are related to the number of operators currently logged in. |
Setup errors | These errors relate to problems regarding control records that have not yet been created. |
Program loading errors | These errors usually indicate that the system is attempting to load a program, but cannot successfully continue due to a problem. |
Screenset errors | These errors relate to problems when the program attempts to load a screenset. |
Security access errors | These messages indicate that the operator code and/or the operator group or role does not have access to load the program, to perform an activity and/or to continue with the transaction. These include the Electronic Signatures messages. |
Transaction processing errors | |
File status errors | These errors usually indicate that the program is attempting to perform an action on a file or a table, but cannot complete the operation successfully due to a specific problem. |
File status 9-xxx errors | These errors usually indicate that the program is attempting to perform an action on a file or a table, but cannot complete the operation successfully due to a specific problem. |
SQL errors | These errors only occur in a SQL environment and can indicate that there is either a problem in the SQL statement or SQL optimized code or there may be a problem with the SQL handles. These errors are normally program errors. |
Program processing errors | Occasionally the program(s) can be corrupt and
reloading the programs will solve the problem. Report this to your distributor or local SYSPRO regional office (see Reporting program errors). |
Other errors | |
Hardware and/or operating system errors | These errors are often the result of power fluctuations, causing either temporary or permanent corruption. If the machine is re-booted and the error still exists, then further checks are required. |
Network and/or file permission errors | These errors usually require the expertise of the network and/or the system administrator. |
Cause | Remedy |
---|---|
This message indicates that you have attempted to load SYSPRO and the number of concurrent users would exceed the number of licensed users that are available. | Possible remedies include:
This message can also be an indication of a corrupt operator user count file. Report this to your distributor or local SYSPRO regional office (see Reporting program errors). |
Cause | Remedy |
---|---|
This message indicates that your logged-in session in SYSPRO is no longer active. | This message normally indicates that the system
administrator has logged you out of SYSPRO. Contact the system administrator to check if you were logged out intentionally. This message can also be an indication of a corrupt operator user count file. Report this to your distributor or local SYSPRO regional office (see Reporting program errors). |
Cause | Remedy |
---|---|
This message indicates that you have attempted to load a program that you are already using. | The program cannot be loaded twice. Close the first
instance of the program. Use the View Users program to check your open instances. Check the Release Notes section on the SYSPRO InfoZone for possible program corrections. Report this to your distributor or local SYSPRO regional office (see Reporting program errors). |
Cause | Remedy |
---|---|
This message indicates that the program is attempting
to use a file that has not yet been opened. This message generally indicates a program error. |
Report this to your distributor or local SYSPRO regional office (see Reporting program errors). |
Cause | Remedy |
---|---|
This message indicates that you have attempted to open a program that does not exist. |
Check the Release Notes section on the SYSPRO InfoZone for possible program corrections. Report this to your distributor or local SYSPRO regional office (see Reporting program errors). |
Cause | Remedy |
---|---|
This message indicates that you have attempted to open too many programs. | Close the programs that you are not using.
Use the View Users program to check your open instances. |
Cause | Remedy |
---|---|
This message indicates that you have attempted to run
a program that cannot be run standalone. The program
requires one or more parameters which have not been
provided. Most SYSPRO programs can be run without requiring any parameters to be passed, however, some SYSPRO programs are always called directly from other programs and are passed mandatory parameters. These programs do not appear on the SYSPRO menu and if you attempt to run them using the Run a Program function (Ctrl+R) this message is displayed. If you receive this message and you did not use the Run a Program function (nor have you added the program to a menu) then this may indicate a program error. |
Do not:
Report this to your distributor or local SYSPRO regional office (see Reporting program errors). |
Cause | Remedy |
---|---|
This message indicates that you have attempted to open/run a program which is part of an unlicensed module. | Contact the system administrator to check the company's license. If this is a program that is required, then the system administrator must contact SYSPRO's licensing department. |
Cause | Remedy |
---|---|
This message indicates that you have attempted to load a SYSPRO program to which you do not have access. The program name is displayed in the error message. | Contact the system administrator to check the program access levels of the operator group to which you belong. |
These error messages relate to problems regarding control records that have not yet been created.
Control records contain information relating to each module in SYSPRO.
Information contained in control records include:
the current financial year and month (for all modules that integrate to the General Ledger)
next journal number
opening and closing control balances
month status flags
month end dates
archive numbers
period-to-date values
Control records are created automatically when you add a new company, or if you add a new module to an existing company where the control record for the new module does not exist.
When you set up a new company, you are required to select the modules to be installed. Thereafter, you are required to specify the year and month for each of the modules that still require the financial year to be defined. As soon as you do this, all control records for the modules you are installing are created.
The modules that integrate to the General Ledger are immediately populated with the year and month you have defined. These modules include Accounts Receivable, Accounts Payable, Cash Book, General Ledger, Inventory, Work In Progress and Fixed Assets.
Additional information is added to control records according to the entries made and the options chosen within the setup programs of each module.
In a C-ISAM environment, the control records are stored in the data folder. In a SQL environment, the control tables are part of the main SYSPRO database.
In some instances these error messages may also be an indication that the programs cannot find the data path (in a C-ISAM environment) defined in the System Setup program. It may also indicate that for some reason the data path(s) is blank. In a SQL environment it may be an indication that some of the control tables are missing.
Cause | Remedy |
---|---|
The following is a list of possible errors relating
to missing control records:
|
Possible remedies include:
|
SYSPRO is developed as a multi-tier system - one of the tiers being the user interface. The user interface consists of the entire user experience and includes the various windows and dialog boxes that are used to interact with the user.
A screenset contains the definition of the user interface for a program. This includes the windows, dialog boxes and all the controls that reside within them (e.g. push buttons, radio buttons, check boxes, entry fields, list boxes, etc). In addition, a screenset responds to events, performs necessary validation and communicates with the main business logic tier.
Screenset errors normally indicate that there is a problem with the screenset programs either on the application server or on the client machine(s). Standard screenset names are suffixed by .RS, while customized screensets are suffixed by .GS.
These errors are normally returned as DS RUN errors and/or datablock inconsistency errors.
Some of these error messages can occur in various programs and situations. The causes and solutions listed in this document are not absolute and merely serve as a basis for troubleshooting this error. The possible remedies listed are based on previous experience. Support consultants can use these as a basis for troubleshooting the error. |
Cause | Remedy |
---|---|
This message indicates that the screenset file the program is attempting to access cannot be opened. | This error message may be returned by various
programs. Determine if this error message is specific to:
If this error is client machine specific, then possible remedies include:
If this error occurs on all client machines and the application server, then possible remedies include:
|
Cause | Remedy |
---|---|
This message indicates that the program cannot read the screenset file. This can also be an indication of a disk corruption. | This error message may be returned by various
programs. Determine if this error message is specific to:
If this error is client machine specific, then possible remedies include:
If this error occurs on all client machines and the application server, then possible remedies include:
Report this to your distributor or local SYSPRO regional office (see Reporting program errors). |
Cause | Remedy |
---|---|
This message indicates that the program is attempting
to open a screenset which is not recognized as a valid
screenset. It might be that the screenset name defined in the program is incorrect or that the screenset is from a previous version of the dialog system. |
This error message may be returned by various
programs. Determine if this error message is specific to:
If this error is client machine specific, then possible remedies include:
If this error occurs on all client machines and the application server, then possible remedies include:
Report this to your distributor or local SYSPRO regional office (see Reporting program errors). |
Cause | Remedy |
---|---|
This message indicates that an invalid function
exists in the screenset, but the dialog system cannot
identify at what stage the error occurred. This message generally indicates a program error. |
Check the Release Notes section on the SYSPRO InfoZone for possible program corrections. Report this to your distributor or local SYSPRO regional office (see Reporting program errors). |
Cause | Remedy |
---|---|
This message indicates that an invalid procedure
number exists in the screenset. This message generally indicates a program error. |
Check the Release Notes section on the SYSPRO InfoZone for possible program corrections. Report this to your distributor or local SYSPRO regional office (see Reporting program errors). |
Cause | Remedy |
---|---|
This message indicates that the program is attempting
to load a screenset, but the program and the screenset do
not contain the same view of the screenset. The data block
version in the screenset does not match the data block
version in the program. This can also occur when the screensets on the client machine(s) are not the same version as the screensets on the application server. This can happen if the self-healing process fails. |
This error message may be returned by various
programs. Determine if this error message is specific to:
If this error is client machine specific, then possible remedies include:
If this error occurs on all client machines and the application server, then possible remedies include:
Report this to your distributor or local SYSPRO regional office (see Reporting program errors). |
Cause | Remedy |
---|---|
This message indicates that the internal screen manager detected an error. | This error message may be returned by various
programs. Determine if this error message is specific to:
If this error is client machine specific, then possible remedies include:
If this error occurs on all client machines and the application server, then possible remedies include:
Report this to your distributor or local SYSPRO regional office (see Reporting program errors). |
Cause | Remedy |
---|---|
This message indicates that the program is attempting to open a screenset file, but the file cannot be located. | This error message may be returned by various
programs. Determine if this error message is specific to:
If this error is client machine specific, then possible remedies include:
If this error occurs on all client machines and the application server, then possible remedies include:
Report this to your distributor or local SYSPRO regional office (see Reporting program errors). |
Cause | Remedy |
---|---|
This message indicates that a bad parameter exists in the screenset. |
Check the Release Notes section on the SYSPRO InfoZone for possible program corrections. Report this to your distributor or local SYSPRO regional office (see Reporting program errors). |
Cause | Remedy |
---|---|
This message indicates that the dialog system is
attempting to call a program, but it failed. This error message may be returned by various programs. |
Check the Release Notes section on the SYSPRO InfoZone for possible program corrections. Determine if this error message is specific to:
If this error is client machine specific, then possible remedies include:
If this error occurs on all client machines and the application server, then possible remedies include:
Report this to your distributor or local SYSPRO regional office (see Reporting program errors). |
Cause | Remedy |
---|---|
These messages indicate that the program is
attempting to post a transaction, but has failed. As you are using SYSPRO in a C-ISAM environment, it cannot automatically undo any changes that may have been part-applied to your data files. You may have out-of-balance data files and data corruption is a possibility. These errors are possibly caused by:
|
Possible remedies include:
Report this to your distributor or local SYSPRO regional office (see Reporting program errors). |
Cause | Remedy |
---|---|
This message indicates that an unexpected condition
was detected during the SQL transaction before it was
completed. When a SYSPRO program posts new transactions or changes/deletes existing information, it typically performs this inside a SQL Server transaction. If you receive this error, then any additions, changes or deletions performed since the start of the transaction have been rolled back (i.e. undone). This ensures that you do not have a database containing partially-updated data. This rollback can possibly be caused by:
|
Refer to the Transaction Processing in a SQL
environment topic. Possible remedies include:
Report this to your distributor or local SYSPRO regional office (see Reporting program errors). When reporting the transaction processing error, provide the following additional information in the error report:
|
Cause | Remedy |
---|---|
This message indicates that the program attempted to
write information to a SQL object which is invalid or does
not exist. If you select to view the Extended SQL Information, then you can view the SQL statement that was being executed just before the error was returned. The invalid table or column name is also displayed. |
The system administrator must check the integrity of
the database. Use the SQL Server Diagnostic program to confirm that:
If the program identifies missing standard SYSPRO tables and columns, then this usually indicates that the data conversion was unsuccessful. For example: you could be attempting to connect to a SQL database which is in a format of a previous version of SYSPRO, but you are connecting to this database using a later version of SYSPRO. In this case, you need to redo the conversion for the release of SYSPRO you want to run. If the program identifies missing primary indexes, then you need to generate and execute the relevant SQL script (e.g. ADDKEY70) against the database. This will recreate the primary indexes on all the standard SYSPRO tables. Report this to your distributor or local SYSPRO regional office (see Reporting program errors). |
Cause | Remedy |
---|---|
Some SYSPRO programs use a timestamp to control data
contention. This message indicates that the timestamp
changed between the time the operator selected the item and
the time the operator attempted to change the item. For example: when changing the Accounts Receivable terms using the AR Invoice Terms program, the maintenance program reads the timestamp against the terms code being changed and stores it. When the operator saves any changes, then the timestamp on the row is compared to the saved timestamp and if they differ then a timestamp error message is shown. The timestamp against the row only changes if another process has changed data on the same row since the original timestamp was saved. |
Ensure that other operators are not updating the same
item at the same time. Use the System Information program
(Shift+F7) to see which operator is accessing which
programs. Report this to your distributor or local SYSPRO regional office (see Reporting program errors). |
Cause | Remedy |
---|---|
This message indicates that SYSPRO detected an
unexpected condition when interacting with SQL
Server. If you select to view the Extended SQL Information then you can view the SQL statement that was being executed just before the error was returned. There is also detail regarding the condition that caused the problem. |
When you receive this error:
Report this to your distributor or local SYSPRO regional office (see Reporting program errors). When reporting the Invalid SQL command error message, provide the following additional information in the error report:
|
Cause | Remedy |
---|---|
This message indicates a duplicate key condition. The program is attempting to WRITE a record that would create a duplicate primary key in the indexed file or table. | This error message is generally caused by a
data-related problem, but can in some cases be caused by a
program error. The primary key and the file name is displayed in the error message. Check the Release Notes section on the SYSPRO InfoZone for possible program corrections. Other possible remedies include:
Report this to your distributor or local SYSPRO regional office (see Reporting program errors). When reporting the Duplicate key file error message, provide the following additional information in the error report:
|
Cause | Remedy | ||||||
---|---|---|---|---|---|---|---|
This message indicates that an attempt has been made
to access a record, identified by a key, and that record
does not exist in the file. This message can be caused by one of two actions:
|
This error message is generally caused by a
data-related problem, but can in some cases be caused by a
program error. The item key and file name is displayed in the error message. Check the Release Notes section on the SYSPRO InfoZone for possible program corrections. Other possible remedies include:
Report this to your distributor or local SYSPRO regional office (see Reporting program errors). When reporting the Record not found file error message, provide the following additional information in the error report:
|
Cause | Remedy | ||||
---|---|---|---|---|---|
This message indicates that a physical limit imposed
by the C-ISAM file system has been reached. Typically, when
the file size reaches or exceeds this limit, the last record
written to file is truncated. Reindexing will complete successfully as the Reindex program only opens the files for INPUT (i.e. the file is read sequentially). All the other SYSPRO programs (or the ISAM to SQL migration wizard program) open the files for INPUT and OUTPUT. If the runtime system detects that a file has exceeded the file size limitation, this error message is displayed. For C-ISAM files, the runtime supports an approximate maximum file size of 4GB on Windows-based operating systems. |
|
Cause | Remedy | ||||
---|---|---|---|---|---|
This message indicates that the program is attempting to open a file for writing when it was set to read-only. | This message generally indicates a permission problem
either on the file name or the folder name reported in the
error message. Possible remedies include:
If you receive this message when you run the Requirements Calculation program on a SQL-based system, check the following:
|
Cause | Remedy |
---|---|
This message indicates that the record length, primary key or alternate key definition in the program does not match the settings of the C-ISAM file. | Possible remedies include:
|
Cause | Remedy |
---|---|
This message indicates that the program is attempting
to open a file that has already been opened. This message generally indicates a program error. |
Check the Release Notes section on the SYSPRO InfoZone for possible program corrections. Report this to your distributor or local SYSPRO regional office (see Reporting program errors). |
Cause | Remedy |
---|---|
This message indicates that the program is attempting
to close a file that has already been closed. This message generally indicates a program error. |
Report this to your distributor or local SYSPRO regional office (see Reporting program errors). |
Cause | Remedy | ||||
---|---|---|---|---|---|
This message indicates that the program is attempting to read the next record on a file when there is no valid pointer to that file (i.e. a valid starting point has not been obtained). This is both a data-related error and a program error and only occurs on a C-ISAM file. It is usually caused by a START being performed on the file and failing. The program does not check for the failure and continues to read the next record. | This message can indicate that there is a
data-related problem on the file name displayed in the
message. The key of the record is displayed in the message.
Use the DDSBFI program to establish what the primary key field is for this file and investigate the relevant data file. This can be an indication of a missing or corrupt record in one of the files. Report this to your distributor or local SYSPRO regional office (see Reporting program errors). When reporting this error, provide the following additional information in the error report:
|
Cause | Remedy |
---|---|
This message indicates that the program is attempting
to perform a READ or START operation on a file not opened in
INPUT mode. This message generally indicates a program error. |
Check the Release Notes section on the SYSPRO InfoZone for possible program corrections. Report this to your distributor or local SYSPRO regional office (see Reporting program errors). |
Cause | Remedy |
---|---|
This message indicates that the program is attempting
to write to a file that was either not opened at all, or was
opened for reading only. This message generally indicates a program error. |
Check the Release Notes section on the SYSPRO InfoZone for possible program corrections. Report this to your distributor or local SYSPRO regional office (see Reporting program errors). |
Cause | Remedy |
---|---|
This message indicates that the program attempted to
open a file that contains an illegal character for the
operating system. This could be any character that is not part of the permitted character set or it could be a system-dependent delimiter, which on most systems is the space character. An example of an illegal file name is TEST FIL.DAT where there is a space between TEST and FIL.DAT. |
Check the Release Notes section on the SYSPRO InfoZone for possible program corrections. Report this to your distributor or local SYSPRO regional office (see Reporting program errors). |
Cause | Remedy |
---|---|
This message indicates that the disk is full.
Every SYSPRO program that writes data, tests the status of the write after it has been performed. There is a common routine in SYSPRO programs to display any message returned from the operating system (including a disk full) and if job logging is enabled, then the status is saved to the log file. |
Exit SYSPRO immediately and notify your System
Administrator. The System Administrator needs to look at the following possibilities to clear disk space:
|
Cause | Remedy |
---|---|
This message indicates that the specified folder does
not exist. This can also be an indication of incorrect permissions on the folder. This occurs if:
|
|
Cause | Remedy |
---|---|
This message indicates that the runtime cannot create
another process because a limit has been reached. One of the following has occurred:
|
|
Cause | Remedy |
---|---|
This message indicates that the file displayed does
not exist, or you do not have permissions to access it.
This can occur if:
|
|
Cause | Remedy |
---|---|
This message generally indicates that you have exceeded an operating system limit that restricts the number of concurrently opened files. | You can run a diagnostic utility (Diagnostics - Max C-iSAM Files) to verify
the maximum number of files that can be opened on the
operating system. This program does not use existing files. Files are created in the Base folder, starting from TST001. We recommend that you remove any previously generated TSTxxx files before starting a new test. |
Cause | Remedy |
---|---|
This message generally indicates that you have exceeded an operating system limit that restricts the number of concurrently opened indexed files. | You can run a diagnostic utility (Diagnostics - Max C-iSAM Files) to verify
the maximum number of files that can be opened on the
operating system. This program does not use existing files. Files are created in the Base folder, starting from TST001. We recommend that you remove any previously generated TSTxxx files before starting a new test. |
Cause | Remedy |
---|---|
This message generally indicates that at least one
record in a C-ISAM file is corrupt or truncated. This error
most commonly occurs when reindexing a file and is caused by
the presence of one or more corrupt records in the file
being accessed. Specifically, a part record has been found at the end of a file. As the reindexing utility does not find a complete record at the end of file, it reports this error. This error usually occurs if a program does not terminate correctly (e.g. a power loss occurs when a file is in use by a program). An important note is that if there is a data corruption in a data file (.DAT) then that can cause all subsequent records to be treated as corrupt. The reason is as follows:
|
|
Cause | Remedy |
---|---|
This message indicates that the program is attempting
to open a C-ISAM file, but a folder with that name already
exists. Alternatively, the file attributes are not set up correctly to allow you to access a file (i.e. it is marked as read-only, or you do not have sufficient permissions to open it). |
Report this to your distributor or local SYSPRO regional office (see Reporting program errors). |
Cause | Remedy |
---|---|
This message indicates that the device is full.
Every SYSPRO program that writes data, tests the status of the write after it has been performed. There is a common routine in SYSPRO programs to display any message returned from the operating system (including a disk full), and if job logging is enabled, then the status is saved to the log file. |
Exit SYSPRO immediately and notify your System
Administrator. The System Administrator needs to look at the following possibilities to clear disk space:
|
Cause | Remedy |
---|---|
This message indicates that the program has attempted
to open an indexed file, but you have exceeded an operating
system limit that restricts the number of concurrently
opened indexed files. Alternatively, the program may be attempting to use a process id that does not exist, or which the operating system no longer recognizes. |
You can run a diagnostic utility (Diagnostics - Max C-iSAM Files) to verify
the maximum number of files that can be opened on the
operating system. This program does not use existing files. Files are created in the Base folder, starting from TST001. We recommend that you remove any previously generated TSTxxx files before starting a new test. Report this to your distributor or local SYSPRO regional office (see Reporting program errors). |
Cause | Remedy |
---|---|
This message indicates that the program has attempted an operation on a file, but the owner of the file has not given you the necessary permission for that operation. |
|
Cause | Remedy |
---|---|
This message indicates that the indexed portion of
the C-ISAM file does not match the data portion. The runtime system does not recognize the control information for an indexed file and as the index is corrupt in some way the data in the file is no longer accessible by the system. |
Report this to your System Administrator so that the file can be reindexed. |
Cause | Remedy |
---|---|
|
|
Cause | Remedy |
---|---|
This message indicates that the program is attempting
to perform a fixed-point divide by zero. This message generally indicates a program error. |
Report this to your distributor or local SYSPRO regional office (see Reporting program errors). |
Cause | Remedy |
---|---|
This message indicates that the program is attempting
to open a file which has been locked exclusively by another
user. Alternatively, the program has attempted to lock a
file exclusively which is already in use by another user.
This typically occurs under one of the following conditions:
|
Check the Release Notes section on the SYSPRO InfoZone for possible program corrections. Report this to your distributor or local SYSPRO regional office (see Reporting program errors). |
Cause | Remedy |
---|---|
This message indicates that the program has attempted
to insert a record with the same key as an existing item.
The primary key is shown for information. If the file has alternate keys, then it is possible that one of these has caused the message to appear. |
Report this to your distributor or local SYSPRO regional office (see Reporting program errors). |
Cause | Remedy |
---|---|
This message indicates that the program has attempted to read a record that is locked by another user. | Most SYSPRO programs will handle this situation
without requiring additional action. Possible remedies include:
Report this to your distributor or local SYSPRO regional office (see Reporting program errors). |
Cause | Remedy |
---|---|
This message generally indicates that the program has exceeded an operating system limit that restricts the number of concurrently opened indexed files. | You can run a diagnostic utility (Diagnostics - Max C-iSAM Files) to verify
the maximum number of files that can be opened on the
operating system. This program does not use existing files. Files are created in the Base folder, starting from TST001. We recommend that you remove any previously generated TSTxxx files before starting a new test. Report this to your distributor or local SYSPRO regional office (see Reporting program errors). |
Cause | Remedy |
---|---|
The message indicates that the program is attempting to use a file which is corrupt, or there is an internal system error. |
Report this to your distributor or local SYSPRO regional office (see Reporting program errors). |
Cause | Remedy | ||||||
---|---|---|---|---|---|---|---|
This message can be caused by one of two actions.
The item key is shown for information so that the support consultants can identify whether the item still exists in the file. |
Report this to your distributor or local SYSPRO regional office (see Reporting program errors). |
Cause | Remedy |
---|---|
This message indicates that the program has attempted to open a file with a null (blank) file name. |
Check the Release Notes section on the SYSPRO InfoZone for possible program corrections. Report this to your distributor or local SYSPRO regional office (see Reporting program errors). |
Cause | Remedy |
---|---|
This message indicates that the runtime system is unable to allocate sufficient memory space to successfully carry out the attempted operation, probably because of insufficient memory space on the system. | You should obtain more memory in which to run the
program. Refer to your operating system documentation for
details of how you can obtain more memory. Check the Release Notes section on the SYSPRO InfoZone for possible program corrections. Report this to your distributor or local SYSPRO regional office (see Reporting program errors). |
Cause | Remedy | ||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
This message indicates that the operating system has
detected a memory access violation. Some of the possible causes include:
|
This error message may be returned by various
programs. Determine if this error message is specific to:
If this error is operator code specific, then possible remedies include:
If this error is operator role specific, then possible remedies include:
If this error is client machine specific, then possible remedies include:
If this error is program/menu specific, then possible remedies include:
Report this to your distributor or local SYSPRO regional office (see Reporting program errors). When reporting this error, provide the following additional information in the error report:
|
Cause | Remedy |
---|---|
This message indicates that a part of the runtime system is unable to allocate sufficient memory to the program. |
Report this to your distributor or local SYSPRO regional office (see Reporting program errors). |
Cause | Remedy |
---|---|
This message indicates that the program is attempting
to access a file that cannot be located, or which does not
exist. This can occur if:
|
Report this to your distributor or local SYSPRO regional office (see Reporting program errors). |
Cause | Remedy | ||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
This message indicates that a subscript which the
program is using is out of the defined range (i.e. it is
either less than one or it is greater than the number of
occurrences of the item). Some of the possible causes include:
|
This error message may be returned by various
programs. Determine if this error message is specific to:
If this error is operator code specific, then possible remedies include:
If this error is operator role specific, then possible remedies include:
If this error is client machine specific, then possible remedies include:
If this error is program/menu specific, then possible remedies include:
Report this to your distributor or local SYSPRO regional office (see Reporting program errors). When reporting this error, provide the following additional information in the error report:
|
Cause | Remedy |
---|---|
This message indicates that the program has used
GO TO to jump out of the range of a
PERFORM rather than to jump to an EXIT
statement at the end of its range. This normally indicates a program error. If you receive this error message on the IMPSTD program, then it might indicate a problem with the SYSPRO installation on the application server. |
Report this to your distributor or local SYSPRO regional office (see Reporting program errors). |
Cause | Remedy | ||||
---|---|---|---|---|---|
This message indicates that either the program is too
large for the available memory space, or the stack is full.
The developer should have specified the ON OVERFLOW/EXCEPTION in the CALL statement. This message generally indicates a program error. |
Report this to your distributor or local SYSPRO regional office (see Reporting program errors). When reporting this error, provide the following additional information in the error report:
|
Cause | Remedy |
---|---|
This message indicates that a program is attempting
to perform an illegal operation on a numeric field.
Possible causes include:
This message generally indicates a program error. |
Report this to your distributor or local SYSPRO regional office (see Reporting program errors). |
Cause | Remedy |
---|---|
This message indicates that the contents of a numeric
or numeric edited field are inconsistent with the picture
definition of that field. This error occurs when the environmental variable COBSW -F is not set. |
Check that the environment variable COBSW
-F is set on the application server and all the
client machines. Report this to your distributor or local SYSPRO regional office (see Reporting program errors). |
Cause | Remedy |
---|---|
This message indicates that the program is attempting
to call a module that is already active. This message generally indicates a program error. |
Check the Release Notes section on the SYSPRO InfoZone for possible program corrections. Report this to your distributor or local SYSPRO regional office (see Reporting program errors). |
Cause | Remedy | ||||
---|---|---|---|---|---|
This message indicates that the program has a
PERFORM statement or a series of
CALL statements nested too deeply.
This message generally indicates a program error. |
Report this to your distributor or local SYSPRO regional office (see Reporting program errors). When reporting this error, provide the following additional information in the error report:
|
Cause | Remedy |
---|---|
This message indicates that the program is attempting
to call another program which cannot be located on the
application server. Possible causes include:
|
Possible remedies include:
Check the Release Notes section on the SYSPRO InfoZone for possible program corrections. Report this to your distributor or local SYSPRO regional office (see Reporting program errors). |
Cause | Remedy |
---|---|
This message indicates that the program is attempting
to remove a currently executing program from memory.
This message generally indicates a program error. |
Check the Release Notes section on the SYSPRO InfoZone for possible program corrections. Report this to your distributor or local SYSPRO regional office (see Reporting program errors). |
Cause | Remedy |
---|---|
This message generally indicates that a file marker
used to indicate that the end-of-file has been reached is
missing from one of the files. Specifically, a part record has been found at the end of a file. As the reindex utility does not find a complete record at the end of the file, it reports error 9-018 or 9-180. |
|
Cause | Remedy | ||||||||
---|---|---|---|---|---|---|---|---|---|
This message indicates that the program cannot locate
the runtime. The runtime can be located using various methods indicated below:
SYSPRO does not set the COBDIR variable, therefore this problem should not arise, but some customers use third party applications that were written in a different version of the development language. These installations use the COBDIR variable.
|
In order to resolve the situation and yet have both
applications run:
Report this to your distributor or local SYSPRO regional office (see Reporting program errors). |
Cause | Remedy | ||||
---|---|---|---|---|---|
This message indicates that the system cannot load a
program module. A CALL statement has failed because:
Possible reasons include:
|
This error message may be returned by various
programs. Determine whether this error message is specific to:
If the error is client machine specific, then possible remedies include:
If this error is program/menu specific, then possible remedies include:
Report this to your distributor or local SYSPRO regional office (see Reporting program errors). |
Cause | Remedy |
---|---|
This is the result of an internal system error. | Contact your System Administrator or Network
Administrator. Check the Release Notes section on the SYSPRO InfoZone for possible program corrections. Report this to your distributor or local SYSPRO regional office (see Reporting program errors). |
Cause | Remedy |
---|---|
This message indicates that a system call has
returned an unexpected error number which is not documented.
It indicates that there is possibly an operating system problem (e.g. permissions, corruption or a bad sector on the hard drive). |
Restart the application server. Report this to your distributor or local SYSPRO regional office (see Reporting program errors). |
Cause | Remedy |
---|---|
This message indicates that the runtime system cannot
locate the root or overlay of a program that is currently
loaded in memory. Alternatively, this could indicate:
|
Possible remedies include:
Report this to your distributor or local SYSPRO regional office (see Reporting program errors). |
Cause | Remedy | ||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
This message indicates that the program is attempting
to use an object reference that contains an incorrect or
non-existent object handle. Some of the possible causes include:
|
This error message may be returned by various
programs. Determine if this error message is specific to:
If this error is operator code specific, then possible remedies include:
If this error is operator role specific, then possible remedies include:
If this error is client machine specific, then possible remedies include:
If this error is program/menu specific, then possible remedies include:
Report this to your distributor or local SYSPRO regional office (see Reporting program errors). When reporting the error provide the following additional information in the error report:
|
SYSPRO running on Microsoft SQL Server is designed for rock-solid data integrity. This is achieved using Transaction Processing - the ability of an application to define a logical business function.
For example: If the General Ledger system requires that both a debit and credit are posted, then this can be defined as a transaction. The BEGIN TRANSACTION and COMMIT/ROLLBACK logic included in SYSPRO programs ensures that both the debit and credit part transactions are applied or (in the case of any problem - including system failure) that neither is applied to the database.
System maintenance requirements are dramatically reduced by using Transaction Processing.
When SYSPRO programs are about to perform a logical business function, they explicitly issue a BEGIN TRANSACTION SQL statement. This informs SQL Server that a transaction is to start.
Any access to the database while the transaction is in progress will cause locks to be acquired by SQL Server. This prevents other processes from accessing the same data - especially ones also inside a transaction.
Other processes trying to access the same data from within a transaction will wait for the transaction to end. This will appear as a small delay in the running of the second and subsequent program.
SYSPRO programs generally do not keep transactions open for a 'long period of time'. For example, a transaction only starts when you select Post or OK in a SYSPRO posting program. SYSPRO programs do not have SQL transactions open while operator input is being requested.
During a transaction it is possible for several problems to occur. These are described in the table below:
Short description of problem | Short explanation of problem |
---|---|
The SYSPRO program detects unexpected data. Some
examples of error messages are:
|
The transaction has started, and then the SYSPRO
program finds an unexpected set of data. The program issues
an explicit ROLLBACK. Any database changes made since the start of the transaction are undone. All locks are released and an appropriate error message is displayed. The job logging details are updated with the transaction status updated to Rolled back. |
The client workstation or network connectivity fails.
Normally a CCITCP2 connection failure error message is
displayed. Common causes of communication problems include:
|
The transaction has started, and then a client
workstation or the network connectivity fails. SQL Server
detects a break in the connection to the database and issues
a ROLLBACK immediately. Any database changes made since the start of the transaction are undone. All locks are released and an appropriate error message is displayed. The job logging transaction status is left as In progress for all open transactions. |
The SQL server or the Windows server fails. | The transaction has started, and then the SQL server
or the Windows server fails. The job logging transaction
status is left as In progress for all open
transactions. The next time SQL Server is loaded (and before anyone can log in) any open transactions are rolled back. |
The server has a hard disk crash. | The transaction has started, and then the hard disk
crashed. The job logging transaction status is left as In
progress for all open transactions. If the SYSPRO database resides on a hard disk that crashed, then once a new disk drive has been mounted, the system administrator can do the following:
SQL Server will then roll back any open transactions that were open at the time of the disk crash. |
SYSPRO makes use of a job logging file to assist in determining SYSPRO system health. When a SYSPRO program starts a transaction, a message is inserted into the job logging file indicating that a transaction has started and stores a short description of the transaction. A transaction status is written to the job logging file:
Status | Description |
---|---|
Normal | The transaction is completed successfully and the program issues a COMMIT statement. This indicates that the transaction is finished and the transaction status is updated to Normal. |
In progress | If an implied ROLLBACK statement was issued by SQL Server itself, then the transaction status is left as In progress. |
Rolled back | The program issued an explicit ROLLBACK statement because of unexpected data. The transaction status is marked as Rolled back and the description of the transaction remains in the job logging file. |
Failed | This status is relevant only in a C-ISAM environment. |
Some locking techniques in a SQL Server environment are:
Optimistic Concurrency Control
Exclusive Locking
There is a system overhead when using Transaction Processing. This includes row locks on the data affected by the transaction together with the transaction logs that have to be maintained.
However, in many instances it is unlikely that data is being changed by multiple users at the same time. For example, it is unlikely that the A/R Terms Code Maintenance program is used regularly. The terms codes certainly don't change every day. Usually it is one operator's responsibility to ensure that the terms codes are correct, so concurrent updates are extremely unlikely.
Optimistic Concurrency Control is a technique that can be used to avoid the system overhead of Transaction Processing.
Optimistic Concurrency Control makes use of the TimeStamp field defined against each SYSPRO table. This field is incremented by the SQL Server system whenever any data is changed in the database. When a specific row is changed the current value of the TimeStamp automatically replaces the previous value for that row.
Therefore, a program can read and save the current value of the TimeStamp against the item being accessed. When/if the user attempts to save any changes, the program can compare the latest value of the TimeStamp for that row with the saved value. If they are the same then the update can take place (as no other change can have taken place since the original TimeStamp value was read) otherwise the operator is informed that the data cannot be updated due to changes having been applied by another user.
In this case no locks are acquired at all and in the event of a program failure there is no lock to be released.
Many of the SYSPRO browse and maintenance programs take advantage of this technique when an operator changes data. Note that posting programs always use Transaction Processing.
Relatively few SYSPRO programs require exclusive use of a table. Examples include period and month-end programs.
These programs will acquire an exclusive table lock on the tables required before the processing starts. This is done inside a transaction. This prevents others from accessing the tables while the transaction is in progress.
SYSPRO programs that attempt to obtain exclusive table locks first verify whether any logged-in SYSPRO operator is using a program that may attempt to access the tables that need locking. A list of operators is displayed and what they were doing when the verification took place.
The operator can either try again later or may contact the other operators and ask them to exit SYSPRO. You can use the Refresh function to verify how many operators are still using the tables required. If all of them exit then you will be able to continue with the desired function.
Do not use the Logout Users option unless you are sure that the other operators are no longer using the table(s). Your process may fail later if you attempt to log out operators prematurely.
If a program fails that has attracted an exclusive lock, then the transaction is rolled back and the exclusive table locks are released.
You need to define the financial year and period for a module before you can continue processing in the module.
Open the Setup Options program.
Indicate the SYSPRO company to review.
Using the Financial Periods category, indicate the required period end dates for each module.
Save the changes.
You typically check the data path file definition in a C-ISAM environment when you receive a Control record not yet created message while attempting to post a transaction in one or more of the modules.
Open the Company Maintenance program.
Select the SYSPRO company to check.
Verify the data file path definition from the Database tab.
Use the System Setup program to correct a blank or incorrect file path definition.
Disabling the SYSPRO Calendar Control may resolve a memory conflict that appears to occur between the Calendar Control and the Word Printing program. This conflict results in an 9-114 Attempts to access items beyond bounds of memory error when printing Word documents in SYSPRO.
Open the SYSPRO Personalize program.
From the Calendar tab, set the Calendar data provider option to None.
Central data storage and speed of access play a huge role in business today.
Data access can become a bottleneck if servers are pushed to the limit. Three important factors must be taken into consideration:
Available memory.
The number of processors (CPUs).
The speed of the processors.
In some instances, a single server may lack the necessary resources to run both SYSPRO and SQL on the same server - hence the need for a 3-tier configuration.
In a 3-tier environment, SYSPRO and SQL (database) reside on separate servers to provide more resources in terms of distributed memory and processor power.
To implement a 3-tier configuration you must address certain security issues. Failure to implement the correct security settings will prevent the BCP process (Bulk Copy Process) from running. The BCP process is used when converting a company from C-ISAM to SQL and when running the Requirements Calculation program.
The following security steps need to be implemented once SYSPRO has been installed:
Create a Domain user account in Active Directory on the SYSPRO application server.
This account will be used to start the SYSPROIMP7 service on the application server. This must not be a Local user account.
Configure the SYSPROIMP7 service on the application server to log on and start as this Domain user account.
Ensure that this Domain user account has full permissions to the SYSPRO folder and sub folders on the SYSPRO application server.
Create and share a folder on the SQL server.
This folder is used as the temporary storage area during the BCP process.
Set the security and sharing on this folder to full control for the Domain user account you created on the SYSPRO application folder.
Maintain each SYSPRO company, entering the SQL username and password you want to use for the BCP process. You also need to enter the full path of the shared folder on the SQL server.
The SQL username must be a member of the Bulkadmin server role (in SQL 2005) or the Bulkinsertadministrator server role (in SQL 2000).
When reporting a problem to your distributor or local SYSPRO regional office, please adhere to the following guidelines:
Ensure that you have full details of your system, including the:
Licensed company name
Operating system and Operating system version
Mapped, client/server and/or terminal server environments
Version of software (Issue and number of ports)
C-ISAM or SQL (version of SQL).
If the problem is specific to a certain program:
Check the Release Notes section on the SYSPRO InfoZone for possible program corrections.
Record the program name and version (run the program and press Shift+F7).
If an error message is displayed:
Record the error number and other details shown (preferably with a screenshot).
Determine whether the error is repeatable and what sequence of steps is required to duplicate the problem.
Refer to specific guidelines and additional information required for specific error messages in the SYSPRO Error Messages guide.
This will help your distributor and/or local SYSPRO regional office to answer your questions as quickly as possible.
If a run time system (RTS) error occurs on a client workstation, an error message is displayed and a log file is generated in the Settings folder on the client. The file is named ADMIN_RTS_ERROR.TXT, where ADMIN refers to the operator code.
The log file includes information from the error message as well as additional information about the environment (e.g. operating system, company, operator role, operator). The information is designed to assist support personnel in diagnosing the problem.
In addition, up to 10 messages are written to the log file indicating the last functions performed in the user interface before the RTS error occurred. These additional messages are output only if the program that caused the RTS error is a user-control program (running from Bin). The additional information is not included for other errors.
If a run time system (RTS) error occurs on the server, then the program that trapped the RTS error generates a log file in the Settings folder on the server. The file is named ADMIN_RTS_ERROR.TXT, where ADMIN refers to the operator code.