The installation tries to add the BUILTIN\BUILTIN access inside SSRS but fails, due to it might already be there.
Solution:
Enable inheritance on the folder: System Center\Service Manager inside SSRS before running installation. This should remove BUILTIN\BUILTIN and will be readded by the installation.
See blog post:https://blog.jhnr.ch/2016/11/08/error-when-installing-service-manager-data-warehouse-management-server-the-user-or-group-name-builtinbuiltin-is-not-recognized/
Installation failes with error like “SQL Connection terminated by host”.
This can be due to TLS hardening on the management server, since the installation wizard cannot handle TLS 1.2.
Enable TLS 1.0 and 1.1 in the registry on the management server before starting the installation:
HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0
HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1
These two paths should contain a key called Server and another one called Client for each version.
And in each Server\Client key, two DWORDS:
DisabledByDefault=0
Enabled=1
There could also be an issue with the SQL it self, that it only accepts TLS 1.2.
Reinstallation (disaster recovery) of Data Warehouse management server failed on the stage _RunSMScripts with the following details in the log:
Calling custom action CAManaged!Microsoft.MOMv3.Setup.MOMv3ManagedCAs.RunSMScripts
RunSMSCripts: Error: Requested registry access is not allowed.
Solution:
In the registry, check the permissions on the folder: HKLM\SOFTWARE\Microsoft\System Center\2010\Common\MOMBins,
this is where the encryptionkey to the databases are stored. In my case the inheritance was turned off. After comparing to a working management server I reenabled inheritance in the ACL and restarted the installation.
When installing a brand new management server on a brand new machine, the installation fails on the step when adding new performance counters to windows with the following error: InstallServerPerfCountersForSDK.62894CB9_4320_40DB_B4E4_C0347FAB97B6
SCSMInstall.log also shows this:
MOMPerformanceCounterInstaller: adding perf dll C:\Program Files\Microsoft System Center\Service Manager\Microsoft.EnterpriseManagement.DataAccessService.Core.dll
MOMPerformanceCounterInstaller: Called for Installation of per counters
MOMPerformanceCounterInstaller: Error: The installation failed, and the rollback has been performed.
StackTrace: at System.Configuration.Install.TransactedInstaller.Install(IDictionary savedState)
at Microsoft.MOMv3.Setup.MOMv3ManagedCAs.MOMPerformanceCounterInstaller(Session session, Boolean bInstall)
CustomAction _InstallServerPerfCountersForSDK.62894CB9_4320_40DB_B4E4_C0347FAB97B6 returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Assembly Install: Failing with hr=80070005 at RemoveDirectoryAndChildren, line 393
MOMPerfCtrsInstall.log shows this:
An exception occurred during the Install phase.
System.InvalidOperationException: Invalid performance counter data with type ‘PERF_OBJECT_TYPE’.
Disable 4 perfomance counters in Windows by adding the followin registry keys, and inside each of them create a “Dword (32Bit) value” named “Disable Performance Counters” with a value of 1.
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Intercept CSM Filters\Performance]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Intercept Injector\Performance]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Intercept SyncAction Processing\Performance]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\InterceptCountersManager\Performance]
Source: https://learn.microsoft.com/en-us/answers/questions/2202869/how-to-resolve-service-manager-datawarehouse-insta
Source: https://techcommunity.microsoft.com/discussions/systemcenter/system-center-orchestrator-2022-web-console-issues/4021500
Issue 1: Runbooks not visible in the Web Console.
In this issue the left hand pane where the runbook structure should be populated is blank.
Solution 1: Ran this query on the Orchestrator DB
GRANT CONTROL ON ASYMMETRIC KEY::[ORCHESTRATOR_ASYM_KEY] TO [Microsoft.SystemCenter.Orchestrator.Admins]
GRANT CONTROL ON SYMMETRIC KEY::[ORCHESTRATOR_SYM_KEY] TO [Microsoft.SystemCenter.Orchestrator.Admins]
GRANT EXECUTE ON object::[Microsoft.SystemCenter.Orchestrator].[GetSecurityToken] TO [Microsoft.SystemCenter.Orchestrator.Operators]
GRANT SELECT ON object::[Microsoft.SystemCenter.Orchestrator.Internal].[Settings] TO [Microsoft.SystemCenter.Orchestrator.Operators]
GRANT SELECT ON object::[Microsoft.SystemCenter.Orchestrator.Internal].[AuthorizationCache] TO [Microsoft.SystemCenter.Orchestrator.Admins]
Issue 2: Unable to delete stale or orphaned runbook server instances
I decommissioned some older runbook servers but was unable to delete them from any of the orchestrator consoles.
Solution: Run these sql queries against the orchestartor database
DELETE FROM [Orchestrator].[dbo].[CLIENTCONNECTIONS]
WHERE [ClientMachine] = ‘SCORCHRB’
— Here SCORCHRB is my Runbook Server Name.
DELETE FROM [Orchestrator].[dbo].[ACTIONSERVERS]
WHERE [Computer] = ‘SCORCHRBServer’
— Here SCORCHRBServer is my Runbook Server Name.
DELETE FROM dbo.OBJECTS
where Name = ‘SCORCHRBServer’
— Here SCORCHRBServer is my Runbook Server Name.
Issue 3: Runbooks remain in the checked out state in the web console
I have run into an issue where no matter how many times i check in a runbook, the runbook in the web console remains checked out.
Solution 3: Run this sql query against the orchestrator database
use Orchestrator
GO Truncate table [Microsoft.SystemCenter.Orchestrator.Internal].AuthorizationCache
DECLARE @secToken INT
DECLARE tokenCursor CURSOR FOR
SELECT Id FROM [Microsoft.SystemCenter.Orchestrator.Internal].SecurityTokens
where ExpirationTime >= GETUTCDATE() OPEN tokenCursor
FETCH NEXT FROM tokenCursor
INTO @secToken
WHILE @@FETCH_STATUS = 0
BEGIN PRINT ‘Computing Authorization Cache for Security Token: ‘ + Convert(Nvarchar, @secToken) exec [Microsoft.SystemCenter.Orchestrator].ComputeAuthorizationCache @TokenId = @secToken FETCH NEXT FROM tokenCursor
INTO @secToken END CLOSE tokenCursor DEALLOCATE tokenCursor
$scsmMgmtServer = "scsmMGMTServerHere"
$emg = New-Object Microsoft.EnterpriseManagement.EnterpriseManagementGroup $scsmMgmtServer
#MONSTER WORKFLOW LIST
$wfSubs = $emg.Subscription.GetSubscriptionsByCriteria("Name LIKE '%'")
foreach ($wfSub in $wfSubs)
{
$wfSubFailedInstances = $emg.Subscription.GetFailedSubscriptionStatusById($wfSub.id) | ?{$_.status -eq "Failed"}
foreach ($subFailedInstance in $wfSubFailedInstances)
{
#Ignore
$emg.Subscription.IgnoreFailedSubscription($subFailedInstance)
}
}
Source: https://community.cireson.com/discussion/2581/workflows-arent-getting-created-run-and-scsm-console-administration-workflows-status-is-slow
If the portal is using a HTTPS binding, and you need to update that certificate, you also need to update the PlatformCache service since it sets the certificate in the binding in IIS.
If PlatformCache is not updated, it will automatically wipe the link to the certificate in the binding.
Microsoft has started to reject connections to ExchangeOnline webaccess unless you use at least TLS 1.2, during this week. This can cause your Exchange Connector to stop connecting to it’s mailbox, if you use M365.
To correct this, you need to add some registry keys to make .NET and Windows to use a higher TLS version as default.
More about this on these posts:
https://tdemeul.bunnybesties.org/2021/06/troubleshooting-scsm-exchange-connector.html
If you have many runbook instances that complete at the same time, you might end up with a lot of deadlock errors in the runbookservice log.
These deadlock can also make the runbook jobs fail with the error: Interrupted by user or runbook server
This can be caused by a missing index on the POLICY_REQUEST_ACTION_SERVERS table.
This is described in: https://docs.microsoft.com/en-us/troubleshoot/system-center/orchestrator/runbook-server-goes-offline
The KB above referes to Orchestrator 2012, but I’ve noticed that the index is missing in a brand new 2019 installation aswell.
Add the index with the following T-SQL:
CREATE NONCLUSTERED INDEX [IX_POLICY_REQUEST_ACTION_SERVERS_SeqNumber] ON [dbo].[POLICY_REQUEST_ACTION_SERVERS] ( [SeqNumber] ASC )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, SORT_IN_TEMPDB = OFF, DROP_EXISTING = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]
Now you should end up with a total of two indexes on the table.
I ran into this error when upgrading the Data Warehouse from 2016 to 2019, at the stage when the import of new Management Packs begins.
The installation fails with the error: An error occurred while executing a custom action:_MPProcessorDeferred Upgrade failed after making permanent changes to this management server. A disaster recovery procedure will be necessary to rebuild this machine before attempting upgrade again. Consult the User Guide to determine which action to take next.
and the rolls back the installation.
The problem:
After looking in the SCSMInstall.log file, the installation failed due to a mismatch of collations.
This was caused by 2 columns in a table the DWStagingAndConfig database somehow had changed collation, that differs from the rest of the database.
The solution:
