Agent Setup After Server Change and Software Upgra
Comments
-
Last weekend we moved our Decisions software to a different server and upgraded from version 3.5.1 to 4.0.11. After these changes, our Agents that we had set up within Decisions are no longer working. I tried resetting the agent identity, but that didn’t help because the agent was set up from a different server. From what I can tell, the only way to fix this is to uninstall the agent from the client machines and re-download and install so that it shows as from the current server for Decisions. Is that correct?
-
The bootstrapper agent service, the main service does need to be reinstalled so it can download the new agent core pieces from the app server. You do NOT need to delete the agent from your portal, just open the portal from the agent host machine and run the download agent action to reinstall.
How many agents do you have?
-
We only have two agents, currently. I just tried uninstalling and reinstalling on one of the agent machines. The uninstall worked, but I cannot re-install. Do I need to restart that client for the uninstall to be fully completed?
Howdy, Stranger!
Categories
- 4.2K All Categories
- 67 General
- 11 Training
- 202 Installation / Setup
- 1.1K Flows
- 106 Rules
- 262 Administration
- 212 Portal
- 490 General Q & A
- 695 Forms
- 333 Reports
- 3 Designer Extensions
- 47 Example Flows
- 52 CSS Examples
- 1 Diagram Tile
- 7 Javascript Controls
- 179 Pages
- 5 Process Mining
- New Features
- 179 Datastructures
- 69 Repository
- 221 Integrations
- 28 Multi-Tenant
- 27 SDK
- 78 Modules
- 56 Settings
- 25 Active Directory
- 12 Version 7
- 35 Version 8
- 83 Lunch And Learn Questions