Skip to main content

SCOM Discovery wizard stuck

We faced an issue with Discovery wizard getting stuck on discovering Windows objects in SCOM 2016

Turned out that we were running out of space for OpsmgrDB

Make sure OpsmgrDB is set for autogrowth as it is not by default

Hope this helps

Labels:

Comments

Post a Comment

Popular posts from this blog

Citrix XenApp 6.5 Discovery fails Event 3989

Citrix XenApp 6.5 Service account password change caused console discovery to fail and we saw event ID 3989 in System Event logs "Citrix XenApp failed to connect to the Data Store. ODBC error while connecting to the database: 28000 -> [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed. The login is from an untrusted domain and cannot be used with Windows authentication." After changing the service account password needed to run the following command on the delivery controllers. DSMAINT CONFIG /user:abc\ABCSVCCitrix /pwd:nP@ssword /dsn:"C:\Program Files (x86)\Citrix\Independent Management Architecture\mf20.dsn" Restart IMA service You should now be able to run the discovery successfully Hope this helps
Post a Comment
Read more

Group Policy Object did not apply because it failed with error code '0x80070534 No mapping between account names and security IDs was done

One of our servers was losing the Local Admin settings as we control them using GPO (restricted Groups) We were receiving the following event on this particular server : Event ID 4098 Application Event Log The computer 'Administrators (built-in)' preference item in the 'Servers Local Admins {odjd9DBD-22AF-48EA-ADF5-F42ADE4182hst}' Group Policy Object did not apply because it failed with error code '0x80070534 No mapping between account names and security IDs was done.' This error was suppressed. To fix the issue we deleted all the folders from the following location and rebooted the server C:\ProgramData\Microsoft\Group Policy\History Hope this helps.
Post a Comment
Read more

StoreFront 2.0 Propagate Changes Event ID 0 and 1 .There was no endpoint listening at net.tcp

When we add server to the Citrix storefront 2.0 server gropup , it may happen that the Propagate changes give us an error You will see the following events on the Primary StoreFront 2.0 Server Event Id 0: Error in retrieving synchronization information. Citrix.DeliveryServices.PowerShell.Command.Runner.Exceptions.PowerShellExecutionException: An error occured running the command: 'Get-DSClusterConfigurationUpdateState' ---> System.Management.Automation.ActionPreferenceStopException: Command execution stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: There was no endpoint listening at net.tcp://storefront02/Citrix/ConfigurationReplication that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. Event Id 1: Citrix.DeliveryServices.PowerShell.Command.Runner.Exceptions.PowerShellExecutionException, Citrix.Delive...
2 comments
Read more