Which Of The Following Is A Production Error That Can Occur When Creating Aã¢â‚¬â€¹ Document?

Production errors

When staging and running a production chore, staging, validation, and branding errors can occur.

This page contains the following information:

Staging errors

Staging errors occur when

The same document is constitute in multiple data sources.
When the aforementioned document is found in multiple data sources, y'all will receive an fault bulletin. The mistake message identifies the data sources that pulled back the same document and which document they pulled back. To resolve the mistake, modify the saved searches that you selected every bit your data sources to ensure that they practice not pull dorsum whatsoever of the same documents.
At that place are no documents in the data sources.
When no documents are found in the information sources, you will receive an fault message. To resolve the fault, make sure that the saved searches that you selected as your information sources are pulling dorsum documents.

Validation errors

There are 2 types of validations errors:

When a validation fault occurs, click View Production Errors and Warnings on the Production panel to open the Error Starting Production pop-up. The Error Staging Production pop-upward lists the errors that occurred.

Error Starting Production

At that place are 2 types of validation errors.

Data source - occurs when documents in the information source practise not have images or natives. To resolve the error, alter the data sources so click Stage and Run Production.

Conflict - occurs when the data sources accept documents that are also in the saved search selected in the Production Restriction field.

Conflict resolution option	Fix
Remove the conflict	Remove documents from the production set that are also in the saved search selected in the Production Restriction field. To remove the conflict: Click Bank check for Conflicts on the Production console. The Product Restrictions pop-upwards will open up. Click Remove Conflict on the Production Restrictions pop-up. Click Run Production on the Production panel.
Override the conflict	Keep the documents in the production set that are also in the saved search selected in the Production Brake field. To override the disharmonize: Click Run Production on the Production console. The Production Warnings pop-upward will open. Click Override and Keep on the Production Warnings pop-up. The production job volition proceed without removing the conflict documents.
Modify the production restriction	Change the Production Brake field so none of the documents in the product restriction saved search are also in the production set. For information on modifying a product restriction, see Adding and editing production restrictions. After modifying the production restriction, click Stage and Run Production on the Production console.

Conflict resolution option

Fix

Remove the conflict

Remove documents from the production set that are also in the saved search selected in the Production Restriction field.

To remove the conflict:

Click Bank check for Conflicts on the Production console. The Product Restrictions pop-upwards will open up.
Click Remove Conflict on the Production Restrictions pop-up.
Click Run Production on the Production panel.

Override the conflict

Keep the documents in the production set that are also in the saved search selected in the Production Brake field.

To override the disharmonize:

Click Run Production on the Production console. The Production Warnings pop-upward will open.
Click Override and Keep on the Production Warnings pop-up. The production job volition proceed without removing the conflict documents.

Modify the production restriction

Change the Production Brake field so none of the documents in the product restriction saved search are also in the production set. For information on modifying a product restriction, see Adding and editing production restrictions.

After modifying the production restriction, click Stage and Run Production on the Production console.

Branding errors

To resolve branding errors:

Click View Branding Errors on the Production panel to open the Branding Errors popular-up.

Read the Branding Fault Bulletin to determine the cause of the error and resolve it. Possible errors include:

Branding Fault Message	Set up
All branding managers are disabled or no branding managing director exists.	Enable or create the Branding Manager and Product Manager agents. For more data on agents, meet Agents.
Could non discover file <file path>.	Since the arrangement can not find the file path to the image, make certain the image exists at the file path mentioned in the Branding Mistake Message. You may need to paradigm or import the document again.
The file at <file path> could non be opened or is not a valid prototype file.	If the certificate is encrypted, add the document's password to the Countersign Bank. For more information, see Countersign Depository financial institution. Make sure Relativity supports the file type of the image. You may need to prototype or import the document once again.
The procedure cannot access the file <file path> because it is being used by another procedure.	This is usually the result of antivirus software. To resolve the mistake, click Rerun Errored Documents on the Product console. If you receive the aforementioned error after rerunning the errored documents, unlock the file or folder mentioned in the Branding Mistake Message and and then click Rerun Errored Documents.

Click Rerun Errored Documents to end the product job.