Bizzdesign Support - Horizzon error and warning messages

When working with the Team Platform functionality, error, and warning messages of Horizzon may appear, with a link to an explanation.

The information in the message explanation is intended for system administrators. The following information is shown in an explanation:

Title The title of the topic, usually a description of the problem.
Summary A summary of the problem or steps to reproduce the error.
Solution Steps or information to resolve the problem.

If the problem persists or if you need to send information, please contact Bizzdesign Support.

S_400: Bad request

Summary:

This error indicates that Horizzon could not process the input that was provided. When this error occurs, inspect the extra details that are given.

Solution:

Inspect the details of the message and see if it gives the solution. For example, when the message's text is: "You must list at least one user e-mail to do this invitation", an e-mail address must be filled in, and the action can be retried.

If the details of the message do not give a clear solution, try to solve the problem by trying again. Perhaps there were several actions simultaneously, which caused the action to fail the first time.

When that does not reveal the problem, please report the issue to Bizzdesign Support and provide a scenario to reproduce the error.

S_401: User not authenticated

Summary:

This error occurs when the user cannot authenticate, or a request is performed without authorization.

Solution:

When authenticating with an external identity provider, error details can be found in the server log.

S_403: User not authorized

Summary:

This error occurs when the user is not authorized for the action the user tries to perform. For several actions, the user must have Administrator or System Administrator rights or be the creator of the selected model package or project.

Solution:

Look in the details of the message to see what action failed and check on the user's page in Horizzon what permissions this user has. Act yourself or assign the user the necessary right to act himself.

S_404: Resource not found

Summary:

This error occurs when a requested resource (user, site, model package, data block, etc.) cannot be found.

Solution:

Check the Horizzon log file for any relevant logs. Additionally, if the resource may have been changed or removed by a different user, refresh the Horizzon page to ensure it has an up-to-date set of resource references. If the problem persists, please contact Bizzdesign Support and provide as much information as possible.

S_409: Resource conflict

Summary:

A resource (user, site, model package, data block, etc.) could not be created or updated because it would conflict with an existing resource.

Solution:

Check the Horizzon log file for any relevant logs. Additionally, if a different user may have changed the resource, refresh the Horizzon page to ensure it has an up-to-date set of resource references. If the problem persists, please contact Bizzdesign Support and provide as much information as possible.

S_429: Too many requests

Summary:

Solution:

Please try again later and wait at least 10 minutes before sending another request to this endpoint. If the problem persists, please contact Bizzdesign Support and provide as much information as possible.

S_500: Internal server error

Summary:

This error indicates that the server has behaved unexpectedly and/or has reached an inconsistent state. There can be several causes described in the details of the error message.

Solution:

Step 1: Determine the scenario to reproduce the error

Try to determine the scenario in which this error occurs. It is recommended to reduce the number of steps in the scenario as much as possible while still getting the same "Internal server" error. Write down each scenario step so that Bizzdesign can reproduce the problem.

Step 2: Record the preconditions and environment

Provide as much information as possible to ensure Bizzdesign can reproduce your scenario. Try to provide the following information:

Step 3: Send in your detailed report to Bizzdesign Support

Bizzdesign will analyze the problem, suggest a proper course of action, and fix any potential bugs so that the problem will not occur in a next release of the Bizzdesign product.

S_501: Invalid hash

Summary:

This error is given when something went wrong while encoding or decoding a hash value.

Solution:

If the error can be reproduced, send a report to Bizzdesign Support. Bizzdesign will analyze the problem and suggest a proper course of action and fix any potential bugs so that the problem will not occur in a next release of the Bizzdesign product.

S_502: Mail error

Summary:

Solution:

Check that the hostname and port are correct in the configuration settings and that the username, password, and security settings are valid.

It might be that the mailbox of the receiver is full. Most systems have a limit on how much e-mail is allowed to reside on the server for each user, and once that limit is reached, there is no room to accept new incoming mail. Check the details of the message to see if this is the case.

When the details of the message state that the receiver is unknown, then the account the user is trying to mail to no longer exists. It may have been shut down, or you may have misspelled the username or domain. Check to make sure that there are no errors in the e-mail address.

Depending on firewalls or misspelled domains, there may be an issue with the remote SMTP server. Check the configurations.

If the error cannot be solved, please Bizzdesign Support and report the detailed error message.

S_503: Horizzon Server not configured

Summary:

Solution:

Configure the Horizzon Server by opening a browser and going to the URI hostname/setup to show the setup page and create the necessary configuration.

S_504: Unable to locate the SQL database driver

Summary:

Solution:

