Runtime CATIA Environment Check
If there is a version, service pack mismatch (or sometimes even hot fix) between CATIA application and CATIA abstraction library, Windchill Workgroup Manager for CATIA V5 may not work properly and may become unstable.
CATIA environment validation check supplies self-diagnosis on the known environment conflict issues and to avoid potential premature exits:
1. Pre-requisites check for compiling the CATIA V5 Workgroup Manager abstraction libraries when executing CATIA V5 abstraction builder.
a. Verify the version compatibility among CATIA, RADE, CAA versions (GA, Service Pack and Hot fix). If GA or SP level version mismatch exits, build process will stop with an error message.
b. Verify the Visual Studio version (version, service pack and update) compatible with selected CATIA V5 version.
2. Runtime Environment Validation when running Windchill Workgroup Manager client
a. Verify the version compatibility between the installed CATIA version and the abstraction libraries when registering CATIA version in Windchill Workgroup Manager client
▪ GA or SP version has mismatch: Registration failed with error message
▪ HF version has mismatch: Success with a warning message
b. Verify the version compatibility between the installed CATIA version and the abstraction libraries when CATIA starts with connecting to Windchill Workgroup Manager client
▪ GA or SP version has mismatch: Connection failed with error message
▪ HF version has mismatch: Success with a warning message
3. Checks Microsoft CRT library compatibility
Way to bypass runtime CATIA environment check
If customers want to use multiple service packs of the same CATIA version with a single abstraction library on the same machine, despite the recommendation. The PTC_WGM_IGNORE_CATIA_SP_MISMATCH environment variable allows to bypass the restriction.
• This environment variable can be set to, true, false or any other value.
• If this environment variable is set, Windchill Workgroup Manager ignores CATIA Service Pack level mismatch. No warning message appears at the client message area.
