Interesting.... usually its either SSLOCATE or SSMAUTOOPEN that is not set to '1' - both should be for SSM to open automatically when an SSM-enabled drawing is opened/linked to an existing DST file.
This may be related to the version/creation date of the DST or the SSM files. I have read online that SSM files/templates originally created from older versions of AutoCAD 'can' occasionally create an functionality issue where something isn't working correctly. FYI - I have not experienced this directly myself.
However, I have had a couple DST files go bad (where something went wrong, perhaps corrupt, bloated, etc.). Generally we will rebuild the DST from scratch (slow, tedius) or completed the following:
- Open AutoCAD and Open the effected DST within SSM
- Go to Windows Explorer and locate the DST file
- Cut/Paste the effected DST file to a backup location (or DELETE the DST outright)
- You will notice the DST file magically returns (rebuilds automatically)
- Return to AutoCAD, close/shutdown to save changes/write back to the DST
- Restart AutoCAD and check SSM issues/functionality to see if they remain
Question: Does this SSM issue occur on all SSM projects opened in Civil 3D 2017? What about for other users (get another user within your office to open the SSM project/file and see if the same issue is replicated)?
- If it's replicated it could be more of a global issue, requiring SSM templates/files to be updated to current version.
- If the issues cannot be replicated, it could be a drawing issue/error, user profile or something related to an install problem/fix required, etc.
Keep me/us posted on what you identify in your testing. Good luck!!
Chad Franklin
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
