tag:blogger.com,1999:blog-7396481053359703519.post5097261175664961929..comments2024-03-26T04:04:33.060+01:00Comments on Henk's blog: Setup could not install SQL RMO, ConfigMgr installation cannot be completedHenk Hoogendoornhttp://www.blogger.com/profile/01066841733613965112noreply@blogger.comBlogger7125tag:blogger.com,1999:blog-7396481053359703519.post-64814471854196783382019-01-27T19:44:15.987+01:002019-01-27T19:44:15.987+01:00Great stuff, this helped out in my installation as...Great stuff, this helped out in my installation as well. Thanks a lot.Unknownhttps://www.blogger.com/profile/08199395379508944688noreply@blogger.comtag:blogger.com,1999:blog-7396481053359703519.post-6717291665010952952018-05-31T02:14:26.518+02:002018-05-31T02:14:26.518+02:00I had the same error for more that 10 times, what ...I had the same error for more that 10 times, what I did was I reduced the sql memory size limit and it worked.Anonymoushttps://www.blogger.com/profile/15370084074956842764noreply@blogger.comtag:blogger.com,1999:blog-7396481053359703519.post-60830226812132379892017-10-29T10:21:53.174+01:002017-10-29T10:21:53.174+01:00Hi guys =) thanks for your inspiration (now it wor...Hi guys =) thanks for your inspiration (now it works). @ Ull Rotta (the same by me).<br /><br />I have run it in HyperV with Server 2012R2 , first SQL Server 2012 and later update to SP1 in my testlab @ home (for my new jobrole)<br /><br />Its funny (you can run: precheck without errors and i was very happy .. and finaly then the s.... SQL RMO error ;) ... . My next step is to built a Testlab for SCCM 2016. I am Newbie @ SystemCenter ;/Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7396481053359703519.post-50625560865480109962017-03-20T01:59:59.482+01:002017-03-20T01:59:59.482+01:00Thanks for your blog Henk, great stuff.
Had the ...Thanks for your blog Henk, great stuff. <br /><br />Had the same error described here but I had to take a slightly different approach. <br /><br />1) Ran Sharemanagementobjects.msi and installed the components <br />2) Ran msxml6_x64.msi (also in the prerequisites folder) <br /><br />My log was showing msxml6_64.msi returning an error code, running the component manually appears to have fixed the issue. Anonymoushttps://www.blogger.com/profile/12740869899429839472noreply@blogger.comtag:blogger.com,1999:blog-7396481053359703519.post-88191675738039725132016-12-05T15:37:47.366+01:002016-12-05T15:37:47.366+01:00Thank you, this applies to SCCM Current Branch as ...Thank you, this applies to SCCM Current Branch as well. At least it did in my instance. Specifically, re-running SharedManagementObjects.msi. Good find.Chrisnoreply@blogger.comtag:blogger.com,1999:blog-7396481053359703519.post-79167488458692922652016-07-18T21:44:50.061+02:002016-07-18T21:44:50.061+02:00My pleasure and thanks for feedback.My pleasure and thanks for feedback.Henk Hoogendoornhttps://www.blogger.com/profile/01066841733613965112noreply@blogger.comtag:blogger.com,1999:blog-7396481053359703519.post-53611888711291220022016-07-18T14:54:06.363+02:002016-07-18T14:54:06.363+02:00OMG! Spent 2 hours searching for a solution. "...OMG! Spent 2 hours searching for a solution. "Have you tried turning it off, and then back on again?" Thanks, it worked :DLou Gouberhttps://www.blogger.com/profile/02183100034241812668noreply@blogger.com