Highlighted
Absent Member.
Absent Member.
4831 views

Visual COBOL for MS Visual Studio 2017, what is step 3?

Jump to solution

I am new to MS Visual Studio 2017 and to Micro Focus and its COBOL.  I down loaded both but now what is step 3?  I do see I can choose C# and Visual Basic.  But COBOL does not come up as an option.

File/New/Project

and in the NEW PROJECT window on the left panel under Templates there is no COBOL

0 Likes
1 Solution

Accepted Solutions
Highlighted
Micro Focus Frequent Contributor
Micro Focus Frequent Contributor

RE: Visual COBOL for MS Visual Studio 2017, what is step 3?

Jump to solution
Yes, the first step is to ensure you have a working Visual Studio 2017 installation. A repair might be sufficient or you could uninstall/re-install it. It will be quite quick to do this since the components will already have been cached on your machine. Then re-install Visual COBOL. If you already have Visual COBOL installed, you may be able to get going by re-registering the Visual COBOL extension. There's a utility called MFVSIXInstall.exe installed in VC which you can just run to do this (it's documented in the Visual COBOL release notes)

View solution in original post

0 Likes
18 Replies
Highlighted
Respected Contributor.
Respected Contributor.

RE: Visual COBOL for MS Visual Studio 2017, what is step 3?

Jump to solution
You may need to install additional components in Visual Studio 2017. Go to Help -> Micro Focus Product Help and there may be an option to install additional components. I know I had to install like 4 additional items.
0 Likes
Highlighted
Absent Member.
Absent Member.

RE: Visual COBOL for MS Visual Studio 2017, what is step 3?

Jump to solution
I opened the Help in MS Visual Studio 2017 and there is not 'Micro Focus Product Help'. The is Send Feedback, Samples, Register Product, Technical Support, Online Privacy Statement, Manage Visual Studio Performance, About Microsoft Visual Studio.
0 Likes
Highlighted
Absent Member.
Absent Member.

RE: Visual COBOL for MS Visual Studio 2017, what is step 3?

Jump to solution
Just to be clear or maybe I need to be corrected I am assuming 'Visual COBOL' is the item made by Micro Focus and is used in MS Visual Studio.
I am looking at this page:
www.microfocus.com/.../
0 Likes
Highlighted
Absent Member.
Absent Member.

RE: Visual COBOL for MS Visual Studio 2017, what is step 3?

Jump to solution
I do have....
C:\Program Files (x86)\Micro Focus\Visual COBOL
which contains about 19 folders and two windows batch files.
0 Likes
Highlighted
Respected Contributor.
Respected Contributor.

RE: Visual COBOL for MS Visual Studio 2017, what is step 3?

Jump to solution
I would try rerunning the vcvs2017_30.exe file you should have downloaded following the link from Micro Focus Distribution. I know it took a few hours for the email to come to me after I filled in the information.
0 Likes
Highlighted
Absent Member.
Absent Member.

RE: Visual COBOL for MS Visual Studio 2017, what is step 3?

Jump to solution
I may not get an email because I get a message that 'Micro Focus Visual COBOL for Visual Studio 2017' Set up failed.
0x80070bb9 – The specified printer driver is currently in use.

And the last part of the log had
[1490:1138][2017-04-12T19:32:02]i000: WIXSTDBA: OnExecuteProgress() - package: MFVSIXINSTALL, progress: 50%, overall progress: 92%
[1490:1138][2017-04-12T19:32:02]i000: WIXSTDBA: OnExecuteProgress() - calculated progress: 64%, displayed progress: 94%
[1490:1138][2017-04-12T19:32:03]i000: WIXSTDBA: OnExecuteProgress() - package: MFVSIXINSTALL, progress: 50%, overall progress: 92%
[1490:1138][2017-04-12T19:32:03]i000: WIXSTDBA: OnExecuteProgress() - calculated progress: 64%, displayed progress: 94%
[1698:1704][2017-04-12T19:32:03]e000: Error 0x80070bb9: Process returned error: 0xbb9
[1698:1704][2017-04-12T19:32:03]e000: Error 0x80070bb9: Failed to execute EXE package.
[1490:1138][2017-04-12T19:32:03]e000: Error 0x80070bb9: Failed to configure per-machine EXE package.
[1490:1138][2017-04-12T19:32:03]i319: Applied execute package: MFVSIXINSTALL, result: 0x80070bb9, restart: None
[1490:1138][2017-04-12T19:32:03]e000: Error 0x80070bb9: Failed to execute EXE package.
[1490:1138][2017-04-12T19:32:03]i399: Apply complete, result: 0x80070bb9, restart: Required, ba requested restart: No
0 Likes
Highlighted
Respected Contributor.
Respected Contributor.

