Solving the Inability to Debug Elliott on a New Server

Release Date: 5/23/20
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

Developer Documentations

  1. Received Code 9999 with Web Services Call
  2. Received Return Status Code 3 When Using Elilogin Login Method
  3. Elliott Web Service Requirements
  4. Elliott eStore Checklist
  5. LN API
  6. FN API
  7. RN API
  8. IN and DF API Change (V9.0)
  9. FA API Changes (V9.0)
  10. VA API Changes (V9.0)
  11. CartService
  12. EliarachService
  13. ElicshtxService
  14. EliattrbService
  15. ElisyscdService
  16. EliNoteService
  17. El2rstimService
  18. EliOrderService
  19. ItemInquiry
  20. EliitmiqService
  21. EliShiptoService
  22. El2getfrService
  23. Steps Required to Test ReportWriter in V8.2
  24. Installation of ElliottService, NETcellent’s Web Services for Elliott
  25. ResellerFinder
  26. EliaptrxService
  27. VendorInquiry
  28. EliloginService
  29. ElislsmnService
  30. EliserhsService
  31. EliatpobService
  32. ElievprcService
  33. ElihdtrxService
  34. ElicuswlService
  35. QueryTurnaround
  36. InvoiceInquiry
  37. ElicustmService
  38. EligetcdService
  39. OrderInquiry
  40. EliordiqService
  41. EliecontService
  42. EliautdpService
  43. El2CrCrdService
  44. Log-Timer / ElliottTimer.Ini Support
  45. Alpha Document Number Support (V8.5/V9.0)
  46. ElliottService System.TypeInitializationException
  47. Feature - Printing API to Dynamically Set Number of Copies
  48. The Values and Meanings of Distribution Types - ARDISFIL, APDISFIL, IMDISFIL, BMDISFIL
  49. DD API Changes (V9.0)
  50. PA API (8.5)
  51. Validate License API
  52. AP API
  53. TP API: Temporary Path
  54. Data Structures for Report Desk Defaults and Enforcements
  55. COBOL to VB Interface Programs
  56. IN API: Option to Support Files and Folders Validation
  57. FF API: File Functions
  58. ID API
  59. LK: Links API
  60. FFLNearYou
  61. Report Desk Developing and Debugging
  62. Developing a New Elliott V8.6 Report Desk User Defined Report (UDR)
  63. CustomerInquiry
  64. Elliott API (JSON Web Service)
  65. Animating COBOL Code in Elliott V8.5
  66. Preliminary Programming Changes for Elliott 8.6
  67. CV API
  68. System Lock File Requirements
  69. How to Write Test Codes for C# ESS Projects
  70. Solving the Inability to Debug Elliott on a New Server
  71. Report Desk: Developing Custom Reports
  72. Report Desk Tables
  73. Report Desk Database Delivery Strategy

Feedback and Knowledge Base