{"id":382232,"date":"2024-09-10T20:30:48","date_gmt":"2024-09-10T20:30:48","guid":{"rendered":"https:\/\/innovationspace.ansys.com\/forum\/forums\/topic\/unexpected-issues-with-sccm-deployment-of-ansys-fluids-and-structures-2024-r1\/"},"modified":"2024-09-10T20:30:48","modified_gmt":"2024-09-10T20:30:48","slug":"unexpected-issues-with-sccm-deployment-of-ansys-fluids-and-structures-2024-r1","status":"publish","type":"topic","link":"https:\/\/innovationspace.ansys.com\/forum\/forums\/topic\/unexpected-issues-with-sccm-deployment-of-ansys-fluids-and-structures-2024-r1\/","title":{"rendered":"Unexpected issues with SCCM deployment of Ansys Fluids and Structures 2024 R1"},"content":{"rendered":"

<p>So, I’m in a AD and SCCM managed windows environment and Ansys Fluids and Structures 2024 R1 is one of the pieces of software we’re deploying to our physical labs on campus and we’ve been encountering a consistent problem with the SCCM mandatory deployment. At this point, because it’s been packaged once using single line cmd installer\/uninstaller and now again using powershell, I’m wondering if it’s something going wrong with the setup executable. In the AppEnforce.log file, when it evaluates the mandatory deployment and begins to install it, the package downloads to the cache fine, and the script starts without incident. Where things go awry is that setup.exe is returning code 0 (success) between 5-15 seconds after the process gets created: <\/p><p>\"\"<\/p><p>Note that process 5392 is the script starting at 4:52:44 and it returns code 0 after a mere 11 seconds. <\/p><p>In the application log of Event Viewer for that same machine,  the related entry gives Event ID 1000, task categroy 100, and the details read as follows: <\/p><p>Faulting application name: instcore.exe, version: 0.0.0.0, time stamp: 0x65492a1c<br>Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000<br>Exception code: 0xc0000005<br>Fault offset: 0xffffffff<br>Faulting process id: 0x2bf4<br>Faulting application start time: 0x01db02f5f4904a32<br>Faulting application path: C:\\WINDOWS\\TEMP\\ans_install_tmp12008\\instcore.exe<br>Faulting module path: unknown<br>Report Id: 77cd7a70-cee3-4b26-9c67-7617294a17c6<br>Faulting package full name: <br>Faulting package-relative application ID: <\/p><p>I’ve checked other machines and they all show the same thing. instcore.exe stops functioning and setup.exe returns code 0. However, initiaing a self-service install functions properly and this problem does not occur with the other 2024 R1 applications (Electronics and Granta EduPack). Does anyone have any insight on this? <\/p><\/p>\n","protected":false},"template":"","class_list":["post-382232","topic","type-topic","status-publish","hentry","topic-tag-install-error","topic-tag-InstallationSCCMsystem-1"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t