tag:blogger.com,1999:blog-4414432572587218573.post715060837623639437..comments2023-05-06T15:20:16.638+02:00Comments on Thoughts on Azure, OMS & SCOM: SharePoint Server 2013 MP: How About Monitoring The SharePoint Databases?Marnix Wolfhttp://www.blogger.com/profile/09487479325587450184noreply@blogger.comBlogger12125tag:blogger.com,1999:blog-4414432572587218573.post-42320678174017655262014-12-15T13:18:23.410+01:002014-12-15T13:18:23.410+01:00I Can confirm that SP2013 mp doesn't need to o...I Can confirm that SP2013 mp doesn't need to override connection string, only correct rights need to be granted to action account on SP databasesAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-4414432572587218573.post-80690396527724628802014-09-09T23:20:14.790+02:002014-09-09T23:20:14.790+02:00Had the opportunity to have a look at the SPS2010 ...Had the opportunity to have a look at the SPS2010 management pack connection strings today.<br /><br />The connections will not work with the original connection strings. <br />The monitor returns “Data Source could not be initialized”.<br /><br />So to summarize:<br /><br />Changing the connection strings and granting public rights to the management server action account on the configuration and content databases should get you going.<br />/GHGreenhelmethttps://www.blogger.com/profile/03129106527893909946noreply@blogger.comtag:blogger.com,1999:blog-4414432572587218573.post-35320237004607605102014-09-03T09:46:51.658+02:002014-09-03T09:46:51.658+02:00Truthfully I can't remember in which order I a...Truthfully I can't remember in which order I applied the steps when troubleshooting the issue. Currently the connection strings are changed according to http://support.microsoft.com/kb/2690744<br /><br />For SPS 2013 the original connections strings will Work.<br /><br />I’ll revisit the SPS2010 system next week, and will test the original connections strings and post back. Cheers.<br />Greenhelmethttps://www.blogger.com/profile/03129106527893909946noreply@blogger.comtag:blogger.com,1999:blog-4414432572587218573.post-62051205088455085152014-09-02T16:24:21.548+02:002014-09-02T16:24:21.548+02:00@Greenhelmet are you saying that once you grant th...@Greenhelmet are you saying that once you grant that level of permissions, that you do not have to edit the ConnectionString?Anonymoushttps://www.blogger.com/profile/12356627247574953368noreply@blogger.comtag:blogger.com,1999:blog-4414432572587218573.post-86665514982120711812014-09-02T13:19:18.534+02:002014-09-02T13:19:18.534+02:00Came across this blogpost yesterday and wanted to ...Came across this blogpost yesterday and wanted to offer my to cents.<br /><br />One possible workaround, is to give the Management Server Action Account public rights on every content or configuration database you want to monitor. <br />This is how I get past the issue, when the connection monitors are requested. Cheers! Greenhelmethttps://www.blogger.com/profile/03129106527893909946noreply@blogger.comtag:blogger.com,1999:blog-4414432572587218573.post-86526132255051669182014-08-11T11:14:37.994+02:002014-08-11T11:14:37.994+02:00Even in my environment the database is using defau...Even in my environment the database is using default action account and not SharePoint Run as Account. Do we have a solution or suggestion ?Anonymoushttps://www.blogger.com/profile/01002651025775768994noreply@blogger.comtag:blogger.com,1999:blog-4414432572587218573.post-28448973481449871922014-01-21T20:43:37.606+01:002014-01-21T20:43:37.606+01:00Also seeing this issue. I was also under the impre...Also seeing this issue. I was also under the impression that the workflow will use the account designated in the RunAs profile to handle all of the SP workflows. We've got a Farm Admin account for this, but this "lovely" management pack seems to be using the Default Action Account, NOT the RunAs account, to perform this connection.<br /><br />Workaround anyone?Anonymoushttps://www.blogger.com/profile/12356627247574953368noreply@blogger.comtag:blogger.com,1999:blog-4414432572587218573.post-4243111119955011462014-01-21T20:43:02.517+01:002014-01-21T20:43:02.517+01:00Also seeing this issue. I was also under the impre...Also seeing this issue. I was also under the impression that the workflow will use the account designated in the RunAs profile to handle all of the SP workflows. We've got a Farm Admin account for this, but this "lovely" management pack seems to be using the Default Action Account, NOT the RunAs account, to perform this connection.<br /><br />Workaround anyone?Anonymoushttps://www.blogger.com/profile/12356627247574953368noreply@blogger.comtag:blogger.com,1999:blog-4414432572587218573.post-2427150042530027322013-09-26T18:54:00.705+02:002013-09-26T18:54:00.705+02:00We are having a similar issue in the database conn...We are having a similar issue in the database connection fails with the default action account. Its not using the SharePoint Run As account. We have assigned the distribution to the SQL Cluster and we have changed the default action account for the cluster agents but the database query is still using the SCOM default action account.<br /><br />GoVikes01 did you manage to resolve this issue? If so how?Anonymoushttps://www.blogger.com/profile/17545013251692262079noreply@blogger.comtag:blogger.com,1999:blog-4414432572587218573.post-23852406700051021392013-05-03T15:18:16.040+02:002013-05-03T15:18:16.040+02:00Hi GoVikes01.
I see the same behavior with the Re...Hi GoVikes01.<br /><br />I see the same behavior with the Reports of this MP. Only two of them are uploaded to the SSRs instance and the remaining lot fails. I have blogged about it (http://thoughtsonopsmgr.blogspot.nl/2013/05/bug-alert-sharepoint-server-2013-mp.html) and contacted Microsoft about this issue.<br /><br />Cheers,<br />MarnixMarnix Wolfhttps://www.blogger.com/profile/09487479325587450184noreply@blogger.comtag:blogger.com,1999:blog-4414432572587218573.post-18035750516547475142013-05-02T08:05:02.170+02:002013-05-02T08:05:02.170+02:00Hi GoVikes01.
The SCOM Action account requires ac...Hi GoVikes01.<br /><br />The SCOM Action account requires access to the SharePoint databases and requires Farm Admin permissions on the SharePoint Farm as well in order to make it work.<br /><br />Can you tell me what problems you have with the SharePoint Reports, or better, the import issue.<br /><br />Cheers,<br />MarnixMarnix Wolfhttps://www.blogger.com/profile/09487479325587450184noreply@blogger.comtag:blogger.com,1999:blog-4414432572587218573.post-48056022046480060852013-04-25T15:15:11.435+02:002013-04-25T15:15:11.435+02:00I followed your steps and created an override for ...I followed your steps and created an override for a SharePoint database to test but the monitor is in an unhealthy state because SCOM is connecting to the database using the default Agent Action Account instead of the SharePoint Run As Account. How were you able to tell SCOM to use the SharePoint account instead? Also, did you have a problem importing the SharePoint 2013 reports? I am missing those as well. Thanks!GoVikes01https://www.blogger.com/profile/17398824875512770605noreply@blogger.com