To resolve this problem, you must shut down the Horizzon Server and ensure you have installed the SQL driver properly.

S_505: Pagination exception

Summary:

This error is given when retrieving data for the next or previous page. The data on the page could not be retrieved because the data has been changed since the data was last loaded.

Solution:

S_506: License error

Summary:

Solution:

Bizzdesign support and request a license key. Activate your license by registering the license key on the Horizzon License page.

S_507: Invalid URL

Summary:

Solution:

Ensure that the URL protocol is HTTP or HTTPS and that the URL is formatted properly. For example:


  http://hostname:8080.

S_508: E-mail settings error

Summary:

Solution:

Check if the required e-mail settings are filled in and if all settings are correct (Settings > E-mail).

S_509: Could not initialize hosted session

Summary:

This error is given when something unexpected has happened when starting Enterprise Studio Online.

Solution:

S_510: General settings error

Summary:

Solution:

Check if the required settings are filled in and if all values are correct (Settings > General).

S_512: Hosting session settings error

Summary:

Solution:

S_513: Entra ID settings error

Summary:

Solution:

In Horizzon, check if the required settings are filled in and all values are correct via Settings > Authentication. Check if the error message provides more information about the error.

The Horizzon log files may also contain more information about the underlying problem.

S_514: SAML 2.0 settings error

Summary:

Solution:

In Horizzon, check if the required settings are filled in and all values are correct via Settings > Authentication. Check if the error message provides more information about the error.

The Horizzon log files may also contain more information about the underlying problem.

S_515: Invalid license key

Summary:

There is a license key, but it is not valid. The error should be reported to an administrator.

Solution:

S_516: License expired

Summary:

Solution:

S_517: License activation expired

Summary:

The Enterprise Studio software license has to be activated within a given time. When that time has passed, this message is given.

Solution:

S_518: License invalid server ID

Summary:

The server ID specified in the license does not match the ID of the Horizzon Server for which this license is being activated.

Solution:

S_519: Invalid IP ranges

Summary:

Invalid IP ranges have been entered for embedded views or the Open API on the Horizzon settings page. The IP range fields accept either IPv4 or IPv6 in CIDR notation. In case of multiple ranges, they need to be separated by a comma.

Solution:

More information about the CIDR notation can be found online. If the problem persists, please contact Bizzdesign Support and provide as much information as possible.

S_601: Version too old

Summary:

The Horizzon server does not support the client version. The version of the client is too old.

Solution:

S_602: Version too new

Summary:

The Horizzon server does not support the client version. The client is newer than what the server supports.

Solution:

S_1000: Model package or project does not exist

Summary:

This error occurs when the user tries to access a model package or project that does not exist. It can be presented as a Not Found (404) HTTP result code.

Solution:

Verify that the error can be reproduced. Please report this issue and the scenario to Bizzdesign Support to reproduce the error.

S_1001: Claiming objects error

Summary:

Something went wrong during the process of claiming or blocking an object. Claims and blocks are generated automatically when the user starts editing a shared model package.

Solution:

Try again in a few moments to see if you can reproduce the error. If the problem persists, please follow these steps:

Step 1: Determine the scenario to reproduce the error

Try to determine the scenario in which this error occurs. It is recommended to try to reduce the number of steps in the scenario as much as possible while still getting the same "claiming objects" error. Write down each scenario step so that Bizzdesign can reproduce the problem.

Step 2: Record the preconditions and environment

Provide as much information as possible to ensure Bizzdesign can reproduce your scenario. Try to provide the following information:

Step 3: Send in your detailed report to Bizzdesign Support

Bizzdesign will analyze the problem, suggest a proper course of action, and fix any potential bugs so that the problem will not occur in a next release of the Bizzdesign product.

S_2000: Contribution does not exist

Summary:

Solution:

Verify that the error can be reproduced. Please, report this issue to Bizzdesign Support, along with the scenario to reproduce the error.

S_2001: Contribution parse error

Summary:

The contributions are saved in a specific format. A contribution parse error is given if this cannot be parsed to process a contribution.

Solution:

Check that the versions of the Bizzdesign tools you are using are compatible. If the problem persists and you can reproduce it, please follow these steps:

Step 1: Determine the scenario to reproduce the error

Try to determine the scenario in which this error occurs. It is recommended to try and reduce the number of steps in the scenario as much as possible, while still getting the same "contribution parse" error. Write down each scenario step so that Bizzdesign can reproduce the problem.

Step 2: Record the preconditions and environment

Provide as much information as possible to ensure Bizzdesign can reproduce your scenario. Try to provide the following information:

