Resolve a Muhasib Startup Interruption
How to Resolve a Muhasib Startup Interruption in Muhasib ERP
Overview
This guide will help you classify a startup interruption and take a safe recovery action without risking the business database or licence assignment.
If this issue is stopping your work, do not worry. Follow the steps one at a time, and check the result before trying again.
Muhasib advances to the next allowed lifecycle state or preserves the current state for safe diagnosis; the verification section identifies the expected result.
Who can do this
You need access to Use requires the rights and business authority described by the workflow. Database, licence, user, company, or system changes require the responsible administrator.
Before you start
Record the application version/build if known, database server and database name without credentials, the exact message, and whether this is a new installation, ordinary launch, or upgrade.
Where to find it
Follow the launch, wizard, login, company-selection, Back Office, or power path described in the procedure; the available starting screen depends on current installation state.
Resolve a Muhasib Startup Interruption
Step 1: Identify the stage that failed
Identify the stage that failed:
- before database selection: workstation settings or installation;
- while connecting: server, network, authentication, or database selection;
- while initializing: missing base records, database revision, or migration;
- during activation: network, account, subscription, pairing, or terminal state;
- after activation: plan feature or capacity limit;
- before workspace: company, user, role, or terminal registration.
Step 2: Copy the exact error text or take a sanitized screenshot
Step 3: Check only the dependency named by the error. For example,
Check only the dependency named by the error. For example, check network reachability before changing database settings.
Step 4: Retry once after correcting a known temporary condition
Step 5: If the error concerns migration, partial database creation, licence transfer,
If the error concerns migration, partial database creation, licence transfer, or an unknown data change, stop and contact support.
Step 6: Provide the installed version, database revision when available, terminal type,
Provide the installed version, database revision when available, terminal type, and recent change that preceded the failure.
Check your work
The corrected launch advances past the failed stage and reaches the expected next screen. Make sure the selected company and database are the intended ones.
If something goes wrong
If the expected result is not shown, stop repeated attempts, check the active database/workspace/user/licence context, preserve the exact message, and follow the related recovery article.
Related guides
- Launch Muhasib ERP
- Connect Muhasib ERP to an Existing Database
- Review and Maintain Muhasib Licence Access
- Check the Installed Muhasib Version and Database Revision
- Request Muhasib Support