Hello there,
I finally needed also to create an account in this forum as it is my last resort.
I have threads open in M$ Community and on reddit, both not very successful.
Here is my issue:
Problem 1: Device categories can't be managed since update to version 2503 + hotfix install in october. The old devices still show the device categories assignes but if we try to assign new ones or try to manage them at all we get an error message. Didn't seem like a big deal than, had a lot to do a lot of other stuff and put it aside.
In November we applied the 2nd hotfix and the available hotfix rollup, since than we have problem Number 2: All new installed devices have troubles with some (not all!) software. Szenario 1 would be, that the software is discovered (Log proves) but it does not show up in softwarecenter. Szenario 2 is, that software is available but does not install with 0x0 error code -> location unavailable. Other (old) devices in same collection, same location, same network have no issues.
Now the error codes:
When we click on manage device categories we get the following message:
Microsoft.ConfigurationManagement.ManagementProvider.SmsConnectionException
Stack Trace:
In Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryResultsObject.<GetEnumerator>d__75.MoveNext()
In Microsoft.ConfigurationManagement.AdminConsole.Common.Utilities.WmiDataObject.GetAll[T](ConnectionManagerBase connection)
In Microsoft.ConfigurationManagement.AdminConsole.Features.Common.Dialogs.DeviceTagging.DeviceCategory.GetAllCategories(ConnectionManagerBase connection)
In Microsoft.ConfigurationManagement.AdminConsole.Features.Common.Dialogs.DeviceTagging.DeviceCategoryControl.<>c__DisplayClass12_0.<ReloadCategoryList>b__6()
In System.Threading.Tasks.Task`1.InnerInvoke()
In System.Threading.Tasks.Task.Execute()
-------------------------------
System.Runtime.InteropServices.COMException
Stack Trace:
In
Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryResultsObject.<GetEnumerator>d__75.MoveNext()
In Microsoft.ConfigurationManagement.AdminConsole.Common.Utilities.WmiDataObject.GetAll[T](ConnectionManagerBase connection)
In Microsoft.ConfigurationManagement.AdminConsole.Features.Common.Dialogs.DeviceTagging.DeviceCategory.GetAllCategories(ConnectionManagerBase connection)
In Microsoft.ConfigurationManagement.AdminConsole.Features.Common.Dialogs.DeviceTagging.DeviceCategoryControl.<>c__DisplayClass12_0.<ReloadCategoryList>b__6()
In System.Threading.Tasks.Task`1.InnerInvoke()
In System.Threading.Tasks.Task.Execute()
In the SmsAdminUi.log the following output appears:
[106, PID:28308][12/01/2025 13:53:03] :System.Runtime.InteropServices.COMException
In System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
And the SmsProv.log shows an error too, I attached the picture.
If we open a fresh console we see a lot of missing management class descriptions in the SmsAdminUI.log, I also attached a picture of that log.
Sooooo.
We figured out that the console uses the xml under "\AdminConsole\XmlStorage\ConsoleRoot\ManagementClassDescriptions.xml" and in "AdminConsole\XmlStorage\Extensions\ManagementClasses" shall be the management classes we use. The folder for the management classes is empty -> We don't know if the folder was empty before the update or not or what files should be in there.
Probably this is our key problem but how to we get the files back in there or how do we create new ones?
What did we tried or checked already:
- rebuild WMI Repository
- re-register classes
- reset of the Site
- repair of console / new install
--> deleted the "Microsoft.ConfigurationManagement.ApplicationManagement.config" in "%Localappdata%\Microsoft\Configmgr10" to exclude the corruption of the console.
- reviewed the smsexec.log after fresh restart of CAS, nothing unusual as far as I can tell
- does not matter if console is open from another server or windows machine.
- Prerequisites where green execpt two warnings about MS Store and Network access account.
We have one CAS and 15 primary sites. Monitoring shows no related issues in system status or component status.
Compability level of SQL Server is on 140, we have SQL Server 2022
Any help is appreciated!
Best regards & thank you,
LinP
I finally needed also to create an account in this forum as it is my last resort.
I have threads open in M$ Community and on reddit, both not very successful.
Here is my issue:
Problem 1: Device categories can't be managed since update to version 2503 + hotfix install in october. The old devices still show the device categories assignes but if we try to assign new ones or try to manage them at all we get an error message. Didn't seem like a big deal than, had a lot to do a lot of other stuff and put it aside.
In November we applied the 2nd hotfix and the available hotfix rollup, since than we have problem Number 2: All new installed devices have troubles with some (not all!) software. Szenario 1 would be, that the software is discovered (Log proves) but it does not show up in softwarecenter. Szenario 2 is, that software is available but does not install with 0x0 error code -> location unavailable. Other (old) devices in same collection, same location, same network have no issues.
Now the error codes:
When we click on manage device categories we get the following message:
Microsoft.ConfigurationManagement.ManagementProvider.SmsConnectionException
Stack Trace:
In Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryResultsObject.<GetEnumerator>d__75.MoveNext()
In Microsoft.ConfigurationManagement.AdminConsole.Common.Utilities.WmiDataObject.GetAll[T](ConnectionManagerBase connection)
In Microsoft.ConfigurationManagement.AdminConsole.Features.Common.Dialogs.DeviceTagging.DeviceCategory.GetAllCategories(ConnectionManagerBase connection)
In Microsoft.ConfigurationManagement.AdminConsole.Features.Common.Dialogs.DeviceTagging.DeviceCategoryControl.<>c__DisplayClass12_0.<ReloadCategoryList>b__6()
In System.Threading.Tasks.Task`1.InnerInvoke()
In System.Threading.Tasks.Task.Execute()
-------------------------------
System.Runtime.InteropServices.COMException
Stack Trace:
In
Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryResultsObject.<GetEnumerator>d__75.MoveNext()
In Microsoft.ConfigurationManagement.AdminConsole.Common.Utilities.WmiDataObject.GetAll[T](ConnectionManagerBase connection)
In Microsoft.ConfigurationManagement.AdminConsole.Features.Common.Dialogs.DeviceTagging.DeviceCategory.GetAllCategories(ConnectionManagerBase connection)
In Microsoft.ConfigurationManagement.AdminConsole.Features.Common.Dialogs.DeviceTagging.DeviceCategoryControl.<>c__DisplayClass12_0.<ReloadCategoryList>b__6()
In System.Threading.Tasks.Task`1.InnerInvoke()
In System.Threading.Tasks.Task.Execute()
In the SmsAdminUi.log the following output appears:
[106, PID:28308][12/01/2025 13:53:03] :System.Runtime.InteropServices.COMException
In System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
And the SmsProv.log shows an error too, I attached the picture.
If we open a fresh console we see a lot of missing management class descriptions in the SmsAdminUI.log, I also attached a picture of that log.
Sooooo.
We figured out that the console uses the xml under "\AdminConsole\XmlStorage\ConsoleRoot\ManagementClassDescriptions.xml" and in "AdminConsole\XmlStorage\Extensions\ManagementClasses" shall be the management classes we use. The folder for the management classes is empty -> We don't know if the folder was empty before the update or not or what files should be in there.
Probably this is our key problem but how to we get the files back in there or how do we create new ones?
What did we tried or checked already:
- rebuild WMI Repository
- re-register classes
- reset of the Site
- repair of console / new install
--> deleted the "Microsoft.ConfigurationManagement.ApplicationManagement.config" in "%Localappdata%\Microsoft\Configmgr10" to exclude the corruption of the console.
- reviewed the smsexec.log after fresh restart of CAS, nothing unusual as far as I can tell
- does not matter if console is open from another server or windows machine.
- Prerequisites where green execpt two warnings about MS Store and Network access account.
We have one CAS and 15 primary sites. Monitoring shows no related issues in system status or component status.
Compability level of SQL Server is on 140, we have SQL Server 2022
Any help is appreciated!
Best regards & thank you,
LinP
