Karthik Rajendran (Partner) asked a question.

November 7, 2025 at 1:14 AM
Why VBSetLicenseInfo keeps hanging for hours for the below windows Native stack, any idea or solution?

ntdll!NtWaitForSingleObject+14  mswsock!SockWaitForSingleObject+1bd  mswsock!WSPRecv+3a0  ws2_32!WSARecv+174  dwsqls28!VBSetLicenseInfo+72933  dwsqls28!VBSetLicenseInfo+1651e  dwsqls28!GetXaSwitch+35a9  dwsqls28!GetXaSwitch+304e  dwsqls28!getFileVersionStringW+7e71  dwsqls28!getFileVersionStringW+1f9ed  dwsqls28!VBSetLicenseInfo+283f2  dwsqls28!VBSetLicenseInfo+27988  dwsqls28!VBSetLicenseInfo+269c8  dwsqls28!SQLExtendedFetch+88  odbc32!SQLExtendedFetch+29c  pmsqlsodbc!TSQLSODBCDb::useTimeStampFraction+9ce3  pmsqlsodbc!TSQLSODBCDb::useTimeStampFraction+996a  pmodlnt!TStatementImpl::Fetch+9a  pmodlnt!TStatement::nFetch+49  pmrelrdr!relReader::fetch+19a

  • 2 answers
  • 146 views

  • Libby Krause (Progress Software)

    @Karthik Rajendran (Partner)​ Seeing VBSetLicenseInfo in the stack just indicates that the stack was collected using a driver without symbols. Please open a support case to troubleshoot the issue.

    Selected as Best

  • Libby Krause (Progress Software)

    @Karthik Rajendran (Partner)​ Seeing VBSetLicenseInfo in the stack just indicates that the stack was collected using a driver without symbols. Please open a support case to troubleshoot the issue.

    Selected as Best

  • SANJAY kumar (SysInfoTools)

    The VBSetLicenseInfo() call can hang for hours because it interacts with Windows licensing, COM, and cryptographic services. This can happen if license keys are missing or corrupted, if registry permissions are insufficient, or if there are COM/crypto deadlocks. Network delays, domain checks, certificate revocation, or antivirus/security hooks can also cause the call to stall.