🔧 Troubleshooting Guide

Sometimes a previous instance didn't fully close. Kill all Electron and AMS processes:

taskkill /f /im "Woven Model AMS.exe"
taskkill /f /im electron.exe

Then try launching again.

Open the app log file to see what went wrong:

notepad "%APPDATA%\woven-model-ams\Logs\app.log"

Look for lines with "level":"error". Common startup errors include missing database files, permission issues, or native module failures.

If the log shows "SQLITE_BUSY" or "database is locked", a previous instance may still be holding the lock. Follow the Database Locked section below.

If the log mentions database corruption, rename the database and restart. The app will create a fresh one:

cd "%APPDATA%\woven-model-ams\Data"
ren AssetManagement.db AssetManagement.db.corrupt

You can try restoring from a backup afterward.

Download a fresh copy of the installer or portable EXE and reinstall. Your data is stored in %APPDATA%\woven-model-ams and won't be affected by a reinstall.

If you forgot the admin password, you can reset it directly in the database:

sqlite3 "%APPDATA%\woven-model-ams\Data\AssetManagement.db"
SELECT * FROM users;                         -- see all users
UPDATE users SET password_hash = NULL WHERE username = 'admin';  -- clear password
.quit

Then restart the app. You'll be prompted to create a new password via the Setup page.

If you don't have sqlite3 installed, use the bootstrap script instead.

If the database was reset or this is a fresh deployment and the Setup page isn't appearing, create an admin user manually:

node scripts/create-test-user.cjs

This creates: admin / admin123. Log in and change the password immediately.

If you were kicked out mid-session, your session token expired. Default timeout is 8 hours. Log in again. You can adjust the timeout in Settings → Session Timeout.

This is a known build issue. After npm run build, you must generate and inject Tailwind CSS manually:

npm run build
node /tmp/build-tailwind.cjs

Then copy the generated CSS over the Vite output:

$assetsDir = "out\renderer\assets"
$viteCss = Get-ChildItem $assetsDir -Filter "index-*.css" | Select-Object -First 1
Copy-Item "$assetsDir\index.css" $viteCss.FullName -Force

If you downloaded a pre-built installer or zip and see a white screen, contact support — the build is missing the CSS step. Download a corrected build.

taskkill /f /im electron.exe
taskkill /f /im "Woven Model AMS.exe"

Wait 5 seconds, then relaunch.

The database uses WAL (Write-Ahead Log) mode. Stale WAL files can sometimes cause lock contention. Close the app, then:

cd "%APPDATA%\woven-model-ams\Data"
del AssetManagement.db-wal
del AssetManagement.db-shm

These files will be recreated automatically on next launch.

If taskkill doesn't work or processes are stuck, a full reboot will clear all file locks.

If you have a recent backup, restore it:

# Stop the app first
cd "%APPDATA%\woven-model-ams\Data"
copy AssetManagement.db AssetManagement.db.pre-restore   # safety copy
copy ..\Backups\AssetManagement_Backup_YYYY-MM-DD.db AssetManagement.db

Replace YYYY-MM-DD with the actual backup date.

You can also restore via the app UI: Settings → Backup → select a backup → Restore.

sqlite3 "%APPDATA%\woven-model-ams\Data\AssetManagement.db"
PRAGMA integrity_check;
-- If errors found:
.mode insert
.output dump.sql
.dump
.output stdout
.quit
-- Then create a fresh DB from the dump:
sqlite3 new.db < dump.sql

Rename the corrupted database so the app creates a new one:

ren AssetManagement.db AssetManagement.db.corrupt_2026

Restart the app. You'll need to recreate your admin account and re-import data. If you have a backup, restore it after creating the admin account.

$db = "$env:APPDATA\woven-model-ams\Data\AssetManagement.db"
(Get-Item $db).Length / 1MB

If the database is >500MB, consider archiving old audit logs:

sqlite3 "$env:APPDATA\woven-model-ams\Data\AssetManagement.db"
DELETE FROM audit_logs WHERE created_at < date('now', '-1 year');
PRAGMA wal_checkpoint(TRUNCATE);
VACUUM;

sqlite3 "$env:APPDATA\woven-model-ams\Data\AssetManagement.db"
REINDEX;