RE: Visual COBOL for MS Visual Studio 2017, what is step 3?

Jump to solution
Hopefully, some one from Micro Focus will chime in on this topic. I can't think of anything else. Good luck!
0 Likes
Highlighted
Micro Focus Frequent Contributor
Micro Focus Frequent Contributor

RE: Visual COBOL for MS Visual Studio 2017, what is step 3?

Jump to solution
Hi Rod/Mike, the exception "0x80070bb9 – The specified printer driver is currently in use" is misleading. That error code is actually a general exception thrown by the Visual Studio extension installer and indicates an error installing the COBOL extension to Visual Studio. There should be a file with a name beginning 'MFVSIX*' in your %TEMP% folder. Can you post the last lines of that file which should give the actual exception?

In answer to the more general question, the installation sequence should be to install Visual Studio 2017 (Community, Pro or Enterprise are all supported). You can install just the minimum or specific Visual Studio workloads at this point. It's important Visual Studio itself installs correctly so check the installer page for any errors or warnings.

Then you need to run the Visual COBOL installer. This will install the required Visual Studio features that are missing (if any). Once installed, COBOL templates should appear in the File -> New Project dialog. Additional optional features that are not already installed can be installed from the Help -> Micro Focus Product Help -> Install Missing Feature(s) menu.
0 Likes
Highlighted
Absent Member.
Absent Member.

RE: Visual COBOL for MS Visual Studio 2017, what is step 3?

