This version of SQL Prompt in ADS has expired. Please download the latest version to continue using
johnnythebadger
Posts: 5 Bronze 1
I use SQL Prompt in Azure Data Studio.
It has been working fine, but today I have started getting this error message:
It has been working fine, but today I have started getting this error message:
Error formatting SQL: Error: Unhandled exception: System.Exception: This version of SQL Prompt in ADS has expired. Please download the latest version to continue using it.
at RedGate.SqlPrompt.Format.Engine.AzureDataStudio.TimeBomb.Check() in D :\BuildAgentA\work\dc5fefc0dc183d00\Engine\Format.Engine\AzureDataStudio\TimeBomb.cs:line 13
at RedGate.SqlPrompt.Format.Engine.AzureDataStudio.CommandLine.Commands.FormatSqlOptions.Run(String authToken, String adsStylesPath, String styleName, Boolean applyCasing) in D :\BuildAgentA\work\dc5fefc0dc183d00\Engine\Format.Engine\AzureDataStudio\CommandLine\Commands\FormatSqlCommand.cs:line 33
at System.CommandLine.Handler.<>c__DisplayClass5_0`4.<SetHandler>b__0(InvocationContext context)
at System.CommandLine.Invocation.AnonymousCommandHandler.Invoke(InvocationContext context)
at System.CommandLine.Invocation.InvocationPipeline.<>c__DisplayClass4_0.<<BuildInvocationChain>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass17_0.<<UseParseErrorReporting>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass12_0.<<UseHelp>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass22_0.<<UseVersionOption>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass19_0.<<UseTypoCorrections>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c.<<UseSuggestDirective>b__18_0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass16_0.<<UseParseDirective>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c.<<RegisterWithDotnetSuggest>b__5_0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass8_0.<<UseExceptionHandler>b__0>d.MoveNext()
Please ensure you highlighted a valid block of T-SQL.
I have downloaded and installed the latest version of the extension but the problem persists.
Is anyone else having the same problem? Can someone please suggest a fix?
I have downloaded and installed the latest version of the extension but the problem persists.
Is anyone else having the same problem? Can someone please suggest a fix?
Tagged:
Best Answer
-
Robyn Posts: 196 Gold 1The new update is now available. You should be able to update as normal through ADS but if you cannot here is a link to the VSIX to install it from
https://download.red-gate.com/EAP/SQLPromptADS/SQLPromptADS_0.2.15.0.zip
Thank you for your patience whilst we have been waiting on this release!
Answers
Hopefully this means it will be fixed soon :-)
Had to transfer from SSMS to Data Studio. Big disappointment when I realised thata sql prompt does not work properly in data studio. Please try to fix this.
Apologies for the radio silence on this one. We can see it have evidently had a wider impact in the community that support were initially exposed.
The development team are aware and have been working on a fix. Our understanding is this will be deployed in the next release of SQL Prompt, so watch out for this imminently.
Thanks for the update.
Could you also give us an estimation on when this release will be deployed?
Kind regards
The same problem here
@Robyn
Any solution?
Thanks for all
@Robyn is there any ETA for the solution as this is impacting our ability to work efficiently
Sorry that there has been no update - we simply haven't had the information to share!
We now know that a release will not happen before the end of the week. With the UK Bank Holiday on Monday the earliest we anticipate the release is Tuesday 27th. However, we have still not been given a firm ETA.
Should we get any further information, it will be shared here.
Looks good now
https://download.red-gate.com/checkforupdates/SQLPrompt/SQLPrompt_10.14.21.9884.exe