Skip to main content

Licensense error while opening a COBOL file.

  • June 28, 2024
  • 3 replies
  • 0 views

I have installed the Microfocus Visual Cobol 9 after downloading the product from the "">www.microfocus.com/.../overview". I have also installed a community edition of Visual Studio 2022 prior to the Visual Cobol install, and I can develop .net applications in it. However I am unable to create any of the "Visual COBOL" template projects. Creating these gives an error in Visual Studio. I cannot even open a COBOL file and when I try to do so, I can see the an error listed below the ribbon(Screen shot attached) in Visual Studio. The error reads as follows

"Visual Cobol for Visual Studio does not have a valid License".

When I try to install the License following the visual studio link in the error message, I get the error shown in the attached screenshot.

Please note that I have already installed the Visual Cobol License Manager and activated the product on the Microfocus Site.

How do I get past this installation error and start some coding in COBOL.


#VisualCOBOL
#COBOL
#Installation
#license
#VisualStudio

3 replies

Chris Glazier
Forum|alt.badge.img+2
  • Moderator
  • 3697 replies
  • June 28, 2024

I have installed the Microfocus Visual Cobol 9 after downloading the product from the "">www.microfocus.com/.../overview". I have also installed a community edition of Visual Studio 2022 prior to the Visual Cobol install, and I can develop .net applications in it. However I am unable to create any of the "Visual COBOL" template projects. Creating these gives an error in Visual Studio. I cannot even open a COBOL file and when I try to do so, I can see the an error listed below the ribbon(Screen shot attached) in Visual Studio. The error reads as follows

"Visual Cobol for Visual Studio does not have a valid License".

When I try to install the License following the visual studio link in the error message, I get the error shown in the attached screenshot.

Please note that I have already installed the Visual Cobol License Manager and activated the product on the Microfocus Site.

How do I get past this installation error and start some coding in COBOL.


#VisualCOBOL
#COBOL
#Installation
#license
#VisualStudio

Can you please email me the license file that you are using so that I can check its validity?

Send it to cglazier@rocketsoftware.com

Also could you clarify your statement

"Please note that I have already installed the Visual Cobol License Manager and activated the product on the Microfocus Site"

Thanks


  • Author
  • Rocketeer
  • 19312 replies
  • June 29, 2024

Can you please email me the license file that you are using so that I can check its validity?

Send it to cglazier@rocketsoftware.com

Also could you clarify your statement

"Please note that I have already installed the Visual Cobol License Manager and activated the product on the Microfocus Site"

Thanks

Already sent you an email and clarified the quote.


  • Author
  • Rocketeer
  • 19312 replies
  • July 4, 2024

I have installed the Microfocus Visual Cobol 9 after downloading the product from the "">www.microfocus.com/.../overview". I have also installed a community edition of Visual Studio 2022 prior to the Visual Cobol install, and I can develop .net applications in it. However I am unable to create any of the "Visual COBOL" template projects. Creating these gives an error in Visual Studio. I cannot even open a COBOL file and when I try to do so, I can see the an error listed below the ribbon(Screen shot attached) in Visual Studio. The error reads as follows

"Visual Cobol for Visual Studio does not have a valid License".

When I try to install the License following the visual studio link in the error message, I get the error shown in the attached screenshot.

Please note that I have already installed the Visual Cobol License Manager and activated the product on the Microfocus Site.

How do I get past this installation error and start some coding in COBOL.


#VisualCOBOL
#COBOL
#Installation
#license
#VisualStudio

Chris provided me with another license key and the authorization worked well. The issue is resoloved. Must be some issue with the default key generated.