Skip to end of metadata
Go to start of metadata

When working with the Team Platform functionality in Enterprise Studio, error and warning messages of the Activity Console 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, pleasecontact BiZZdesign Support.




Internal console error

Error ID: D_500

Summary:

An internal error indicates that the Activity Console 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: Verify your login credentials to the Team Server

  1. In Enterprise Studio, go to File > Options.

  2. On the Storage Places tab, select your available storage place, and then click Change.

  3. Make sure the server URL and username are correct.

  4. To verify your password, remove it from the box, and re-enter it.

  5. Click Finish to make sure you are making a new connection to the Team Server.

Step 2: Check the Activity Console for error messages

If step 1 has not resolved the issue, check your Activity Console to see if it shows any error messages. To view the Activity Console, click its icon in your system tray to open it.

If there are error messages, try to resolve the problem, if possible.

Step 3: Determine the scenario to reproduce the error

If the previous step has not resolved the problem, 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 error. Write down each scenario step so that the problem can be reproduced by BiZZdesign.

Step 4: 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).
  • Environment: which type of machine, operating system, deployment configuration and so forth.
  • Activity Console error messages (if applicable).

Step 5: 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.
 

Model package or project does not exist

Error ID: D_1000

Summary:

This error occurs when the user tries to access a model package or project 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.
 

Model package delete error

Error ID: D_1010

Summary:

This error occurs when something goes wrong with deleting a model package.

Solution:

It might be that the model package is still in use, verify that the user has closed the model package, wait for a few minutes and try again. If the problem persists, please report this issue to BiZZdesign Support, along with the scenario to reproduce the error.
 

Unexpected state of model package

Error ID: D_1020

Summary:

The model package or project was in an unexpected state.

Solution:

If this error occurs when removing a storage place in the Enterprise Studio Options, you are still contributing to one or more model packages or projects stored at the storage place.

In Enterprise Studio, click File > Open, click the storage place you want to remove, and then click Suspend contributing to this model package or Suspend contributing to this project next to the model packages and projects that are in the list.

If this error occurs in another scenario, verify that the error can be reproduced. Please, report this issue to BiZZdesign Support, along with the scenario to reproduce the error.
 

Increment already exists

Error ID: D_1200

Summary:

This error occurs when something goes wrong when trying to claim a branch that is already claimed.

Solution:

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

Increment does not exist

Error ID: D_1201

Summary:

The requested claim 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.
 

Increment committed error

Error ID: D_1202

Summary:

The requested claim is on an increment (keeps track of the claims for the uncommitted changes the users make)  that is already committed.

Solution:

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

Claim synchronization error

Error ID: D_1203

Summary:

This error occurs when something goes wrong when trying to claim a branch that is already claimed.

Solution:

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

Increment removed error

Error ID: D_1204

Summary:

This error indicates that a claim cannot be created because the increment (keeps track of the claims for the uncommitted changes the users make) has been removed.

Solution:

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

Checkout does not exist

Error ID: D_1206

Summary:

This error indicates that the requested checkout 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: D_1207

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, please report this issue to BiZZdesign Support, along with the scenario to reproduce the error.
 

Increment already exists

Error ID: D_1208

Summary:

This error indicates that the increment (keeps track of the claims for the uncommitted changes the users make) 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: D_1209

Summary:

Meta-increments are created to prepare metamodel migrations. Only one such meta-increment (keeps track of the claims for the uncommitted changes the users make) 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.
 

Checkout with metamodel changes

Error ID: D_1210

Summary:

When making changes to the metamodel, the model cannot be checked out to make changes to the model.

Solution:

First commit your changes to the metamodel.
 

Metabranch out of date

Error ID: D_1211

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.
 

Contribution does not exist

Error ID: D_1500

Summary:

This error indicates that the requested contribution 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.
 

Related contribution does not exist

Error ID: D_1501

Summary:

This error indicates that the requested related contribution 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.
 

Model package or project does not exist

Error ID: D_1600

Summary:

This error occurs when the user tries to access a model package or project 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.
 

Create model package or project not allowed

Error ID: D_1601

Summary:

It is not allowed to create the model package of the given type. It is only allowed to create a project for a model package. For example, creating a project for another project is not allowed.

Solution:

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

Invited by does not exist

Error ID: D_1700

Summary:

This error indicates that the user who invited a user for this model package 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.
 

Database SQL error

Error ID: D_2000

Summary:

This is an error that indicates something went wrong during the execution of an SQL query in a database.

Solution:

Verify that the error can be reproduced. Please, report this issue, together with the SQL query that can be found in the details of the error message, to BiZZdesign Support, along with the scenario to reproduce the error.
 

Activity Console integrity check error

Error ID: D_2900

Summary:

Every time the Activity Console is started, it performs an integrity check on the databases. These checks are done in order to protect the user against loss of data.

This error occurs if one of integrity checks has failed. In order to prevent possible further corruption of data, the Activity Console will not start.

