AS 6.3 Compilation Error When turn on the mappVision Online Teaching

Ask Questions HMI & Visualization
1

Hello everyone，

When my customer turn on the mappVision online teaching function and then tries to compile a project in Automation Studio, the compilation fails with an error. However, the exact same project compiles successfully on my PC without any issues.

What you’ve tested

  1. Checked if the issue was caused by long project paths → No effect
  2. Checked for invalid or special characters in the project name → No effect
  3. Moved the project from other drives (D:, E:, etc.) to the C: drive → Compilation succeeded
  4. Moved the project back to other drives while mappVision page is open → Compilation failed again

Key finding: The project compiles successfully only when located on the C: drive

Software: Automation Studio 6.3.2.2

  • Application: mappVision 6.7.0
  • Operating System: Windows 10

image
image824×352 28.3 KB

image
image1238×259 82.5 KB

2

Hi @dingh ,

I see this known issue in our database: "Using mappVision 6.4.0, mappView 6.5 AS compile error occurred for not finding Stylesheet :

Kategorie Datum/Zeit Beschreibung Fehler Position Datei
193 Fehler 22.01.2026 08:10:54,1151 Error: Can’t find stylesheet to import.
203 Fehler 22.01.2026 08:10:54,6515 Error: Can’t find stylesheet to import. D:\Projekte\APK_old_6_2\Temp\Objects\Simulation\5APC3100_KBU0_000\.mappView\data\wwwRoot\BRVisu\release\mappVisionThemeFlat.scss"

R&D is working on that, so far they only recommend to change project path to C: drive .

@Note: Double check if the error reported in our database is the same as yours, I don’t see very well the text in your screenshot.

Thanks
Ciao
Valerio

3

Hi @valerio.manenti ,

Thanks for your information！
It’s indeed the same error you described.
But my PC compiles successfully no matter which drive I use. Could this be due to certain software I’ve installed?

4

Thanks @dingh for your feedback,
R&D is still investigating the case. During their initial review, they asked the customer who reported the issue to move the project path to the C: drive. The customer rebuilt the project in the new path without any errors. Therefore, R&D recommends this workaround if you encounter the same issue. Time is important too, you need to continue your work and cannot test every combination indefinitely. Once the investigation is complete, I am sure we will have more information.

Ciao
Valerio