In this article, you will find a set of best practices to follow to use the Site Factory optimally. We present the most frequently encountered errors and how to resolve them. Each error follows a clear and organized structure:

Structure of each error section:

• Error Description: Clear explanation of the encountered problem
• Possible Causes: List of the most frequent reasons behind the error
• Resolutions: Step-by-step solutions to fix the problem
• Prevention: Tips and best practices to prevent the error from recurring

💡 If the proposed solutions do not resolve your issue, do not hesitate to contact Jint Support for specialized technical assistance.

📋 Table of Contents

1. Access is denied
2. A duplicate field name 'MyFieldName' was found
3. The field was found
4. Column 'MyFieldName0' does not exist
5. Cannot contact site at the specified URL
6. The remote server returned an error: (429)
7. Cannot enable the site collection app catalog feature in this site collection because it has not been approved by the tenant admin
8. There was an exception invoking the custom extensibility
9. Scope of template does not match target
10. A Task Was Cancelled

⚠ Fundamental Rule 

After any modification of the model site, it is mandatory to update the model before applying it to another site. This step is crucial because:

• Changes made to the model site are not automatically included in the existing model
• Applying a non-updated model can lead to errors or inconsistencies
• Updating the model ensures that all recent changes are correctly replicated on target sites

Recommended Procedure:

• Make your modifications on the model site
• Test that everything works correctly
• Update the model from the Site Factory
• Apply the updated model to your target sites

❌ Access is denied 

The "Access is denied" error in SharePoint indicates that the user attempting to apply a model or perform an action does not have the necessary permissions to complete this task.

Frequent Causes of the Error:

• User is not a site administrator: The main cause of this error is that the user trying to apply a model does not have administrator rights on the target site. To apply a model, administrative permissions on the site are required. The user must be able to make structural changes to the site, such as adding or modifying columns, lists, etc.
• User lacks necessary permissions on resources linked to the model: Sometimes, the model may include elements for which the user does not have appropriate permissions. For example, the user may not have access to image files stored on another SharePoint site and referenced in the model site.
• Permission issues at the site collection or term set level: If the model involves columns of the Managed Metadata type (Term Store), the user must have the necessary permissions on the term sets or on the Term Store settings in the SharePoint admin center. Lack of access to this Term Store can also lead to the "Access is denied" error.
• Permission issues related to the use of scripts or custom features: If the model uses features that depend on custom scripts or extensible features, the user might be denied access if the scripts are disabled for security reasons, or if security settings prevent their execution.

Resolutions:

• Grant administrator rights on the target site: Ensure that the user has administrator rights on the target site or on the library/item with which the model interacts.
• Check permissions on necessary resources: Verify that the user has the necessary permissions to access libraries, lists, term sets, and other resources that the model might use.
• Check permissions at the site collection and Term Store level: Ensure that the user has the necessary permissions to access Term Stores and other resources shared between multiple sites.
• Review security settings and access restrictions: If security restrictions or script settings are in place, check SharePoint's security policies to ensure that the user can perform management tasks on the site.

👉 In summary, the "Access is denied" error mainly occurs when the user does not have the necessary permissions to apply a model, usually because they lack administrator rights or specific permissions at the site, library, or necessary resources level (such as term sets). The main resolution is to ensure that the user has the appropriate rights to perform this action.

❌ A duplicate field name 'MyFieldName' was found 

The error "A duplicate field name 'MyFieldName' was found" indicates that an attempt to create a column failed because another column with the same internal name already exists on the site or in a list/library. This means that SharePoint encounters a conflict between column identifiers, even if they seem to have different names.

Possible Causes of the Error: 

• Column manually created with the same internal name: If a column was manually created on the site or in a list/library, it is possible that it shares the same internal name as a column that the model is trying to create. This can happen if a column was added to the site before applying the model, and the internal name of this column is identical to the one defined in the model.
• Existing column due to the application of another model containing the same column: If another model containing the same column has already been applied previously on the target site, SharePoint has already created the column with a specific internal name. When the current model tries to create this column again, a conflict occurs because the internal name of the column is already used by an existing column.
• Existing column because the column from the model was recreated: If the column from the model site was deleted and then recreated, its identifier was modified. However, if the model had already been applied to a target site, then the identifier of this column no longer matches the column from the model, even though both columns use the same internal name. When the current model tries to create this column again, a conflict occurs because the internal name of the column is already used by an existing column.

Resolution:

• Check for the existence of the column with the same internal name: Access the list/library where the error occurs and check if a column with the same internal name already exists. This can be done by accessing the list/library settings and searching for the columns already present. You can also check the site settings and explore the columns to see if the column in question is already listed there.
• Delete or modify the existing column: If you find a column with the same internal name, you can either:
  • Delete it (if it is not used or if it is not important),
  • Modify its internal name (but this can be complex, as SharePoint does not directly allow modifying the internal name of a column),
  • Recreate the column from the model site using a different internal name.
