Anyone have a way to search with a query or programming in PDM to find the folders and files which are causing this error 'path is too long' to appear on 'Get Latest Version'?
Sincerely
Dwayne Parrott CSWP, SolidWorks Instructor and Support technician
Alternative:
Search files, open as CSV in Excel, combine Found In and File Name columns (= A2&"\"&B2), make excel count characters (=LEN(C2)).
You'll get something like this:
Thanks, this helped!
Hi Dwayne,
is this a get-latest of an assembly? If so, are there any internal (Virtual) components? there is an SPR that when you make many copies of an internal component it will make the name of the copy larger (i.e Copy of Copy of Copy of Copy of....Name) and cause this message to appear in many actions where PDM needs to read the references of a file. if this is the case, I would contact your VAR for further support.
Francisco
Thanks for mentioning this, Francisco! One of my users just ran into this problem today and I would have been chasing my tail for hours had this not been the first solution I ran across!
This issue is due to the windows limitation of having a path length less than or equal to 256 characters. SWPDM does not track the lenght of the Path and actually only records the path starting at the folder in the root folder of the vault. So, if someone saves a file to a local view like: c:\OurVault with a path+filename that approaches the 256 character limit they will be able to check it in and access it with no issues.
On the other hand if someone else happens to have their local view saved to C:\Users\UserName\AppData\Roaming\SolidWorks\LocalViews\OurVault then they would not be able to access that file because Windows could not process the name.
The only thing I can think of would be to create an SQL script that looks through the Projects table of the database for any Path value that is over 230 characters long. That would help you narrow the search down to specific files.
You should also try and standardize everyone on the same location of the local view so that you don't run into this in the future.
Edited to add a sample SQL query:
SELECT
CASE WHEN LEN(Path) >= 230
THEN Path
ELSE 'value less than specified length'
END As Suspect_File_Paths
FROM dbo.Projects
***Noticed that I had the "Then" and "Else" statements backwards - It is fixed now.
You can change the path length, I just picked that as a starting point.