There are 2 checks that happen during an import of a Solution that would make that error message appear:
- SignatureStatus is 0 (enum of Valid, Unsupported, Incompleted etc…)
- Disabled is TRUE
You can easily see those values if you extract your .cab and look at the BpMethod .xml file.
Easiest way to refresh the Signature is within Directive Update → Directive Recompile Setup Tab.
Refresh Signatures
When selected, method and trigger signatures of selected directives will be regenerated at the beginning of the recompile process.On the Directive Recompile Setup sheet, you can recompile the group of directives, optionally refreshing signatures of the methods or tables they are attached to, in order to make them compatible with the current version of the application.
I don’t know the full detail what Refreshing the Signature does; other than it makes modifications to Ice.BpMethod, Ice.BpDirective and Ice.BpArgument tables.
I had an up-to-date Data Directive and it showed Compatible and works well, but until I refreshed Signatures, I couldn’t import it, meanwhile Method’s worked fine.
Anyways; thought id share some of my research, I was curious myself. Seems to affect In-Transactions more than others in my case.