Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Any build ends with "internal error occurred" #1403

Open
TKapitan opened this issue Jan 18, 2025 · 2 comments
Open

[Bug]: Any build ends with "internal error occurred" #1403

TKapitan opened this issue Jan 18, 2025 · 2 comments
Labels
bug Something isn't working

Comments

@TKapitan
Copy link

AL-Go version

6.2

Describe the issue

I'm still testing the AL-Go, but now I'm getting internal error that I can't resolve. It's the first time I tried to actually run the build (except one try when I created the project) so it's possible I broke something in setup (even though I'm following the readme)...

I've sent the full log to your email @freddydk

  Compiling C:\actions-runner\_work\AppSourceApps\AppSourceApps\A00-AppName\AppName
  Copying DLLs from C:\Program Files\Microsoft Dynamics NAV\252\Service to assemblyProbingPath
  Removing dotnet Framework Assemblies
  Using Symbols Folder: C:\actions-runner\_work\AppSourceApps\AppSourceApps\A00-AppName\.packages
  Processing data from remote server bca00-appname12831792387 failed with the following error message: An internal error occurred. For more information, see the about_Remote_Troubleshooting Help topic.
  
  Exception Script Stack Trace:
  at Invoke-ScriptInBcContainer, C:\ProgramData\BcContainerHelper\6.0.30\BcContainerHelper\ContainerHandling\Invoke-ScriptInNavContainer.ps1: line 61
  at Compile-AppInBcContainer, C:\ProgramData\BcContainerHelper\6.0.30\BcContainerHelper\AppHandling\Compile-AppInNavContainer.ps1: line 280
  at <ScriptBlock>, C:\ProgramData\BcContainerHelper\6.0.30\BcContainerHelper\AppHandling\Run-AlPipeline.ps1: line 1139
  at <ScriptBlock>, C:\ProgramData\BcContainerHelper\6.0.30\BcContainerHelper\AppHandling\Run-AlPipeline.ps1: line 2184
  at <ScriptBlock>, C:\ProgramData\BcContainerHelper\6.0.30\BcContainerHelper\AppHandling\Run-AlPipeline.ps1: line 1692
  at <ScriptBlock>, C:\ProgramData\BcContainerHelper\6.0.30\BcContainerHelper\AppHandling\Run-AlPipeline.ps1: line 1687
  at <ScriptBlock>, C:\ProgramData\BcContainerHelper\6.0.30\BcContainerHelper\AppHandling\Run-AlPipeline.ps1: line 1259
  at Run-AlPipeline, C:\ProgramData\BcContainerHelper\6.0.30\BcContainerHelper\AppHandling\Run-AlPipeline.ps1: line 1244
  at <ScriptBlock>, C:\actions-runner\_work\_actions\microsoft\AL-Go-Actions\v6.2\RunPipeline\RunPipeline.ps1: line 395
  at <ScriptBlock>, C:\actions-runner\_work\_temp\37cdb31d-697f-4cae-8a04-f068a1d524ab.ps1: line 3
  at <ScriptBlock>, C:\actions-runner\_work\_actions\microsoft\AL-Go-Actions\v6.2\Invoke-AlGoAction.ps1: line 17
  at <ScriptBlock>, C:\actions-runner\_work\_temp\37cdb31d-697f-4cae-8a04-f068a1d524ab.ps1: line 2
  at <ScriptBlock>, <No file>: line 1
  
  PowerShell Call Stack:
  at Invoke-ScriptInBcContainer, C:\ProgramData\BcContainerHelper\6.0.30\BcContainerHelper\ContainerHandling\Invoke-ScriptInNavContainer.ps1: line 71
  at Compile-AppInBcContainer, C:\ProgramData\BcContainerHelper\6.0.30\BcContainerHelper\AppHandling\Compile-AppInNavContainer.ps1: line 280
  at <ScriptBlock>, C:\ProgramData\BcContainerHelper\6.0.30\BcContainerHelper\AppHandling\Run-AlPipeline.ps1: line 1139
  at <ScriptBlock>, C:\ProgramData\BcContainerHelper\6.0.30\BcContainerHelper\AppHandling\Run-AlPipeline.ps1: line 2184
  at <ScriptBlock>, C:\ProgramData\BcContainerHelper\6.0.30\BcContainerHelper\AppHandling\Run-AlPipeline.ps1: line 1692
  at <ScriptBlock>, C:\ProgramData\BcContainerHelper\6.0.30\BcContainerHelper\AppHandling\Run-AlPipeline.ps1: line 1687
  at <ScriptBlock>, C:\ProgramData\BcContainerHelper\6.0.30\BcContainerHelper\AppHandling\Run-AlPipeline.ps1: line 1259
  at Run-AlPipeline, C:\ProgramData\BcContainerHelper\6.0.30\BcContainerHelper\AppHandling\Run-AlPipeline.ps1: line 1244
  at <ScriptBlock>, C:\actions-runner\_work\_actions\microsoft\AL-Go-Actions\v6.2\RunPipeline\RunPipeline.ps1: line 395
  at <ScriptBlock>, C:\actions-runner\_work\_temp\37cdb31d-697f-4cae-8a04-f068a1d524ab.ps1: line 3
  at <ScriptBlock>, C:\actions-runner\_work\_actions\microsoft\AL-Go-Actions\v6.2\Invoke-AlGoAction.ps1: line 17
  at <ScriptBlock>, C:\actions-runner\_work\_temp\37cdb31d-697f-4cae-8a04-f068a1d524ab.ps1: line 2
  at <ScriptBlock>, <No file>: line 1
  Compile-AppInBcContainer Telemetry Correlation Id: b5ca9ef7-c3b4-4101-b445-3746ea286102

Expected behavior

No error or specific error with details except "internal error"

Steps to reproduce

Any pipeline with build - Test Current, Pull request build or CI/CD

Additional context (logs, screenshots, etc.)

No response

@TKapitan TKapitan added the bug Something isn't working label Jan 18, 2025
Copy link

We've found some similar issues:

If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue.

Note: You can give me feedback by 👍 or 👎 this comment.

@TKapitan
Copy link
Author

What I've tried so far

  • Update the VM to the latest version
  • Review the logs in VM
  • Do a few more changes in the configuration

Additional note: The VM is currently used for our Azure DevOps pipeline and the same app runs without any issue. That means there must caused by a way how Al-Go creates container etc.

I've sent you @freddydk the log from both Al-Go and our Azure DevOps pipeline (same VM, same extension).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant