Problem with FNO Patch 12.0.0.2

[stevecarlucci]

After applying FNO Patch 12.0.0.2, manual activation is no longer working. There are no error messages during the activation process. The client generates the request file without error. FNO generates the response file without error. The client loads the response file into trusted storage without error. However, when our application then tries to check out a feature, the Flexible API claims that it is not an active feature.

We also noticed a difference in how appactutil displays the feature lines in the fulfillment. Before we applied the patch (when manual activation was still working), calling "appactutil -view" would display each feature on its own line. After applying the patch and going through a manual activation again, "appactutil -view" is displaying all feature lines on the same line, and they look somewhat corrupt.

[stevecarlucci]

Something about how the response files are getting generated must have changed after applying the patch, because it caused our application activation utility to load the file incorrectly. This caused the feature lines in trusted storage to be corrupt. We were able to fix the issue by changing the way we were loading the response file into memory.