Skip to end of metadata
Go to start of metadata

When working with the Team Platform functionality, error and warning messages of the Team Server 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.
Error ID The error ID.
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.




Bad request

Error ID: S_400

Summary:

This error indicates that the Team Server 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 text of the message is: "You must list at least one user e-mail to do this invitation" an e-mail address needs to be filled in and the action can be retried.

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

When that does not reveal the problem, please report the issue to BiZZdesign Support, along with a scenario to reproduce the error.

User not authenticated

Error ID: S_401

Summary:

This error occurs when the user cannot be authenticated, or when a request is performed without being authenticated.

Solution:

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

User not authorized

Error ID: S_403

Summary:

This error occurs when the user is not authorized for the action the user tries to perform. For several actions, the user needs to have Administrator or System Administrator rights or has to 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 the Team Server what rights this user has. Perform the action yourself, or assign the user the necessary right to perform the action himself.

Internal server error

Error ID: S_500

Summary:

This error indicates that the server has behaved in an unexpected way 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 try and 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 the problem can be reproduced by BiZZdesign.

Step 2: Record the preconditions and environment

To ensure your scenario can be reproduced by BiZZdesign, provide as much information as possible. Try to provide the following information:

  • Team Server version.
  • Modeling tool version (the tool that uploaded the data to the server).
  • Team Server environment: which type of machine, operating system, deployment configuration, and so forth.

Step 3: Send in your detailed 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.
 

Invalid hash

Error ID: S_501

Summary:

This error is given when something went wrong during the encoding or decoding of a hash value.

Solution:

If the error can be reproduced, send in 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.
 

Mail error

Error ID: S_502

Summary:

This error indicates that there is a failure while sending an e-mail.

Solution:

Check that in the configuration settings the hostname and port are correct 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.

It is possible that there is an issue with the remote SMTP server, depending on firewalls or misspelled domains. Check the configurations.

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

Team Server not configured

Error ID: S_503

Summary:

The Team Server has not been configured yet.

Solution:

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

Unable to locate the SQL database driver

Error ID: S_504

Summary:

This may mean the Team Server was not correctly installed.

Solution:

To resolve this problem you will need to shut down the Team Server and ensure that you installed the SQL driver properly. The steps to accomplish this can be found in the Team Server installation and setup.
 

Pagination exception

Error ID: S_505

Summary:

This error is given when retrieving data for a 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:

Start from page 1 again, or go back to the home page.
 

License error

Error ID: S_506

Summary:

No license has been activated.

Solution:

Please contact BiZZdesign support and request a license key. Activate your license by registering the license key on the Team Server License page.
 

Invalid URL

Error ID: S_507

Summary:

The URL is not a valid URL.

Solution:

Make sure that the protocol of the URL is HTTP or HTTPS, and that the URL is formatted properly. For example: http://hostname:8080.
 

E-mail settings error

Error ID: S_508

Summary:

There is a problem in the settings of the Team Server e-mail configuration.

Solution:

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

Could not initialize hosted session

Error ID: S_509

Summary:

This error is given when something unexpected has happened during generating the URL for starting Enterprise Studio Online (hosted solution).

Solution:

To resolve this, please contact BiZZdesign Support.
 

General settings error

Error ID: S_510

Summary:

There is a problem in the general settings of the Team Server.

Solution:

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

Active Directory settings error

Error ID: S_511

Summary:

There is a problem in the Active Directory settings of the Team Server.

Solution:

Check in the Team Server if the required settings are filled in and if all values are correct via Settings > Authentication (Settings > Directory integration in Team Server versions before 3.1.1).
 

Hosting session settings error

Error ID: S_512

Summary:

Applicable only to Enterprise Studio Online (hosted solution).
There is a problem in the hosting session settings of the Team Server.

Solution:

Please contact BiZZdesign Support to fix this problem.
 

Azure Active Directory settings error

Error ID: S_513

Summary:

There is a problem in the Azure Active Directory settings of the Team Server.

Solution:

Check in the Team Server if the required settings are filled in and if all values are correct via Settings > Authentication. Check if the error message provides more information about the error.

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

SAML 2.0 settings error

Error ID: S_514

Summary:

There is a problem in the SAML 2.0 settings of the Team Server.

Solution:

Check in the Team Server if the required settings are filled in and if all values are correct via Settings > Authentication. Check if the error message provides more information about the error.

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

Invalid license key

Error ID: S_515

Summary:

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

Solution:

Request a new license key.

License expired

Error ID: S_516

Summary:

The license has expired. The error should be reported to an administrator.

Solution:

Request a new license key.

License activation expired

