[et_pb_section fb_built=”1″ _builder_version=”4.17.4″ _module_preset=”default” custom_padding=”6px|||||” global_colors_info=”{}” theme_builder_area=”post_content”][et_pb_row _builder_version=”4.17.4″ _module_preset=”default” custom_padding=”1px|||||” global_colors_info=”{}” theme_builder_area=”post_content”][et_pb_column type=”4_4″ _builder_version=”4.17.4″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][et_pb_text _builder_version=”4.17.4″ _module_preset=”default” min_height=”185px” global_colors_info=”{}” theme_builder_area=”post_content”]<\/p>\n
If you have used SOLIDWORKS for any length of time you have certainly come across a scenario where you have tried to open an assembly or drawing and found yourself faced with a message saying that SOLIDWORKS is unable to find one or more files.<\/p>\n
In this blog, we will look at why this message appears in the first place and how we can resolve this issue.<\/p>\n
The message \u201cUnable to locate the file\u2026\u201d shown below appears when SOLIDWORKS is unable to find the exact file in the expected location.<\/p>\n
[\/et_pb_text][et_pb_image src=”https:\/\/tms-scotland.com\/solidworks\/wp-content\/uploads\/sites\/5\/2023\/03\/Missing-fles2.png” title_text=”Missing fles2″ align=”center” _builder_version=”4.17.4″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][\/et_pb_image][et_pb_text _builder_version=”4.17.4″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”]<\/p>\n
To understand the logic behind this better, we need to understand two main concepts. How does SOLIDWORKS know the difference between files, and what file search logic does SOLIDWORKS use?<\/p>\n
Most people may think that SOLIDWORKS just uses the File Name<\/strong> to know \u2018which file is which\u2019 but this is not the case, otherwise, you would never get an error message similar to the one below.<\/p>\n [\/et_pb_text][et_pb_image src=”https:\/\/tms-scotland.com\/solidworks\/wp-content\/uploads\/sites\/5\/2023\/03\/Missing-fles3.png” title_text=”Missing fles3″ align=”center” _builder_version=”4.17.4″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][\/et_pb_image][et_pb_text _builder_version=”4.17.4″ _module_preset=”default” hover_enabled=”0″ global_colors_info=”{}” theme_builder_area=”post_content” sticky_enabled=”0″]<\/p>\n In this example, SOLIDWORKS has a file called \u201cPin_&.SLDPRT\u201d already open (used in another assembly) and is now trying to open a new assembly which contains a part with the same name. However, rather than simply using this part, SOLIDWORKS knows that the two files are not the same, but merely that someone has created a duplicate file name.<\/p>\n This is because SOLIDWORKS assigns all files a unique \u201cID\u201d which is what SOLIDWORKS uses for all references between files. This is not a value which is commonly known (or set) by the user, although users can obtain this ID value if required. This is how SOLIDWORKS was able to determine that the two Pins were not the exact same file.<\/p>\n In the above example, you would want to fully close any files with the same name and files which reference\/use the file with the same name.<\/p>\n Both the file name and ID must match for SOLIDWORKS to open the file as expected.<\/p>\n When opening a SOLIDWORKS file with references, SOLIDWORKS follows a set list of locations to look for the file in question before prompting the user to manually browse to the file (or suppress the file).<\/p>\n The search routine that SOLIDWORKS uses to find referenced files is:<\/p>\n Note – The paths for \u201cReferenced Documents\u201d are searched only if \u201cSearch file locations for external references\u201d is selected in Tools > Options > System Options > External References.<\/p>\n There are many reasons why SOLIDWORKS may not be able to find the correct file as discussed below.<\/p>\n Five of the most common reasons are listed below along with how to prevent each from being an issue:<\/p>\n 1. When emailing files to another user a common mistake is only sending an assembly\/drawing file and not the part files as well.<\/p>\n The best way to prevent this is to have your top-level assembly (or drawing) open and go to File > Pack and Go. This can gather all the required and referenced files together and put them either in a single folder, or zip them all together, allowing you to then just send someone the zipped which will give them all the files they need to open your model successfully.<\/p>\n Alternatively, you would need to send all the referenced files manually, which could be tricky if files are scattered over multiple folders.<\/p>\n 2. A user has manually re-named a file in Windows Explorer.<\/p>\n When re-naming a file you should either re-name the file inside SOLIDWORKS with the file open or if re-naming in Windows Explorer you should right-click and use the SOLIDWORKS > Rename tool (image below), which will automatically update all references to the file.<\/p>\n If you are using a PDM vault and all files are inside PDM you can rename the file in Windows Explorer as normal (slow double-click or right-click > rename) as PDM will manage the files references being updated automatically.<\/p>\n 3. A user has moved a file from one folder to another via drag and drop.<\/p>\n Like point 2 above, when moving a file in Windows Explorer you should use the right-click, SOLIDWORKS > Move (image below), option to perform this.<\/p>\n If using PDM you are free to drag a file from one PDM folder to another PDM folder without issues.<\/p>\n If using the 3DEXPERIENCE Platform, you can move files from one Collaborative Space to another or move files to a different bookmark while still maintaining the references.<\/span><\/p>\n 4. A user has deleted the file.<\/p>\n Before deleting a file, the user should check if the file is being used\/referenced by an assembly or drawing by checking its references.<\/p>\n If using PDM you can check this quickly by looking at the \u201cwhere used\u201d tab.<\/p>\n 5. If you are migrating a lot of data (moving folders from 1 location to another) such as moving files into PDM for the first time you may need to move the project folders and Design Libraries separately.<\/p>\n In cases like this you would want to add the second (and subsequent) folder to your SW \u201cReference Location\u201d so that the files can automatically be found when opening your projects rather than having to manually browse to the files.<\/p>\n There are several ways we can fix our files once we are in a situation where we need to re-link our file references.<\/p>\n [\/et_pb_text][et_pb_image src=”https:\/\/tms-scotland.com\/solidworks\/wp-content\/uploads\/sites\/5\/2023\/03\/Missing-fles4.png” title_text=”Missing fles4″ align=”center” _builder_version=”4.17.4″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][\/et_pb_image][et_pb_text _builder_version=”4.17.4″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”]<\/p>\nWhere does SOLIDWORKS search for files?<\/h3>\n
\n
Common causes and prevention<\/h2>\n
\n
<\/ul>\n<\/li>\n<\/ol>\n
Resolving the issue<\/h2>\n
\n