Search Engine: Elastic

Article ID: 131332, created on Aug 18, 2017, last review on Aug 18, 2017

  • Applies to:
  • Operations Automation 7.1

Symptoms

Office 365 Provisioning "Subscription" task fails:

"code": 500,
"message": "Input string was not in a correct format."

sitelog error:

ERROR aps_endpoint: SubscriptionsController.Post finished by exception System.FormatException: Input string was not in a correct format.
ERROR aps_endpoint: System.FormatException: Input string was not in a correct format.
StackTrace:    at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)

Cause

One of the parameter values of type String contains unsupported symbols. For example, MPN_ID parameter contains the "{" symbol - what is unexpected.

In order to check which parameter value is not correct, obtain all <string></string> tags from the sitelog and analyze its values. For instance, this parameter value is not correct:

<value>
<string>MPN_ID</string>
</value>
<value>
<string>{{mpn_id}}</string>
</value>

since MPN_ID should contain only digits or chars.

Resolution

Modify corresponding parameter in Billing UI.

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 8c199f0ee4305da1a577740620df4a51 1941880841f714e458ae4dc3d9f3062d

Email subscription for changes to this article
Save as PDF