Hi Jeffrey.This is an old posting and to be frank, I am not sure whether this issue is still at play. Fill in your details below or click an icon to log in: Email (required) (Address never made public) Name (required) Website You are commenting using your WordPress.com account. (LogOut/Change) You are Maybe Kevin's post is a kind of help: https://blogs.technet.com/b/kevinholman/archive/2013/10/24/opsmgr-sql-mp-version-6-4-1-0-capabilities-and-configuration.aspx February 25, 2014 at 8:12 pm #219136 Anonymous Yeah, I hear ya. I have been through that document several times. I will It is solely my own personal opinion.

If the database does not exist in the SQL instance you need to create it either by running the installer or running the scripts. This lead me think it was some kind of permissions issue but I’ve made the SCOM Action Account “SA” on all SQL servers. What's up with that? http://activecomputer.net/cannot-login/cannot-login-to-nko.php RSS Feed for this topic.

on a 64-bit computer)...

Added this account to these three profiles: SQL Server Default Action Account, SQL Server Discovery Account and SQL Server Monitoring Account. A: Actually you are. Any ideas as to what is going on here that I am missing or that I can check? Pleasecheck whetherRun As Account exist on the target system, whether Run As Accounthave enough permissions on those instances.

Over 25 plugins to make your life easier Home » Michael Skov » Run As Account does not exist on the target system or does not have enough permissions Authors What to do Check the DatabaseConnectionMS registry key for the provider being used, e.g. Management Group: MGMTGOUP. http://activecomputer.net/cannot-login/cannot-login-viwawa.php The login failed.

The login failed Cause There are various causes for this issue. Click here to get your free copy of Network Administrator. Tags: OpsMgr, opsmgr 2012, Run As Account, Run As Account does not exist on the target system or does not have enough permissions, Run As profile, SCOM, SCOM 2012, SQL Category: June 17, 2014 at 2:24 pm #221319 Michael HParticipant I implemented the low-privilege setup from the SQL MP guide because on a few standalone SQL instances and one SQL 2012 cluster,

What to do Check the database account can log on to the management server computer, no policy is preventing it (DC - admins only for example) Check the account details specified On one server, it says it doesn't have permission to model and on the other it reports insufficient permission to the ReportServerTempDB. In SCOM: 1. Running the following command in a command prompt: runas /user:[account] cmd would be a good test that the account can log on to the computer.

What can you do if the customer will not allow you to make this change to their database? The database does not exist. The Run As Account you are using for SQL either doesn’t exist on the SQL server/instance/database or it doesn’t have sufficient permission. Note: In Windows 2008/7/2012 you must first expand the folder 'Windows log' and then select the 'Application' log.