Investigate PCS 7 V7.1 SP3 Error 300:13 When a Multiproject Hierarchy Will Not Display

PCS 7 V7.1 SP3 Error 300:13 in this report occurs when SIMATIC Manager cannot start a multiproject subproject database, preventing the project hierarchy from displaying. The discussion does not establish the cause or a confirmed repair. Preserve a supported project backup, record the failing context and logs, compare only on safe copies, and obtain a PCS 7 V7.1 SP3-specific recovery procedure before changing project data.

What Error 300:13 establishes

In the reported PCS 7 V7.1 SP3 multiproject, two projects would not display their hierarchy and SIMATIC Manager reported Error 300:13 (unable to start database). The available discussion points to two related Siemens support topics, but the archived replies omit those links and give no confirmed correction. The error text identifies a project-database startup failure in that context; it does not establish a specific cause or safe repair.

Preserve project integrity before diagnosis

Stop repeated open attempts if the failure is consistent and make a recoverable backup of the multiproject using the supported PCS 7/STEP 7 project archive procedure. 2. Record which projects fail, which still open, the full error text, project storage path, Windows account, and recent edits or system changes. 3. Confirm that the project is being opened with the same compatible engineering installation used for PCS 7 V7.1 SP3. 4. Check available disk space and Windows/application logs for errors at the exact time the hierarchy is opened. 5. Compare behavior on a separate backup copy and a known-good project without modifying originals.

Escalation data to collect

Collect the SIMATIC Manager and PCS 7 component versions, Windows version, multiproject/project path, precise project view and action that raises the error, whether the same projects fail on another authorized engineering station, and any contemporaneous database/service or access errors. Include the full Siemens support reference if it can be recovered. A concise reproduction and unmodified backup are more useful than deleting or rebuilding databases.

Why common repair guesses are unsafe

The thread does not confirm a database repair command, SQL service change, registry edit, file deletion, or successful recovery. Do not rebuild project hierarchy, remove internal database files, or apply a generic “database problem” workaround without a PCS 7 V7.1 SP3-specific Siemens procedure and a verified rollback copy.

Verification

After an approved repair on a copy, reopen the affected project in SIMATIC Manager and confirm that the hierarchy and relevant objects display consistently. Reopen the multiproject and verify other projects remain intact. Do not treat absence of the dialog on one attempt as proof that the project database is healthy.

Limitations and Operational Precautions

The ticket includes no screenshots, project files, database logs, Windows details, recent-change history, or actual resolution. The two reply links referenced by the commenters are absent. No root cause can therefore be selected from the evidence. Preserve source backups and request Siemens support guidance applicable to PCS 7 V7.1 SP3 before attempting repairs that alter project data.

Engineer FAQ

Does Error 300:13 identify the exact database fault? No. The archived text provides only “unable to start database” and does not identify a cause.

Did the replies provide a verified fix? No. They refer to two support topics, but their links and procedures are absent from the archived thread.

Can I delete database files to force a rebuild? The available evidence does not support that action; protect the project and use a documented recovery procedure.

How can I narrow down whether the fault is local or project-specific? Test only an authorized backup copy on a compatible engineering station and compare with a known-good project while recording the same error context.

What should be sent to Siemens Support? The exact PCS 7/STEP 7 and Windows versions, project path, steps, full error, logs, and a backup handled under site data-security rules.

Technical References

Siemens support forum: “Database problem”, supplied by the original poster as a related thread; the page was not accessible during verification and is not treated as a validated repair procedure.
No accessible release-matched Siemens procedure explaining or repairing Error 300:13 in PCS 7 V7.1 SP3 was located; the exact recovery remains unresolved.