When I was installing SCOM 2007 R2, I met following error msg: error 26204.Error - 2147217900 : failed to execute SQL String, error detail: can not find NT user or group 'SAMPLE\...\administrator', 'sdk_users' I use domain administrator account as action and sdk account. Please help me to solve this problem, thanks.

Looks like something I have done wrong a few times. When typing the account names in the boxes do not type the domain name. Because it is listed in a third selection box. So if you type the account name as domain\administrator you will be getting the errors as the wizard does not understand that you already defined the domain name in another field.. This should show up in the error log as well if this is the case. Let me know if you did the same.Bob Cornelissen - BICTT (My BICTT Blog)

The error appeared during the installation process. I already input all vaild filed, so it is not the problem you mentioned. Do you have any other suggestions? Thanks!!

The error appeared during the installation process. I already input all vaild filed, so it is not the problem you mentioned. Do you have any other suggestions? Thanks!!

I was actually also talking about the installation process. Remember to only use the account name in the field asking for the name. The third field will ask for the domain name. I say this because you type SAMPLE\...\administrator and so it looks like there is something in between there. So if that is covered you could take a look at the account. Check out this KB atricle http://support.microsoft.com/kb/324321/en-us . Also I would suggest splitting the SDK account as a separate account. make sure it is local admin on all scom boxes (including the sql box) and you can use that as the SDK account. You could even run the installation using this account. In any case also if you split the accounts you can better pinpoint where things go wrong.Bob Cornelissen - BICTT (My BICTT Blog)

I was actually also talking about the installation process. Remember to only use the account name in the field asking for the name. The third field will ask for the domain name. I say this because you type SAMPLE\...\administrator and so it looks like there is something in between there. So if that is covered you could take a look at the account. Check out this KB atricle http://support.microsoft.com/kb/324321/en-us . Also I would suggest splitting the SDK account as a separate account. make sure it is local admin on all scom boxes (including the sql box) and you can use that as the SDK account. You could even run the installation using this account. In any case also if you split the accounts you can better pinpoint where things go wrong.Bob Cornelissen - BICTT (My BICTT Blog)

Hi, I suggest referring to the following OpsMgr security account rights mapping and make sure the user right to install SCOM R2 was used correctly: OpsMgr security account rights mapping - what accounts need what privileges? http://blogs.technet.com/b/kevinholman/archive/2008/04/15/opsmgr-security-account-rights-mapping-what-accounts-need-what-privileges.aspx Please 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.

If its reporting installation that its failing on, you might want to check this: http://support.microsoft.com/kb/944347 From here: http://opsmgr.wordpress.com/2007/05/14/recieve-error-2147217900-when-installing-scom-rms/ It could be you account doesn't have write access to the scom database (you can always try db_owner too) And there is this too: http://blogs.technet.com/b/edwalt/archive/2007/08/24/1818438.aspx