hello prasad ,
thanks for the response as per the observation we have seen latency time going upto 260 ms in command prompt . yes we tried asking client to work offline but performance is better than worst after unchecking the epdm addin from solidworks the crashes have come down. but please tell me is there any problem if we have EPDM installed as admin image and solidworks installed through normal installation in an local machine . will there be problem on this please update me as we are facing lot problems from the client
Hello, 260ms is very high. I believe the highest limit recommended by SolidWorks is around 200ms. Anything beyond that is basically unworkable. This is the issue you will have to address, is it a WAN (Wide area network) that your clients are working over? Speak to your IT people about WAN optimization, and improving the latency.
There is no problem I can see with having EPDM installed from an admin image, and SolidWorks from a local install.
Kind regards,
Prasad
Jason Capriotti @Prasad Bhonsule
Hello prasad and Jason,
thanks a lot for the response .user having replicated archive server in bangalore and the main archive server is located in US.
the replication takes once in a day during start of the day. we suspect this is issue happen whenever file tries fetch meta data from the vault for latest version of the file would make solidworks unstable due high latency and also suspect replication which happen during the morning time is not happening compeletely is there any method to check this . we did ask a user to work compeletely isolate pdm from solidwork by unplugging LAN cable and we didnt see any crash on that day and performance was also good. is there any way we can speed up the replication process and as far the firewall customer is not having any firewall in the server . . looking forward for your feeback
I am having similar issues. my ping to my server is great, 128, 0 packet losses. Here is the weird thing
Open Assembly 1, open a part in a sub assembly of the assembly, take 30s or longer to close the part to get back to the main assembly even if you made 0 changes. (doesn't matter if assembly is checked out or not)
Pack and Go said assembly. In the copy of said assembly outside of PDM professional, Every thing works prefect
Closes the copy assembly and opens the original assembly, EVERY THING WORKS PERFECT until... You open up the drawing of said assembly, now you are back to square one. Even if you close the drawing and close the original assembly, and just open the assembly it has the hang up on closing sub assemblies and parts.
This problem happens across all assemblies I have tested so far
hello John Huntington,
we are facing the same problem as we accessing the files from the us server inspite having replication value , the performances of this assemblies is very dead slow and client is very much frustrated from performance pdm addin. working without epdm is very difficult as there usage is more depended on epdm vault files
with regards
madhusudan.g
I set up some maintenance plans to rebuild the indexes in SQL. I ran it manually but it didn't seem to fix it much, but it ran again over the weekend and on a Monday everything works 100%. *knock on wood* we are not having any performance issues with PDM professional in the last 4 weeks
Hi.
Try turning of the pdm add-in. Read somewhere that it could slow down performance in 2016 version.
Regards
T-R
hello Tom-Rune Jensen,
thanks for the update
as per the observation we have seen latency time going upto 260 ms in command prompt . yes we tried asking client to work offline but performance is better than worst after unchecking the epdm addin from solidworks the crashes have come down. but please tell me is there any problem if we have EPDM installed as admin image and solidworks installed through normal installation in an local machine . will there be problem on this please update me as we are facing lot problems from the client
with regards
madhusudan.g
Do you have a replicated archive server in your location that your clients are pointed to?
Just curious here but did you set up a "test" environment and was it working then?
Also, do you have a virus software running on the server and can it be turned off? Client?
Have you updated the older files to the current version?
We've tried these things before but I'm not running EPDM, I'm running Smarteam.
Steve C
We've had the same issues since we rolled it out in late December of 2015. I guess my only question as I've tried everything everyone else seems to have tried with the exception of updating all of our part and assembly files to SolidWorks 2016 format is has anyone received ANY help from their VAR or SolidWorks directly?
I am shocked we are all still dealing with this, it's costs me hours each day and giving reliable deadlines for Engineering releases is pretty much pointless due to the severity of the issue. I have several larger assembly files and associated assembly drawings that take 25 plus minutes just to open, manipulating any data beyond that takes hours. I've never seen something quite this bad in terms of its overall effects on performance and I'm a CSWP who's been using the software since 1998.
Can you open a Command Prompt and ping the server from any client machine? What is the response time? Are there any changes that have been made on your server recently? (Windows updates, firewall configuration etc)
From the screenshot provided it seems that there are either connection settings that are not configured correctly (wrong sa password) or the connection time is extremely long.
Kind regards,
Prasad