Hello team,
While compiling i get the following error
2023-02-28 00:25:54,747 [75] ERROR IIS APPPOOL\test_site Build BuildInternal - An error occured while running dotnet cli
System.ComponentModel.Win32Exception (0x80004005): The system cannot find the file specified
at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
at Terrasoft.Core.Compilation.ProjectBuilder.BuildInternal(String projectFilePath, String tempPath, BuildCommandParameters parameters).
I have already tried the suggestion in this thread : https://community.creatio.com/questions/buildcompile-error
and still keep getting the same error
Sasori
Like
Sasori Oshigaki
Can you please share the complete error captured in log file?
Make sure the IIS AppPool user has full write access to CreatioWebroot\Terrasoft.WebApp\Configuration
Ryan
I also have this problem, how can i fix this? I checked the IIS configs, changed identity pools from ApplicationPoolIdentity to LocalSystem, and created it manually C:\Windows\System32\inetsrv\NuGet\Migrations
```
2025-12-10 11:07:12,039 [146] ERROR NT AUTHORITY\СИСТЕМА Build BuildInternal - An error occured while running dotnet cli
System.ComponentModel.Win32Exception (0x80004005): The specified file cannot be found
at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
at Terrasoft.Core.Compilation.ProjectBuilder.BuildInternal(String projectFilePath, String tempPath, BuildCommandParameters parameters)
```
Hello Baiel,
If you encounter this issue, it is usually related either to the .NET installation on the server or to insufficient file system permissions. Please make sure that the required .NET Framework / .NET Core (SDK) components are properly installed and available to the user account under which the application is running. In some cases, the components are installed correctly, but the environment variables (especially PATH) are not applied, which prevents the application from locating the dotnet executable. As a troubleshooting step, you can uninstall the .NET components, restart the server, and then reinstall them to ensure all variables are applied correctly.
Another common cause is insufficient permissions for the account running the application on the directory used for NuGet migrations. Please verify access to the folder
C:\Windows\System32\inetsrv\NuGet\Migrations
and ensure that the IIS_IUSRS group has Read and Modify permissions. If access to this directory is denied, the compilation process may fail during NuGet-related operations.