"String or binary data would be truncated"

Epicor ERP 10
1

In one of our testing environment we have begun encountering frequent instances of the error message shown below. These appear for various reports/tasks and for various users. Some users see it with every attempt to run a report.

image.png952Ă—289 13.8 KB

The stack trace consistently includes reference to UserActivityLog
We have restarted all instances, task agents and servers but the issue persists.Some users are fine, but others are not.

Is there any know issue related to the Activity log that might be the source of this error?

2

just taking a guess…i know i’ve seen this before. I thought it was that some fields somehow, got data jammed in them longer than the allowed number of characters/size etc. It might only appear intermittently depending on if those columns got brought in on selected records. Is this a migration? take a hard look at the tables/records being brought in. Sometimes this can be vetted out easier using ssms.

1 Like
3

Rob,

This is a migration. We have several instances/DB’s where testing is underway, and this is only occurring on one. Some users can still run reports with no error, but others cannot run anything now…it seems to be propagating to other users as well.

Since it is consistently UserActivityLog related and loginfailed, we are double checking all system type account passwords to make sure none have changed.

4

hmmm memory failing…its been a while except that’s when i remember seeing it as well :slight_smile: how helpful is that?

5

lol - its perfectly helpful - always good to know others have been in the same boat.

6

The database is set to only allow x characters and the extended properties on the column are set to allow X+10

e.g.
DB says 20 characters, the metadata 30.

That’s an oops. If this is a migration it looks like the script did not check that the column size changed. Ticket please!

3 Likes
7

Thank you sir!

8

Ok…some more details
If we Uncheck the “Require Single Sign On” for the users affected, the issue goes away and they are able to continue as normal generating reports.

9

Hi Ed, did you ever find out what was causing this? We are having the same problem and are also using single sign on.

Thanks

10

Adding my experience with this for users that may be searching for a resolution:

Need to systematically remove or update fields until the operation causing the error works.
E.g. this came up for a user when trying to copy a templated quote line to a different quote line during the “Get Details” operation. I systematically removed materials and operations, trying the “Get Details” after each removal until it worked. Once I found the offending line, I started systematically updating fields and doing a “Get Details” until I could find the offending field.

11

I used to have this issue earlier this year, it was solved after removing the Required Single Sign On check box, under user maintenance for all of those having this issue.

in the beginning this was the quick a useful workaround i found while waiting for the Tech support response which you can find down below:

Some previous background: Basically the problem usually is caused by the Appserver deployed for SSO Single Sign-on, It is likely missing a password in a database table that is needed.

This is a known issue where the System Agent password does not get saved in the database with a SSO deployed appserver. In a standard deployed Appserver with a Binding of: UsernameWindowsChannel it does store the SysAgent ID/PW correctly the first time. fortunately, if you have a Non-SSO appserver already deployed that you could log into the Application database with, you could correct the missing PW in the System Agent ( and it corresponding database table would be updated. The password (hash) should be saved and viewable in the DB Table: Ice.SysAgent.SysPassWord, but when the SSO Appserver is used ( usually created first, before a Non-SSO Appserver is deployed, that record in the DB table ( Ice.SysAgent.SysPassWord) will possibly be blank. we used the steps below to get the PW into the DB.

To resolve:
· Open a non-SSO deployed appserver client, log in as a system manager.
· Browse to System Agent Maintenance
· Stop the SSO Task Agent from Epicor Admin Console
· Update the password in System Agent Maintenance and save
· Start the SSO Task Agent again.
· Verify Ice.SysAgent.SysPassWord has been updated.

  • Login to the SSO Client and test printing a SSRS report
1 Like
12

Hi, some of my users are having similar issues/error sometimes when trying to bring operations from another quote line to a particular one. Seems it’s happening only since we upgraded from 10.1.400.38 to 10.2.200.24. Did you find what was the culprit in your case?

thanks,

13

I don’t know the root cause; it was something to do with the data in the field.
Once I identified it, I changed it to something else, then back again and everything worked after that.

14

Aaron,

you dont remember which field by any chance?

thanks,

15

Umm, I believe it was the Supplier ID, but it’s been awhile.

image
image.png1048Ă—771 35.5 KB

16

I’ve recently been having this issue and it’s because of the description of the BAQ and the number of characters used. Once I shortened the description, it completed without errors.