What is that error message about “Visual Basic Command Line Compiler has stopped working” about?


We have been notified of a mysterious error message that can display when sending or compiling reports on computers that are not Windows 10. This blog post explains what the error message is about and how to avoid it.

Symptoms

This applies to RDLC report layouts in Dynamics NAV 2016 on computers with Visual Studio 2015 installed and running all Windows versions that are supported by Dynamics NAV 2016, except Windows 10. You get an error when you perform one of the following tasks:

  • From the Dynamics NAV Windows or Web client, you print/send a report to PDF, Microsoft Word, or Microsoft Excel.
  • From the Dynamics NAV Development Environment or Windows client, you modify and compile an RDLC report layout.

Error:

Visual Basic Command Line Compiler has stopped working

The details section of the error displays a message similar to the following:

Problem signature:
Problem Event Name: APPCRASH
Application Name: vbc.exe
Application Version: 14.0.1055.0
Application Timestamp: 563c1d26
Fault Module Name: s\SYSTEM32\MSVCP120_CLR0400.dll!__crtGetFileInformationByHandle
Fault Module Version: 6.3.9600.18146
Fault Module Timestamp: 5650afd4
Exception Code: c0000139
Exception Offset: 0009d572
OS Version: 6.3.9600.2.0.0.16.7
Locale ID: 1039
Additional Information 1: 1abe
Additional Information 2: 1abee00edb3fc1158f9ad6f44f0f6be8
Additional Information 3: 1abe
Additional Information 4: 1abee00edb3fc1158f9ad6f44f0f6be8
---------------------------
Microsoft Dynamics NAV Development Environment
---------------------------
Error while validating RDL content:
...

Cause

The error occurs if Microsoft .NET Framework 4.6 was not installed on the computer before Visual Studio 2015 was installed. You can read more about this issue in Knowledge Base (KB) article 3118750. This typically pertains to the computer on which the Dynamics NAV Development Environment is installed.

Resolution

On the computer where Visual Studio is installed, complete the resolution that is described in the Resolution for scenario 1 section of KB article 3118750.

Comments (1)

  1. RAJA says:

    how to solve the visual basic has stopped working in windows 7 due to Problem Event Name: APPCRASH and Fault Module Name: MSBIND.DLL

Skip to main content