Visible to Intel only — GUID: GUID-C34ED8AF-A913-4358-BD43-CA08027EC5C5
Legal Information
Getting Help and Support
Introducing the Intel® SDK for OpenCL™ Applications
What's New in This Release
Which Version of the Intel® SDK for OpenCL™ Applications Should I Use?
Intel® Code Builder for OpenCL™ API Plug-in for Microsoft Visual Studio*
Intel® Code Builder for OpenCL™ API Plug-in for Eclipse*
Debugging OpenCL™ Kernels on GPU
Intel® SDK for OpenCL™ Applications Standalone Version
OpenCL™ 2.1 Development Environment
Intel® FPGA Emulation Platform for OpenCL™ Getting Started Guide
Troubleshooting Intel® SDK for OpenCL™ Applications Issues
Configuring Microsoft Visual Studio* IDE
Converting an Existing Project into an OpenCL™ Project
OpenCL™ New Project Wizard
Building an OpenCL™ Project
Using OpenCL™ Build Properties
Selecting a Target OpenCL™ Device
Generating and Viewing Assembly Code
Generating and Viewing LLVM Code
Generating Intermediate Program Binaries with Intel® Code Builder for OpenCL™ API Plug-in
Configuring OpenCL™ Build Options
Visible to Intel only — GUID: GUID-C34ED8AF-A913-4358-BD43-CA08027EC5C5
RPC Server is Unavailable
Symptom: RPC server is unavailable
The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)
Solution: Add firewall exceptions
- Log in to your target machine.
- Verify that the WMI traffic is enabled, if not, add an exception, via the firewall UI, or command-line: Using firewall UI:
-
- Control Panel > Windows Firewall > Allow an app or feature through Windows Firewall
- Click on 'Change settings' if available
- In the Allowed apps and features: pane, select Windows Management Instrumentation (WMI) and apply it to your network setup (for example, select Domain if both the host and the target use the same domain) NOTE: for more information about Domain/Private/Public please consult your system administrator and/or MSDN documentation on this topic.
- Click OK.
Using command-line:
netsh advfirewall firewall set rule group="windows management instrumentation (wmi)" new enable=yes
- Launch the debugger again. If the RPC server is still unavailable, you may need to open the DCOM TCP port 135. To open the port, add an exception:
netsh advfirewall firewall add rule dir=in name="DCOM" program=%systemroot%\system32\svchost.exe service=rpcss action=allow protocol=TCP localport=135
For more information, see: Connecting to WMI Remotely Starting with Windows Vista (https://docs.microsoft.com/en-us/windows/desktop/WmiSdk/connecting-to-wmi-remotely-starting-with-vista)