Cloud29 · Guide
Deploy, connect and manage Evolution Anywhere for Sage 200 Evolution — a step-by-step guide aligned with the official workflow, from download through to Evolution integration.
- Register as a Reseller (if you haven’t already).
- Download the Evolution Anywhere application.
- Install SQL Server 2022 on the server.
- Set up a Server connection in the EA app, then set up Client connections.
- Upload & Deploy your database and start a File Share for BIC if required.
- Manage servers & clients; purchase licenses as needed.
Role
Registered Evolution Anywhere Reseller.
Server
Windows server with SQL Server 2022 installed and reachable.
Workstations
Windows 10/11 for EA client installs.
Network
Stable internet; open/forward required ports per EA guidance.
Quick Access Guide Download EA SQL Server 2022 Setup Server Connection Client Connection Manage Connections Upload & Deploy File Share Buy Licenses
These links mirror Evolution Anywhere’s wiki structure to keep your docs consistent.
- Download the Evolution Anywhere installer from the official site.
- Run the installer and complete the setup wizard.
- Open the EA application from the desktop/start menu.
- Install SQL Server 2022 per the EA guide.
- Note the instance name and TCP port used by SQL.
- In EA, create a Server connection (New → Server → Standard).
- Complete company & contact details and Register Server under your reseller account.
- Verify the generated Access Key/Password and SQL Server name fields.
- Install the Evolution Anywhere app on each workstation.
- When prompted, select installation type: Client.
- In EA, create a Client connection and name it clearly.
- Start the client connection; confirm status shows Active/Ready.
Licensing: To free up a license, stop the client connection when the user is done, then start it for the next user.
- Use the EA accounts portal to view registered servers and their connected clients.
- Open an EA Server/Client from the dashboard to manage remote settings and check network status.
Use EA’s Upload & Deploy to move SQL databases from a source instance or a .bak backup to an EA‑managed server. This helps centralize data for multi‑site access.
Open Guide
- Create a File Share in EA (New → Server → File share) and start it.
- Map the network path on the server; use the provided username/password.
- Point Sage BIC metadata to the mapped drive (not a local path).
File Share Setup
Identify the Sage 200 Evolution company database and confirm the SQL instance/credentials.
Ensure BIC metadata is stored on the mapped network drive created via EA File Share.
Server/Client Connection Fails
- Check required TCP ports and firewall rules.
- Verify Access Key/Password and SQL Server details in the EA app.
SQL Connectivity Issues
- Confirm the SQL instance is listening on the expected TCP port and that EA is updated with that port.
License Availability
- Stop an active client connection to release a license, then start it for the next user.
Q: Do I need a tenant URL?
A: No. Evolution Anywhere uses Server and Client connections configured inside the EA application.
Q: Does it work with Sage 200 Evolution?
A: Yes. Follow the Sage integration guidance and use File Share mapping for BIC.
Q: How do I free a license?
A: Stop the in‑use client connection; the license becomes available for the next user.
For assistance, contact Cloud29 Support:
© Cloud29. All rights reserved.