Skip to main content

The customer has installed an SU9 environment and upgraded the database from 14.5 to 15.4SU9. we encounter the following issue, we can’t create service order for exemple or if there is no attachment on an existing service order when we click on attachment we have an error message ‘error system contact your dba” in the event log we have the same type of error : 

“enable to fin table 0”

it’s the first time i see this kind of issue, have you already encounter this ? (as on our own customer environment in Sixaxe everything is working well). thanks for your feedback

HI Christophe,

I have not seen this specific message before but I am wondering if there are Customizer customizations or other customization layers involved which an incorrect DAL might be causing a problem?

Based on that it seems to be happening only for their updated database, environment I would review whether the proper order of deployments were done to bring the environment to 15.4 and then SU9.  Perhaps something was skipped (e.g. database upgrade utility brings it 15.4.0 but the SU9 also has its own DB upgrade as would usually any custom local releases too).

Hi Christophe,
If you go a little bit further back in the Event Viewer log files, do you see any additional information on the error message captured there?  Sometimes the root cause of the issue is detailed a couple of records behind the one with the Ref # string on it...or you can at least look at the call stack details to track down the line of code that is triggering the problem, maybe that will help to diagnose the issue.
Thanks,
Reid

Hi we found the issue, the customer installed sql 2022 with no Service Pack...;when we have set up the compatibility level of the database too sql 2019 we didn’t have any more the errors. when we installed the latest Service Pack and change the compatibility level to 2022 no more error messages too.

Christophe

HI Christophe,

Great to hear… so it was a deployment issue in general since it was environmental.

Glad you sorted out the problem though it was not Alliance deployments that were advised to check.

Reply


Terms & ConditionsCookie settings