Does anyone know what this error message is indicating?
"The job Cleanup Slot Locks-CPS last run was unsuccessful. It occured on 07/02/2015 08:30:00. Please contact your system administrator."
Also I myself have been getting the following one a lot lately and it kicks me out of GE. Any thoughts?
"The system has encountered an error and must close. We apologize for the inconvenience.
Message: Error occurred in class WebServiceClientBase, method CallWebService
Exception: CommunicationException: An error (The request was aborted: The request was canceled.)"
Cleanup slot locks is a SQL agent scheduled task called every 5 minutes. It launches a SP called "slotClearOldLocks." I've never looked a the SP before now. It appears to clear appointment slots that are locked due to user activity after a certain period of time. It looks mostly like a bandaid to clear issues with poor code not clearing a lock imho.
Incidentally, if you would like to change who sees these type of messages (after all, most of your staff doesn't care), here's where that can be set:
Users get a system message on login showing system information such as the max number of concurrent users and licensed features
- This is a system message. To disable, login to CPS, go to Administration > System > User and Resource Management > Users > Security > Security > Security by Permission, then expand Main Menu > Administration > > Administrative Security > Show System Warnings. Define the users or groups who are to see system messages and warnings upon login. Remove any users or groups who should not see these messages.
Thanks for your help on the cleanup slot locks one!!
Here is another one that has recently occured:
"The system has encountered an errror and must close. We aplogize for the inconvenience.
Message: Unhandled Exception caught in App_DispatcherUnhandledException
Exception: Win32Exception: Not enough quota is available to process this command."
Is this on a terminal server? I'd probably start with task manager. Enable view for the columns Handles, Threads, User Objects, and GDI objects. Monitor resource consumption when the crash occurs.
Also, in a TS environment, you want to increase the GDI process handle quota:
The default number of GDI objects available for a process is 10,000. The default can be increased to 20,000 by setting the following registry entry to 20,000 (DWORD): HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows\GDIProcessHandleQuota
You may be hitting against another quota as well. It could take some time to troubleshoot.
We have an Administrative Group set in the "Show System Warnings" section in security.
For the last few weeks all the Administrative Group members have been receiving this pop up warning message upon login: "The job Backup - master last run was unsuccessful. It occurred on 07/11/2015 02:01:00. Please contact your system administrator."
I thought in times past when a back up did not run as scheduled the Administrative group members would get the system pop up warning for a few days, but then it would go away. This one has stayed for several weeks now.
Any idea how to remove it?
Thanks!
Mike
@mcwilson, ideally you need to fix your daily scheduled backup job so it work. Or you could go with the head-in-the-sand approach and disable the warnings. 🙂
As I recall, there is a remote possibility that there is an old record in the medlists table, and the new record for a successful backup is also there, but I can't say I've seen that happen in a few years.
@SLHV Thanks for the reply.
Our backups only failed on the day the error message points out. Ever since then they have completed without error. The issue is every time someone from the Administrative group logs in to Centricity they get the annoying pop up mentioning the failed Backup from July 11th (over a month ago).
So the real question is how do we get the system to quit giving us the pop up alert about the very old failed backup from July 11th?
This is a scheduled SQL job automatically created by Centricity during install that runs backups. That is what is generating your error. I'll bet if you check the SQL logs you'll see that job is failing.
I agree, the SQL Job did fail on July 11, 2015. However, it has run successfully every day since then so the July 11 failure is a moot point and I do not need to see the Pop Message any more.
The question that remains unanswered is: How do we clear out the July 11th entry so it will quit popping up every time we log in to Centricity?
If that's the case, then it sounds possibly like the issue with an extra row in the medlists table. If you look at the medlists table (which is just a catch-all misc stuff table), there will be a row regarding the backups. Actually probably 2 rows. The July 11 row, and another for your most recent SQL agent backup.
Here's my notes from long ago about this:
- Open SQL Server Management Studio, then the target database.
- Tables > Open table "dbo.MedLists". Medlists is a table that holds all kinds of special lists.
- Open the table to view the contents.
- Open the SQL Pane to enter/view SQL code.
- Enter SELECT * FROM MedLists WHERE (TableName LIKE '%jobs%'). This will pull rows where the TableName column contains some form of the word Jobs.
- Click the Run icon (the exclamation point) to execute the query.
- Delete the daily job entry rows in this table (cleanup slot locks, backups, etc) that refer to a database other than the current database. This will delete the incorrect entries.
This was for firing up a copy of a database, but I think it gives you the idea.
Thanks Dave!
That was it. There was an entry in the MedLists table - once it was deleted the annoying pop up went away.
That is a strange table. There are all sorts of things in that table.
Glad that worked! Yes, it is a table of tables.