Step 3: Send in your detailed report to Bizzdesign Support

Bizzdesign will analyze the problem, suggest a proper course of action, and fix any potential bugs so that the problem will not occur in a next release of the Bizzdesign product.

S_3001: Branch does not exist

Summary:

Solution:

Verify that the error can be reproduced. Please, report this issue to Bizzdesign Support and the scenario to reproduce the error.

S_3002: Branch update error

Summary:

Solution:

Verify that the error can be reproduced. Please, report this issue to Bizzdesign Support and the scenario to reproduce the error.

S_3003: Branch already exists

Summary:

Solution:

If the user has given a name for the branch himself, the user has to supply a different one. When the error comes with a function that does not include a specific branch name, report this issue to Bizzdesign Support.

S_3004: Increment does not exist

Summary:

An increment is information about the uncommitted changes a user makes and the associated claims.

Solution:

Verify that the error can be reproduced. Please, report this issue to Bizzdesign Support and the scenario to reproduce the error.

S_3005: Removed claims

Summary:

This error is given when there are removed claims, but the user tries to claim or block objects. Claims and blocks are generated automatically when the user starts editing a shared model package.

Solution:

The removed claims need to be handled first. Open the model package with the design tool to create a backup. The changes in the model package will then automatically be reverted, and the error should not occur anymore.

S_3006: Checkout does not exist

Summary:

This error indicates that the requested checkout (for working offline) could not be found.

Solution:

Verify that the error can be reproduced. Please, report this issue to Bizzdesign Support and the scenario to reproduce the error.

S_3007: Checkout of an unchangeable model

Summary:

This error indicates that a model could not be taken offline for offline editing because it is read-only in the current collaboration (e.g., the project you are working on). It is possible that someone recently changed the scope of the collaboration to exclude the model you attempted to take offline.

Solution:

Synchronize the Activity Console or check the collaboration in Horizzon to verify its scope. If the model is part of the scope and the error persists, report this issue to Bizzdesign Support and the scenario to reproduce the error.

S_3008: Increment already exists

Summary:

This error indicates that the increment that was to be created already exists on the server.

An increment is information about the uncommitted changes a user makes and the associated claims.

Solution:

The error can be ignored, and the increment can be considered successfully created.

S_3009: Too many meta-increments

Summary:

Meta-increments are created to prepare metamodel migrations. Only one such increment can be active for a shared model package anytime. This error indicates that a meta-increment could not be created because one already exists for the model package.

An increment is information about the uncommitted changes a user makes and the associated claims.

Solution:

Wait for the current migration to be finished, or (ask your Horizzon administrator to) remove the user's claims that has created the current meta-increment.

S_3010: Metabranch out of date

Summary:

The metamodel cannot be updated because there are updates of the metamodel available.

Solution:

Update your model package or project with new commits of the metamodel. If the updates are not yet visible in the Activity Console, synchronize the Activity Console with Horizzon.

S_3012: Increment committed

Summary:

This happens when an increment is changed, but the increment is already committed. The increment should not be committed when adding new claims to the increment, recalling claims of an increment, or creating a commit for an increment.

An increment is information about the uncommitted changes a user makes and the associated claims.

The Activity Console normally prevents this situation by creating a new increment after committing to storing new claims for the changes being made. The data stored in the Team Data folder is inconsistent with those stored on Horizzon.

Solution:

Close Enterprise Studio and the Activity Console and remove the local state stored in the Team Data folder. All pending changes will be lost. After restarting Enterprise Studio, the connection with Horizzon (configuration file) must be added again.

S_3013: Out-of-date with retired increments

Summary:

After a commit is available on the model package for at least a year, the increment containing the claims for the changes inside the commit has been deleted.

Solution:

Update the model package or project with new commits. When working on a project, updating the project with new commits (latest contributions) from the model package could be necessary.

S_4000: User does not exist

Summary:

Solution:

Check the Users page in Horizzon to see if the user on whom one has tried to perform an action (this might also be oneself) is still listed. Check that this user is not deleted.

When that does not reveal the problem, report the issue to Bizzdesign Support and a scenario to reproduce the error.

S_4002: No e-mail address

Summary:

This error indicates an e-mail address is not filled in or passed to the request.

Solution:

A valid e-mail address should be filled in where requested. If this is not possible, report the issue to Bizzdesign Support and a scenario to reproduce the error.

S_4003: No password

Summary:

This error indicates that a password for a user is not filled in or passed to the request.

Solution:

A password should be filled in where requested. If this is not possible, report the issue to Bizzdesign Support, along with a scenario to reproduce the error.