• Check previously applied models: If the error occurs after applying a previous model, check the models that have already been applied to the target site. It is possible that a column with the same internal name has already been created. In this case, it is not necessary to create this column again, and you may need to adjust the model accordingly to avoid recreating the column.

Prevention:

• Pre-check existing columns: Before applying a model, it is useful to check if columns with the same internal name already exist on the site or in the targeted lists/libraries. This helps avoid conflicts before even applying the model.
• Use unique internal names: When creating models or columns, make sure to use unique internal names to avoid collisions. This may require some control from users who create or modify columns on the site.

👉 In summary, the error "A duplicate field name 'MyFieldName' was found" is caused by the attempt to create a column whose internal name already exists, either due to a manually created column or due to a previously applied model. The resolution involves checking existing columns and managing identifier conflicts.

❌ The field was found invalid 

The error "The field was found invalid" indicates that a Managed Metadata field in the model or on the target SharePoint site presents a validation problem when applying the model. This error usually occurs when a field associated with a Term Store does not meet the constraints expected by SharePoint. More specifically, it often manifests when a term set or term referenced in a Managed Metadata column cannot be found or is invalid on the target site.

Possible Causes of the Error:

• Missing term set or term: This error is common when the term set or term referenced in the Managed Metadata field does not exist on the target SharePoint site. This can occur if the term set has been deleted or if a specific term, to which the column is associated, has been removed.
• Modification of the term set hierarchy: If the term set hierarchy has been modified (for example, a parent term has been renamed or deleted), this can render the reference invalid. SharePoint will no longer be able to find the specified term or establish the correct relationship between terms.

Resolution:

• Check the existence of terms and term set on the target site: Verify that the term set and all referenced terms exist on the target SharePoint site. To do this, access the Term Store administration in the SharePoint admin center and check the presence of the term set as well as the terms associated with the Managed Metadata field.
• Check the integrity of the term hierarchy: If the term hierarchy has been modified, check if the parent term still exists and if all child terms are valid. Confirm that the terms referenced in the column are present and that their hierarchy is correct.
• Update references in the model: If modifications have been made to the term set or terms, it is necessary to update the references in the model so that they point to valid terms on the target site.
• Restore missing terms: If the term set or missing terms were previously present, it is possible that the reference has been lost. In this case, you may need to restore or recreate the term set on the target site to resolve the error.

Prevention:

• Avoid modifying the term hierarchy after their use in Managed Metadata fields, especially in a production environment, to avoid breaking existing relationships.

👉 In summary, the error "The field was found invalid" is generally related to a problem of availability or modification of term sets or terms referenced in a Managed Metadata field. Checking the existence and structure of terms on the target site usually resolves this issue.

❌ Column 'MyFieldName0' does not exist 

The error "Column 'MyFieldName0' does not exist" usually occurs when applying the model when SharePoint does not find the expected column, MyFieldName, in a target library or list. This error is caused by an internal name conflict between a site column and a library column, having similar display names but different internal names.

Cause of the Error: When a site column MyFieldName has been added to a library or list, SharePoint detected an internal name conflict with another column already having the same display name ("My Field") but a different internal name. To avoid this conflict, SharePoint automatically created a column MyFieldName0 in the library, so as not to overwrite the existing column. The problem occurs when the column MyFieldName0 is deleted, but the model refers to MyFieldName, and SharePoint no longer finds the column under this internal name, leading to the error "Column 'MyFieldName0' does not exist."

Typical Example:

• A column MyFieldName was initially created at the site level.
• Subsequently, a similar column was added in a library or list of the site, but SharePoint created a new internal column called MyFieldName0 to avoid a conflict with the site column.
• The column MyFieldName0 was then deleted, but the site column MyFieldName remained in the library with a different internal name. When you apply the model, SharePoint searches for MyFieldName, but since the internal column has been changed to MyFieldName0, it does not find it and generates the error.

Resolution:

• Delete the column MyFieldName0 in the library: The first step is to delete the column MyFieldName0 in the target library or list. This column was created automatically to avoid a name conflict, but it is no longer necessary once we have aligned the references.
• Add the site column MyFieldName back to the library: After deleting MyFieldName0, you need to add the site column MyFieldName back to the target library or list. This ensures that the site column with the correct internal name is present and that SharePoint can find it when applying the model.
• Check existing columns: If the error persists, make sure that the column MyFieldName is present in the library and correctly linked to the site column. You can also check the library and site column settings to ensure there are no other duplicates or internal name conflicts.
• Update the model if necessary: If, after resolving the conflict, you apply the model again, make sure it refers to the column MyFieldName and not another internal name. If the model is misconfigured, you may need to update it to point to the correct column.

