Seitenvergleich

Congree cannot be updated as long as Congree components are running.

Close all open Congree components and all editors with Congree integration.

1. Check whether the URL can be reached.
   1. To do so, start a browser of your choice on the host on which the crossTerm API is installed.
   2. Open http://localhost/Across/crossTerm/api/v1 in your browser.
      In a multi-server environment, also check whether the API can be reached from other hosts.
      An error occurs: The crossTerm API cannot be reached -> proceed with point 3.
      A service is opened: The crossTerm API can be reached -> proceed with point 4.
2. If an error occurs while checking the reachability, proceed as follows:
   1. Review the Across log file. By default, it is called Across.Services.CrossTerm.log and is located in C:\Program Files (x86)\across\log.
      • If the log folder should have changed: By default, it is defined in the registry in HKLM\Wow6432Node\across in the value LogPath.
   2. If the login data are invalid, modify the Across.Services.CrossTerm.config (default location: C:\Program Files (x86)\across\AcrossServices\crossTerm).
      • The password must be entered in plain text. By default, this is the password of the Across user Default.
3. If the crossTerm API can be reached, but you have received the error message nevertheless:
   
   1. Check your configuration of the server components for the Congree Back End Connector for Across. Has the correct password been entered for the Across user for Congree?
   2. Check your Across Server. (Licensed? All services running?)