Product(s):	APM Implementation and Performance Management
	Version(s):	7
	Environment:	N/A
	Area:	N/A
	Subarea:	N/A

Problem Description

User recently pushed out a MS Windows update (KB5013943) to a DEV environment and the DEV smart clients immediately started crashing on launch. It was later found that the user had pushed the same update to QA and Production environments without any issue experienced by the smart clients in those environments. Upon analysis, it was found that the Prod and QA environment had been repackaged with in the last month but that DEV was still using a smart client that was packaged that several months earlier.

Solution

The QA and Production environments were packaged post application of the Windows update. Because the DEV smart client was packaged prior to the Windows update, one or more referenced MS Windows components had likely gone obsolete. To correct the DEV smart client, the user reapplied the MS Windows update (KB5013943) and repackaged and redeployed the DEV smart client. The Dev smart clients were then run and automatically updated with the newly deployed smart client package and ran without issue afterward.