Configuring security in BizTalk Server should be straightforward. You go to the Group Properties, select your certificate for encoding or signing, and click OK. Recently, I had to do that. I needed to configure a certificate in the BizTalk Group to sign messages using the S/MIME component in the pipeline. But when I try to apply the configurations, I encounter the following error:
“An amended object cannot be put unless WBEM_FLAG_USE_AMENDED_QUALIFIERS is specified (System.Management)”
TITLE: BizTalk Server 2006 Administration Console
——————————
An amended object cannot be put unless WBEM_FLAG_USE_AMENDED_QUALIFIERS is specified (System.Management)
——————————
BUTTONS:
OK
——————————
📝 One-Minute Brief
When assigning a thumbprint to the BizTalk Group properties for encryption or signing, you may encounter the error: “An amended object cannot be put unless WBEM_FLAG_USE_AMENDED_QUALIFIERS is specified.” This issue is typically caused by a mismatch in how WMI handles localized or “amended” class definitions. The solution involves using the Certificate Selection dialog instead of manual entry, or ensuring the BizTalk Administration tools are synchronized with the underlying WMI repository.
Cause
This isn’t actually a BizTalk logic error; it’s a WMI (Windows Management Instrumentation) conflict.
In WMI, “amended” qualifiers are used for localized information (like descriptions in different languages). When you try to update the BizTalk Group object through the Administration Console, the console may be trying to overwrite an object that contains these localized “amended” properties without providing the necessary flag to WMI.
Solution
You don’t believe it, but try repairing your installation. If that doesn’t work, call MS support.
