Troubleshooting APS

You might encounter the following error messages when running APS Planning or when performing the ATP/CTP function and incremental planning. You should be able to diagnose and fix these errors using the solutions described below. To find a particular error message below, press Ctrl + F to open the Find dialog and search for the message.

If a documented solution does not fix the problem, contact Infor Technical Support.

Errors may appear in one or more of these places in the system:

Activity or Process	Error Type	Location
Get ATP/CTP	Error	Error message displayed on the form when you click the Get ATP/CTP button.
Planning activity: preprocessing, planner database reload, or core planning algorithm processes	Error	Background Task History form (Task Messages tab).
Planning activity or Get ATP/CTP: preprocessing, planner database reload, or core planning algorithm processes--additional detail	Error	ERRORLOG table in application database.
Planning activity or Get ATP/CTP: preprocessing, planner database reload, or core planning algorithm processes--additional detail	Error	apserror.txt file (located on the machine where the Planning and Scheduling Service is installed--usually in c:\winnt\system32).
Planning activity or Get ATP/CTP: core planning algorithm processes--additional detail. Available after planning algorithm completes.	Error	ol_error.txt file (located on the Planning server machine--usually in ..\projects\`database name`\\ol_log under your Planning Server installation or on the machine where the Planning and Scheduling Service is installed--usually in c:\winnt\system32).
Planning activity or Get ATP/CTP: problems related to a parameter causing a date to exceed the Plan Horizon, information about demands being blocked, and other assorted messages etc. Available after planning algorithm completes.	Error, Warning, or Informational	ol_sched.txt file (located on the Planning server machine--usually in ..\projects\`database name`\ol_log under your Planning Server installation).

Note: Errors from the CloudSuite Industrial Scheduler are logged in the TRACELOG table in the CloudSuite Industrial application database.

This topic describes the Get ATP/CTP, Background Task History, ERRORLOG, and the View Planning Messages form messages.

Get ATP/CTP Messages

The errors listed in the table below appear when you click the Get ATP or Get CTP button on certain CloudSuite Industrial transactions.

