Hello guys,

I found an old thread about missing OS application in the component view.

I have here application where this is also the case.

Opening project on a other ES does not deliver any problems, so the ES is a problem.

I checked the WinCCInstallation docs (RASetup, citamis.str etc.) but I cannot see any problems.

I checked SQL server and in the databases section, I see one database which has the mark: (supect) behind it.

There is no info at all and completely empty. Does someone know if this could be the problem? A suspect database is bad, according to the help section of sql.

What happens if I delete the database? It is on a ES, does simatic manager make a new one? How is this being done.

Thxxx

Hello Jumo,

Thx for your reaction:

No, OS is gone always, also after restart. There was some days before a redundancy problem of the hard disk, maybe database got corrupted.

Lanquage is the same, English, HF is not installed, I checked the manual but no improvements based ona missing OS station.

Cant I just delete the database?

Oreca

Cant I just delete the database?

Hello Guys,

I just figured it out.

There was a corrupt database, not from WinCC but from VersionDoc (the software that makes backups of the PCS7 projects and checks changes).

I deleted the database as it was not from a project and voila, the OS returned.

Note: All projects that were retrieved, were missing the OS.

So somehow SQL server says to Simatic Manager: No OS for you, maybe its a fail safe plan or something, but the problem is solved.

Oreca

Hello Guys,

I just figured it out.

There was a corrupt database, not from WinCC but from VersionDoc (the software that makes backups of the PCS7 projects and checks changes).

I deleted the database as it was not from a project and voila, the OS returned.

Note: All projects that were retrieved, were missing the OS.

So somehow SQL server says to Simatic Manager: No OS for you, maybe its a fail safe plan or something, but the problem is solved.

 Would you please guide us through the path to the corrupt database that you mentioned 
cause I have this problem and I can't find a solution for it 
it is for PCS 7 V9.1 SP2

If you are referring to migration from PCS 7 6.1 SP4 to V9.1, you will need to follow a migration step properly before it will work. 

For example, you might need to migrate to PCS 7 V7.1 SP3 first, then jump to next version , probably PCS 7 V8 or 9. 

A database marked as (suspect) in SQL Server is usually due to corruption or startup issues, and yes, that can definitely cause problems in WinCC/Simatic. Don’t delete it outright — some of these DBs are critical and not automatically recreated.

First, run:

DBCC CHECKDB('YourDBName') WITH NO_INFOMSGS, ALL_ERRORMSGS;

to check corruption. If it’s repairable, you can try EMERGENCY mode with REPAIR_ALLOW_DATA_LOSS.

If CHECKDB doesn’t help and you don’t have a clean backup, I’d suggest using a tool like Stellar Repair for MS SQL to recover the database safely without risking further damage.