locked
Failed to retrieve data from database Vendor Code 8115 (Crystal Reports) RRS feed

  • Question

  • User722363233 posted

    I get Arithmetic overflow error converting expression to data type float in sql server 2012 and my crystal report generation fails (version 13).

    Similarly when i run it in sql server 2008, I get the same arithmetic overflow error converting expression to data type float but my crystal report gets generated.

    Any help regarding this.......

    Thursday, March 5, 2015 3:01 AM

Answers

  • User-2027680662 posted

    Tumse na ho payega Sayali,

    check XACT_ABORT function

    and check the connection. Use SQL Server connection rather  SQL Server Native Client.

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Wednesday, March 11, 2015 9:00 AM

All replies

  • User2008642861 posted

    Hi Sayali Tavare,

    Thank you for your post. This issue is more related with Database. About the error message, please refer to the similar cases as below.

    http://blog.sqlauthority.com/2007/07/06/sql-server-fix-error-msg-8115-level-16-state-2-line-2-arithmetic-overflow-error-converting-expression-to-data-type/

    http://stackoverflow.com/questions/12097859/sql-8115-arithmetic-overflow-error-converting-numeric-to-data-type-numeric

    Hope this could be helpful to you.

    Best regards,

    Archer

    Tuesday, March 10, 2015 5:09 AM
  • User722363233 posted

    Thanks for replying. My query is regarding crystal report. It gets generated on one environment but fails in the other resulting the arithmetic overflow error. In both the environment I get the same arithmetic overflow error when i execute the Stored Procedure.

    What is the difference between error message : Msg 8115, Level 16, State 6 (Sql Server 2012) and  Msg 8115, Level 16, State 2 (Sql Server 2008)?  (State 6 and State 2)??

    Could this be a cause of not generating the report?

     

    Tuesday, March 10, 2015 8:14 AM
  • User2008642861 posted

    Hi Sayali Tavare,

    These error messages you got at different SQL server version, and the Level X, State X show you which statement has some error, it could help you to solve your issue. As I know, this could not cause the error, your issue may be caused by your Stored Procedure statement.

    Best regards,

    Archer

    Wednesday, March 11, 2015 5:40 AM
  • User-2027680662 posted

    Tumse na ho payega Sayali,

    check XACT_ABORT function

    and check the connection. Use SQL Server connection rather  SQL Server Native Client.

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Wednesday, March 11, 2015 9:00 AM
  • User722363233 posted

    Thanks Anand. It worked.

    Thursday, March 12, 2015 6:21 AM