Solution:

Please, contact BiZZdesign Support in order to resolve this issue and provide them with the technical information given in the error message.
 

Storage place does not exist

Error ID: D_3001

Summary:

The requested storage place could not be found.

Solution:

Make sure that there is a connection with the network and that the server you try to connect to is available. You can do this by accessing the server via the browser. The URL of the server can be found at the storage places in the Enterprise Studio Options window:

  1. In Enterprise Studio, go to File > Options.

  2. On the Storage Places tab, select your storage place, and then click Change.

  3. In Server, there should be a URL. Copy it, and paste it to your browser, and see if you are able to navigate to it.

If the problem persists and the server is available via the browser, please report this issue to BiZZdesign Support, along with the scenario to reproduce the error.
 

Model package creation error

Error ID: D_3002

Summary:

This error indicates that there was an error during the creation of a model package.

Solution:

Make sure that there is a connection with the network and that the server you try to connect to is available. You can do this by accessing the server via the browser. The URL of the server can be found at the storage places in the Enterprise Studio Options window:

  1. In Enterprise Studio, go to File > Options.

  2. On the Storage Places tab, select your storage place, and then click Change.

  3. In Server, there should be a URL. Copy it, and paste it to your browser, and see if you are able to navigate to it.

If the problem persists and the server is available via the browser, please report this issue to BiZZdesign Support, together with the extra information that can be found in the details of the error message, along with the scenario to reproduce the error.
 

Team Server version error

Error ID: D_3004

Summary:

This error indicates that the version of the Team Server cannot be understood by the Activity Console.

Solution:

Make sure that the Team Server URI you provided when configuring the storage place in Enterprise Studio is correct and points to an accessible Team Server. You can verify this by accessing the Team Server via your preferred browser, using the URI you configured for the storage place. The URI you configured for the storage place is available in the storage place dialog at the modeling tool's application settings.

If the problem persists, please report this issue to BiZZdesign Support, together with the extra information that can be found in the details of the error message, along with the scenario to reproduce the error.
 

User not authorized

Error ID: D_3005

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 rights or has to be the creator of the selected model package.

Solution:

A possible cause could be that the user is invited, but hasn't registered yet. Make sure that the invited user has registered.

If the user already has registered, 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.
 

Sharing not supported

Error ID: D_3006

Summary:

This error indicates that the storage place does not support sharing.

Solution:

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

Network error

Error ID: D_3007

Summary:

Something went wrong in the communication with the Team Server.

Solution:

Make sure that there is a connection with the network and that the server you try to connect to is available. You can do this by accessing the server via the browser. The URL of the server can be found at the storage places in the Enterprise Studio Options window:

  1. In Enterprise Studio, go to File > Options.

  2. On the Storage Places tab, select your storage place, and then click Change.

  3. In Server, there should be a URL. Copy it, and paste it to your browser, and see if you are able to navigate to it.

If you are unable to, please contact your System Administrator.

If the problem persists, please report this issue to BiZZdesign Support, together with the extra information that can be found in the details of the error message, along with the scenario to reproduce the error.
 

Storage place offline

Error ID: D_3008

Summary:

This indicates that this action is not allowed when a storage place is offline.

Solution:

Check your network connection and perform a "Synchronize all" in the Activity Console. If the storage place is still offline, contact the system administrator of the server.

Making offline changes inside a model is allowed by taking the model offline, before going offline. Take the model offline by right clicking it in the model browser, and clicking Edit offline.
 

Unexpected state of storage place

Error ID: D_3009

Summary:

When a user is not allowed to access a storage place anymore, the storage place is marked for removal. Enterprise Studio will remove the working copy and notify the Activity Console.

When the Activity Console is notified, the storage place is expected to be marked for removal.

Solution:

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

Different storage server error

Error ID: D_3010

Summary:

When a user changes the location of a storage place, a check is performed to make sure the storage place itself is the same. If a different storage place, with a different ID, is found, this error is given.

Solution:

Make sure that the new location is correct. If the location is a new or a different location, add a new storage place instead of editing an existing one. When that does not reveal the problem, please report the issue to BiZZdesign Support, along with a scenario to reproduce the error.
 

Certificate rejected

Error ID: D_3011

Summary:

The certificate used by the storage place is self-signed, expired or invalid and therefore rejected by the Activity Console.

Solution:

This certificate is needed to establish a secure connection, and must be accepted by the Activity Console to work with this storage place. If you trust the storage place, activate the Accept all server certificates option in the storage place settings. To access these settings, open the Enterprise Studio Options window, and on the Storage Places tab, select the storage place, and click Change.



 

Team Server version is too new

Error ID: D_3012

Summary:

This error indicates that the version of the Team Server is too new, and communication cannot be safely established. The communication protocol has been upgraded and due to this enhancement has received backward incompatible changes. The Activity Console cannot communicate with that specific Team Server.

Solution:

