Warning: URI generated by PathMapManager is not a canonical MATLAB path URI

When building any software component of my AUTOSAR composition I get a lot of these warnings:

• Warning: URI generated by PathMapManager file:///C:/<MyFile>/autosar/autosar.xmi#<ID> is not a canonical MATLAB path URI

Since the autosar.xmi file is not something modifiable by the end user, I don't know how to fix the issue. It's not blocking because it's just a warning but it makes it harder to spot other warnings related to the code generation.

I also tried to dig into the Configuration Parameters settings of the model but couldn't find anything useful, you can only select the schema version of the generated XML file.

The matlab version that I'm using is the following:

-----------------------------------------------------------------------------------------------------
MATLAB Version: 9.6.0.1472908 (R2019a) Update 9
Operating System: Microsoft Windows 10 Enterprise Version 10.0 (Build 17134)
Java Version: Java 1.8.0_181-b13 with Oracle Corporation Java HotSpot(TM) 64-Bit Server VM mixed mode
-----------------------------------------------------------------------------------------------------
MATLAB                                                Version 9.6         (R2019a)  
Simulink                                              Version 9.3         (R2019a)  
AUTOSAR Blockset                                      Version 2.0         (R2019a)  
Autosar Composition Export                            Version 1.8.1       (R2019a)  
Embedded Coder                                        Version 7.2         (R2019a)  

Answer 1

[Scott Walker]

Hi, did you get a fix from Mathworks? We also see this issue.

[Andrea Congestri]

No unfortunately no answer yet

Answer 2

[zhong ming]

I have the same problem

Answer 3

[Yukta Maurya]

This warning might be due to an unknown interaction with Jenkins when it is setup to use the "Local System Account". The "Local System Account" is a profile in the System32 directory of the Windows server and could have potential permissions issues. The best possible workaround would be to avoid using this setting.