Page 3 of 3
Re: SP3
Posted: Tue Sep 12, 2023 1:44 pm
by AlexLachance
CarrieIves wrote: ↑Tue Sep 12, 2023 1:02 pm
Is anyone running PDM? I have a friend who says they are having trouble where it takes minutes for SolidWorks to open the drawing if you click on open drawing from the right mouse button does it open the drawing for you? In a reasonable amount of time? I can't check it's behavior with PDM without updating PDM.
I do not have PDM and do not encounter the behavior but I've read people having issues with it when the drawing is not located in the same folder as the part/assembly.
Re: SP3
Posted: Tue Sep 12, 2023 1:50 pm
by AlexLachance
Tapani Sjöman wrote: ↑Tue Sep 12, 2023 3:28 am
We are still in SW2022 SP4.0.
Have they repaired the BOM -failure that was presented at 2022 SP5.0?
2022 SP5.0 Error
Can you show an example of the issue, just to be more clear..? I will try and answer, and might have a work around for it depending on the issue.
Re: SP3
Posted: Tue Sep 12, 2023 2:17 pm
by bnemec
CarrieIves wrote: ↑Tue Sep 12, 2023 1:02 pm
Is anyone running PDM? I have a friend who says they are having trouble where it takes minutes for SolidWorks to open the drawing if you click on open drawing from the right mouse button does it open the drawing for you? In a reasonable amount of time? I can't check it's behavior with PDM without updating PDM.
There's several things that will/may happen when user opens (double click, right click open, etc) file from Search Tool or Vault View. While we're still on 2019 we do occasionally have very slow "open" times. Users report things like "Vault crashed" or "Solidworks crashed" when actually its still loading. Most common is when network connection is dropped over night/weekend and the pdm client needs exited and restarted to get new connection. My first step is to select the file and then click each of the tabs below, letting each one load. Then I do a get latest of the file and when the ref file dialog opens I select all and check all. This shows me if the problem is on PDM side of getting data from SQL server (most of the tabs loading) or both servers (caching files). Once that's done I double click the file to see what Solidworks does with it.
Usually that will expose what portion is causing the lag.
As far as I know Solidworks doesn't care if the files are on C:/temp or C:/Vault. It doesn't know the difference outside of what the Solidworks PDM add-in does.
When updating PDM to a new version we don't know if they installed new OS on the servers, had to set up new SQL (along with new licensing as its not included beyond SQL 2016 IIRC), or was it an in-place update? There are tests, already mentioned in these forums, about how to check PDM client to servers connections and latencies. Once PDM is added in there are a lot of things that could affect performance, but I believe it will all show up in caching files or loading the right click menus or loading the tabs. A change somewhere in PDM shouldn't be changing the open times of Solidworks once the files are cached. If it does I'd like to learn about that interaction.