Hi everyone, Vikram Sahay here and I’m back again with another interesting topic on System Center Operations Manager 2007. Hope you find it useful.
Recently we were working on an issue where we were getting an alert from few of the SQL servers as: 'Cannot login to database'
We checked and verified that the 'Agent Action account' or the ‘SQL Monitoring Account’ had the 'SysAdmin' rights on the SQL servers but we were still getting the error as 'Cannot login to database' which puzzled us.
Upon troubleshooting, we found that the alert was only from few of the custom databases and not from all the databases located on a SQL server. Further, we found that when we got the alert we were getting an event like 17137 with the description as ‘Starting up database '<Custom DB name>'. We also found that on the properties of those DBs (for which we get the alerts), the ‘Auto Close’ option was set as ‘True’ whereas the default value is set as ‘False’.
Once we changed the value of ‘Auto Close’ to ‘False’ we no longer got the 'Cannot login to database' alert. This was a fairly rare issue so I thought I would share it here. Hope you will find it useful.
Vikram Sahay | System Center Technical Lead
App-V Team blog: http://blogs.technet.com/appv/ AVIcode Team blog: http://blogs.technet.com/b/avicode ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/ DPM Team blog: http://blogs.technet.com/dpm/ MED-V Team blog: http://blogs.technet.com/medv/ OOB Support Team blog: http://blogs.technet.com/oob/ Opalis Team blog: http://blogs.technet.com/opalis Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/ OpsMgr Support Team blog: http://blogs.technet.com/operationsmgr/ SCMDM Support Team blog: http://blogs.technet.com/mdm/ SCVMM Team blog: http://blogs.technet.com/scvmm Server App-V Team blog: http://blogs.technet.com/b/serverappv Service Manager Team blog: http://blogs.technet.com/b/servicemanager System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials WSUS Support Team blog: http://blogs.technet.com/sus/
This is a very interesting find, and I seem to finding some similar servers that are affected with this issue. The problem I have, these are DB's managed by our customers, and for at least one this was set _intentionally_ is there a way to get around this
issue without tweaking the config of a production database?
Also, I've just found a few servers where auto close is already true, and i'm seeing event 17137