Error ID: S_517

Summary:

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

Solution:

Please contact BiZZdesign to request a new license key.
 

License invalid server ID

Error ID: S_518

Summary:

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

Solution:

Please contact BiZZdesign.
 

Model package or project does not exist

Error ID: S_1000

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, along with the scenario to reproduce the error.
 

Claiming objects error

Error ID: S_1001

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 and 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 the problem can be reproduced by BiZZdesign.

Step 2: Record the preconditions and environment

To ensure your scenario can be reproduced by BiZZdesign, provide as much information as possible. Try to provide the following information:

  • Team Server version.
  • Modeling tool version (the tool that uploaded the data to the server).
  • Team Server environment: which type of machine, operating system, deployment configuration and so forth.

Step 3: Send in your detailed 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.
 

Contribution does not exist

Error ID: S_2000

Summary:

The requested contribution does not exist.

Solution:

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

Contribution parse error

Error ID: S_2001

Summary:

The contributions are saved in a specific format. If this can't be parsed in order to process a contribution, a contribution parse error is given.

Solution:

Check that the versions of the BiZZdesign tools you are using are compatible with each other. 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 the problem can be reproduced by BiZZdesign.

Step 2: Record the preconditions and environment

To ensure your scenario can be reproduced by BiZZdesign, provide as much information as possible. Try to provide the following information:

  • Team Server versions: the current version and the version of the time the contribution was created.
  • Modeling tool version (the tool that uploaded the data to the server): the current version and the version of the time the contribution was created.
  • Team Server environment: which type of machine, operating system, deployment configuration and so forth.

Step 3: Send in your detailed 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.
 

Branch does not exist

Error ID: S_3001

Summary:

This error indicates that there was an exception when a branch is updated.

Solution:

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

Branch update error

Error ID: S_3002

Summary:

This error is given when the creation or update of a branch failed.

Solution:

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

Branch already exists

Error ID: S_3003

Summary:

This error is given when the user tries to create a branch that already exists.

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.
 

Increment does not exist

Error ID: S_3004

Summary:

This error indicates that the requested  increment does not exist.

Solution:

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

Removed claims

Error ID: S_3005

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 in order to create a backup. The changes in the model package will then automatically be reverted and the error should not occur anymore.
 

Checkout does not exist

Error ID: S_3006

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, along with the scenario to reproduce the error.

Checkout of an unchangeable model

Error ID: S_3007

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 currently 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 the Team Server to verify its scope. If the model is part of the scope and the error persists, report this issue to BiZZdesign Support, along with the scenario to reproduce the error.
 

Increment already exists

Error ID: S_3008

Summary:

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

Solution:

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

Too many meta-increments

Error ID: S_3009

Summary:

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

Solution:

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

Metabranch out of date

Error ID: S_3010

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 the Team Server.

Increment committed

Error ID: S_3012

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 of creating a commit for an increment.

This situation is normally prevented by the Activity Console by creating a new increment after committing for storing new claims for the changes being made. The data stored in the Team Data folder is inconsistent with the data stored on the Team Server.

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 Team Server must be added again.


User does not exist

Error ID: S_4000

Summary:

The requested user does not exist.

Solution:

Check the Users page in the Team Server 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, along with a scenario to reproduce the error.
 

No e-mail address

Error ID: S_4002

Summary:

This error indicates that 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, along with a scenario to reproduce the error.
 

No password

Error ID: S_4003

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.
 

Invalid token

Error ID: S_4004

Summary:

The given token is not valid.

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.
 

Token expired

Error ID: S_4005

Summary:

This error is given when the token for the session has expired.

Solution:

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

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

User already exists

Error ID: S_4007

Summary:

This error indicates that adding a user failed because it already exists.

Solution:

When one tries to register a new user to a server, the e-mail address of this user should not already be used for registration. Check the Users page on the server to see if the user is already registered.

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

User not invited

Error ID: S_4008

Summary:

This error indicates that the user is not invited to the model package.

Solution:

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

User removed

Error ID: S_4009

Summary:

Someone has deleted your user account, and you no longer have access.

Solution:

Contact your system administrator for more information.


Last administrator user

Error ID: S_4010

Summary:

The last user with administrator rights who originates from the Team Server cannot be removed.

Solution:

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

Password not secure

Error ID: S_4011

Summary:

The provided password does not meet the security requirements.

Solution:

Make sure the password is conforming to the password policy that has been set for this Team Server. The exact password requirements are mentioned in the error message in the Team Server.

API client removed

Error ID: S_4012

Summary:

Someone has deleted this API client account, and it no longer has access.

Solution:

Contact your system administrator for more information.


