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

Uninstall DuckDB ODBC throughout command line #36

Closed
dangerguest opened this issue Oct 15, 2024 · 1 comment · Fixed by #54
Closed

Uninstall DuckDB ODBC throughout command line #36

dangerguest opened this issue Oct 15, 2024 · 1 comment · Fixed by #54

Comments

@dangerguest
Copy link

How can we uninstall de DuckDB ODBC throughout command line.
I've tried already the odbc_install.exe /uninstall and it doesn't work.
Thanks in Adv

@dangerguest dangerguest changed the title Uninstall throughout command line Uninstall DuckDB ODBC throughout command line Oct 16, 2024
@staticlibs
Copy link
Contributor

odbc_install.exe requires Administrator privileges. But it also support running in a non-privileged shell, in this case it request permissions elevation (UAC screen is shown) and re-launches itself with the copy of input arguments.

The routine that copies the arguments is buggy, and wrong string was passed to the re-launched utility.

For installation - no arguments required (/Install argument is optional), so it was working correctly with both Admin and non-Admin launches.

For uninstallation, it is necessary to specify /Uninstall argument (with this exact capitalization and the forward slash). So uninstallation only works from the Admin shell.

Also note, that the driver uninstallation uses UsageCount value from registry, if the installation was run multiple times (for example, running odbc_install.exe without arguments accidentally) - then it is necessary to run odbc_install.exe /Uninstall multiple times too.

I've filed #54 to fix this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants