![]() If I changed my script to use the Get-EventLog cmdlet, it returned the message: What I learned was rather interesting if not frustrating. Initially I set out in PowerShell to get around this annoyance. When the events are properly populated this is what it would normally look like (message truncated for brevity): csv file that my script creates and as you can see the Type and Message columns are blank: ![]() This has been a thorn in my side for a while as the Get-WinEvent cmdlet I use in my PowerShell script wasn’t returning any messages for this event. You can install or repair the component on the local computer." Either the component that raises this event is not installed on your local computer or the installation is corrupted. "The description for Event ID from source Microsoft Dynamics AX cannot be found. You may have seen this in your own event logs before where varies: An issue that I’ve noticed on a few clients that I’ve performed Health Checks on were that some of the event messages for the Microsoft Dynamics AX provider were missing. I have a PowerShell script that captures the messages on all the servers we review and writes the events into a. There is a lot of useful information that can be harvested from these logs. Dynamics GP to Dynamics 365 Business CentralĪs part of the Dynamics AX Health Check service that we offer, we review the Microsoft Dynamics event log messages.Dynamics NAV to Dynamics 365 Business Central.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
June 2023
Categories |