Solving the Inability to Debug Elliott on a New Server
Release Date: 5/23/20
To resolve this issue, use Windows Explorer to navigate to G:\NSI.SRC\NW86\ELBYTSTR and double click on ELBYTSTR.Sln. Make sure the solution launches Visual Studio 2015 – it might launch a different version by default. If that happens, right-click on ELBYTSTR.Sln and choose Open With and then Microsoft Visual Studio Version Selector. That will launch Visual studio 2015 and attempt to load the solution.
However, the solution will not load because there are missing C++ modules. If you get a dialog like this, that suggests that you install them, click Install and that will solve the problem.
Version: 8.5 and higher
After migrating the Micro Focus COBOL environment onto a new server, it may be that you can run EL850CC.Exe, but you cannot debug EL850CC.
The actual problem appears to be that a project built in C++ named ELBYTSTR.Exe cannot load due to some missing C++ runtime modules.
To resolve this issue, use Windows Explorer to navigate to G:\NSI.SRC\NW86\ELBYTSTR and double click on ELBYTSTR.Sln. Make sure the solution launches Visual Studio 2015 – it might launch a different version by default. If that happens, right-click on ELBYTSTR.Sln and choose Open With and then Microsoft Visual Studio Version Selector. That will launch Visual studio 2015 and attempt to load the solution.
However, the solution will not load because there are missing C++ modules. If you get a dialog like this, that suggests that you install them, click Install and that will solve the problem.
If that dialog does not display automatically, you may see something like this:
Notice in the Solution Explorer tab that ELBYTSTR is
marked (unavailable). Right-click
on ELBYTSTR (unavailable) and select Install missing feature(s). That will present the Install Missing
Features dialog shown above. All you
need to do is click Install and follow the prompts to solve the problem.
If you see a dialog like this during the install process:
…follow the suggestion to close the Visual Studio
application and then continue, following all instructions. This process takes several minutes.
After you follow the above procedure, you should be able to debug EL860CC.
JEG
Related Articles
Debug Libraries for Animating
Release Date: 12/7/2023 Versions: Elliott V8.5 and Up Rationale On occasion, the Netcellent developer will want to test a new version of a COBOL program without disturbing other users or developers sharing the same environment. With this update, the ...How to Migrate Elliott to a New Server
Release Date: 05/23/2024 Version: 7.x & Up Q - I am looking for steps to move Elliott 8.5/PSQL 11 on Windows Server 2012 VM to Elliott 8.5/PSQL 15 on Windows Server 2022 VM. A - In short, you can take the following steps: (1) To install PSQL on the ...How to Use DebugLogLevel Registry Value to Debug Report Desk Issues
Release Date: TBA Version 8.6 Since Report Desk is a brand new feature of Elliott V8.5, you may encounter a problem with it. If you do, a Netcellent support representative may ask you to turn on the debugging of Report Desk so a log file can be ...New Elliott PSQL Server Processor and RAM Suggestions
Q - We are going to upgrade to a new Windows Server 2012 R2 for PSQL 11 64-bit by the end of the year. Does PSQL take advantage of additional Intel processor cores and/or give some advice or algorithms on the amount of RAM that should be installed in ...Inconsistent Elliott Error on Terminal Server
Q - We occasionally run into an issue with our terminal server where Elliott crashes after entering the username/password. After clicking on the shortcut, it prompts for the username / password. After clicking OK, it crashes. We are confused because ...