Prevention:

• Check existing columns before adding new columns: Before adding a column in a list/library of the model site, check if a column with the same internal name already exists in the library or list. This will prevent conflicts before proceeding.
• Use distinct internal names for columns: When adding a column to a library or site, ensure that internal names do not overlap, especially if the site column is added to a library afterward.

👉 In summary, the error "Column 'MyFieldName0' does not exist" occurs due to an internal name conflict between a site column and a column in a library. The resolution involves deleting the column MyFieldName0, then adding the site column MyFieldName back to the target library or list, before applying the model. This ensures that the references are correctly aligned and that the error does not recur.

❌ Cannot contact site at the specified URL

The error "Cannot contact site at the specified URL https://mytenant.sharepoint.com/sites/mysite" indicates that the Site Factory cannot establish a connection with the specified site. This error can have several possible causes, ranging from network or permission issues to configuration errors.

Possible Causes of the Error:

• Incorrect URL or non-existent site: The specified URL might be incorrect or the site may not exist at the indicated location. This can occur if the site has been deleted, moved, or renamed, or if the URL has been incorrectly entered.
• Permission issues: The user may not have the necessary permissions to access the target site. If access permissions to the site have been modified, the user might encounter problems connecting to the site. Verify that the user has the appropriate permissions on the site.
• Private or inaccessible site: The specified site may be private or not shared with the user, which would result in a connection failure. It may be that the site is restricted to certain users or groups and the user attempting to apply the model does not have access.
• Security settings issues: Specific security settings (such as privacy settings or conditional access policies) may prevent access to the site from certain devices, networks, or users.

Possible Resolutions:

• Verify the site URL: Confirm that the site URL is correct. Try accessing the site directly via a browser to see if the URL is valid and if the site is accessible.
• Check site access permissions: Ensure that the user has the necessary permissions to access the site. If the site is private, it may be necessary to verify that the user is properly added to the site or the appropriate group.

📎 Example URL: https://mytenant.sharepoint.com/sites/mysite

Prevention:

• Regularly check site permissions and accessibility: To avoid this type of problem, ensure that site permissions and accessibility are regularly updated and checked, especially if the site is shared with multiple users or groups.
• Verify the URL and site settings before applying a model: Before applying a model, ensure that the site URL is correct and that the site is accessible from the network used to apply the model.

👉 In summary, the error "Cannot contact site at the specified URL" can be caused incorrect URL issues, access permissions, or security restrictions. The resolution involves verifying the URL, permissions, and security settings to ensure that the user can access the site without restrictions.

❌ The remote server returned an error: (429) 

The error "The remote server returned an error: (429)" is related to a SharePoint throttling limitation. It occurs when server resources are excessively solicited, leading to an exceeding of quotas or limits imposed by SharePoint to protect services from overloads. This error is common when a too-heavy operation is performed, such as applying a model containing a large amount of content.

Possible Causes of the Error (429):

• Excessive solicitation of SharePoint resources:
  • Execution of heavy operations: If the model contains an excessive amount of content, such as numerous lists, libraries, items, columns, or pages, this can lead to a server overload in SharePoint.
  • Too high request rate: When frequent or numerous requests are sent in a short time, SharePoint may apply limitations to avoid overload and ensure service stability.
  • Over-solicited source site: If the source site serving as a model is currently used by users, especially for regularly publishing content, this can lead to excessive solicitation of this site. SharePoint applies limits to prevent heavy operations on the model from affecting active users.
  • Use of SharePoint in a production environment: The error may occur if the source site is a production site (used by users for daily work) and therefore contains a lot of content, including site pages with many components.

Possible Resolutions:

• Reduce the model size: Simplify the model by reducing the amount of content or elements included. For example, reduce the number of lists, libraries, or columns in the model to decrease the load that SharePoint must manage.
• Use a specific site for models: Ensure that the source site used to create and apply models is a dedicated model site. This site should be specifically designed to serve as a model and not be actively used for regular content publishing or management tasks by users. It should be a stable and un-solicited environment.
• Check the use of the source site: If the source site is actively used by users, it is preferable not to use it as a model. Prefer a dedicated, un-solicited site that is not affected by other publishing or frequent update operations.

Prevention:

• Use dedicated sites for model application: It is important to create a dedicated model site for generating and applying models, to avoid overloading a production site.
• Test the model size before application: Before applying a model on a large scale, test the application of smaller models to ensure the process is smooth and does not lead to excessive solicitation of resources.
• Perform operations outside working hours: Schedule heavy operations, such as model application, during periods of low activity to reduce the risk of server solicitation.

