Thomas Michels Posted October 9, 2023 Share Posted October 9, 2023 Hello, opening Stortfront MMC fails on every startup with Application-Log Error ID1000 and ID1023 on both StoreFront Servers. Sever are Windows 2019 Standard with 2203 CU3 Controller and 3.23.3000.14 Storefront installed. ----------------------------------------------------------------------------------------------------------------------------- ID1000 Log Name: Application Source: Application Error Date: 09.10.2023 10:29:26 Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: Server1.xy.xy Description: Faulting application name: mmc.exe, version: 10.0.17763.1697, time stamp: 0x6e7d0aa5 Faulting module name: clr.dll, version: 4.8.4645.0, time stamp: 0x648f6f63 Exception code: 0xc0000005 Fault offset: 0x0000000000018551 Faulting process id: 0x3cb0 Faulting application start time: 0x01d9fa8ab55fc846 Faulting application path: C:\Windows\system32\mmc.exe Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll Report Id: d3bb2467-95c0-4d53-9980-097a48fb8d8d ---------------------------------------------------------------------------------------------------------------------------------------- ID1023 Log Name: Application Source: .NET Runtime Date: 09.10.2023 10:29:25 Event ID: 1023 Task Category: None Level: Error Keywords: Classic User: N/A Computer: Server1.xy.xy Description: Application: mmc.exe Framework Version: v4.0.30319 Description: The process was terminated due to an internal error in the .NET Runtime at IP 00007FF844B38551 (00007FF844B20000) with exit code 80131506. ---------------------------------------------------------------------------------------------------------------------------------------------- Thanks! Thomas Michels Link to comment Share on other sites More sharing options...
Thorsten Kruumlger Posted October 10, 2023 Share Posted October 10, 2023 Hello, we have exactly the same problem. Apparently after the latest Microsoft updates, on various storefront servers the console no longer starts. Fortunately, the services are working, but it is unclear how to fix the problem. Will a storefront update help or will it break the storefront group? I am sending the latest Microsoft updates as a screenshot. It affects the following versions in our case: - Storefront 2203 CU3 on Windows Server 2016 - Storefront 2308 on Windows Server 2022 Thanks, Thorsten Link to comment Share on other sites More sharing options...
Uwe Zimmer Posted October 10, 2023 Share Posted October 10, 2023 Hello, opening Stortfront MMC fails on every startup with Application-Log Error ID1000 and ID1023 on both StoreFront Servers. Sever are Windows 2019 Standard with 2203 CU3 Controller and 3.23.3000.14 Storefront installed. ----------------------------------------------------------------------------------------------------------------------------- ID1000 Log Name: Application Source: Application Error Date: 09.10.2023 10:29:26 Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: Server1.xy.xy Description: Faulting application name: mmc.exe, version: 10.0.17763.1697, time stamp: 0x6e7d0aa5 Faulting module name: clr.dll, version: 4.8.4645.0, time stamp: 0x648f6f63 Exception code: 0xc0000005 Fault offset: 0x0000000000018551 Faulting process id: 0x3cb0 Faulting application start time: 0x01d9fa8ab55fc846 Faulting application path: C:\Windows\system32\mmc.exe Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll Report Id: d3bb2467-95c0-4d53-9980-097a48fb8d8d ---------------------------------------------------------------------------------------------------------------------------------------- ID1023 Log Name: Application Source: .NET Runtime Date: 09.10.2023 10:29:25 Event ID: 1023 Task Category: None Level: Error Keywords: Classic User: N/A Computer: Server1.xy.xy Description: Application: mmc.exe Framework Version: v4.0.30319 Description: The process was terminated due to an internal error in the .NET Runtime at IP 00007FF844B38551 (00007FF844B20000) with exit code 80131506. ---------------------------------------------------------------------------------------------------------------------------------------------- Apparently after the latest Microsoft updates, on various storefront servers the console no longer starts. Fortunately, the services are working, but it is unclear how to fix the problem. Will a storefront update help or will it break the storefront group? Only Servers with .NET Framework 4.8 are affected (Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full) Storefront on a server with .NET Framework 4.7.02558 still works fine. in our case it affects the following versions : - Storefront 2203LTSR CU3 on Windows Server 2016 (.NET 4.8.03761) - Storefront 2308 on Windows Server 2022 (.NET 4.8.04161) Anybody any ideas/solutions/workasounds? THX Uwe. Thanks! Uwe Link to comment Share on other sites More sharing options...
CarlStalhood Posted October 10, 2023 Share Posted October 10, 2023 I'm not able to duplicate this. What security software do you have installed? Link to comment Share on other sites More sharing options...
Uwe Zimmer Posted October 10, 2023 Share Posted October 10, 2023 Trellix Endpoint Security is in use on all Servers the only difference is the .net version found another identical post: https://discussions.citrix.com/topic/419474-opening-storefront-mmc-fails/ Link to comment Share on other sites More sharing options...
Uwe Zimmer Posted October 10, 2023 Share Posted October 10, 2023 Hi Thomas, we have the same problem too, opened a Post under the Storefront Category https://discussions.citrix.com/topic/419480-opening-storefront-fails-mmc-crash-server-16-server-22-net-48/ Apparently after the latest Microsoft updates, on various storefront servers the console no longer starts. Fortunately, the services are working, but it is unclear how to fix the problem. Will a storefront update help or will it break the storefront group? Only Servers with .NET Framework 4.8 are affected (Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full) Storefront on a server with .NET Framework 4.7.02558 still works fine. in our case it affects the following versions : - Storefront 2203LTSR CU3 on Windows Server 2016 (.NET 4.8.03761) - Storefront 2308 on Windows Server 2022 (.NET 4.8.04161) best Uwe Link to comment Share on other sites More sharing options...
Thomas Michels Posted October 10, 2023 Author Share Posted October 10, 2023 We have the same Problem and also Trellix installed. Link to comment Share on other sites More sharing options...
Jonathan Adams1709163648 Posted October 10, 2023 Share Posted October 10, 2023 I've updated the.NET versions on a Windows 2022 server with StoreFront 2308 but I can't reproduce this. If you remove Trellix does the issue go away? Link to comment Share on other sites More sharing options...
Uwe Zimmer Posted October 11, 2023 Share Posted October 11, 2023 Hi Jonathan, which .NET version is running? Link to comment Share on other sites More sharing options...
Thomas Michels Posted October 11, 2023 Author Share Posted October 11, 2023 Excluding <C:\Windows\System32\mmc.exe> and <C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll> in Trellix, the problem was solved. Storefront MMC opens. Link to comment Share on other sites More sharing options...
Uwe Zimmer Posted October 11, 2023 Share Posted October 11, 2023 I removed Trellix with the trellix EndpointProductRemoval-tool and whoops, Storefront starts as usual. Now I've got to talk with our Security Advisor how to proceed from here...as there were no notifications/alarms/log entries within trellix. Link to comment Share on other sites More sharing options...
Uwe Zimmer Posted October 12, 2023 Share Posted October 12, 2023 Hi Thomas, I can confirm your solution. Excluding <C:\Windows\System32\mmc.exe> and <C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll> in Trellix, solved the problem. Storefront MMC opens again. what a relief. interestingly though Trellix itself never logged or documented anything of it's own doing during this whole process. Link to comment Share on other sites More sharing options...
Dirk Becker Posted November 22, 2023 Share Posted November 22, 2023 In my environment the solution was C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe update /force Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now