tag:blogger.com,1999:blog-4414432572587218573.post8331256985069502645..comments2023-05-06T15:20:16.638+02:00Comments on Thoughts on Azure, OMS & SCOM: Installation error when installing a SCOM R2 Management Server: ‘Error validating current user and server’Marnix Wolfhttp://www.blogger.com/profile/09487479325587450184noreply@blogger.comBlogger12125tag:blogger.com,1999:blog-4414432572587218573.post-54919788820432960582012-01-06T14:41:21.949+01:002012-01-06T14:41:21.949+01:00Hi,
I had the same problem,restarting the server ...Hi,<br /><br />I had the same problem,restarting the server worked fine for me........Anonymoushttps://www.blogger.com/profile/08384733862740672636noreply@blogger.comtag:blogger.com,1999:blog-4414432572587218573.post-1877134773092708602010-10-08T07:43:53.329+02:002010-10-08T07:43:53.329+02:00Hi Micheal.
Thanks for visiting my blog.
There c...Hi Micheal.<br /><br />Thanks for visiting my blog.<br /><br />There could be many causes at play here. Check out the file momx.log (where x is a number, starting at zero, you have to check out the latest one).<br /><br />This file is located in the folder %temp% and check it for value 3. This will tell you more where it went wrong.<br /><br />Cheers,<br />MarnixMarnix Wolfhttps://www.blogger.com/profile/09487479325587450184noreply@blogger.comtag:blogger.com,1999:blog-4414432572587218573.post-72028827473609363602010-10-08T01:15:10.251+02:002010-10-08T01:15:10.251+02:00Hi there-
I too am having a problem, only it'...Hi there-<br /><br />I too am having a problem, only it's with the RMS. We lost the server and I'm re-installing the RMS on a new server. We used log shipping for the OperationsManager DB and that is fine, data is all there. When I try and install the RMS I get the validation error dialog box when inputting the SDK Config user account credentials (I checked everything and it's fine) The SDK user has the appropriate rights on the DB. The Action account worked just fine. <br /><br />I'm sure I'm missing a critical step here, thankfully this is our dev environment ;) I do have the encryption key backed up. Any ideas? -MichaelUnknownhttps://www.blogger.com/profile/16787478124610157321noreply@blogger.comtag:blogger.com,1999:blog-4414432572587218573.post-69146153009717953552010-08-24T19:35:01.891+02:002010-08-24T19:35:01.891+02:00Hi Lt.Ripley.
Good to hear all is well again. Som...Hi Lt.Ripley.<br /><br />Good to hear all is well again. Sometimes the road the success with SCOM is a bit rough and challenging! :)<br /><br />But you faced it! A job well done. You can always contact me. Not that I know it all (is impossible) but I do have my contacts...<br /><br />Thanks for your nice comments on my blog. Blogging consumes a lot of my time but all hobbies do that. And comments like yours keep me going.<br /><br />Cheers,<br />MarnixMarnix Wolfhttps://www.blogger.com/profile/09487479325587450184noreply@blogger.comtag:blogger.com,1999:blog-4414432572587218573.post-18612204297773257392010-08-24T18:24:07.691+02:002010-08-24T18:24:07.691+02:00I'm happy to report that after rebuilding the ...I'm happy to report that after rebuilding the MS with a new OS install, the SCOM install finally completed. The only "new" behaviour was that after the OS install, the prerequisite check failed with "Microsoft.interop.security.azroles.dll is not registered in the global assembly cache". I hadn't seen that before, but I registered the dll and the pre-req check passed. Installed fine this time.<br /><br />Marnix, thanks so much for your prompt replies. Your blog is one of the best on SCOM and we follow it closely. I was compelled to write to you when I got that same error you did as I had never seen it before, in all the installs I'd done. I'll no doubt have more questions for you in the future, but take care for now!Lt.Ripleyhttps://www.blogger.com/profile/11718240368618814634noreply@blogger.comtag:blogger.com,1999:blog-4414432572587218573.post-18134686702505624182010-08-23T09:58:28.238+02:002010-08-23T09:58:28.238+02:00Hi Sam.
Never ever install a SCOM Agent on any SC...Hi Sam.<br /><br />Never ever install a SCOM Agent on any SCOM Server (RMS, MS or Gateway Server). <br /><br />Cheers,<br />MarnixMarnix Wolfhttps://www.blogger.com/profile/09487479325587450184noreply@blogger.comtag:blogger.com,1999:blog-4414432572587218573.post-2868839243078611982010-08-20T20:30:25.631+02:002010-08-20T20:30:25.631+02:00I notice I had installed the agent on the MS SERVE...I notice I had installed the agent on the MS SERVER, Which is not require, I uninstall all system center config components, I deleted the agent in the agent managed section of the root mangement server. <br />rebooted server I reinstalled management server and it worked.samhttps://www.blogger.com/profile/07291697122477891533noreply@blogger.comtag:blogger.com,1999:blog-4414432572587218573.post-41555523675907411792010-08-20T07:37:02.527+02:002010-08-20T07:37:02.527+02:00Hi Lt.Ripley.
Thanks for your comments. Much appr...Hi Lt.Ripley.<br /><br />Thanks for your comments. Much appreciated. Please let me know the results.<br /><br />Cheers,<br />MarnixMarnix Wolfhttps://www.blogger.com/profile/09487479325587450184noreply@blogger.comtag:blogger.com,1999:blog-4414432572587218573.post-76872771956615154302010-08-19T18:23:09.820+02:002010-08-19T18:23:09.820+02:00Reinstalling SCOM on the original server didn'...Reinstalling SCOM on the original server didn't work for me (but an installation on a test server DID work). I'm going to rebuild the original server today and then try again from scratch. If I'm unable to reinstall SCOM on this server even after a new OS installation, I'll be officially stumped. I will post the results. Thanks again for the response. Your blog is excellent.Lt.Ripleyhttps://www.blogger.com/profile/11718240368618814634noreply@blogger.comtag:blogger.com,1999:blog-4414432572587218573.post-48902129660349243932010-08-18T19:31:51.820+02:002010-08-18T19:31:51.820+02:00Thank you for replying so quickly. You're rig...Thank you for replying so quickly. You're right - I meant to say that I removed SCOM from a single SCOM Mgmt Server while leaving the SCOM Mgmt Group in tact. So we have the RMS and one other Mgmt Server that appear to be working. The server that I removed SCOM from entirely was just another failover/backup MS. I have been unable to reinstall SCOM on it since that time. I removed the server from the Mgmt Servers list in SCOM and have ensured it is not in Agent Managed or Agentless Managed. We queried the SQL database to try and remove all instances of that server, but I still get this error on install. I reproduced it on a brand new server as well so I thought the problem must be with the RMS or SQL. I just tried this again today though on a different server and the install worked. I'm going to try again on the original server and will post my results.Lt.Ripleyhttps://www.blogger.com/profile/11718240368618814634noreply@blogger.comtag:blogger.com,1999:blog-4414432572587218573.post-309545098704072252010-08-18T09:58:35.784+02:002010-08-18T09:58:35.784+02:00Hi.
Thanks for visiting my blog.
About the issue...Hi.<br /><br />Thanks for visiting my blog.<br /><br />About the issue you are experiencing, do I understand it correctly that you have removed SCOM entirly? The DBs as well?<br /><br />Or do you mean you removed a single SCOM Management Server while leaving the SCOM Management Group in tact?<br /><br />And are you having issues now with reinstalling the SCOM Management Server?<br /><br />Cheers,<br />MarnixMarnix Wolfhttps://www.blogger.com/profile/09487479325587450184noreply@blogger.comtag:blogger.com,1999:blog-4414432572587218573.post-17952386830015760902010-08-17T23:21:18.380+02:002010-08-17T23:21:18.380+02:00I'm having the same problem. We had an RMS pr...I'm having the same problem. We had an RMS problem and we thought we had it fixed by reinstalling all of the .NET components. After that time however, we noticed one of the failover management servers couldn't launch the console. In the course of troubleshooting, we removed SCOM entirely. I have not been able to reinstall it since that time. Rebooting this server, along with the RMS had no effect. Can you think of anything on the RMS that might be causing this? I'm now able to replicate the problem on other new servers (just trying to install SCOM). The user account has the required permissions in SQL and is the same account that we used to install the other management servers. All ideas/suggestions are welcome.Lt.Ripleyhttps://www.blogger.com/profile/11718240368618814634noreply@blogger.com