AMS uses ~200-500MB RAM. If you're running many applications simultaneously, close some to free up memory.

In the Assets table, reduce the "Items per page" setting. Smaller pages load faster.

Supported formats:

• Excel: .xlsx or .xls
• CSV: .csv

Make sure your file is not password-protected or in an unsupported format (e.g., OpenDocument .ods).

After selecting your file, you must map your spreadsheet columns to AMS fields. Make sure:

• Every required AMS field has a column mapped to it
• Column names in the dropdowns match your spreadsheet headers

• Remove empty rows at the top of the spreadsheet
• Make sure dates are in a recognizable format (YYYY-MM-DD recommended)
• Ensure numbers are formatted as numbers, not text
• Remove any merged cells

If you're on the Community Edition, you can only import up to 10 total assets. If you already have assets in the system, you won't be able to import more without upgrading or deleting existing assets.

Barcode generation in the main process has a known issue with jsbarcode requiring a DOM. Use the barcode generation option from the Settings page, which runs through the renderer.

Barcode and QR code generation is only available in Professional and Enterprise editions. Community Edition users cannot generate barcodes.

Auto backups are only available in Professional and Enterprise editions. Community Edition users must back up manually by copying the database file.

copy "%APPDATA%\woven-model-ams\Data\AssetManagement.db" "%APPDATA%\woven-model-ams\Backups\manual_backup.db"

Make sure you have enough free disk space. Each backup is roughly the same size as your database.

Go to Settings and verify:

• Auto backup is enabled
• Backup interval is set (default: 24 hours)
• Max backups is > 0 (default: 10)

The app may not have write permission in the Backups folder. Verify:

dir "%APPDATA%\woven-model-ams\Backups\"

If you see permission errors, run the app as Administrator once to create the folder, then return to normal user mode.

Feature gates are re-evaluated on every call — unlocked features take effect as soon as the license is activated; no restart is required. If a locked feature still seems unavailable after activating, check the License page to confirm the edition was applied.

License activation requires a one-time internet connection to validate the key against the licensing server. Make sure you're online during activation. After activation, the app works offline.

The key should be a long alphanumeric string. Make sure you're copying the entire key without extra spaces. Paste it exactly as provided.

If a previous activation attempt failed, clear the stored license and try again:

del "%APPDATA%\woven-model-ams\license.dat"

Restart the app and re-enter your license key.

Go to the License page (shield icon). If it shows "Expired", your subscription may have ended. Contact support to renew.

The Community Edition is limited to 10 assets. Upgrade to Professional or Enterprise for unlimited assets.

Visit the Woven Model Licensing Portal or book a meeting to purchase a license.

If you need to stay on Community Edition, delete some existing assets to make room for new ones. Each deletion permanently removes the asset and its history — back up first.

Many features are edition-gated. Check your license on the License page:

• Minimize: Windows Key + Down Arrow
• Maximize: Windows Key + Up Arrow
• Close: Alt + F4

Window controls were added in a recent update. Make sure you're running the latest build. Download the latest version from the AMS page.

This is exactly what backups are for. Restore the most recent backup from before the deletion:

# Stop the app
cd "%APPDATA%\woven-model-ams\Data"
copy AssetManagement.db AssetManagement.db.safety   # safety copy first
copy ..\Backups\AssetManagement_Backup_BEFORE_DELETION.db AssetManagement.db

Or use the restore function in Settings → Backup.

If you have Professional or Enterprise and can still access the History page, you can see exactly what was deleted and when. This helps you choose the right backup to restore.

• Enable auto-backups in Settings
• Create a manual backup before bulk operations
• Use the role system — give delete permissions only to trusted admins

1. Close the app completely
2. Delete the database:

   del "%APPDATA%\woven-model-ams\Data\AssetManagement.db"

3. Optionally, delete backups and license too:

   rmdir /s /q "%APPDATA%\woven-model-ams\Backups"
   del "%APPDATA%\woven-model-ams\license.dat"

4. Optionally, clear logs:

   del "%APPDATA%\woven-model-ams\Logs\app.log"

5. Restart the app — the Setup page will appear for a fresh admin account

rmdir /s /q "%APPDATA%\woven-model-ams"

This removes the entire app data folder. Next launch creates everything from scratch.