This can be caused by the SolidWorks PDM Database Server Service hanging on the server. Try to restart this service ( in Control panel, services), that could resolve the problem.
Thanks Michael for quick response.
Actually we have tried this option but still not able to receive notifications & BOM.
Is there any way to resolve this query?
ok, then it is no that easy...
I could imagine the user, under which the service is running does not have sufficient permissions for the locations outside the vault. By default the services run as "local system", which would not be allowed to write to e.g. a mapped drive.
You could try and set the service to run as domain admin user( for a test), maybe that helps?
Hi, check the Application Log in Event Viewer on the server. Notifications and BOM exports are handled by the database server service, so if not working correctly could point to a problem with that service.
Also what version of PDM and service pack are you using? There is a known bug with notifications and BOM exports in PDM 2016 SP4 See the below from the Knowledge base:
The following two problems affect the SOLIDWORKS® PDM 2016 SP4 Professional and Standard software:
SPR#972893: Database Server Service fails to generate Notifications and Custom Columns are not shown using PDM Standard 2016 SP4. This problem prevents the automatic generation of notifications. It also prevents the display of custom columns.
SPR#973673: Export Rule for BOM data does not output XML file in SOLIDWORKS PDM Professional 2016 SP4. This problem prevents the export and import of XML data.
These problems do not exist in SOLIDWORKS PDM 2016 SP3 or in older service packs of the SOLIDWORKS PDM 2016 software. Both SPRs have been implemented in SOLIDWORKS PDM 2016 SP5 and 2017 SP0 or later versions.
Hello Prasad, the service pack I am using is SWX 2017 SP 0. But it is not service pack related issue.
Try recreating the notification. I have had this happen before after an upgrade. Once I recreated the notifications, everything was fine. I never looked into why it happened since I had a quick fix.
Thanks for your responses and help.
There is one article on Knowledge base S-08226. I referred that resolved my issue.
Restarting SWX PDM Databse server is first thing but if its not working then please follow the steps in the KB article.@
Restart the database server. Those are both managed by it. I recommend to all our clients to setup a task to restart the DB server on a weekly basis to avoid this.
Hope this helps,