The Team Server has been upgraded to a newer version, but your Activity Console has not yet been upgraded. If you want to communicate with the selected server you must upgrade your Activity Console as well. You can accomplish this by installing a newer version of Enterprise Studio.

Contact your system administrator and verify if there is a new version of Enterprise Studio available, or contact BiZZdesign Support to request a new version.
 

Team Server version is too old

Error ID: D_3013

Summary:

This error indicates that the version of the Team Server is too old, and communication cannot be safely established. Your Activity Console requires a newer version of the Team Server, as it requires specific features that are not provided by the Team Server you are trying to connect with.

Solution:

The Team Server should be upgraded to a newer version so it supports the features your Activity Console needs.

Contact your system administrator and request an upgrade of the Team Server.
 

Hosting session file version too new

Error ID:D_3014

Summary:

Applicable only to Enterprise Studio Online (hosted solution).

This error occurs if the hosting session file contains a version that is not compatible with the version the Activity Console expects. The hosting session file version is too new and has broken backward compatibility. The Activity Console must be upgraded.

Solution:

Please, report this issue to BiZZdesign Support, along with the scenario to reproduce the error.
 

Hosting session file version too old

Error ID: D_3015

Summary:

Applicable only to Enterprise Studio Online (hosted solution).

This error occurs if the hosting session file contains a version that is not compatible with the version the Activity Console expects. The version of the hosting session file is too old. The Activity Console requires a newer version with new specific features.

Solution:

Please, report this issue to BiZZdesign Support, along with the scenario to reproduce the error.
 

Incompatible hosting session file version

Error ID: D_3016

Summary:

Applicable only to Enterprise Studio Online (hosted solution).

This error occurs if the hosting session file contains a version that is not compatible with the version the Activity Console expects. A development version is expected, while a released version is provided.

Solution:

Please, report this issue to BiZZdesign Support, along with the scenario to reproduce the error.
 

Hosting session file version error

Error ID: D_3017

Summary:

Applicable only to Enterprise Studio Online (hosted solution).

This error occurs if the Activity Console is unable to interpret the hosting session file. The hosting session file does not contain the version property needed to determine the version of the file.

The error also occurs if the hosting session file contains an invalid format for the version.

Solution:

Please, report this issue to BiZZdesign Support, along with the scenario to reproduce the error.
 

Storage place removal error: active model package or project

Error ID: D_3018

Summary:

This error occurs if there is still an active model package or project when the user tries to delete a storage place. A storage place can only be removed if contributing to all model packages and projects on the storage place has been suspended.

Solution:

Suspend contributing for all model packages and projects on the storage place you try to remove, and try to remove the storage place again.
 

Storage place removal error: model package or project being suspended

Error ID: D_3019

Summary:

This error occurs if a model package or project is still in the process of being suspended for contributing when the user tries to delete a storage place. A storage place can only be removed if contributing to all model packages and projects on the storage place has been suspended, and that the suspension process has been synchronized.

Solution:

Please wait for the synchronization to succeed, and try to remove the storage place again. If you do not wait, you risk losing unsynchronized contributions and retaining unused claims and checkouts on the Team Server.
 

Sign in to Team Server was canceled

Error ID: D_3020

Summary:

This error occurs when the authentication step of adding a storage place is canceled by the user. Enterprise Studio delegates the authentication step to the Activity Console. When the user cancels that step, Enterprise Studio receives this error.

Solution:

Make sure you choose one of the authentication options in the authentication dialog after clicking Finish in the Add storage place wizard of Enterprise Studio.
 

Data service could not be found

Error ID: D_3021

Summary:

Enterprise Studio tries to access a service API that is unknown to the Team Server associated with the corresponding storage place.

Solution:

Configure the service in the application.conf file, at horizzonServiceUrl.
 

Storage place synchronize error

Error ID: D_3023

Summary:

Some actions require synchronizing data of the storage place with the server. For example adding a new storage place, or applying the commits of a project to its master model package. An internal error occurred synchronizing data of the storage place.

Solution:

If the details of the message are not giving a clear solution, try to solve the problem by trying again. There could have been 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.

Token refresh error

Error ID: D_3024

Summary:

The access token for accessing the Team Server could not be renewed.

Solution:

The Activity Console will retry automatically until the problem is resolved. The details of the error message can give additional information about the problem. Please contact your System Administrator if you are unable to resolve the problem. 

If the problem persists, please report this issue to BiZZdesign Support, together with the extra information that can be found in the details of the error message.

User does not exist

Error ID: D_4000

Summary:

The requested user does not exist.

Solution:

Check the users page 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, please report the issue to BiZZdesign Support, along with a scenario to reproduce the error.
 

The e-mail address does not belong to the user associated to this storage place

Error ID: D_4001

Summary:

This error indicates that the new e-mail address does not match the e-mail address linked to the user in the Team Server.

Solution:

Enter the e-mail address that is registered with the user in the Team Server.