Resolving 'Project Language Not Compatible' Error When Opening SIMATIC PCS 7 Projects on Another PC

In SIMATIC PCS 7 and STEP 7, the error 'The project contains data of a language that is not installed on your computer' occurs when a project created on a computer with a specific regional language or codepage (such as Turkish, Russian, German, or Dutch) is opened on an Engineering Station lacking that Windows language pack. To quickly resolve this, navigate to the project directory in Windows Explorer, open the Global folder, and delete or rename the metadata file named Language. When reopened, SIMATIC Manager automatically regenerates this file matching the local computer's installed regional language.

Why SIMATIC Manager Enforces Project Language Compatibility

When sharing SIMATIC PCS 7 or STEP 7 projects between multinational engineering teams, system integrators, and plant sites, engineers frequently encounter a project opening lockout:

The project contains data of a language that is not installed on your computer. 
Do you want to open the project with language English (United States)?

Or worse, a fatal blocking dialog:

The project cannot be opened because the required project language 
is not installed on your operating system.

This error occurs because classic STEP 7 (V5.5 / V5.6) and PCS 7 engineering databases were architected prior to complete universal Unicode adoption. Projects encode symbols, block comments, and plant hierarchy strings using specific regional Windows non-Unicode character sets (such as Windows-1252 for Western Europe, Windows-1254 for Turkish, or Windows-1251 for Cyrillic).

When a project is created, SIMATIC Manager stamps the project's primary engineering language and active Windows system locale into an internal tracking file.

The Role of the `Language` Metadata File in the Global Directory

Within every STEP 7 / PCS 7 project folder, there is a subfolder named Global. Inside Global, the operating system maintains a small metadata file simply named Language (without a file extension):
* This file records the binary codepage ID, language identifier (LCID), and default translation table used when the project was last saved.
* When SIMATIC Manager attempts to open the project on a new PC, it compares the LCID stored inside Global\Language against the languages currently installed in the host Windows operating system.
* If the host PC lacks the matching language pack or non-Unicode system locale, STEP 7 halts initialization to prevent potential character corruption of database strings.

The Zero-Risk Deletion Solution

Because the Language file only stores a session preference pointer and does not contain the actual user program logic, function blocks, or CFC charts:
* Deleting or renaming Global\Language causes SIMATIC Manager to treat the project as language-unassigned.
* Upon opening, SIMATIC Manager automatically queries the destination computer's active Windows language (e.g., English US) and generates a fresh, fully compatible Language file matching the local PC!

Comparison Table - Methods for Resolving Language Incompatibility

The following table compares different approaches to resolving language compatibility errors in PCS 7.

Resolution MethodExecution TimeRequires Windows Reboot?Risk to Project LogicRecommended StatusDelete / Rename Global\Language< 30 secondsNoZero RiskIndustry Best PracticeInstall Windows Language Pack15 - 30 minutesOften YesZero RiskViable if native text must be viewedChange Windows System Locale10 minutesYes (Mandatory reboot)Moderate (Affects all PC apps)Not recommended for multi-client ESSave As with Reorganization5 - 15 minutesNoZero RiskUseful secondary cleanup

Step-by-Step Recovery and Codepage Realignment Procedure

To clear the language incompatibility block and successfully open the PCS 7 project, execute the following steps:

Close SIMATIC Manager:
* Ensure SIMATIC Manager and all engineering tools (CFC, SFC, HW Config) are completely closed.
Locate the Global\Language File:
* Open Windows Explorer.
* Navigate to the project root directory (e.g., D:\Projects\Plant_Project\).
* If the project is a Multiproject, open each contained sub-project folder.
* Open the Global folder.
* Locate the file named Language (File type: File, typically 1 KB to 4 KB in size).
Rename or Delete the File:
* Rename the file to Language.old (or delete it directly).
* If working with a Multiproject, repeat this for the Master Data Library's Global folder and each AS project's Global folder.
Reopen the Project in SIMATIC Manager:
* Launch SIMATIC Manager.
* Select File -> Open and browse to the .s7p or .s7m project file.
* The project opens smoothly without any language incompatibility dialogs.
* SIMATIC Manager automatically writes a new Language file configured for your local Windows system locale.
Set Default Project Language to English (United States):
* To prevent future issues when sharing with other engineers:
* In SIMATIC Manager, select Options -> Manage Multilingual Texts -> Change Language.
* Select English (United States) as the default project language.
* Check Always open project in current language.
* Click OK.

Verification

Confirm that the project is fully accessible and functionally healthy:

Verify Project Hierarchy Navigation:
* In SIMATIC Manager, click through Component View and Plant View.
* Confirm that all folders, charts, and hardware objects display clearly without question marks (???) or gibberish character substitution.
Open HW Config and CFC Charts:
* Open HW Config; confirm that rack definitions load cleanly.
* Open a CFC chart and inspect block names, comments, and parameter values.
Verify File Regeneration:
* In Windows Explorer, check <Project_Dir>\Global\.
* Confirm that a new Language file has been created with the current timestamp.

Limitations and Operational Precautions

Foreign Character Set Display: While deleting Global\Language allows the project to open, text strings originally entered in Cyrillic, Chinese, or Arabic will appear as accented Latin characters or question marks unless the appropriate Windows Language Pack is installed on the operating system.
Never Delete the Entire Global Folder: Only delete the specific file named Language. The Global folder contains other essential database indices (s7finfo, cross-reference pointers) that must never be purged.
Archiving Best Practice: Always archive projects using SIMATIC Manager (File -> Archive); raw zip utilities can preserve stale file locks.

Engineer FAQ

Does deleting the Language file delete any PLC program code or block logic?

No. The Language file stores only the character codepage preference and default language pointer for the engineering editor. It contains zero logic, zero DB values, and zero CFC chart data.

Why does SIMATIC Manager ask 'Do you want to open in English US'?

If the project language exists in Windows but is not the active system locale, STEP 7 offers to translate the session view to English US. Clicking Yes opens the project safely.

Can this error occur with WinCC projects?

WinCC projects handle languages differently via the Text Distributor and WinCC Text Library. This specific Global\Language error is strictly an S7 / SIMATIC Manager database mechanism.

How do I prevent this error when sending projects to international clients?

Before archiving, set the default project language to 'English (United States)' under Options -> Manage Multilingual Texts -> Change Language, and check 'English (United States)' as the default language for display.

Technical References

Related Tags

STEP-7
Project-Language
Codepage
Global-Folder
SIMATIC-Manager
Multiproject

6 respuestas

Resolving 'Project Language Not Compatible' Error When Opening SIMATIC PCS 7 Projects on Another PC