tag:blogger.com,1999:blog-4414432572587218573.post88949801363238814..comments2023-05-06T15:20:16.638+02:00Comments on Thoughts on Azure, OMS & SCOM: SCOM Database OwnerMarnix Wolfhttp://www.blogger.com/profile/09487479325587450184noreply@blogger.comBlogger8125tag:blogger.com,1999:blog-4414432572587218573.post-57215609740663897882009-05-12T09:20:00.000+02:002009-05-12T09:20:00.000+02:00Hi Brian.
Thank you for your nice words. Whenever...Hi Brian.<br /><br />Thank you for your nice words. Whenever you have a question do not hesistate to ask me. <br /><br />Best regards,<br />MarnixMarnix Wolfhttps://www.blogger.com/profile/09487479325587450184noreply@blogger.comtag:blogger.com,1999:blog-4414432572587218573.post-25741884888393527932009-05-11T21:58:00.000+02:002009-05-11T21:58:00.000+02:00Hi Marnix,
Thanks for the information on the SPN ...Hi Marnix,<br /><br />Thanks for the information on the SPN links. It turns out that my issue was stemming from installing the OpsMgr DB while logged in locally as the Config/SDK account I created. This prevented the OpsMgr install from setting the correct users and permissions on the SQL database. So for me it was solved by uninstalling the DB & RMS, logging in under a domain admin account and reinstalling.<br /><br />Thanks for having this blog... it will come in very helpful I feel.Brian Deyohttp://www.briandeyo.usnoreply@blogger.comtag:blogger.com,1999:blog-4414432572587218573.post-82611534710393713952009-05-06T08:15:00.000+02:002009-05-06T08:15:00.000+02:00Hello Brian.
Thanks for visiting my blog.
Eventh...Hello Brian.<br /><br />Thanks for visiting my blog.<br /><br />Eventhough I do not have more information from Barry than he mentioned in his comments, I logically presume it is the SDK domain account he changed the SPN on.<br /><br />Kevin Holman has blogged about resolving this issue, to be found here: http://blogs.technet.com/kevinholman/archive/2007/12/13/system-center-operations-manager-sdk-service-failed-to-register-an-spn.aspx.<br /><br />Please let me know whether this helped.<br /><br />Best regards,<br />Marnix WolfMarnix Wolfhttps://www.blogger.com/profile/09487479325587450184noreply@blogger.comtag:blogger.com,1999:blog-4414432572587218573.post-27850254031012411622009-05-05T21:58:00.000+02:002009-05-05T21:58:00.000+02:00Hi Marnix, Barry,
It wasn't specified on what obj...Hi Marnix, Barry,<br /><br />It wasn't specified on what object in AD you changed the SPN on, was it the RMS? Was it on the SDK/Config svc account you have setup?<br /><br />I'm experiencing the same symptoms you are having, and am also reinstalling OpsMgr, but didn't remove the computer objects from AD before I reinstalled. If you happen to see this I would appreciate any response you can offer me.<br /><br />thanks!Brian Deyohttp://www.briandeyo.usnoreply@blogger.comtag:blogger.com,1999:blog-4414432572587218573.post-65450525338516167752009-04-02T08:34:00.000+02:002009-04-02T08:34:00.000+02:00Hi Barry.Good to know all is well again.Best regar...Hi Barry.<BR/><BR/>Good to know all is well again.<BR/><BR/>Best regards,<BR/>MarnixMarnix Wolfhttps://www.blogger.com/profile/09487479325587450184noreply@blogger.comtag:blogger.com,1999:blog-4414432572587218573.post-79872288913364584302009-04-01T21:39:00.000+02:002009-04-01T21:39:00.000+02:00Marnix,I ended up having to call MS support. The ...Marnix,<BR/>I ended up having to call MS support. The problem was that the SPN was not set correctly. I was doing a reinstall and the SPN was still registered with the machine name from the previous installation, rather than with the active directory account I was using for the SDK service. We deleted the 2 entries for MSOMSDKSVC and then added them back with the correct account. Thanks for getting back with me.Barrynoreply@blogger.comtag:blogger.com,1999:blog-4414432572587218573.post-58436477951132135672009-03-31T08:17:00.000+02:002009-03-31T08:17:00.000+02:00Hi Barry.When the discovery wizard doesn't work (i...Hi Barry.<BR/><BR/>When the discovery wizard doesn't work (it hangs) it could be a problem with the SQL Broker not working. Check this posting of mine where you can check whether that's the case and how to resolve it. Keep me posted about how you're doing.<BR/><BR/>Posting: http://thoughtsonopsmgr.blogspot.com/2009/01/scom-discovery-wizard-doesnt-work.html<BR/><BR/>Best regards,<BR/>MarnixMarnix Wolfhttps://www.blogger.com/profile/09487479325587450184noreply@blogger.comtag:blogger.com,1999:blog-4414432572587218573.post-56940713026755150352009-03-30T17:02:00.000+02:002009-03-30T17:02:00.000+02:00I just installed OpsMgr 2007 SP1 and I'm getting t...I just installed OpsMgr 2007 SP1 and I'm getting these errors you're talking about. The account I used to install OpsMgr is a member of the local administrator group and is also the db owner of the OpsMgr databases. Do you have any suggestions about how to fix these errors. Right now the discovery wizard hangs and doesn't discover any computers. I've already looked at KB 938994, but it didn't help.Barrynoreply@blogger.com