License seats exceeded

Error ID: S_4013

Summary:

Adding or inviting users failed because the Team Server 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 the Team Server 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.

Username error

Error ID: S_4014

Summary:

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

Solution:

Provide a longer username.
 

Synchronize users error

Error ID: S_4015

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:

The error provides an additional message about the cause of this error.

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.

You cannot remove yourself

Error ID: S_4016

Summary:

You are removing yourself as a user of the Team Server.

Solution:

Let another administrator user remove you as a user of the Team Server.

If you are synchronizing users with LDAP, check if the LDAP query is removing you from the Team Server.
 

Only existing users allowed

Error ID: S_4017

Summary:

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

Solution:

The user to be invited is not present in the Team Server yet. Therefore it needs to be added to the Team Server 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 the Team Server. If that is the case, this user just cannot be invited.
 

Reset password not possible

Error ID: S_4018

Summary:

It is not possible to reset a password of a user from Active Directory.

Solution:

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


User cannot be removed

Error ID: S_4019

Summary:

A user that is synchronized with Active Directory via LDAP cannot be removed this way.

Solution:

Users that are synchronized with Active Directory via LDAP can only be removed by changing the LDAP query on the Team Server Directory Integration Settings page of the Team Server, or by removing them from the LDAP server.
 

Group already exists

Error ID: S_4020

Summary:

A group with the given name already exists.

Solution:

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

Group does not exist

Error ID: S_4021

Summary:

The requested group does not exist.

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, along with a scenario to reproduce the error.
 

Only users with Designer role can be invited

Error ID: S_4022

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 the Team Server.

Solution:

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

Incorrect MFA codes

Error ID: S_4023
 
Please try again. The device generates a new code every 30 seconds, you have to provide two consecutive codes. If you keep on having problems, it could mean that the clock of your device needs to be synchronized.

Summary:

You have registered an MFA device, and for that reason, you have to provide two consecutive codes produced by the device when you sign in to the Team Server. 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 on having problems, it could mean that the clock of your device needs to be synchronized.
 

Your password has expired

Error ID:S_4024

Summary:

When you attempt to sign in to the Team Server or attempt to add a storage place in Enterprise Studio, you may get a message saying that your password has expired.

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

Solution:

Visit the Team Server 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.
 

You have reused your expired password

Error ID: S_4025

Summary:

When your Team Server 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, the Team Server will return an error.

Solution:

Ensure that your new password is different from your current password.

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.
 

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

Error ID: S_4026

Summary:

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

Solution:

Choose an e-mail address with an allowed domain.
 

The user profile is invalid

Error ID: S_4027

Summary:

When authenticating with an external identity provider, a user profile is returned. The user profile must contain certain attributes for identifying a user 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.


Just-in-time user provisioning failed

Error ID: S_4028

Summary:

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

Solution:

There is no solution yet. The logs of the Team Server contain detailed information about the error.
 

The provided passwords are not equal

Error ID: S_4029

Summary:

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

Solution:

Try to enter your new password again.
 

MFA code needed

Error ID: S_4030

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:

Please enter an MFA code to complete the sign-in.
 

Invitation does not exist

Error ID: S_4031

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, along with the scenario to reproduce the error.
 

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

Error ID: S_4032

Summary:

A REST request was made with an unknown "order by" option for groups.

Solution:

Please contact BiZZdesign Support to fix this problem.
 

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

Error ID: S_4033

Summary:

A REST request was made with an unknown "order by" option for users.

Solution:

Please contact BiZZdesign Support to fix this problem.


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

Error ID: S_4034

Summary:

A REST request was made with an unknown "order by" option for API clients.

Solution:

Please contact BiZZdesign Support to fix this problem.


API client already exists

Error ID: S_4035

Summary:

An API client with the provided client ID already exists.

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 the Team Server if the client ID already exists.


API client does not exist

Error ID: S_4036

Summary:

The requested API client does not exist.

Solution:

Check the API Clients page in the Team Server 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, along with a scenario to reproduce the error.


Model package or project does not exist

Error ID: S_5000

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, along with the scenario to reproduce the error.
 

Model package or project deleted

Error ID: S_5001

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, along with the scenario to reproduce the error.
 

Model package or project ordering method not correct

Error ID: S_5004

Summary:

This error occurs if a request is made to the Team Server 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 the Team Server. If you are sure your connection is not tampered and you keep seeing this error, please contact BiZZdesign Support.
 

The type is not known for model packages and projects

Error ID: S_5005

Summary:

A REST request was made with an unknown collaboration type.

Solution:

Please contact BiZZdesign Support to fix this problem.