Skip to main content

Troubleshooting Schedule Release Errors

Michael Dirne
  • Updated

You may run into errors that look like this when releasing a schedule from FeneVision CORE:

General Troubleshooting

There is usually a problematic line item that is causing the schedule release to fail. The first step is to split up the schedule into smaller schedules to narrow down the problematic line item. Start by splitting the schedule in half, then keep releasing and splitting the schedules until you encounter the error. The line item is often:

  • A new part just added to Core
  • A part never scheduled before, or rarely ordered
  • A unique or uncommon type of product with an unusual shape or options

Once you narrow down the problematic item, send a screenshot of the schedule release error message along with the order and line item numbers to support@fenetech.com. If the situation is urgent, follow up with a phone call to support (330-995-2830).

Specific Errors

Glass part has not been assigned to racks for these items

This checklist helps with troubleshooting this error:

1) H, W and T attributes must exist on glass part in the BOM. Generate a Part Breakdown to see if the glass part has these attributes.
2) SEQ attribute that is set in work route setup must exist on glass part in the BOM and must be set as released to production.
3) The work route attribute must return a valid value and must be released to production. This attribute must be located at the ordered part level in the BOM.
4) The work cell attribute for cutting must return a valid value and must be released to production. This attribute must be on the glass part level of the BOM.
5) The thickness of the glass part must be set in inventory setup.
6) The glass part type configured in work route setup must be assigned to the glass part being returned by the bill of material (the actual inventoried part, not the dynamic part).
7) Check ‘Secondary Rack’ in Work Route Setup. Case: Cut work cell had a primary rack assigned, but it didn’t have a secondary rack assigned in Work Route Setup.

 

ERROR: Divide by zero error encountered. The statement has been terminated.

There is most likely a part on the schedule that does not have a Thickness set in Inventory Setup.

 

Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

Typically, this means that data processing took too long on the database server. You can try:

  • Releasing the schedule directly on the database server, instead of a client PC, to eliminate networking factors.
  • Splitting the schedule up into smaller releases, to reduce the data processing load.
  • Some portions of these articles may be applicable depending on your situation: 

Additional Tips

  • BOM configuration changes between order entry and schedule release can cause problems. 

    • The system validates that the FVMaster database tables OrderDetailParts, OrderDetailAttributes, and ProdCustomDetails are in sync. If BOM or edgework config was changed between when the order was entered and when the schedule is released, you'll get errors like: 

      "Glass part MasterKey=X and ParentKey=Y from ProdDetails does not exist in OrderDetailParts"

      "Edgework attributes exist in OrderDetailAttributes but not in ProdCustomDetails" (or vice versa)

      The fix is to pull back the order and re-enter it (or reconfigure the options/BOM and re-finalize) so the tables are back in sync.

  • If your company uses Opti-Glass, your schedules are probably being automatically imported into Opti-Glass when released from Core. The import script that handles this step could be custom for your company and may run into unexpected problems that FeneTech cannot test for during software development. The SQL stored procedure responsible for this import will be called something like uspx_optiglassImportSchedule in the FVMaster database, or uspx_Fenevision_ImportSchedule in the FVOptiGlass database.

Related articles