# Recover from a Database or Startup Failure

### Recover from a Database or Startup Failure

### Overview

This guide will help you identify the startup stage that failed and restore safe application access without risking the database.

If this issue is stopping your work, do not worry. Follow the steps one at a time, and check the result before trying again.

Startup resumes at the correct stage or the issue is isolated without uncontrolled database changes.

### Who can do this

You need access to Application launch is general; connection, SQL Server, migration, restore, and settings changes require administration authority.

### Before you start

Record stage, full sanitized message, time, version/build, server/database identity, last successful launch, recent changes, service/network state, free space, and verified backup.

<div id="bkmrk-%F0%9F%9A%A8-importantmake-sure" style="border-left: 4px solid #dc2626; background: #fef2f2; padding: 12px 16px; margin: 15px 0; border-radius: 4px;">Before saving, check that the correct company is open and that you have permission to complete this task.</div>### Where to find it

Launch Muhasib and use Database Setup/Connection Manager only after identifying the failure stage.

### Recover from a Database or Startup Failure

#### Step 1: Stop repeated launch attempts if migration or write activity is possible

#### Step 2: Confirm executable/version and workstation clock/resources

#### Step 3: Check SQL Server service, network, server name, authentication, and database

Check SQL Server service, network, server name, authentication, and database availability without printing credentials.

#### Step 4: Confirm configuration points to the intended database

#### Step 5: Preserve logs and create/verify a backup before migration or repair

#### Step 6: Reproduce on an isolated copy where possible

#### Step 7: Escalate with sanitized evidence if integrity is uncertain

### Check your work

Muhasib reaches login/company workspace and representative read-only reports show expected data/version.

<div id="bkmrk-%F0%9F%92%A1-tipcheck-the-saved" style="border-left: 4px solid #2563eb; background: #eff6ff; padding: 12px 16px; margin: 15px 0; border-radius: 4px;">Take a moment to check your work before closing the window. This small check can save time later.</div>### If something goes wrong

- Do not create a new empty database merely because the existing one is unreachable.
- Never restore over the target without explicit authorization and a pre-restore backup.

### Related guides

- [Connect Muhasib ERP to an Existing Database](https://docs.muhasiberp.com/link/554)
- [Restore a Database Backup Safely](https://docs.muhasiberp.com/link/284)
- [Collect Safe Diagnostic Evidence for Support](https://docs.muhasiberp.com/link/594)

### What to do next

<div id="bkmrk-%E2%9C%85-next-actioncontinu" style="border-left: 4px solid #16a34a; background: #f0fdf4; padding: 12px 16px; margin: 15px 0; border-radius: 4px;">[**Connect Muhasib ERP to an Existing Database**](https://docs.muhasiberp.com/link/554).</div>