Skip to main content
Question

FME Server problem reading AutoCAD with OD data: AutoCAD Reader: Error opening file...during version check

  • February 25, 2019
  • 3 replies
  • 116 views

Forum|alt.badge.img

Good afternoon,

I am trying to run a workspace on FME Server that utilized the AutoCAD OD reader. When I run the workspace I receive the following error code:

"AutoCAD Reader: Error opening file 'C:\\ProgramData\\Safe Software\\FME Server\\resources\\temp\\Chicago_Building_1_201902251923396464_cad\\DP_L_2_CAD.dwg, C:\\ProgramData\\Safe Software\\FME Server\\resources\\temp\\Chicago_Building_1_201902251923396464_cad\\DP_L_1_CAD.dwg' during version check "

I have checked the file path and both CAD files exist in the folder. So I am a bit puzzled why I am receiving this error. I have tested the workbench on FME Web Portal with the same workspace and it ran correctly, but running through the API failed and caused the above error code.

Any assistance would be great!

Thanks,

David

3 replies

Forum|alt.badge.img+2

Hi @david_prosack88

 

Is there any difference between how you're running it in the web and through rest api? Possibly user or service? Does it work/run correctly if you use the direct url?

Forum|alt.badge.img

Hi @jlutherthomas,

The issue has been resolved. The API was sending string elements into our input parameters when multiple CAD files were being read. So we changed them to an array. Everything is working fine now.

Thanks!

David


Forum|alt.badge.img
jlutherthomas wrote:

Hi @david_prosack88

 

Is there any difference between how you're running it in the web and through rest api? Possibly user or service? Does it work/run correctly if you use the direct url?

Hi @jlutherthomas,

The issue has been resolved. The API was sending string elements into our input parameters when multiple CAD files were being read. So we changed them to an array. Everything is working fine now.

Thanks!

David


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings