locked
Cannot apply business rule - greater than decimal datatype RRS feed

  • Question

  • Hello,

    I've encountered such a irritating problem, which I can repeat only on specific environment (even if both tested for sql server 2012).

    I created a business rule for 'arg' datatype decimal. The condition is "if is not blank" and the action is "must be greater than 0". After publishing business rules I hit "apply rules" in excel add-in and I received this error:

    "Error converting data type nvarchar to numeric. Transaction count after EXECUTE indicates as mismatching number of BEGIN and COMMIT statements. Previous count = 0, current count = 1.Transaction count after EXECUTE indicates as mismatching number of BEGIN and COMMIT statements. Previous count = 0, current count = 1.Transaction count after EXECUTE indicates as mismatching number of BEGIN and COMMIT statements. Previous count = 0, current count = 1.Transaction count after EXECUTE indicates as mismatching number of BEGIN and COMMIT statements. Previous count = 0, current count = 1. Uncommittable transaction is detected at the end of the batch. The transaction is rolled back. "

    So far I am 100% sure, that the problem is caused by this specific business rule. There are no values in 'ARG' that return the error of "converting nvarchar to numeric", I've already tried to query that from db level witch cast or checked any uncommitted transactions.

    Do you have any ideas what the cause is?

    Tuesday, June 30, 2015 6:44 AM

Answers

All replies

  • >I've encountered such a irritating problem, which I can repeat only on specific environment

    What is the version and service pack level of the environments?

    Can you create a new model with a simplified repro?

    David


    David http://blogs.msdn.com/b/dbrowne/

    Tuesday, June 30, 2015 2:17 PM
  • https://support.microsoft.com/en-us/kb/3023634

    Did you try the above update?

    Wednesday, July 1, 2015 9:17 PM
  • @David

    Microsoft SQL Server 2012 - 11.0.5556.0 (X64) SP2. I've tried to do that on another environment (I'm not allowed to use current one for that kind of tests), but everything worked fine.

    @Vincent

    Looks like it can solve my problem - I've asked admin to install the fix. I'll keep you up to date about how it turns out.

    Monday, July 6, 2015 12:15 PM
  • @Vincent

    Thanks a lot, this solution works fine :)

    Wednesday, July 15, 2015 9:53 AM