Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error installing on an old version of Windows Server #235

Closed
mtreg opened this issue Sep 8, 2020 · 4 comments
Closed

Error installing on an old version of Windows Server #235

mtreg opened this issue Sep 8, 2020 · 4 comments

Comments

@mtreg
Copy link

mtreg commented Sep 8, 2020

Describe the bug
When trying to install from the Plugins repository in a desktop environment within Windows Server (2012 R2) I get the following error: "This Windows version (6.3.9600) does not support the required Bluetooth API. Consider updating to a more recent Windows (10.0.10586 or above)."

To Reproduce
Steps to reproduce the behavior:

  1. Within Windows Server 2012 R2, go to install the Data Plotly plugin via the plugin manager.
  2. See error

Screenshots
All text that appeared is in the bug description.

Desktop (please complete the following information):

  • OS: Windows Server 2012 R2
  • e.g. QGIS 3.10 and QGIS 3.12
  • Latest Data Plotly release (may apply to older releases as well)

Additional context
I realize it might be a very specific OS issue, but since the error was regarding a bluetooth API, which would seem irrelevant for this Plug-in, figured I'd file this bug report and see if it's something easily managed - if so, great! If not, no worries.

Thank you so much for your work! This plug-in is great!
Mike

@mtreg mtreg added the bug label Sep 8, 2020
@ghtmtt
Copy link
Owner

ghtmtt commented Sep 9, 2020

I think it is a duplicate of the closed issue GIS4WRF/gis4wrf#103. Can you test it?

@ghtmtt ghtmtt added the feedback label Sep 9, 2020
@mtreg
Copy link
Author

mtreg commented Sep 13, 2020

Thanks @ghtmtt! I'll see if I can test, but due to permissions and administration, might not be able to. But the solution to test would be renaming the dll as described here? Or is there something

@ghtmtt
Copy link
Owner

ghtmtt commented Sep 14, 2020

@mtreg I cannot test it since I don't have a Windows machine.

@ghtmtt
Copy link
Owner

ghtmtt commented Nov 10, 2020

please reopen if necessary

@ghtmtt ghtmtt closed this as completed Nov 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants