Issue
A PCS deploy fails and an error message comes up with the text "Xif nnn could not be found"
Environment
Project Configuration Server (PCS)
StruxureWare Building Operation 1.5 and newer
Cause
An import originating from a live system that has LON network containing network variables on the local node becomes a potential risk in PCS, but will import correctly as long as no local node variables are deleted. There is not currently support for dynamic update of changes on the local node in PCS.
Resolution
Leave an import containing Local Node variables unchanged, if importing to PCS