S_4004: Invalid token

Summary:

Solution:

When the token is part of the URI and it is entered via copy-and-paste or by typing, make sure that it is correct and complete.

S_4005: Token expired

Summary:

Solution:

If this error occurs during the registration process, the user is already registered. Check this by going to the user's page in Horizzon and see that the user's name is listed.

In other cases, the token for this session is not valid and the user has to sign in again to get a new token.

S_4007: User already exists

Summary:

Solution:

When one tries to register a new user with Horizzon, this user's e-mail address should not already be used for registration. Check the Users page in Horizzon to see if the user is registered.

To add a user to a model package, use the Invite button on the model package page in Horizzon.

S_4008: User not invited

Summary:

Solution:

The invitation for the model package has been deleted, and the user does not have the right to view and edit the model package anymore. Check the message details to see who has deleted the invitation and when.

S_4009: User removed

Summary:

Solution:

S_4010: Last administrator user

Summary:

The last user with administrator rights originating from Horizzon cannot be removed.

Solution:

Make sure there is always a user with administrator rights present who has been created in Horizzon. When synchronizing users with Active Directory the last administrator user must not be selected by the LDAP query.

S_4011: Password not secure

Summary:

Solution:

Make sure the password conforms to the password policy that has been set for this Horizzon. The exact password requirements are mentioned in the error message in Horizzon.

S_4012: API client removed

Summary:

Solution:

S_4013: License seats exceeded

Summary:

Adding or inviting users failed because Horizzon license does not allow more active users.

Solution:

The error message indicates how many users could not be added or invited. Reduce the number of users you are adding or inviting, or reduce currently active users on Horizzon so that you can add or invite other users. You can reduce the number of active users by removing the Designer or Lead Designer role from these users. Make sure that these users have committed their work on model packages and projects they have been working on before you remove their role; by removing the role these users' invitations to model packages and projects will automatically be revoked, and any uncommitted work will be lost.

If you do not want to reduce the number of active users or if you are not able to, you can contact Bizzdesign Sales for a license for additional seats.

S_4014: Username error

Summary:

The username is too short, it does not comply with the Horizzon username policy.

Solution:

S_4015: Synchronize users error

Summary:

The users retrieved from Active Directory cannot be synchronized, because a required attribute is missing. Or an unknown error occurred when retrieving users from Active Directory.

Solution:

It could be that the LDAP query returns items that do not have the required attributes for synchronizing.

The following attributes are required: "objectGUID", "sAMAccountName" and "mail".

Try to modify the LDAP query, or make sure the required attributes are available for all users in Active Directory.

S_4016: You cannot remove yourself

Summary:

Solution:

If you synchronize users with LDAP, check if the LDAP query removes you from Horizzon.

S_4017: Only existing users allowed

Summary:

A new user has been invited to a model package, but inviting users is limited to inviting only existing Horizzon users (via the Invitations limited to existing users and groups with the Designer or Lead Designer role option on the General Settings page of Horizzon).

Solution:

The user to be invited is not present in Horizzon yet. Therefore, it needs to be added to Horizzon first by an administrator user. It is possible, however, that this user is not allowed to contribute to model packages and has, therefore, not been added to Horizzon. If that is the case, this user just cannot be invited.

S_4018: Reset password not possible

Summary:

Solution:

You can use your Windows username and password to sign in. If you forgot your Windows credentials, please contact your system administrator.

S_4020: Group already exists

Summary:

Solution:

Each group should have a unique name. The check if a name is unique is case insensitive. Check on the Groups page in Horizzon if the name already exists.

S_4021: Group does not exist

Summary:

Solution:

Check the Groups page to see if the group on whom one has tried to perform an action is still listed. Check that this group is not deleted.

If that does not reveal the problem, report the issue to Bizzdesign Support and a scenario to reproduce the error.

S_4022: Only users with Designer role can be invited

Summary:

This error occurs if users are invited that do not have the Designer or Lead Designer role, assigned directly (individual) or indirectly (via a group) in Horizzon.

Solution:

To invite the user, make sure on this user's page in Horizzon that the user has the Designer of Lead Designer role assigned, individually or via a group.

S_4023: Incorrect MFA codes

Please try again. The device generates a new code every 30 seconds. You have to provide two consecutive codes. If you keep having problems, it could mean your device's clock needs to be synchronized.

Summary:

You have registered an MFA device, so you must provide two consecutive codes produced by the device when you sign in to Horizzon. The codes you provided are incorrect.

Solution:

Please try again. The device generates a new code every 30 seconds. You have to provide two consecutive codes. If you keep having problems, it could mean your device's clock needs to be synchronized.

