Tekla model recovery

A Tekla model database integrity error requires the complete model folder and backup generations—not one isolated DB file.

Tekla Structures models use multiple database files and shared relationships. A program crash, disk problem, interrupted write-out, or mismatched database set can make the model unreadable or unsafe to share.

Understand the symptom

Tekla database files must represent one coherent model generation.

WHY

What is happening

Tekla documents fatal integrity errors and invalid database versions in Model Sharing. Backup DB files may be used, but mixing files from different generations can create further inconsistency. Diagnose and repair operations should therefore be performed only after a full copy exists.

What you may see

Symptoms that change the recovery path.

01

Fatal database integrity error

Tekla detected model database inconsistency.

02

Model on disk is corrupted

The stored model cannot be opened safely in its current state.

03

Invalid database files detected

One or more DB files do not match the active model generation.

04

Sharing read-in or write-out fails

Local and shared model state may have diverged.

Protect the source

Actions that can make the situation worse.

01

Mixing DB and DB.BAK generations creates inconsistency

Treat the folder as one database set.

02

Repair operations modify the model

Make a full verified copy first.

03

Writing out a damaged shared model propagates errors

Pause sharing until the stable generation is identified.

Do this now

Safe steps before evaluation.

01

Copy the complete model folder

Keep every DB, backup, log, drawing, reference, and environment file together.

02

Stop Model Sharing activity

Prevent additional read-in and write-out operations.

03

Record the incident sequence

Note last write-out, crash, backup, version upgrade, and exact message.

04

Preserve server and workstation copies

Do not choose one as authoritative before timestamps and state are compared.

NEPFOSYS process

How a data-first evaluation proceeds.

01

Database-set comparison

NEPFOSYS maps DB generations, backups, autosaves, logs, and sharing history.

02

Copy-based diagnosis

Tekla-supported diagnostics and backup substitution are evaluated on complete duplicated folders.

03

Model validation

Objects, numbering, drawings, attributes, references, and sharing readiness are reviewed.

A clear next step

Preserve the original device before another repair or recovery attempt.

Start a case with the exact symptoms, incident timeline, prior attempts, encryption details, and the files that matter most. NEPFOSYS will route the case to the appropriate DFW intake or nationwide mail-in path.

Start with a case review

Questions, answered

What customers ask before starting.

Can I replace all DB files with DB.BAK files?

Only on a complete copy and with generation consistency verified. Mixing backup and current files can create another invalid set.

Should I run Diagnose and Repair immediately?

Preserve the entire model folder first because repair changes the database.

Can Model Sharing repair a corrupt local model?

Sharing has backup and repair paths, but damaged state can also propagate. Pause collaboration until the model generation is understood.

DFW local · Nationwide mail-in

Protect the device. Start with the facts.

Start my recovery case