Versions Compared

Old Version 2

changes.mady.by.user Kirstin Seidel-Gebert

Saved on

compared with

New Version 3

changes.mady.by.user Kirstin Seidel-Gebert

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space WBRIDGE and version 20.1c

...

ProblemPossible ReasonSolution
Deploying an xUML service with defined proxy server, the deployment error message Could not start server! is returned.The port of the proxy service instance defined in the component diagram is used by another process.Correct the port number accordingly and redeploy the xUML service.
The proxy start log in the file system (default: <your bridge data directory>\proxies\logs\start.log) reads Access denied.The user (possibly the domain user) that runs the Bridge has no permission to start the proxy.Either assign the user to the local administrator group (not recommended) or grant permissions to allow starting services (e.g. for Windows as described here: How to Grant Users Rights to Manage Services (Start, Stop, Etc.).

The proxy start log in the file system (default: <your bridge data directory>\proxies\logs\start.log) reads

The E2E Proxies xxx service could not be started.
A service specific error occurred: 1.
More help is available by typing NET HELPMSG 3547.

Your proxy configuration is not compatible with the current Apache installation.

With Bridge 7, Apache has been updated to version 2.4. It may be that your proxy configuration is still based on the templates of Apache version 2.2.

Re-apply your modifications of the proxy configuration to the new templates. For more information refer to the Bridge 7 Migration Guide.


The proxy start log in the file system (default: <your bridge data directory>\proxies\logs\start.log) reads
httpd (pid xxxx) already running

but no corresponding httpd process is running.

File <your bridge data>\proxies\logs\httpd.pid has not been automatically deleted, when the proxy has been stopped last time.Remove the mentioned file <your bridge data>\proxies\logs\httpd.pid and start the proxy once again.
In the Windows event log it reads Invalid address or port.You have deployed services that use 0 as proxy port. You can check this in file <your Bridge data directory>/proxies/conf/httpd.conf.Delete the related services and redeploy them with a correct proxy port (or none).

Proxy Service Cannot be Stopped

...