AutoCAD 2017 - Stuck in loop saving files with X-Refs

[JamieVJohnson2]

AutoCAD 2017 gets stuck when saving or opening files with X-refs, where AutoCAD 2016 does not.  The CPU processes one core at max, indefinitely.  I can repeat the same tasks in 2016 on the same files, and have no issue.

Files are very clean, before you ask.

Machine has 2017 and 2016 installed at same time.

Oddity, if I copy all the files to the same desktop, then I can xref, and save/open the file without issue.

Folder where files are normally stored (D:\ drive of local computer), using MKLINK /j (junction) to redirect to c: drive.

Saved paths are full path, not relative.

Please help.

[TravisNave]

Interesting.  Is there any reason you are making a link to the files on D:\ to make it appear that they are on C:\ drive instead?

[JamieVJohnson2]

I'm glad you asked that.

Our machines are mostly (not all) dual drive systems, drive 1 is a minimally sized (250gb) SSD drive.  Drive 2 is a nice plump 2tb 7200rmp platter drive.  We want to protect both longevity and space on the ssd so we moved the vault working folder into drive d.  Then because many programs want files to be in the same place, we use the NTSF "Junction" to create a mock C:\VaultWorkingfolder\ path that points to d (same place).  This has been flawlessly transparent for most programs with the exception of AutoCAD's Autosave sub routine MoveBak (express tools add on), This one can't use the junction, so we just point it to d drive.  However at this time moveback is not implemented.

Some CAD machines (laptops) only have 1 drive, and have to locate files on C:\VaultWorkingFolder, so that is the lowest common denominator.

[JamieVJohnson2]

I did some testing this morning this is definitely a program bug with the use of the NTSF Junction.  I removed the junction, ran the X-ref test directly to drive D and everything worked.  Then I put it back, opened that same file, then simply went to Xref manager, and change the path from D:\ to C:\ where it would have to use the junction, and it stalled out.

Can anybody else confirm?

Autodesk please hot fix AutoCAD 2017 quickly, this is a fundamental flaw in the program.  I'd really like to use the 2017 version if I could.

Thanks,

[JamieVJohnson2 · Accepted solution]

This issue was tested by Autodesk's Jon Dean, and I received a screen cast of how the MKLINK junction can now be replaced with a symbolic link use /d instead of /j.  In the past I was not able to get a symbolic link to work, but now it appears to be the method to use.  It also tested out well with Inventor and Vault 2017 systems.  It also works in AutoCAD 2016.

Thank you,

[mockymock11]

this post was extremely helpful for me... We're a small biz and we use Drop Box to sync our CAD work as we're located all over the place.  By ensuring we all use the same folder structure, DB worked great with xref's and data shortcuts.  But I bought a new laptop and have two hard drives, a small fast one for the operating system (C drive) and a larger 1 TB data drive for my CAD folders...  We've been using the C drive for Drop Box...  I tried to find a way to install Windows 10 and use a letter other than C to no luck at all... Then I tried the junction /J and then just watched 2017 get stuck in a loop... couldn't open anything with an xref....  changing to a symbolic link with /d seems to have done the trick!!!  I'll be running it through the ringer the next few weeks but I'm optimistic this is the way to go...  I know this is an decent sized issue for many Drop Box users trying to sync with multiple hard drives....