👉 In summary, the error "The remote server returned an error: (429)" occurs when SharePoint is over-solicited, usually due to the execution of too-heavy operations, such as applying models containing too much content. To resolve this issue, it is crucial to ensure that the source site is a dedicated model site, not solicited by active users, and to simplify or distribute the model application to avoid exceeding the throttling limits imposed by SharePoint.

❌ Cannot enable the site collection app catalog feature in this site collection because it has not been approved by the tenant admin 

The error indicates that a model site containing an App Catalog is attempted to be applied to a target site that does not have an App Catalog or whose App Catalog activation has not been approved by the organization administrator.

Possible Causes of the Error:

• Model site containing an unapproved App Catalog: This error occurs when the model site has an activated App Catalog, but the target site, on which the model is applied, does not have this same App Catalog activated. SharePoint requires approval from the tenant admin to activate this feature on a site, especially if the App Catalog activation has not been approved or properly configured at the tenant level.
• Incompatibility between sites: The model contains app catalog configurations that are not compatible with the target site, either because this feature is not activated for this site or for the entire tenant.
• Lack of permissions to activate the App Catalog: The organization or tenant administrator must explicitly approve the activation of this feature on sites, and if this approval is not given, the App Catalog activation fails, preventing the model application.

Possible Resolutions:

• Restart the model site from scratch: If the current model poses a problem due to the App Catalog activation, it is recommended to restart the model site without including this feature. You can create a new model site without activating the App Catalog, which will allow it to be easily applied to other sites without encountering this error.
• Ask Jint Support to manually remove the App Catalog from the model: If the App Catalog is not necessary or if you do not wish to modify the model site, you can contact Jint Support to have them manually remove this feature from the model. Once this is done, you can apply the model to a new blank site that can then serve as a new model site.
• Approve the App Catalog activation in the tenant: If the App Catalog activation is necessary, it may be useful to ask the tenant administrator to approve this feature at the tenant level, which would allow it to be activated on target sites. This requires access to tenant management settings in SharePoint Online administration to activate this feature globally.

Prevention:

• Check model requirements before applying: Before applying a model to a target site, ensure that this model does not include features incompatible with target sites, such as the App Catalog. Also, verify that target sites are configured to accept the necessary features for model application.
• Use a streamlined model site: To avoid this type of problem, it may be useful to use a streamlined model site that contains only essential configurations and elements, without specific features like the App Catalog or other extensions requiring specific approval.
• Ensure good communication with the tenant administrator: If the use of the App Catalog is essential for your process, ensure that the organization administrator is well informed of this requirement and has authorized this feature at the tenant level.

👉 In summary, this error occurs when the model site contains an App Catalog, but the target site does not have this feature activated or approved by the tenant administrator. To resolve this issue, you can either restart the model site without the App Catalog, ask Jint Support to manually remove this feature, or ask the tenant administrator to approve the App Catalog activation on target sites.

❌ There was an exception invoking the custom extensibility

 The error "There was an exception invoking the custom extensibility" indicates that there was a problem during the generation of a model. This error remains rare but can occur.

Cause of the Error: 

This error is often related to a SharePoint evolution that needs to be addressed.

Resolution: 

In this specific case, there is no immediate alternative to an internal technical resolution, as this requires specific technical adjustments. 👉 The best approach to follow in this case is to contact Jint Support for an in-depth analysis of the extension and its components, as this type of error generally falls under technical expertise.

❌ Scope of template does not match target

Cause of the error:

The site type (communication site or team site) used to create the template is different from the target site.

Resolution:

👉 Make sure that your template site is the same type as your target site.

Example: if your template site is a communication site, then your target site must also be a communication site. Likewise, if your template site is a team site, your target site must also be a team site.

How to check the site type:

1. Click on the gear icon at the top right of the site page

2. Select Site information

3. If the Privacy settings field appears (see below), it is a team site.
   If it does not appear, it is a communication site.

❌ A Task Was Cancelled

Cause of the Error

This error occurs when multiple templates are applied simultaneously across different sites.

Resolution

👉 Please ensure that you wait until a template has been fully applied before starting another one on a different site.

Templates should be applied sequentially to prevent task interruptions or cancellations.

📝 Conclusion 

This guide covers the most common errors you may encounter when using the Jint Site Factory. Most of these errors are related to permission issues, column name conflicts, or missing references in SharePoint.

Key Points to Remember:

• Permissions: Always ensure you have the appropriate administrator rights on the target site
• Column Names: Check the uniqueness of internal column names before applying a model
• References: Confirm that all referenced elements (terms, term sets, etc.) exist on the target site
• URLs: Verify the accuracy and accessibility of target site URLs

📞 If you encounter errors not covered by this guide or if the proposed solutions do not resolve your problem, do not hesitate to contact Jint Support for specialized technical assistance.