BC 365 SaaS v24.5 Report Error - CVTRES.EXE?

(1) Share

Report

Posted on by gregarican1968

Trying to print a transfer shipment report, one of our users received the error below. Searching for this CVTRES.EXE file, it appears to be part of a client's .NET Framework deployment. Although since BC 365 SaaS is operating "in the cloud" I would assume that the client just using a web browser wouldn't be the catalyst behind the error. Assuming this is just a transient error on the Microsoft tenant side?

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (5)

Answers (1)

Gerardo Rentería Ga... 25,555 Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!

Hi, good day
I hope this can help you, and give you some hints.

It would be advisable to generate a support case, to fully understand the error and its origin.

Technical support overview - Business Central | Microsoft Learn

You could also review the error details to determine the origin.

Share error details to get help from another user | Microsoft Learn

Best Regards
Gerardo

Was this reply helpful? Yes No
gregarican1968 6 on at

Like (0)

Report
Copy link

Link copied!

Thanks for the reply. Unfortunately, the user who hit this error didn't click the Share Details link to copy/paste the specifics. I keep reminding folks of the importance of this. I haven't heard any additional trouble reports of this happening, so I'm thinking it was a transient error on the Microsoft tenant hosting side...

Was this reply helpful? Yes No
Suggested answer

YUN ZHU 99,090 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

I haven't encountered this problem. It seems to be a problem when exporting files.
If it happens frequently, it might be better to contact Microsoft.

Thanks

ZHU

Was this reply helpful? Yes No
Greg Kujawa 787 on at

Like (1)

Report
Copy link

Link copied!

Thanks for the response Yun Zhu! I believe our user was just previewing the report to their screen, as opposed to exporting. Otherwise it was quiet, so I assume this was just a random error and not widespread across our user base. :)

Was this reply helpful? Yes No
Verified answer

Greg Kujawa 787 on at

Like (1)

Report
Copy link

Link copied!

Final follow-up on this. The user reported it was indeed a transient issue. Her workflow for generating this report has remained the same, as has the underying extensions. Chalking this one up as a sporadic server-side issue and moving on. Thanks all!

Was this reply helpful? Yes No