This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Remove From My Forums

SharePoint 2016 Management-Packs; RunAs Account

Question
0

Sign in to vote

Hi folks

I have installed the SharePoint 2016 Management Pack. So far the installation went fine with the official MP-Guid... BUT:

not all of the SharePoint 2016 - SQL-DBs are listed. After some hours, the following alert occured:

OleDb-Modul hat Fehler 0x80004005 während der Ausführung erkannt und stellt diesen als Ausgabedatenelement bereit. Unspecified error
: Login failed for user 'DOAMIN\Management-Server-Action Account'.
Workflowname: Microsoft.SharePoint.2016.SPDatabase.Connection
Instanzname: XYZ\XYZ
Instanz-ID: {XYZ}
Verwaltungsgruppe: XYZ

it seems, there is a bug, that SCOM isnt using the defined RunAs-Account for monitoring the DBs! SCOM still use the monitoring action account.

we already faced the exact same error in the SharePoint 2013 Management-Pack.

similar errors are also reported here:

https://social.technet.microsoft.com/Forums/systemcenter/en-US/d9204c0f-72f5-4af9-a8a5-c9dfbaec9fdb/sharepoint-2010-mp-for-scom-2007-r2-issues-contentconfig-database-in-status-not-monitored?forum=operationsmanagermgmtpacks

https://social.technet.microsoft.com/Forums/Azure/en-US/fcb309b7-0f1f-4853-b770-531c7a19acef/sharepoint-2013-mp-configuration-database-connection-failed?forum=operationsmanagermgmtpacks

Does anyone have the same errors / is using the SharePoint 2016 Management-Pack?

It's a bit frustrating that microsoft could not fix this error after years... :-/

Friday, June 29, 2018 6:00 AM

Answers

0

Sign in to vote
Hi Xin

Thank you for the reply. I have to apologize, we did a review of the content-dbs and most of the sharepoint-dbs are listed correctly now. the other dbs on our sql-cluster for sharepoint are technicaly not content-dbs and so they don't have to be listed. so everything is fine.

so there is only a small issue left with the monitor "SharePoint: Database Connection Failed". and we could fix this issue with an overide (the DB-Connection-String seems to be false / scom cannot handle the variable. we set the db-connection-string manually).
- Marked as answer by Sandro D'Incà Thursday, July 5, 2018 9:27 AM
Thursday, July 5, 2018 9:27 AM

All replies

0

Sign in to vote

Hi Sandro,

I totally understand your concern. and we're very sorry for any inconvenience that may caused.
we will also report this issue and hopefully receive an answer as soon as possible.
If your case is quite urgent, we recommend you open a case in Microsoft CSS support.

Support options for business users
https://support.microsoft.com/en-us/gp/support-options-for-business?wa=wsignin1.0

Thanks for your understanding.
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

Monday, July 2, 2018 9:40 AM
0

Sign in to vote
Hi Xin

Thank you for the reply. I have to apologize, we did a review of the content-dbs and most of the sharepoint-dbs are listed correctly now. the other dbs on our sql-cluster for sharepoint are technicaly not content-dbs and so they don't have to be listed. so everything is fine.

so there is only a small issue left with the monitor "SharePoint: Database Connection Failed". and we could fix this issue with an overide (the DB-Connection-String seems to be false / scom cannot handle the variable. we set the db-connection-string manually).
- Marked as answer by Sandro D'Incà Thursday, July 5, 2018 9:27 AM
Thursday, July 5, 2018 9:27 AM