This section provides information on the following issues:
If Atelier is slow or unresponsive when starting, it may be because of the processing required to index large databases. See Improving Start-up Performance for information how to solve this problem.
Some actions in Atelier can take a long time to complete and consume a large percentage of resources while they are running, which has a negative impact on performance. Actions that make heavy use of the parser or the network can fall into this category, as can tasks such as importing many classes and routines from an XML file, opening large files in an editor, and copying a large number of files from the server. If you would like to terminate such a long-running process, you can do so from the Progress View. You can open this view by selecting Window > Show View > Other > General > Progress from the main menu. You can also use double-click on the progress bar in the lower right of the workbench as a short cut.
In the progress view, click on the red button on the right to terminate the process.
Dialogs and views that show a progress bar often also have a red button that you can click to terminate the process.
See Responsive UI for additional information.
Atelier uses the Eclipse secure storage mechanism to store connection information. Normally, access is handled by Atelier without the need for user intervention. On Mac platforms, problems can arise with this system.
In some cases, secure storage becomes corrupted, and connections become unusable. Symptoms of corruption are:
The Workbench User Guide provides information on resolving problems with secure storage. You can also find more detailed information on the secure storage preference page
If none of the suggestons in these resources provide a lasting solution to the problem, as a last resort, disable use of your OS X keyring with Atelier by taking the following steps:
If you receive an error that reads Forbidden: Check your security and license settings. or Service Unavailable: Check your security and license settings. consider the following possibilities when resolving the issue:
Atelier provides two views that can be helpful in troubleshooting. One is the standard Eclipse error log, which you can find at Window > Show View > Error Log. The other is a log of network activity. This view is specific to Atelier and can be found at Window > Show View > Other > Atelier > Network Activities. The information it provides can be useful in troubleshooting problems with communication between the Atelier client and the server.
Eclipse provides a default mechanism for authenticating HTTP connections. This default authenticator, called NetAuthenticator, enables the use of authenticated connections by providing a UI dialog to handle entry of credentials and other details. The Atelier plug-in overrides this default authenticator, as do many other Eclipse plug-ins. Installing the Atelier plug-in overrides the default authenticator, and any other authenticator provided by a plug-in you have installed. As a result, after you have installed Atelier, authentication in other plug-ins does not function as it did previously. Similarly, installing a plug-in that provides its own authentication mechanism overrides what Atelier has installed, and can alter authentication of connections in Atelier.
Plug-ins that supply an authenticator include:
If you are having problems with authenticated connections in Atelier or another Eclipse plug-in, contact the InterSystems Worldwide Response Center for information on how to resolve this issue.
If syntax errors appear in Atelier in previously error-free code, it may be because Atelier has detected syntax errors that Studio and the ObjectScript compiler did not detect. For example, due to a bug in Studio, code such as this was allowed:
When you encounter such anomalies, check the code for accuracy and edit where needed.
If synchronizing a project results in errors of the form:
ERROR #5883: Item 'filename' is mapped from a database that you do not have write permission on.
A likely reason is that you have copied files from one namespace to another, and the copied files are already mapped to the project's namespace from a database for which you do not have write permission.
For example, this problem can arise if you copy files from %SYS to a project mapped to USER. The %SYS files are all mapped to USER, so attempting to synchronize those files to the server always points to a read-only database which results in the error.
Due to recent security enhancements, if you are running on a Mac using macOS 10.12 or later, your Eclipse instance must be installed in the
/Applications directory for Eclipse updates to work correctly. If it is installed in another directory, update fails with the error:
Cannot complete the request. See the error log for details. Atelier IDE will be ignored because it is already installed, and updates are not permitted.
If you are not familiar with Eclipse, you might choose to store your workspace directory on a network drive. Doing so results in substantial delays during synchronization, as well as during the use of underlying Eclipse features related to the workspace. You should put the workspace on a local drive when possible. You can link resources from other locations if necessary. Since you will typically use source control, linked projects will be configured automatically (projects will be in their local repository workspace) with no additional effort.
When you configure Atelier to use an InterSystems database server on an IIS port, IIS needs a handler mapping
/api/atelier* to know how to handle the request."
InterSystems documentation on configuring IIS with the CSP Gateway recommends mapping *.csp, *.cls, *.zen and *.cxw to the CSP Gateway module. When you run the installer on a Windows machine and allow it to set up IIS with the CSP configuration, it creates *.csp, *.cls, *.zen and *.cxw handler mappings. With this default IIS configuration for the CSP Gateway, testing the connection to a server configured in Atelier throws the error "Not Found. Check the web server configurations."
For Atelier communication to the server, IIS needs a handler mapping at the IIS Default Web Site level so that REST requests are passed on to the CSP Gateway. Something like:
Template context options have changed between Atelier 1.0 and 1.1, which renders templates from 1.0 incompatible with a 1.1 instance. Templates from 1.0 imported into Atelier 1.1 are not visible. Any templates you created in 1.0 need to be recreated when you update to 1.1.