Citect 2016 Deployment server Issues

Hi,

we have setup the deployment server and deployment client using the configurator on both machines.

the auth file generated from the server was used to enable the client to connect to the server.

we've ensured port 443 is open. 

when starting the citect runtime manager the services fails with the following

Service cannot be started. System.InvalidOperationException: Unhandled Exception occured ---> System.InvalidOperationException: Cannot start the service until the console mode manager has been shut down 5:18:52 PM

Also on the deployment server, the client status is shown as offline.

how can this be resolved?

  • Hi Ignatius,
    Is there another instance of Citect Runtime Manager on this machine? Could you check with Task Manager?
    My understanding is that you can only run one instance of CRM on a machine. I assume that "Console Mode" is referring to CRM being run in non-Service Mode.
    What OS are you running this on? Any patches on Citect 2016?
  • its the July 2018 patch.
    1. we tried to run the Citect Runtime manager as a service but it would fail.
    2. we then manually run the Citect Runtime manager but it says there's no project.
    3. we had to take a compiled project repo from another machine and copy it to the deployment folder in the client machine because the deployment server wasn't able to deploy to the client machine.
    4. to get it to run we had to modify the citect.ini manually to point to the deployment folder etc.
    5. this is not ideal
    6. we've also confirmed the firewall port 443 is open between server and client and both profiles are set to 'Public'
    7. we've also uninstalled the citect studio/program at least twice to start from the beginning, but the client is still 'offline' on the deployment server.

    any other suggestions? are there any other log files which we can review to find the cause?
  • here's a question concerning the citect deployment server service.
    1. can the deployment client be used on a client machine setup to be a remote desktop server?
    2. the reason for the remote desktop server is to allow remote desktop users to access citect views remotely.
    3. what other alternatives are there to get this scenario to work?