Solidworks PDM Email Notifications randomly stop working in SW2018 SP4.0.
IT has to reboot the server after hours and this resolves the issue. Is there a more permanent fix for this? This has occured 3 times in the last 6 months.
For more than a handful of customers i have just made a script that will restart the "SOLIDWORKS PDM Database Server" service each morning, to keep it alive. It can, randomly, just stop. No log, no warnings, no reasons. A restart is all that it takes to go live again.
I use Windows Task Scheduler to run the script.
it is possible to try to adjust in Properties of Service - restarts at failures.
Also will not prevent in *.exe properties of the file to set start with the rights of the Administrator.
It is also possible to add to exceptions of an antivirus and to configure firewall ports.
Will not prevent to look also in case of a problem at Log-s.
It is possible to check the tables SQL dbo.BroadcastEvens and dbo.DocumentActionsInfo - possibly in lists of mailing there are any more not existing recipients or Vaults.
I guess you don't need to use task scheduler, just try to set "recovery" actions for "SOLIDWORKS PDM Datavase Server" service.
(Image below is from google because I'm using non-English Windows version)
Hi Kamil. It's been a while since i saw the problem, but i think i remember that the process remains running, so the service is flagged as running too. But the program still has stopped working. Otherwise i agree.
We contacted our VAR and we are going to reboot the server weekly to try and avoid this from happening. Thanks everyone
During the SolidWorks PDM Database Server restart, does it disable everyone form working in it? I would assume users would not be able to check anything in/out change states, etc. Is that correct?
We have never tried a reboot while users were working on Solidworks. To be safe we complete the reboot after-hours. Potentially you would not be able to open the Vault during the reboot (if you tried, it would freeze and crash your explorer/Solidworks). If you started the reboot mid-session, users would be unable to open new parts from the vault/ change state/ check-in until the reboot was complete. But I would recommend not doing this.
Database server service shoulnd't cause any problem at all to reboot on production time, done that many many times as we have had so many problems with it.
It only checks DocumentActionInfo, BroadcastEvent and Exportbatches tables from Database.
Service will continue with the data that there is in the table after restart. When service has handled all in table(s) it will empty it.
Database server service does not affect state changes or check-ins etc.
State changes, check-ins and pretty much everything else is handled directly in DATABASE, not with service.
Basically it handles notifications, xml exports and card lists to be shown in datacards.
Let's check if SQL user which is used in "Database Server Settings" tool (on SQL server) is correct and check if password doesn't expire.
There is actually this registry key which helped our case with database server problems:
and inside it all servers: Server1;server2;server3;server4
This is some spr but cannot remember which one.
Retrieving data ...