Jump to solution
Here is the lines of code from that file:
4/12/2017 7:31:52 PM - Skipping Install of 'Microsoft.VisualCpp.CRT.arm.OneCore.Desktop,version=14.10.25017.0' since the package or a parent package had a vital failure.
4/12/2017 7:31:52 PM - Skipping cache of package 'Microsoft.VisualCpp.CRT.arm.OneCore.Desktop,version=14.10.25017.0' since the package or a parent package had a vital failure.
4/12/2017 7:31:52 PM - Skipping cache of package 'Microsoft.VisualStudio.PackageGroup.UWP.Common,version=15.0.26208.0' since the package or a parent package had a vital failure.
4/12/2017 7:31:52 PM - Skipping cache of package 'Microsoft.VisualStudio.Component.Windows10SDK.15063.UWP,version=15.0.26403.0' since the package or a parent package had a vital failure.
4/12/2017 7:31:52 PM - Skipping cache of package 'Microsoft.VisualStudio.ComponentGroup.UWP.Cordova,version=15.0.26403.0' since the package or a parent package had a vital failure.
4/12/2017 7:31:52 PM - Skipping cache of package 'Microsoft.VisualStudio.ComponentGroup.UWP.Xamarin,version=15.0.26403.0' since the package or a parent package had a vital failure.
4/12/2017 7:31:52 PM - Skipping cache of package 'Microsoft.VisualStudio.Component.UWP.Support,version=15.0.26403.0' since the package or a parent package had a vital failure.
4/12/2017 7:31:53 PM - Skipping cache of package 'Microsoft.VisualStudio.Workload.Universal,version=15.0.26403.0' since the package or a parent package had a vital failure.
4/12/2017 7:31:54 PM - Package 'Win10SDK_10.0.15063.Desktop,version=10.0.15063.8' failed to install. Command executed: "c:\windows\syswow64\\windowspowershell\v1.0\powershell.exe" -NonInteractive -NoLogo -NoProfile -ExecutionPolicy Bypass -InputFormat None "$ErrorActionPreference="""Stop"""; $VerbosePreference="""Continue"""; $ScriptPath="""C:\ProgramData\Microsoft\VisualStudio\Packages\Win10SDK_10.0.15063.Desktop,version=10.0.15063.8\WinSdkInstall.ps1"""; $SetupExe="""winsdksetup.exe"""; $SetupLogFolder="""windowssdk"""; $PackageId="""Win10SDK_10.0.15063.Desktop"""; $LogFile="""C:\Users\Rod\AppData\Local\Temp\dd_setup_20170412193127_003_Win10SDK_10.0.15063.Desktop.log"""; $SetupParameters="""/features OptionId.DesktopCPPx64 OptionId.DesktopCPPx86 OptionId.SigningTools OptionId.MSIInstallTools OptionId.UWPManaged OptionId.UWPCPP /quiet /norestart"""; Get-Content -Raw $ScriptPath | Invoke-Expression; if (!$?) { exit 1603 } elseif ($LastExitCode) { exit $LastExitCode }", Return code: 1, Details: Incorrect function., Signature: PackageId=Win10SDK_10.0.15063.Desktop;PackageAction=install;ReturnCode=1
4/12/2017 7:31:54 PM - Skipping cache of package 'Microsoft.VisualStudio.Component.Windows10SDK.15063.Desktop,version=15.0.26403.0' since the package or a parent package had a vital failure.
4/12/2017 7:32:03 PM - Microsoft.VisualStudio.Setup.PackageFailureException: Package 'Win10SDK_10.0.15063.UWP' failed to install;Package 'Win10SDK_10.0.15063.Desktop' failed to install
at Microsoft.VisualStudio.Setup.InstallOperation.Run(CancellationToken token)
at Microsoft.VisualStudio.Setup.Engine.RunOperation(InstallOperation installOperation, CancellationToken token, ExecuteAction action, ITelemetryOperation telemetryOperation)
at Microsoft.VisualStudio.Setup.Engine.RunCoreOperation(InstallOperation coreOperation, ExecuteAction action, ITelemetryOperation telemetryOperation, CancellationToken token)
at Microsoft.VisualStudio.Setup.Engine.Install(Product product, String destination, CancellationToken token)
at Microsoft.VisualStudio.ExtensionManager.ExtensionEngineImpl.PerformSetupEngineUnInstall(IInstalledExtension extension)
at Microsoft.VisualStudio.ExtensionManager.ExtensionEngineImpl.UninstallInternal(IInstalledExtension extension, Boolean forceDelete, Version targetedVSVersion)
at Microsoft.VisualStudio.ExtensionManager.ExtensionEngineImpl.Uninstall(IInstalledExtension extension, Version targetedVSVersion)
at VSIXInstaller.App.UninstallExtensionFromSKU(String vsixID, SupportedVSSKU sku)
at VSIXInstaller.App.UninstallSilently(String vsixId, IEnumerable`1 validSKUs)
at VSIXInstaller.App.OnStartup(StartupEventArgs e)
0 Likes
Highlighted
Micro Focus Frequent Contributor
Micro Focus Frequent Contributor

RE: Visual COBOL for MS Visual Studio 2017, what is step 3?

Jump to solution
This looks like an error installing Visual Studio itself. Errors with the Windows 10 SDK seem to be quite common with the current Visual Studio installer, especially if you are using an OS other than Windows 10. Visual COBOL itself does not require this so I assume you had selected a workload that included it (C++, UWP). Your Visual Studio installer app may be showing an error/warning if you start it up. The Visual Studio 2017 release notes (www.visualstudio.com/.../vs2017-relnotes contain a section relating to Windows 10 SDK issues. Their advice is to make sure you have the correct updates/patches (especially if Windows 7) and/or to install the Windows 10 SDK separately.
0 Likes
Highlighted
Absent Member.
Absent Member.

RE: Visual COBOL for MS Visual Studio 2017, what is step 3?

Jump to solution
And to add there was a failure in installing Visual Studio. This same failure happened on two different PCs. But then I could bring up VS just fine. Here is the error from the log Which I guess I need to go to MS for that issue.


Package 'Win10SDK_10.0.15063.Desktop,version=10.0.15063.8' failed to install.
Search URL: aka.ms/VSSetupErrorReports
Impacted workloads
Desktop development with C++ (Microsoft.VisualStudio.Workload.NativeDesktop,version=15.0.26403.0)
Impacted components
Windows 10 SDK (10.0.15063.0) for Desktop C++ x86 and x64 (Microsoft.VisualStudio.Component.Windows10SDK.15063.Desktop,version=15.0.26403.0)
Log
C:\Users\Rod\AppData\Local\Temp\dd_setup_20170412201311_328_Win10SDK_10.0.15063.Desktop.log
Details
Command executed: "c:\windows\syswow64\\windowspowershell\v1.0\powershell.exe" -NonInteractive -NoLogo -NoProfile -ExecutionPolicy Bypass -InputFormat None "$ErrorActionPreference="""Stop"""; $VerbosePreference="""Continue"""; $ScriptPath="""C:\ProgramData\Microsoft\VisualStudio\Packages\Win10SDK_10.0.15063.Desktop,version=10.0.15063.8\WinSdkInstall.ps1"""; $SetupExe="""winsdksetup.exe"""; $SetupLogFolder="""windowssdk"""; $PackageId="""Win10SDK_10.0.15063.Desktop"""; $LogFile="""C:\Users\Rod\AppData\Local\Temp\dd_setup_20170412201311_328_Win10SDK_10.0.15063.Desktop.log"""; $SetupParameters="""/features OptionId.DesktopCPPx64 OptionId.DesktopCPPx86 OptionId.SigningTools OptionId.MSIInstallTools OptionId.UWPManaged OptionId.UWPCPP /quiet /norestart"""; Get-Content -Raw $ScriptPath | Invoke-Expression; if (!$?) { exit 1603 } elseif ($LastExitCode) { exit $LastExitCode }"
Return code: 1
Return code details: Incorrect function.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.