Error Message	Explanation and Solution
Availability request requires a demand quantity greater than zero.	You cannot perform Get ATP/CTP on a demand that has a quantity of zero. For example, a customer order line's demand quantity = Qty Ordered - Qty Reserved - Qty Shipped. A forecast's demand quantity = Outstanding Requirement.
A batch planning run is in progress. Please try again later.	Another client session is running the APS Planning activity. Wait a few minutes and try again.
Cannot be completed within the current planning horizon.	The system did not find sufficient capacity or material to plan an order within the time period specified in the Plan Horizon field (on the Planning Parameters form). You can try reducing the quantity, using a later Due Date, or adding new resource capacity to allow the demand to be planned. Sometimes this error occurs if the resources in a resource group are on mutually exclusive shifts and the operation requires all of those resources.
Cannot retrieve planner connection information for the specified alternative.	The alternative 0 record specified in Planning Parameters does not specify valid planner database connection information (port #, host name, etc.).
Configured items must be cross-referenced to a job.	You performed the Get ATP/CTP function for a configured order line, but the order line was not cross-referenced to a job. In order to get an ATP or CTP date for a configured item, the item must be cross-referenced to a job.
Forecasts for MPS items must be planned using the MPS Processor.	When you enter a forecast for an MPS item on the Forecasts form, the Get ATP/CTP process does not plan the forecast; to plan this demand, you must run the MPS Processor.
Flush of gateway table is in progress. Please try again later.	The APS Planning activity was running when the Get ATP/CTP process tried to run it. Wait a few minutes and try again.
Flushing of the gateway table was unsuccessful. See ERRORLOG table for details.	Check the ERRORLOG table in the SQL database. Find the detailed error message in the ERRMSG column. ERRORLOG messages are described below in the ERRORLOG Messages section.
Item not found in planning database.	There are two possible causes: You recently created this item on the Items form, but have not run the APS Planning activity since you created the item. You must run the APS Planning activity to insert the new item into the planner database. The item you are planning was not sent to the planner database during the Get ATP/CTP process. Check the Windows Services program to make sure the Gateway service is running. See the CloudSuite Industrial Installation Guide for information about starting the Gateway service.
Job (number) does not exist.	You performed the Get ATP/CTP function for an order line that is cross-referenced to a job, but the job did not exist in CloudSuite Industrial.
Network communications error.	At some point in the planning or scheduling process, a network connection was lost. There are three possible causes: The site parameters on the Planning Parameters form are not set correctly. Make sure you specify the same Planner Database Port number with which you start the planner database. Your planner database is not running. Use the Planner Manager utility to start the database. There is an operating system configuration, hardware, or network problem.
Out of memory.	The planner database server does not have enough available system resources to run the program. Close any unnecessary applications or add more memory to the server.
Planner database is marked as down.	The planner database specified for the alternative 0 record (in Planning Parameters) is not running. Verify that the database is running in Planner Manager. Then check the ERDB.STATUS field in the SQL database. If the value is -1, change it to 0 to clear the planner database status.
Planner database reload in progress. Please try again later.	Another client session may have been running the APS Planning activity or a Get ATP/CTP process. Wait a few minutes and try again.
The cross-referenced job is already scheduled.	You performed the Get ATP/CTP function for an order line that is cross-referenced to a job, and the job has already been scheduled (it has a status other than Firm). CloudSuite Industrial moves the job's End Date to the order line's Projected field and disables the Get ATP/CTP button.
There already exists a key with that value.	Make sure your ol_schema.txt file includes the correct character width allocation for the indicated database field. If a database field has more characters than are allocated in the ol_schema.txt file, the system truncates the field, which can cause duplicate IDs. See the CloudSuite Industrial Installation Guide for more information about correctly sizing the ol_schema.txt file.
Unable to connect to APS Server.	The APS Server Service Port number specified in Planning Parameters is not valid. Check the Windows Services configuration to verify the port number on which the APS Server Service is running, and correct the entry in Planning Parameters.
Unable to connect to Planner Database Server.	The planner database host machine specified in Planning Parameters was not found or was down.
Version mismatch	The server and client (or DLL) are not compatible software versions. Contact Technical Support.
The firm job for which you are about to check availability may have recently been converted from a PLN with no planning run since its conversion. Under these circumstances, the availability check will return a conservative Projected Date. Use caution if you use the new Projected Date information to change your job End Date. However, if this job was not generated from a PLN, the availability check will be proper. Do you wish to proceed?	If the job on which you are performing Get ATP/CTP was firmed from a planned order, the information is already in the plan and capacity is allocated. If you check availability for this job, you are essentially "double-counting" it, which will result in an artificially conservative Projected date. Click Yes if you are comfortable with this fact. If you do not want to check availability for this job now, click No (and then try it again later after the next run of the APS Planning activity).

Background Task History Messages

The errors listed in the table below appear with the Planning task on the Background Task History form.

Error Message	Explanation and Solution
ApsPlan: Error -30000 running the Planner. Network communications error.	At some point in the planning or scheduling process, a network connection was lost. There are three possible causes: The site parameters on the Planning Parameters form are not set correctly. Make sure you specify the same Planner Database Port number with which you start the planner database. Your planner database is not running. Use the Planner Manager utility to start the database. There is an operating system configuration, hardware, or network problem.
ApsPlan: Error -30001 running the Planner. Network communications setup error.	The process was not able to connect to the Planning and Scheduling Service. Check the Windows Services application to make sure apssrvr.exe is running and that TCP/IP is configured correctly on this machine.
ApsPlan: Error -30002 running the Planner. Cannot resolve host address.	The process was not able to connect to the host machine that is specified in the Planning and Scheduling Service configuration.
ApsPlan: Error -30003 running the Planner. Version mismatch.	The server and client (or DLL) are not compatible software versions. Contact Technical Support.
ApsPlan: Error -30004 running the Planner. Registry access error.	The process was not able to retrieve connection information from the machine's Windows registry. The machine's registry permissions might not be set up correctly, or some of the registry files may have been deleted.
ApsPlan: Error -30005 running the Planner. Error connecting to SQL database.	The process was not able to connect to the SQL database specified in the Planning and Scheduling Service configuration. Make sure the SQL Server Service is running on the SQL Server and that the database exists and is specified correctly in the Planning and Scheduling Service configuration.
ApsPlan: Error -30006 running the Planner. Error in SQL query.	There is an error in the system code or the database schema. Contact Technical Support.
ApsPlan: Error -30007 running the Planner. Alternative not found.	The alternative "0" specified in Planning Parameters was not found in the SQL database. Reenter the alternative 0 record on the Planning Parameters form.
ApsPlan: Error -30010 running the Planner. Cannot retrieve planner connection information for the specified alternative.	The alternative 0 record specified in Planning Parameters does not specify valid planner database connection information (port number, host name, etc.).
ApsPlan: Error -30011 running the Planner. Error connecting to Planner Database Server.	The planner database host machine specified in Planning Parameters was not found or was down.
ApsPlan: Error -30012 running the Planner. Planner API returned error.	Check apserror.txt to find the specific Planner API call and its return code.
ApsPlan: Error -30013 running the Planner. Planner database reload in progress, API call aborted.	Another client session may have been running the APS Planning activity or a Get ATP/CTP process. Wait a few minutes and try the task again.
ApsPlan: Error -30014 running the Planner. Planner database is marked as down.	The planner database specified for the alternative 0 record (in Planning Parameters) is not running. Verify that the database is running in Planner Manager. Then check the ERDB.STATUS field in the SQL database. If the value is -1, change it to 0 to clear the planner database status.
ApsPlan: Error -30016 running the Planner. Planner database reload was unsuccessful. See the ERRORLOG table for details.	Check the ERRORLOG table in the SQL database. Find the detailed error message in the ERRMSG column. ERRORLOG messages are described below in the ERRORLOG Messages section.
ApsPlan: Error -30018 running the Planner. The Planner is currently running for the specified alternative.	The APS Planning activity was running or another client session was accepting the Projected date during a Get ATP/CTP process. Wait a few minutes and try again. If the error persists, verify that the APS Planning activity is not running. If the APS Planning activity is not running, check the ERDB.STATUS field in the SQL database. If the value is 2, change it to 0.
ApsPlan: Error -30019 running the Planner. Generation of planned orders was unsuccessful. See ERRORLOG table for details.	Check the ERRORLOG table in the SQL database. Find the detailed error message in the ERRMSG column. ERRORLOG messages are described below in the ERRORLOG Messages section.
ApsPlan: Error -30020 running the Planner. Flushing of the gateway table was unsuccessful. See ERRORLOG table for details.	Check the ERRORLOG table in the SQL database. Find the detailed error message in the ERRMSG column. ERRORLOG messages are described below in the ERRORLOG Messages section.
ApsPlan: Error -30029 running the Planner. Flush of gateway table in progress, API call aborted.	The APS Planning activity was running when the TaskMan service tried to run it. This error means that the system thinks a Planning function is already running, specifically the flushing of information between the CloudSuite Industrial SQL database and the planner database. This situation can occur if the function had been interrupted for some reason and was unable to reset its status. The solution is to reset the STATUSNO column to 0 (zero) in the ERDB table of the CloudSuite Industrial SQL database.
ApsPlan: Error -30031 running the Planner. Cannot retrieve site connection information for one of the sites.	The data in the APSSITE table for a site defined in the Planning Parameters form is missing or invalid.
ApsPlan: Error -30032 running the Planner. Error connecting to APS Server.	The APS Server Service Port number specified in the Planning Parameters form is not valid. Check the Windows Services configuration to verify the port number on which the APS Server Service is running, and correct the entry in Planning Parameters.
ApsPlan: Error -30034 running the Planner. Planner database host or port does not match site information.	The planner database host and/or port (in the APSSITE table) specified at the local site does not match what is defined at the remote site.
ApsPlan: Error -30035 running the Planner. Error starting global planner run.	Check apserror.txt for more detailed error messages.
ApsPlan: Error -30036 running the Planner. Error ending global planner run.	Check apserror.txt for more detailed error messages.
ApsPlan: Error -30037 running the Planner. ApsSchedulerStartSp returned an error.	For more detailed error messages, check apserror.txt or run this query: EXECUTE dbo.ApsSchedulerStartSp 0, -1
ApsPlan: Error -30038 running the Planner. ApsPlannerStartSp returned an error.	For more detailed error messages, check apserror.txt or run this query: EXECUTE dbo.ApsPlannerStartSp 0, 2, '*', -1
ApsPlan: Error -30039 running the Planner. Add alternative failed, API call aborted.	Check apserror.txt for more detailed error messages.
ApsPlan: Error -30040 running the Planner. Alternative already exists.	Specify a different alternative number.
ApsPlan: Error -30041 running the Planner. Alternative not a valid number, check value or license.	Specify an alternative number between 1 and 999.
ApsPlan: Error -30043 running the Planner. A remote site definition is missing.	Verify that all of your transfer items have a valid site specified.

ERRORLOG Messages

The errors listed in the table below appear in the ERRORLOG table in the CloudSuite Industrial SQL database. These errors include an error code in the ERRPROC column that indicates the area in the system that created the error. These codes are described below:

RELOAD: The error occurred during a bulk reload of all SQL tables to the planner database.
GWP: The error occurred while the Gateway Processor service was transferring data from the SQL tables to the planner database.
API: The error occurred while the system was calling a command from the APS Server Service.

In the list of errors below, the [%s] codes represent actual ID data that will appear in the message (such as an item or order ID).

General Message (ERRMSG column)	Error Function (ERRFUNC column)	Error Code (ERRCODE column)	Description
Order record does not exist for scheduled operation at [%s] for order [%s] and resource [%s]	N/A	N/A	The order listed in the SCHEDOP record does not exist in the ORDER table in the CloudSuite Industrial SQL database. Contact Technical Support.
Unable to add shift [%s] Unable to add calendar [%s] Unable to add offshift [%s] Unable to add overtime shift [%s]	ol_cadd_shift	-100	Invalid value for shift.
		-5	The shift, shift exception, or holiday already exists ("calendar" in the error message refers to a Holiday definition in CloudSuite Industrial).
		-12	The planner database field is full. Increase the width or depth for the Shift field in the ol_schema.txt file.
Unable to add scheduled operation at [%s] for order [%s] and resource [%s]	ol_cadd_frozensch	-12	When attempting to allocate resources to firm demands, the planner database field is full. Increase the width or depth for the Schedule field in the ol_schema.txt file.
Unable assign a priority to site [%s]	ol_cadd_seqsite	-4	The site priority list index is not valid.
Unable to assign BOM [%s] to finished material [%s]	ol_cadd_prt22bom	-1	When trying to add a bill of material to an item. The item was not found in the database.
		-2	The bill of material was not found in the database.
		-4	The item-bill of material list index was not found in the database.
		-12	The planner database field is full. Increase the width or depth of the Prt22Bom field in the ol_schema.txt file.
		-18	Recursive bills of material are not allowed. Make sure the item is not a component of itself, either directly or through a subcomponent.
Unable to assign component material [%s] to BOM [%s]	ol_cadd_bom22prt	-1	When trying to add an item to a bill of material, the bill of material was not found in the database.
		-2	The item was not found in the database.
		-4	The bill of material-item list index is invalid.
		-12	The planner database field is full. Increase the width or depth of the Bom22Prt field in the ol_schema.txt file.
		-18	Recursive bills of material are not allowed. Make sure this task does not make the item a component of itself, either directly or through a subcomponent.
Unable to assign date range [%s] through [%s] to calendar [%s] Unable to assign date range [%s] through [%s] to offshift [%s] Unable to assign date range [%s] through [%s] to overtime shift [%s] Unable to assign timeslot [%s] to shift [%s]	ol_cadd_shfavailable	-1	When adding a range of dates to a shift, shift exception, or holiday, the shift ID to be changed was not found in the database.
		-12	The planner database field is full. Increase the width or depth of the ShfAvailable field in the ol_schema.txt file.
		-23	The shift, holiday, or shift exception has an invalid time or duration.
Unable to assign jobstep [%s] to process plan [%s]	ol_cadd_rte22opr	-1	When adding an operation to a routing, the routing was not found in the database.
		-2	The operation was not found in the database.
		-4	The routing-operation list index is invalid.
		-12	The planner database field is full. Increase the width or depth of the Rte22Opr field in the ol_schema.txt file.
Unable to assign local material [%s] to remote site [%s]	ol_cadd_prt22sit	-1	When adding a supply site definition to an item, the item was not found in the database.
		-2	The remote supply site's Site/Entities record was not found in the database.
		-4	The item-site list index is invalid.
		-12	The planner database field is full. Increase the width or depth of the Prt22Sit field in the ol_schema.txt file. Should be set to the total number of part/remote site configurations.
Unable to assign local order [%s] to remote order [%s]	ol_cadd_xfrparent	-1	When adding information about a parent demand to a planned demand transfer order at the supply site, the parent demand was not found in the database.
Unable to assign local order [%s] to remote order [%s]	ol_cadd_xfrparent	-2	The planned demand transfer order does not exist.
Unable to assign outsourced material [%s] to order [%s]	ol_cadd_ord22prtpur	-1	When adding a purchased item to the order, the order was not found in the database.
		-2	The purchased item was not found in the database.
		-4	The order-item list index is invalid.
		-12	The planner database field is full. Increase the width or depth of the Ord22PrtPur field in the ol_schema.txt file.
Unable to assign process plan [%s] to material [%s]	ol_cadd_prt22rte	-1	When adding a routing to an item, the item was not found in the database.
		-2	The routing was not found in the database.
		-4	The item-routing list index is invalid.
		-12	The planner database field is full. Increase the width or depth of the Prt22Rte field in the ol_schema.txt file.
		-24	The routing is being used by another item.
Unable to assign remote order [%s] to local order [%s]	ol_cadd_xfrchildren	-1	When creating a cross-reference record between a planned demand transfer order and its parent demand order, the parent demand was not found in the database.
		-2	The planned demand transfer order does not exist.
		-4	The order-remoteorder list index is invalid.
		-12	The planner database field is full. Increase the width or depth of the XfrChildren field in the ol_schema.txt file.
Unable to assign resource [%s] to offshift [%s] Unable to assign resource [%s] to overtime shift [%s]	ol_cadd_shf22res	-1	When assigning a resource to a shift exception, the shift was not found in the database.
		-2	The resource was not found in the database.
		-4	The shift-resource list index is invalid.
		-12	The planner database field is full. Increase the width or depth of the Shf22Res field in the ol_schema.txt file.
Unable to assign resource [%s] to resource group [%s]	ol_cadd_cat22res	-1	When assigning a resource to a resource group, the resource group was not found in the database.
		-2	The resource was not found in the database.
		-4	The resource group-resource list index is invalid.
		-12	The planner database field is full. Increase the width or depth of the Cat22Res field in the ol_schema.txt file.
Unable to assign resource [%s] to shift [%s]	ol_cadd_res22shf	-1	When assigning a resource to a shift, the resource was not found in the database.
		-2	The shift was not found in the database.
		-4	The resource-shift list index is invalid.
		-12	The planner database field is full. Increase the width or depth of the Res22Shf field in the ol_schema.txt file.
Unable to assign resource group [%s] to jobstep [%s]	ol_cadd_opr22cat	-1	When assigning a resource group to an operation, the operation was not found in the database.
		-2	The resource group was not found in the database.
		-4	The operation-resource group list index is invalid.
		-12	The planner database field is full. Increase the width or depth of the Opr22Cat field in the ol_schema.txt file.
Unable to assign token [%s] to remote order [%s] in planner database's OrderDashPart table	ol_cadd_orderdashpart	-100	Invalid value for the local order ID (which is part of a cross-reference record to associate the original demand to the planned transfer demand order at the supply site).
	ol_cadd_orderdashpart	-12	The planner database field is full. Increase the width or depth of the OrderDashPart field in the ol_schema.txt file.
Unable to create remote order [%s] for local order [%s]	ol_cadd_remoteorder	-100	When creating the cross-reference between a planned demand transfer order and its parent demand order, the planned demand transfer order was not found in the database.
Unable to create remote order [%s] for local order [%s]	ol_cadd_remoteorder	-12	The planner database field is full. Increase the width or depth of the RemoteOrder field in the ol_schema.txt file.
Unable to include material [%s] on material delivery order [%s] Unable to include material [%s] on order [%s]	ol_cadd_ordlineitem	-1	When adding an item to a demand (purchase order, job, etc.), the demand was not found in the database.
		-2	The item was not found in the database.
		-4	The demand-item list index is invalid.
		-12	The planner database field is full. Increase the width or depth of the OrdLineItem field in the ol_schema.txt file.
Unable to transfer BOM [%s]	ol_cadd_bom	-5	When sending a bill of material to the ERDB, the bill of material already exists.
Unable to transfer BOM [%s]	ol_cadd_bom	-12	The planner database field is full. Increase the width or depth of the BOM field in the ol_schema.txt file.
Unable to transfer configuration parameters to the planner database.	ol_cedt_misc	-101 through -126	A parameter on the Planning Parameters form is invalid (these errors are unlikely to occur; contact Technical Support).
Unable to transfer effectivity [%s]	ol_cadd_effectivity	-5	When sending an effectivity record to the planner database, the effectivity already exists.
Unable to transfer effectivity [%s]	ol_cadd_effectivity	-12	The planner database field is full. Increase the width or depth of the Effectivity field in the ol_schema.txt file.
Unable to transfer jobstep [%s]	ol_cadd_operation	-5	When creating an operation, the operation ID already exists.
Unable to transfer jobstep [%s]	ol_cadd_operation	-12	The planner database field is full. Increase the width or depth of the Operation field in the ol_schema.txt file.
Unable to transfer material [%s]	ol_cadd_part	-5	When sending an item to the planner database, the item ID already exists.
Unable to transfer material [%s]	ol_cadd_part	-12	The planner database field is full. Increase the width or depth of the Part field in the ol_schema.txt file.
Unable to transfer material delivery order [%s] Unable to transfer order [%s]	ol_cadd_order	-5	When sending a demand (such as a purchase order, job, etc.) to the planner database, the demand ID already exists.
	ol_cadd_order	-12	The planner database field is full. Increase the width or depth of the Order field in the ol_schema.txt file.
Unable to transfer order priority rule [%d]	ol_cadd_seqruletype	-12	The planner database field is full. Increase the width or depth of the SeqRuleType field in the ol_schema.txt file.
Unable to transfer process plan [%s]	ol_cadd_route	-5	When sending a routing to the planner, the routing ID already exists.
		-12	The planner database field is full. Increase the width or depth of the Route field in the ol_schema.txt file.
		-103	When sending demands to the planner database, the system is unable to send routings and BOMs. Search the product knowledge base at our support web site for the solution to this problem or contact Support.
Unable to transfer resource [%s]	ol_cadd_resource	-5	When sending a resource to the planner database, the resource ID already exists.
Unable to transfer resource [%s]	ol_cadd_resource	-12	The planner database field is full. Increase the width or depth of the Resource field in the ol_schema.txt file.
Unable to transfer resource group [%s]	ol_cadd_category	-5	When sending a resource group to the planner database, the resource group ID already exists.
Unable to transfer resource group [%s]	ol_cadd_category	-12	The planner database field is full. Increase the width or depth of the Category field in the ol_schema.txt file
Unable to transfer site [%s]	ol_cadd_site	-5	When sending a site record to the planner database, the site ID already exists.
Unable to transfer site [%s]	ol_cadd_site	-12	The planner database field is full. Increase the width or depth of the Site field in the ol_schema.txt file.

View Planning Messages Form Errors

Error Message	Explanation and Solution
WARNING: Routing not found, planning using lead time instead	The item does not have a routing; the system planned it using the item's standard lead time.
BLOCKED: Unsatisfied resource combinations for operation	The operation required more resources than are available from this resource group. The system planned the operation using all available resources from the group and continued planning.
BLOCKED: Line item 1 cannot be planned	The item number refers to the sequencing of end item processing for Order Maximum groupings for the indicated order.