JobBOSS Script Error: How to Diagnose It, and What Triggers and Custom Apps Are
jobboss script error
Also searched as
- jobboss2 triggers
- jobboss2 custom apps
- jobboss script error on save
Short answer
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.
Applies to: JobBOSS and JobBOSS2 installations with custom scripts, triggers or custom apps. How these are built and where they are stored differs by version, so use ECI documentation and your integrator's records.
Diagnose a JobBOSS script error
- 1Write down the exact error text, the screen, the action (save, post, open, print) and the user. Take a screenshot.
- 2Check if it happens for every user and every record, or only for one user or one job. Record-specific errors usually mean bad data.
- 3Find out what changed: a JobBOSS update, a Windows or Office update, a SQL change, or a new workstation.
- 4Identify the script or trigger attached to that screen or event. Your integrator or ECI should have an inventory. If there is none, start one.
- 5Reproduce on a test copy of the database with the same version. Do not experiment in live data.
- 6Read the script logic for dependencies: table and field names, external files, COM or driver references, network paths and email settings.
- 7Fix and retest with edge cases (empty fields, large quantities, special characters), then roll out to all workstations and record the change.
Typical causes
Schema change: an update renames or removes a field the script reads. The script worked for years and fails the day after an upgrade.
Environment: a script calls Office, a printer, a mapped drive or a driver that exists on some workstations but not others. If the error happens on one PC, compare it with a working one.
Data: a null value, an unexpected character or a number that is too large. Scripts often assume clean data.
Permissions: the user cannot read a file or write to a table the script touches.
Triggers and custom apps in JobBOSS2
A trigger runs custom logic when something happens in the system, such as saving a job or changing a status, for example to validate data or notify someone. A custom app extends the interface with extra screens or workflows that suit your shop.
Both are powerful, and both need discipline: version control, a test copy, documentation of what each one does, and a named owner. Prefer a trigger or custom app over editing the database, since they run through the application and its security.
Check with ECI what the supported extension model is for your edition and version.
Preventing script errors
Keep an inventory of every script and trigger with its purpose, owner and dependencies. Test them as part of any upgrade, before production.
Write scripts to fail gracefully: check for nulls, catch errors, log them to a table or file, and show a plain message rather than a raw stack trace.
Try it here, free
JobBOSS to E2 Shop System Migration Checklist
A 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.
Common pitfalls
- !Fixing in production without testing.
- !No inventory of scripts, so nobody knows what fires when.
- !Assuming it is a JobBOSS bug when custom code failed.
- !Scripts that depend on a single workstation's local setup.
- !Skipping script testing after an upgrade.
- !Swallowing errors silently, which hides data problems.
How an ERP-grounded AI assistant handles this
An assistant can help read a script and the failing record: given the error text and the job, it can query the data for nulls or odd values and explain what the script expects. It does not edit or run scripts in production. Where code and data are sensitive, a model running on your own servers keeps both inside your network.
Frequently asked questions
What causes a JobBOSS script error?
Usually custom code hitting a changed field, a missing driver or file, a permission problem or unexpected data, rather than a fault in the core application.
What are JobBOSS2 triggers?
Custom logic that runs when something happens in the system, such as saving a record or changing a status. Confirm availability and syntax for your version with ECI.
What are JobBOSS2 custom apps?
Extensions that add screens or workflows tailored to your shop, built on top of the application.
Can I disable a script to find the fault?
On a test copy, yes. Avoid doing it in production, and record what you change.
Related
JobBOSS 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.
How-toJobBOSS2 API: Documentation, Keys and Integration Options
There is no single public developer portal you can sign up to for instant JobBOSS keys. Integration options are the vendor-provided API or web services where your edition includes them (which ECI grants through your licence and account), direct read access to the SQL Server database for reporting, and file or report-based exchange. Ask ECI or your reseller what API access your version includes and how keys are issued, and use read-only SQL access for analytics.
How-toHow to Install JobBOSS: Server, Workstations and Drivers
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.
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 for JobBOSS2 quoting and scheduling
How AI helps JobBOSS2 job shops quote from past job actuals and explain scheduling conflicts, with read-only access and private hosting options.
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 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.
- 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.
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.
- 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.
- 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.
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 use ChatGPT with ECI JobBOSS2Using ChatGPT with JobBOSS2: exports versus live access, custom GPT actions over an API, enterprise data controls, and when a private model is the safer choice.
- 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.