Catching technical database problem when testing on Tbox

[MatGodRho]

Hey guys,

How to manage:

"Operation could not be completed because of a technical database problem" ... "venv::File::Open:CreateFile (...) Failed: The system cannot find the path specified"

when testing on Tbox.

Thanks !!

[avalgoma]

Hi,

That problem is familiar to me on my TBOX. Not all the data related to the patients is fully migrated in the TBOX. For example, some directories, images, Dicom files... are missing. Apparently the patient is there in ARIA, but for a question of disk space (I suppose) not all the information was migrated by ARIA software engineers.

Regards.

[MatGodRho]

Hello Avalgoma,

I have the same understanding. Do you think its feasible to catch the exception raised by ESAPI and so prevent the code from crashing ?

Thanks !

[avalgoma]

Hi MatGodRho.

I'm not sure. I think it would be feasible, but I have no access to TBOX to check it now.

However, to avoid that catch I had to copy the directories I needed from ARIA server to TBOX and the exception disappeared. I know catching the exception is the good way, but I only wanted to check Entity Framework on ARIA.

Maybe some other programmer here could help.

Regards.

[MatGodRho]

Thanks again :)

[joecastelo]

This happens in TBOX when the patient is not properly loaded.

Also a similar error happens in production for some plans that a try to save with standalones. I don't know why really