Environment
Situation
When deploying a model to your Verastream Host Integrator (VHI) server (using Design Tool or the activatemodel command), you may see the following errors 3851 and 3852:
[VHI 3851] The current model could not be deployed to the Verastream Host Integrator server "servername".
[VHI 3852] Deployment of model failed: Cannot establish management session with VHI server 'servername'
[VHI 3852] Deployment of model failed: Signing principal does not match token issuer.
In Design Tool, some of the above errors are visible after you click the Details button:
View Full SizeResolution
Note: After completing these steps, the session server configuration remains intact (deployed models, session pools, etc.).
- On a Windows system, run the Administrative Console application.
- Connect and log into the management server using administrative credentials.
- If the Session Server Explorer view is not visible, click Perspective > Host Integrator > Session Servers.
- Within the Installation > Servers tree node, note your session server name (as you will re-enter it below).
- Right-click your server and click Remove.
- Right-click Servers and click Add Session Server.
- Enter your session server name and click OK.
Re-try your model deployment. If the problem persists, unregister the session server from the management server as follows:
- Stop the session server service as described in KB 7021352.
- Run the following command (as administrator, since it requires operating system elevation):
Windows: %VHI_ROOT%\bin\resetsessionserver.bat
UNIX/Linux: /opt/attachmate/verastream/hostintegrator/bin/resetsessionserver.sh
- Start the session server service as described in KB 7021352.
- Repeat steps 1 through 7 above.
Note: After completing these steps, the session server configuration remains intact (deployed models, session pools, etc.).