Event ID - 2000

Event Id2000
SourceSeagate Info
Description1: String data, right truncated (null): delete from CI_SECRIGHTS where CI_PRINCIPAL IN (3790) (): Function: CGroup::UpdateDBFromUserGroupXMap()
2:String data, right truncated (null): SELECT CI_GROUP_ID, CI_GROUP_NAME, CI_DESCRIP from CI_GRPINFO WHERE 0 = 1 (): Function: CGroup::UpdateDBFromUserGroupXMap()
3:String data, right truncated (null): SELECT CI_USERID, CI_USERDESC, CI_PASSWORD, CI_USERSECID, CI_DISABLED, CI_WHENDISABLED, CI_PWDLASTSET, CI_PWDHISTORY,CI_USERMEMO FROM CI_USERS (): Function: CUser::UpdateDBFromUserXMap()
Event InformationAccording to businessobjects:
Resolution:

This problem occurred because the size of the CI_GRPINFO.CI_GROUP_NAME field in the Info APS system database is limited to 40 characters. When changes are made in the Info Administrator they are generally committed to the Info APS system database within a few minutes. If the changes are not committed, they will remain in memory until the Info APS is shut down. When the Info APS is restarted, the uncommitted changes will be forgotten if they cannot be written to the database.
When changes are made in the Info Administrator a SQL statement is created to pass the information to the database. In this case, when the new user group name was created and it exceeded 40 characters the Info APS started building the SQL statement. As the other requests were made to assign users to groups and create or delete additional groups, the changes were added to the SQL statement. When the changes were accepted in the Info Administrator the SQL statement was passed to the database. As at least one piece of the SQL statement was invalid (the field with more than 40 characters), the entire SQL statement was rejected and all other changes made in the same session were lost.
This is a known issue with Seagate Info (SI) version 7.0.2.100 and has been tracked. The SCR track ID is: 36896.
As of the date of this writing there is no file update for this issue. Ideally the size of the CI_GRPINFO.CI_GROUP_NAME field would be increased. Other fields are quite large, for example, the Group Description field, CI_GRPINFO.CI_DESCRIP, is set to a size limit of 255 characters. However, a related field, CI_USERS.CI_USERID, that holds the name of the user is limited to 128 characters, while the user description in CI_USERS.CI_USERDESC is limited to only 30 characters. These issues are noted in the track.
A workaround is to be cognizant of the limitation of the Group Name field size and keep all group names to 40 characters or less.
In addition, to limit the loss of other changes during a session it is recommended that each change be accepted an individual basis.
Reference Linksevent id:2000 and source:Seagate Info

Catch threats immediately

We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.

See what we caught

Did this information help you to resolve the problem?

Yes: My problem was resolved.
No: The information was not helpful / Partially helpful.