"Input string was not in a correct format" after upgrade to 4.6.9


Badge +1

Hi,

We just upgrated to version 4.6.9 and are having issues with decimal types. Every single smart object, which is using SQL stored procedure with return field(s) of decimal data type is throwing "Input string was not in a correct format." error. Exact same smart objects are working fine in the production system, which is still on version 4.6.6.

 


4 replies

Userlevel 1
Badge +8

Hi Albert, are you able to post screen shots of one of the stored procedure definitions and the smartobject properties and methods?

 

I would suggest you contact K2 support as this may be a known issue when upgrading to 4.6.9.

Badge +1

Here are screenshots of stored procedure, table structure and smart object properties. I did open ticket with the support team. I was just hopping somebody already went through this issue and know the solution.


11001iD81DDD0C84543B06.png
13094i4932BC16983F1D94.png
13038iCDB83A475CD043E6.png
Userlevel 1
Badge +8

Hi Albert, I can't see any issues with what you have posted. Have you refreshed your SQL service instance? Maybe also try creating a new smartobject based on one of those stored procedures and see if it has the same issue.

Badge +1

K2 Support team was able to figure out the solution. I just want to post it here, just in case if anyone is expiriencing the same issue. The problem was that during instalation of new version, the web.config setting ExecutionCulture was changed from "en-US" to "de-CH" (<add key="SmartObject.ExecutionCulture" value="de-CH" />). As soon as we changed this setting back to "en-US", the issue was fixed. Below is the link to the related aticle

 

http://help.k2.com/kb001458.aspx

Reply