The following messages may appear in the label update report:
Publication xxxxxx: Attempting to serve the yyyyyy issue. It seems like that issue is too far in the future. Check that the current issue is set properly.
This error message appears in the update report if you try to run the issue labels update for an issue that is more than one issue into the future. Usually this is a mistake but in some situations you may find that you actually need to run an issue unusually early. To accommodate such needs there is a checkbox on the 'Issue Labels Update' screen that lets you bypass QuickFill's built-in issue date check and run issues with dates that are far into the future.
Publication xxxxxx: Audit data file yyyyyy for issue #nnn is from an incompatible version of QuickFill.
You may see this error if you have restored an audit galley data file that was created by an older version of QuickFill without also restoring the associated database. To remedy the problem restore the galley data files and the QuickFill database together into a new folder, then open the old database using the current version of QuickFill. QuickFill will detect the old database version and will offer to upgrade it together with its associated audit galley data files.
Publication xxxxxx: The qualification data fields contained in xxxxxx do not match the publication's current qualification form.
Making changes to your qualification form may result in a mismatch between the fields in the most recent audit galley data file and the publication's current qualification form. If QuickFill needs to record the serving of a back issue copy in an existing audit galley data file then this error message appears in the update report and QuickFill will not run an issue label update until the audit galley data file has been regenerated. For more information concerning this problem contact technical support.
Publication xxxxxx: Audit data file xxxxxx for issue #nnn is missing the xxxxxxx field
It should not be possible to encounter this error unless you have manually edited the audit galley data file to remove one or more of the fixed (non-qualification data) fields. If that is not the case, please call CWC's Technical support who will help you investigate the problem.
Publication xxxxxx: No current issue - can't process publication
The current issue has not been marked in the publication's issue table. Open the 'Issues' definition screen and set the current issue pointer.
Publication xxxxxx: Calendar date of current issue is blank - can't process publication
Every issue in the issue table must have the calendar date field filled in. Since QuickFill currently will not let you define an issue without a calendar date, you should only see this error message in very old databases that were created in early versions of QuickFill for DOS.
Publication xxxxxx: Can't find audit data file xxxxxx for issue #nnn
You might see this error message if you have copied the QuickFill database files without also copying the associated audit galley data files. All files with the .qfdat extension should be backed up, restored or copied as a whole, never individually. To remedy this problem you will need to copy the audit galley data file from a backup copy. If you cannot find the audit galley data file then you will need to regenerate it. See the topic 'Regenerate galley data file' for more information.
Publication xxxxxx: The audit data file xxxxxx for issue #nnn contains no records that match the date of the most recent issue label update.
The records in audit galley data files are time stamped. QuickFill verifies that the time stamp in the galley data file matches the 'Update date' on the issue definition screen. If you see this error message then the most likely cause is that you have restored the database from a backup copy without also restoring the associated audit galley data file. All files with the .qfdat extension should be backed up, restored or copied as a whole, never individually.
nnnnn subscriptions were reclassified as nonqualified because their qualification data was more than three years old
nnnnn subscriptions were reclassified as association/group/directory because their qualification data was more than three years old
For an audited publication the 'Issue labels' update automatically reclassifies non-paid qualified subscribers who are more than three years old. For ABC or BPA-audited business publications they are changed to "Nonqualified other". For VAC-audited publications they are changed to "Non-paid association". ABC audited magazines have slightly more relaxed rules: only verified individual request subscriptions (VI with request type INR), and NPI (non-paid individual), NPL (non-paid list source), NPA (non-paid association) and NPM (non-paid club membership) subscriptions are subject to reclassification under the three year rule. QuickFill determines the qualification age of a subscriber based on the difference between the calendar date of the current issue and the subscriber's qualification date.
Warning: Expiring paid bulk subscription: Order: nnnnnn Copies: nnn
Paid bulk subscriptions for large numbers of copies can cause alarming dips in circulation if they are allowed to expire. This message serves to alert you of such an event so that you can take action if needed.
****** nnn labels skipped because the customer record had been deleted
****** nnn bills skipped because the order or customer record had been deleted
****** nnn renewals skipped because the order or customer record had been deleted
The above messages can occur if you run the issue label update in "shared" mode where you or other users are permitted to enter transactions while the update is running. In very rare circumstances it is possible for a customer or subscription to be removed from the database after the subscription has been selected for processing and before the issue label, bill or renewal has been produced. Since you have removed the customer or subscription record you probably did not intend that they should receive an issue anyway.
Order: nnnnnn Can't autorenew controlled orders
A controlled order was accidentally assigned to renewal series that is marked for automatic renewal. You should adjust the order to assign it to a more suitable renewal series.
Order: nnnnnn Expiration issue for subscription is not in table
You need to add issues to the table. Because you haven't defined enough issues, QuickFill replaced the expiration issue date on the label by a row of Xs. Once you add issues, the next update prints labels with the expiration date instead of the Xs.
Order: nnnnnn One member has renewed individually - subscription not autorenewed
Order: nnnnnn Ship-to has renewed - subscription not autorenewed
A group or two-party subscription was assigned to a renewal series that is marked for automatic renewal, but one or more group members had already sent in an individual renewal. If you wish to renew the remaining group members you will need to enter the renewal manually.
Order: nnnnnn Order does not qualify for any renewal offer
The order reported is linked to a renewal series that is marked for automatic renewal, but its service code does not match the service code in any of the offers associated with that series. Examine the order to see if it is linked to the wrong renewal series or if it was entered with the wrong service code. Also examine the renewal series to see if it is linked to the wrong offers.
Order: nnnnnn This subscription has an invalid sequence of orders
Order: nnnnnn Invalid renewal series type. Please contact CWC Software.
These messages indicate an error condition that should never occur. Please contact CWC Software.
Order: nnnnnn Unable to process subscription -- too many future orders
The issue label update can process subscriptions with a maximum of 40 future orders. Subscriptions with more than 40 future orders will not be processed and no issue labels will be generated.
Order: nnnnnn Expiration issue for subscription is not in table
You need to add issues to the table. Because you haven't defined enough issues, QuickFill replaced the expiration issue date on the label by a row of Xs. Once you add issues, the next update prints labels with the expiration date instead of the Xs.
Order: nnnnnn Rolling forward credit balance - may want to extend subscription
QuickFill rolled forward a credit balance from an expiring order to a future order. This balance was so large that the future order (now the new active order) still has a credit balance. Examine the details of the two orders. You might want to extend the subscription by the number of copies equal to the value of the credit balance. Or you can leave the credit balance, and QuickFill will carry it forward to the next renewal.
Error: The calendar date for the current issue for publication xxxxxx is out of sequence.
The date for the previous issue is mm/dd/yy while the date for the current issue is mm/dd/yy
The calendar dates in the issue table are not in ascending sequence. Select 'Issues' from the 'Definitions' menu, select the publication mentioned and compare the calendar date field for the current issue against the prior issue. They should be in ascending sequence. This error will prevent the update from running for the specified publication.
Warning: The calendar date for the issue number nnnn for publication xxxxxx is out of sequence.
The date for the previous issue is mm/dd/yy while the date for the current issue is mm/dd/yy
The calendar dates in the issue table are not in ascending sequence. Select 'Issues' from the 'Definitions' menu, select the publication mentioned and compare the calendar date field for the issue mentioned against the prior issue. They should be in ascending sequence. This message is only a warning and does not prevent the update from running.