Answered by:
The login already has an account under a different user name

Question
-
Hi there,
i moved the database files from C to D drive on my primary site server (stopsite, detach, atach, etc). I've altered the database conform this KB: http://support.microsoft.com/kb/2709082?wa=wsignin1.0
So everything is working fine, however i keep getting this error message on the SMS_HIERARCHY_MANAGER component:
Microsoft SQL Server reported SQL message 15063, severity 16: [42000][15063][Microsoft][SQL Server Native Client 10.0][SQL Server]The login already has an account under a different user name.
I think that this has to do with SCCM trying to configure something on the database. But i don't know how to fix this. Database is in multiuser mode, sa is DB owner, snapshot isolation mode is on and so on.
Does anyone know what SCCM tries to accomplish right before this error is raised?
Regards!!!
Dutch guy
- Edited by Dutch guy Tuesday, November 20, 2012 10:05 AM
Tuesday, November 20, 2012 9:57 AM
Answers
-
i got the solution from the other link below
Thanks to David. This worked for me.
-vrkumar
RajKumar
- Proposed as answer by vrkumar01 Thursday, April 18, 2013 8:57 AM
- Marked as answer by Robert Marshall - MVPMVP Friday, May 10, 2013 8:38 PM
Thursday, April 18, 2013 8:57 AM
All replies
-
SQL Server Profiler should tell you that.
Torsten Meringer | http://www.mssccmfaq.de
Tuesday, November 20, 2012 10:25 AM -
hmm, then i have to wait for lets say 10 minutes because i don't know on what exact moment the event occurs. Undo-able :-S
Probably SCCM tries to configure a login or some permissions?? Maybe delete something to let SCCM be able to finish her task??
Tuesday, November 20, 2012 1:16 PM -
Hi there,
Did you ever resolve this error? We are seeing the same error in our new SCCM 2012 environment w/ a local DB that has not been moved. The error is only being logged over night, I don't think I'll be able to catch it with profiler. Thought I'd see if you found an answer in your environment. Thanks!
- Edited by kit_jj Tuesday, January 15, 2013 5:29 PM
Monday, January 14, 2013 3:55 PM -
Hi Team,
We are also seeign the same error on SCCM 2012, any solution available if so please share.
vrkumar01
RajKumar
Friday, April 12, 2013 6:02 AM -
Hi guys,
Try reviewing the hman.log file a the time the component logs the error. It will give you further information on SMS_Hierarchy_Manager issues and will perhaps lead you to the cause. It might even refer to the logon account that is causing the problem.
Gerry Hampson | Blog: www.gerryhampsoncm.blogspot.ie | LinkedIn: Gerry Hampson | Twitter: @gerryhampson
- Edited by Gerry HampsonMVP Tuesday, June 25, 2013 11:32 PM Edited blog address
Monday, April 15, 2013 5:11 PM -
i got the solution from the other link below
Thanks to David. This worked for me.
-vrkumar
RajKumar
- Proposed as answer by vrkumar01 Thursday, April 18, 2013 8:57 AM
- Marked as answer by Robert Marshall - MVPMVP Friday, May 10, 2013 8:38 PM
Thursday, April 18, 2013 8:57 AM -
Thanks for the update, appreciated
Rob Marshall | UK | My Blog | WMUG | File CM12 Feedback | CM12 Docs | CM12 Release Notes
Friday, May 10, 2013 8:38 PM