We've got our APS running on MS SQL. One site recently updated their reports and noticed in their Win Event Log that they were getting db errors every 5-6 seconds.
The errors are APS "related", but I think that they are more along the lines of a DB problem. I haven't seen the error mentioned on the net, so I'm coming here.
Error details from Event log:
Source: Seagate Info
Category: Database
EventID: 2000
Description: String data, right truncation:
SELECT CI_ID, CI_Name, ... etc FROM CI_INFOOBJECTS WHERE 0=1
ID:351; Type: Report; Name:'Our report name'; Path: '\\servername\si\input\si_f09bu.rpt'; Function: CInfoObject::Update()
Data included in the error is in the form of bytes, and the ascii equivalent is "aps32".
I looked at the table and the record referenced (351) in the error is non-existant. The report object mentioned in the error statement (si_...) doesn't exist, nor do any backwards references to it exist. There are different IDs and report objects mentioned, but always the same errors and results. I looked at the column sizes compared to the data for the report paths, etc., and we're not even 1/2 to filling the columns (255 chars).
We asked the site admin to stop and restart the APS, stop and restart MS SQL, clear his reports cache, etc. We also had the admin convert his APS db back to Access and then convert it back to MS SQL.
There are no changes to the errors or their frequency.
Other reports are published and running correctly.
Has anyone come across this or have an idea for a direction for us to head?
Puzzled and frustrated,
Me
The errors are APS "related", but I think that they are more along the lines of a DB problem. I haven't seen the error mentioned on the net, so I'm coming here.
Error details from Event log:
Source: Seagate Info
Category: Database
EventID: 2000
Description: String data, right truncation:
SELECT CI_ID, CI_Name, ... etc FROM CI_INFOOBJECTS WHERE 0=1
ID:351; Type: Report; Name:'Our report name'; Path: '\\servername\si\input\si_f09bu.rpt'; Function: CInfoObject::Update()
Data included in the error is in the form of bytes, and the ascii equivalent is "aps32".
I looked at the table and the record referenced (351) in the error is non-existant. The report object mentioned in the error statement (si_...) doesn't exist, nor do any backwards references to it exist. There are different IDs and report objects mentioned, but always the same errors and results. I looked at the column sizes compared to the data for the report paths, etc., and we're not even 1/2 to filling the columns (255 chars).
We asked the site admin to stop and restart the APS, stop and restart MS SQL, clear his reports cache, etc. We also had the admin convert his APS db back to Access and then convert it back to MS SQL.
There are no changes to the errors or their frequency.
Other reports are published and running correctly.
Has anyone come across this or have an idea for a direction for us to head?
Puzzled and frustrated,
Me