My envirnoment is having 2 primary sites attached to same SQL box, and 4 secondary servers too. From last couple of days, I am getting an warning message on the component - SMS_DATABASE_NOTIFICATION_MONITOR: Message ID: 619 Microsoft SQL Server reported SQL message 229, severity 14: [42000][229][Microsoft][ODBC SQL Server Driver][SQL Server]The SELECT permission was denied on the object 'sysobjects', database 'mssqlsystemresource', schema 'sys'. Please refer to your SMS documentation, SQL documentation, or the Microsoft Knowledge Base for further troubleshooting information. Any idea what could be the issue ? I have restarted the server but still the warning messages are keeps on growing....

so ignoring the fact the you have two ConfigMgr site db attached to the same SQL server (i.e. not following best pratices) The error message state that you are getting access denied, so I would go and talk to the SQL dba and find out what they changed and find out what the security is set to on the sysobjects in the mssqlsystemresoure db. http://www.enhansoft.com/

There are several accesses need permissions. I suggest you run SQL Profiler to find the root cause. Using SQL Profiler http://technet.microsoft.com/en-us/library/cc966515.aspxPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Thanks for your reply, I have checked with SQL team and as per them they haven’t made any changes to the current setup. In fact for a troubleshooting purpose they have provided the max security privilege (sysadmin) for service account. But still the warnings are keep on growing, And just to update: after providing the sysadmin access to service account, I have restarted the sms services.

In fact for a troubleshooting purpose they have provided the max security privilege (sysadmin) for service account. Which "service account" are you talking about? ConfigMgr usually uses the local system (computer) account for connecting to the database.Torsten Meringer | http://www.mssccmfaq.de

Sorry for the delay in replying to this posts. we aere checking with SQL team for the past couple of days and nothing still worked,. They have given the max security privilages to service account and they have changed many settings and they confirmed that it is nothing related to SQL. So we had another change which we did came into our mind. Few weeks back, the server team had removed the sms service account from Domain Admin Group and now this account has desktop admin privilages. Is this change could be the reason for above issue?

Which "service account" are you talking about? ConfigMgr usually uses the local system (computer) account for connecting to the database. What about answering my question? You are now talking about an "service account" again and it's still not clear what you are talking about.Torsten Meringer | http://www.mssccmfaq.de

Sorry for the confusion, I mean the domain user ID which we used while installing and configuring the SCCM, Thats what i meant by Service Account. I understood the fact that this account is not playing any major role in connecting with SQL, instead as you said the system account is used to communicate with SQL. But Recently we had a change in this Domain user id (Service Account). During the SCCM installation, This ID was a memeber of Domain Admin group. But currently the security team had removed it from the Server Admin Group and it ihas only desktop admin access. Is this a reason for the above mentioned error ?