According to the Cadence Support site, this is an issue when different early, pre hotfix 11, versions of 17.2 are mixed and was fixed in 17.2 hotfix 11, current version is 17.2 hotfix 34. Getting both installations to the latest hotfix should fix this.![]()
↧