Company Upgrade from 8.82 PL01 to PL04 fails [table=@BA_STRN1]

[Former Member]

Hi Experts,

does anyone else have problems with upgrading to 8.82 PL04 (from 8.82 PL01)?

The upgrade from 8.82 PL01 to 8.82 PL03 threw errors at Help-Upgrade, now with PL04 it has problems with the company db (table=@BA_STRN1)...

This comes from the upgrade log, it appears two times and then stops the upgrade process. (Rollback didn't work for COMMON database by the way...)

05/03/2012  15:32:37:560164 	Upg         	NoteLgAlw     	FromVersion=882062	ToVersion=882066	Starting the company 'SBODemoSCS' upgrade	TID=1576
05/03/2012  15:34:38:542352 	Upg         	Err           	FromVersion=882062	ToVersion=882066	table=@BA_STRN1, qurStr=UPG_UpdateOneTable() - error in GetFromTempTable() file:u3A64u645Cu7065u746Fu425Cu5355u424Du425Fu5C31u2E38u3238u525Fu4C45u535Cu4F42u385Cu382Eu5F32u4552u5C4Cu7041u6C70u6369u7461u6F69u5C6Eu624Fu4D6Au7267u505Cu474Fu6E65u3130u632E line#1855, errString=[Microsoft][SQL Native Client][SQL Server]Zeichenfolgen- oder Binärdaten würden abgeschnitten.

@BA is a UDT from FixedAssets. The sql error in the last line means something like "string or binary data would be truncated", but I am not very familiar with chinese so please don't expect a translation for it

Fortunately it is a testing environment, but as long as I cannot upgrade my testing environment, I won't dare to upgrade any customer system.

Any ideas appreciated, thank you.

Sebastian

[Joselito · Accepted solution]

Hi,

For your information:

Before 8.82 Pl 03 Business One allowed having contents in User Defined Fields (UDF) longer than the specific lenght set in Business One for that specific UDF if the content was entered by SDK development as long as the SQL definition allowed that lenght

From now own this will not happen, and if detected in database, the upgrade process will detect and stop.

Unfortunatelly is not always the scenario caused by partner SDK development.

Historically, the Add-on Fixed Assets (which is an SDK development at the end of the day) wrongly inserted descriptions in certain languages and for certain localizations exceeding the lenght defined by the Add-on itself for the user defined field.

Because this control did not exist and the information contained on that fields was just 'information' not having any relevance in function, went undetected all this time.

The solution is quite simple, modify the content of the U_Desc to a nother one that user considers suitable for the business process (SAP given description in a particular language is as valid as any other)

SELET Code,U_Desc from [@BA_STRN1] where len(U_Desc)>30

(to identifiy better what type of transaction is about, and write your alternative description in relevant language)

SELECT U_TrnsName,U_TrnsID FROM [@BA_STRN]

where U_TrnsID IN(select U_TrnsID FROM [@BA_STRN1]

where LEN(U_Desc)>30)

Logically , after 8.82 no new corruption of this type is to happen.

Hope this will help you

If you need help from support, create incident under component SBO-ADD-BA

Kind regards

Jose Antonio Castillo

[Former Member · Accepted solution]

Hi,

we just ran into the same problem. It would be nice if SAP would do these kind of checks BEFORE starting the upgrade.

Since this is a default table which was never updated by us we'll have this error on ALL upgrades...

Kind regards,

Sebastiaan

[S0004823299]

Hello,

When upgrading from 8.81 to 8.82 PL09 is being interrupted with an error in @BA_STRN1.

The following queries will return nothing:

"SELECT Code,U_Desc from [@BA_STRN1] where len(U_Desc)>30"

"SELECT U_TrnsName,U_TrnsID FROM [@BA_STRN]

where U_TrnsID IN(select U_TrnsID FROM [@BA_STRN1]

where LEN(U_Desc)>30)"

What should I do?

Thanks and Regards

Miguel

[bernhard_stbner2]

Hello Miguel,

We had the problem with @BA_STRN1 . Please see note

1645439 - Upgrade may fail with error: String or binary data would be truncated.

Regards

Bernhard