After some database issues the night before, multiple servers (separate from the database servers) are getting the following error when just running the 'Get-ODBCDSN' function from a powershell console:
Get-OdbcDsn : Timeout when waiting for another concurrent operation to complete. At line:1 char:1 + Get-OdbcDsn + ~~~~~~~~~~~ + CategoryInfo : ResourceBusy: (MSFT_OdbcDsnTask:Root/Microsoft/...SFT_OdbcDsnTask) [Get-OdbcDsn], CimExc eption + FullyQualifiedErrorId : MI RESULT 27,Get-OdbcDsn
I have found nothing online about this error. I've tried tweaking the one switch that has any correlation '-ThrottleLimit' but using various values doesn't help.
I believe, that a reboot will resolve this error. However, this function is customer-impacting and needs to 'just work'. I use the module to get all current User DSNs then delete them. Then I rebuild with the New-ODBCDSN function. All of these functions are called in the login script. Some 20 to 50 users may login to a server at once during peak times. Both Get and New-ODBCDSN commands exhibit the same error.
In order to work around the issue in the meantime, I have stopped using the function and switched to setting up DSNs through the registry HKCU:\Software\ODBC.INI\ODBC\etc,etc.. This is not my preferred option.
I'm looking to understand the problem, identify resolutions, or find another workaround.