Task Scheduler unresolved references

[ben.doulis]

I'm trying to do a mass export of .IDW drawings to .DXF using Task Scheduler. It's working fine for most files but a reasonable number are failing due to "unresolved references". When I open a failed file it seems to be fine (both the drawing and associated file) and gives no particular warnings. I found another thread from sometime ago that suggested migrating the file and then exporting however this made no difference. 

I'm a bit lost on what to do next as there's too many failing files to go through them one by one manually export. If anyone has any different suggestions on how to overcome this I'd love to hear them!

[sundars]

Hi Ben,

Typically unresolved references happen when Inventor is not able to find the reference in the folders specified in the project. When you do a mass operation, did you specify folders which are outside your project paths?

In Task Scheduler, when you export files, try creating one task per project and schedule it. That way, Task scheduler will use the specified project when opening files for that particular task.

You can always look at the migration logs to see what's going wrong. If nothing works, please do post your dataset or steps to reproduce.

Thanks

-shiva

[johnsonshiue]

Hi Ben,

Did you activate the proper project? Or, you have been using Default project? The unresolved errors means the files have been relocated or the folder structure or names have been changed. Inventor cannot find the files based on the reference path.

You could try changing the default file open option so that the drawings are opened as is (without resolving). Start up Inventor and go to Tools -> App Options -> File -> File Open Options -> Drawing -> check "Skip unresolved references."

Closed Inventor. Run the task again. The resolve prompt should not come up.

Many thanks!

[ben.doulis]

Hi @johnsonshiue thanks for your response (and @sundars , apologies for not getting back to this sooner). We only use a single project for all of our work so that shouldn't have been causing issues. We went through the log files and manually worked through them as a team (circa 170 files total), some files were understandably broken and needed repairing, others appeared to be completely fine.

We have another larger, messier (but less important) folder to repeat this process on so I'll give your suggestion a go with that soon.

I appreciate your help so far!