Yes, I've experienced this... every time I've seen it one of our IT people has installed one or more Windows Updates but have not restarted the server.
Once the server is restarted everything starts working again... including all the pending notifications being sent!
Restart the EPDM related services on the server.
If that doesn't shake it loose, reboot the archive server.
I usually setup the servers to restart Friday nights automatically.
I’ve had the same issues; my var does not know where to go with it since it’s random and not repeatable. I have an email account made for me that receives all email traffic from the vault. If I don’t see something at least once a day, I do a test email. If that doesn’t go through I restart the Database service and that normally fixes it.
Another solution I have used is reduce the use of notifications altogether and work from saved searches and dashboards.
Defeat the whole concern by a change in philosophy "We pay people to do their work, not check their email."
Set up a saved search for each team based on data card variables & workflow state (also folder location, filetype, etc.) and that becomes their to-do list for each day. They just need to refresh it every 10 minutes or so.
I know, I know, I know...pushing the refresh button is haaarrrrddd... I'm totally poking fun now.
Anyway, that's my philosophy. A little outside the box but it works far better than relying on notifications.
For what its worth!
This has happend a few times for us as well. Restarting the server services has fixed it each time. Our VAR helped us to exclude the EPDM program directories from a regular virus scan hoping that would help. It hasn't come up since then (Jan13).
This is likely happening because the "Solidworks Enterprise PDM Database server" service is not running or needs to be restarted.
Also, your dbo.messages table could be very full/large or even have an error. If you have a large backlog of messages, you may want clean house and empty out that table.
(excerpt from Adminstration guide)
SolidWorks Enterprise PDM Database Server
The SolidWorks Enterprise PDM database server polls Enterprise PDM databases for new
automated messages and schedule changes, and updates central SQL lists.
The server software can be installed on the SQL server machine that hosts the Enterprise
PDM vaults or on another server that connects to the SQL server.
The database server supports the following Enterprise PDM operations:
Automatic notifications - Workflow and other automatic notifications, such as change
state, check out, check in, add, and deadline.
View updates - Automatic updates (refresh) of listings in file vault views and add-ins
Card list updates - Periodic updates of card lists that use SQL queries for their content
Cold store scheduling - Updates of archive servers with changes made to cold store schedules
Replication scheduling – Updates of archive servers with changes made to replication schedules
Index server - administration Administration of the indexing service for content searches
Data import/export - Execution of data import and export rules at predefined intervals.
It should work fine after emptying DocumentActionInfo table (not recommended though),this is where unprocessed mails are stored.
There is also a hotfix for epdm (upgrade to Stored procedure) which modifies the number of Mails processed at one go.
We are having his same issue with EPDM 2012 SP4. For whatever reason it started a couple of months ago and been dealing with it since. We bounce the server and x amount of hours later they slowly start trickling out. This time around we looked in the DB and there we 18 pending. Bounced the server agaiin. This is the second time in last couple of months. What a pain in the butt this is turning out to be.
Restarting the "ConisioDbServer" service usually fixes...it hangs for some reason after a while. I created a scheduled task with a batch program that stops and restarts the service that runs every hour. Very simple and I haven't seen the problem since. Simple code to put in a "bat" file...see below.
NET STOP "ConisioDbServer"
NET START "ConisioDbServer"
Thanks Jason, This is what our IT group found as well. I will pass the 'bat" file idea on to them.