S_4024: Your password has expired

Summary:

When you attempt to sign in to Horizzon or add a connection with Horizzon in Enterprise Studio, you may get a message that your password has expired.

Your Horizzon's system administrator has enabled password expiry, meaning passwords must be changed periodically.

Solution:

Visit Horizzon in your web browser and sign in using your username and current password. You will then be presented with a window that lets you change your password.

S_4025: You have reused your expired password

Summary:

When your Horizzon password has expired and you change your password, you must use a new password. If you attempt to reuse your current password as your new password, Horizzon will return an error.

Solution:

When your password has expired, it is best to pick a new password that is completely different from your expired password so that your new password stays hard to guess.

S_4026: The e-mail address provided does not match the allowed e-mail domains

Summary:

The system administrator of Horizzon has restricted inviting new users to specific e-mail domains. The e-mail domain you used is not allowed.

Solution:

S_4027: The user profile is invalid

Summary:

When authenticating with an external identity provider, a user profile is returned. The user profile must contain certain attributes for identifying or provisioning a user. The user profile is missing one of these attributes. The details of the error will show the missing attribute.

Solution:

The missing attribute must be returned in a SAML assertion or as a claim in a token returned by in case of an identity provider using the OpenID Connect protocol. Please contact the administrator of the identity provider.

S_4028: Just-in-time user provisioning failed

Summary:

An unknown error occurred when creating or updating a user after authentication.

Solution:

There is no solution yet. The Horizzon logs contain detailed information about the error.

S_4029: The provided passwords are not equal

Summary:

When entering a new password after your password has expired, the new password must be entered twice, and these must be equal.

Solution:

S_4030: MFA code needed

Summary:

The user authenticating with a username and password has an MFA device associated. An additional MFA code must be entered to authenticate this user.

Solution:

S_4031: Invitation does not exist

Summary:

This error indicates that the requested invitation does not exist or that the access is managed for an invitation that does not exist.

Solution:

Verify that the error can be reproduced. Please, report this issue to Bizzdesign Support and the scenario to reproduce the error.

S_4032: The "order by" option provided is not known for groups

Summary:

Solution:

S_4033: The "order by" option provided is not known for users

Summary:

Solution:

S_4034: The "order by" option provided is not known for API clients

Summary:

Solution:

S_4035: API client already exists

Summary:

Solution:

Each API client should have a unique client ID. The check if a client ID is unique is case insensitive. Check on the API Clients page in Horizzon if the client ID already exists.

S_4036: API client does not exist

Summary:

Solution:

Check the API Clients page in Horizzon to see if the API client on which one has tried to perform an action is still listed. Check that this API client is not deleted.

If that does not reveal the problem, report the issue to Bizzdesign Support and a scenario to reproduce the error.

S_4038: Search failed

Summary:

Solution:

To be able to use advanced search functions you must follow a specific syntax. Check the documentation about searching through sites using the correct syntax and try again. If that does not reveal the problem, report the issue to Bizzdesign Support and a scenario to reproduce the error.

S_4039: Password too common or breached

Summary:

The password provided does not meet the security requirements. It is either too commonly used, it is (partially) composed of easy to guess words, or it was found in a database of breached passwords.

Solution:

Make sure to pick a unique and complex password. Avoid easily predictable patterns like dictionary words, series of numbers, or repetitions of characters. You are advised to use a password generator.

S_4040: Unauthorized to edit data block

Summary:

This error occurs when the user is not authorized to edit one or more data blocks. The objects and data block name for which the user is not authorized is returned.

Solution:

Ensure a data policy is created, allowing the user to edit the data block. Data policies can be defined in Horizzon in the Policies section of the model package.

S_5000: Model package or project does not exist

Summary:

This error occurs when the user tries to access a model package or project that does not exist. It can be presented as a Not Found (404) HTTP result code.

Solution:

Verify that the error can be reproduced. Please, report this issue to Bizzdesign Support and the scenario to reproduce the error.

S_5001: Model package or project deleted

Summary:

This error occurs when you try to access a model package or project that has been deleted.

Solution:

Verify that the error can be reproduced. Please, report this issue to Bizzdesign Support and the scenario to reproduce the error.

S_5004: Model package or project ordering method not correct

Summary:

This error occurs if a request is made to Horizzon using an invalid or incorrect ordering method when sorting model packages or projects.

Solution:

Make sure that nothing is interfering with the requests sent to Horizzon. If you are sure your connection has not tampered with and you keep seeing this error, please contact Bizzdesign Support.