How to Install JobBOSS: Server, Workstations and Drivers
how to install jobboss
Also searched as
- jobboss workstation
- jobboss workstation driver
- jobboss client install error
Short answer
A JobBOSS install has two halves: a SQL Server database on a server, and a client (workstation) install on each PC that connects to it. Prepare the SQL Server instance and account permissions first, install the server components from the media ECI provides, then run the workstation setup on each PC and point it at the server. Most install failures come from SQL connectivity, permissions or missing prerequisites, not from the installer itself.
Applies to: JobBOSS and JobBOSS2 on-premises installations on Windows with SQL Server. Exact installers, versions and prerequisites come from ECI and change by release, so follow the install guide for your version.
Install JobBOSS from scratch
- 1Get the install media and release notes for your exact version from ECI or your reseller. Read the supported Windows and SQL Server versions before you start.
- 2Prepare the server: current Windows Server patches, enough disk for data and backups, a static address or DNS name, and the right time zone.
- 3Install or confirm SQL Server (or Express if your licence and database size allow it). Enable TCP/IP in SQL Server Configuration Manager and note the instance name and port.
- 4Open the firewall for the SQL Server port between workstations and the server, and allow the SQL Browser service if you use named instances.
- 5Run the server install, create or restore the JobBOSS database, and note the database name and the SQL login the application will use.
- 6On each workstation, install the client from the workstation setup, with any required runtime prerequisites, then configure the connection to the server and database.
- 7Log in as an administrator, test a few core screens and a report, and set up backups before users start entering data.
What the workstation needs
A workstation needs the client application, the runtime libraries the release requires, and a working database connection. What people call the JobBOSS workstation driver is generally the database connectivity component (ODBC or SQL client driver) that the client uses. If the client reports it cannot connect, check that driver and its bitness first.
Install as an administrator, and avoid mapping drives through different credentials than the user will run with, because mapped paths for attachments and report output are a common source of permission errors.
Checking SQL Server connectivity
From the workstation, test the connection outside JobBOSS. If sqlcmd or an ODBC test cannot reach the server, the application never will. The problem is almost always one of four things: TCP/IP disabled, firewall closed, wrong instance name, or the SQL login lacking rights.
sqlcmd -S SERVERNAME\INSTANCE -U app_login -P *** -Q "SELECT @@VERSION"
REM Check the port from a workstation powershell Test-NetConnection SERVERNAME -Port 1433
Common install and first-run errors
Typical failures are an installer that stops on a missing prerequisite, a client that starts but shows a login or database error, and permissions errors on shared folders. Read the exact message and the installer log rather than retrying, because retrying often leaves partial components behind.
If a workstation worked and then stopped after a Windows update or a SQL change, compare it with a working machine: client version, driver version and connection settings. Keep the client version the same as the server database version, since a mismatch can fail at login.
For anything involving licence keys or database creation, use ECI support, since those steps are specific to your contract.
Try it here, free
JobBOSS Classic AI Assistant Sizing and Value Calculator
Estimate peak concurrency, GPU count, index size, hours saved and payback for a private AI assistant on JobBOSS Classic.
Common pitfalls
- !Installing clients of a different version from the database.
- !Leaving SQL TCP/IP disabled, so workstations cannot connect.
- !Using the sa account for the application instead of a least-privilege login.
- !Putting the database on the same disk as backups.
- !Skipping a test restore and backup schedule before go-live.
- !Installing the client while logged in as a user who will not use it.
How an ERP-grounded AI assistant handles this
Installation is not something an AI assistant should do for you. After it is live, a read-only assistant on the same network can answer questions about the data in plain language without installing anything on every workstation, and it stays inside your firewall when deployed on-prem.
Frequently asked questions
What is the JobBOSS workstation?
A PC with the JobBOSS client installed and configured to connect to the JobBOSS database on the server. Each user machine needs one.
Does JobBOSS need SQL Server?
Yes. Data is held in a Microsoft SQL Server database, so the server must have a supported SQL Server edition before you install.
Why can't my workstation connect?
Check TCP/IP is enabled, the firewall allows the SQL port, the instance name is right, and the SQL login has rights. Test with sqlcmd outside JobBOSS.
Can I install on a laptop for testing?
Yes, a test installation against a restored copy of your database is a good way to rehearse upgrades. Use test data, not live access.
Related
How to Back Up the JobBOSS Database
JobBOSS stores its data in a Microsoft SQL Server database, so a backup is a SQL Server backup, not a copy of program folders. Take a full backup on a schedule, verify it with RESTORE VERIFYONLY, copy it off the server, and take an extra one immediately before any upgrade. Practise a restore into a test database at least once so you know it works.
How-toJobBOSS 2 vs JobBOSS: Differences, Versions and How to Update
JobBOSS2 (often written JobBOSS squared or JobBOSS 2) is ECI's newer job-shop ERP, built as a successor to the classic JobBOSS product. Classic JobBOSS is the long-running SQL Server based system; JobBOSS2 is a rewritten platform with a different interface and architecture. Updating within a product is a patch or version install; moving from classic to JobBOSS2 is a migration project with testing, not a simple update.
Error fixJobBOSS Script Error: How to Diagnose It, and What Triggers and Custom Apps Are
A script error in JobBOSS means custom code attached to a screen or event failed, not that the core application is broken. Note the exact message and the action that caused it, identify which custom script or trigger fired, and test the same action with scripts disabled or on a test copy. Common causes are a changed field or table, a missing reference or driver, a permissions problem, and bad data.
Error fixE2 Shop System Error 5093: Causes and How to Troubleshoot
We could not find an authoritative public definition of E2 error 5093, so treat any single-cause answer with caution. In practice, numbered E2 errors raised at login or while opening a module come from the client talking to the database: a changed server name, a SQL permission or login problem, a missing or mismatched driver, or a network or firewall change. Isolate which with the checks below and give Shoptech support the exact context.
How-toE2 Shop System 7.2 (Shoptech): Versions, Manuals, Training, Support and Reporting
E2 Shop System is Shoptech's ERP and MRP software for job shops and make-to-order manufacturers, covering quoting, orders, scheduling, purchasing, inventory, shop floor tracking and accounting integration. Version 7.2 is one release in its line. For manuals, training, support and upgrade eligibility, Shoptech and its resellers are the authoritative source, so confirm details for your own license.
How-toJobBOSS Public API: What Integration Options Exist for JobBOSS and JobBOSS2
Classic JobBOSS stores data in Microsoft SQL Server, so most custom integrations read it by SQL and write through supported import tools or the vendor's SDK rather than by raw inserts. JobBOSS2 is a newer product and its API and database access depend on how it is hosted and licensed, so confirm with the vendor what is available for your edition before designing around it.
AI for ERPAI for ECI JobBOSS2 and E2 Shop System
Add AI to ECI JobBOSS2 or E2 Shop System for faster quoting, tighter scheduling, and shop-floor answers, without sending your job data to the cloud.
AI for ERPAI Agents for ERP, Running On-Prem
A practical guide to on-prem AI agents for ERP: what they can safely automate, where human approval belongs, and how to design the guardrails.
Stuck on JobBOSS / JobBOSS2 (ECI)?
Talk to engineers who work inside JobBOSS / JobBOSS2 (ECI) every week, and who build private AI that answers these questions from your own ERP data.
Keep exploring
Free tools
- JobBOSS Classic AI Assistant Sizing and Value CalculatorEstimate peak concurrency, GPU count, index size, hours saved and payback for a private AI assistant on JobBOSS Classic.
- JobBOSS Classic Private AI Layer Blueprint GeneratorFill in your version, database, hosting and use cases to get an architecture plan for a private, on-prem AI assistant on JobBOSS Classic, ready to share with IT and security.
- JobBOSS to E2 Shop System Migration ChecklistA practical checklist for moving a small shop from JobBOSS to E2 Shop System, from data audit through cutover and first month close. Works in reverse too.
ERP fixes and how-tos
- JobBOSS2 API: Documentation, Keys and Integration OptionsWhat integration options JobBOSS and JobBOSS2 offer: API access, SQL reads, reports and file exchange, how to get access, and how to connect apps or AI safely.
- JobBOSS 2 vs JobBOSS: Differences, Versions and How to UpdateJobBOSS2 versus classic JobBOSS: what changed, how to find your version, and how to update or upgrade an existing installation safely.
- How to Create Custom Reports in JobBOSS and JobBOSS2Create and customise reports in JobBOSS and JobBOSS2: report designer basics, common shop reports, parameters and SQL-based alternatives.
Guides
- Job Shop ERP Comparison: JobBOSS, E2 Shop System, ProShop and Global ShopJob shop ERP comparison for CNC machine shops: JobBOSS2, E2 Shop System, ProShop, Global Shop Solutions and Epicor Kinetic, and the questions to ask.
- ERP for Forging Companies: Requirements and System OptionsWhat a forging ERP must handle: heat number traceability, billet yield, die tracking, furnace batches and outside heat treat, and how common systems compare.
- ERP for Metal Fabricators: What the System Must HandleERP for metal fabricators and sheet metal shops: nested material, multi-level BOMs, heat number traceability, outside processing, and shop floor data.
AI on your ERP
- AI for JobBOSS2 quoting and schedulingHow AI helps JobBOSS2 job shops quote from past job actuals and explain scheduling conflicts, with read-only access and private hosting options.
- AI for JobBOSS2 in Precision Machining: Quotes, Routings and Job Cost Answers from Your Own DataPrivate AI for JobBOSS2 precision machine shops: quote history, routing actuals, job cost variance and on-time delivery answers, kept on your own network.
Integrations
- How to build an MCP server for ECI JobBOSS2How to build a Model Context Protocol server for ECI JobBOSS2: read-only tools, SQL Server auth, stdio vs HTTP transports, permission scoping and audit logging.
- How to add AI agents to ECI JobBOSS2How to add AI agents to ECI JobBOSS2: a read-first tool layer over the SQL Server data and API, agents for quotes, late jobs and POs, with human approval on writes.
Software
- ECI JobBOSS2Independent profile of ECI JobBOSS2, a job shop ERP: what it does, main modules, integration options, strengths, limits, alternatives and where AI can help.
- ECI M1ECI M1 is an ERP for small and mid-sized discrete and process manufacturers from ECI Software Solutions. See modules, integrations, limits and alternatives.