unexpected token - where is it?

GSS

I have an error when trying to perform a SQL Compare of two Azure SQL Server databases.  This is making it impossible to perform any compare of them.

unexpected token: ["Window",<1392>,line=23,col=49] [char=739]

The fact it's line 23 suggests something at the very start, but, using SQL Search I cannot find anything where this may be.

Is there anyway to see the text that the error refers to, so I might actually have an idea what line 23 is?   Thanks.

Peter_Laws

Hello GSS,

I'm sorry to read you've hit this issue. What db object type is Window please?
It's distinctly possible that the exception is occurring on corresponding attributes and we'd need to look at your code to isolate it.

We can do this in a support ticket if you're not comfortable sharing your schema in a public location, just let us know. 

GSS

Thanks for the reply, Peter.  I'm happy to discuss here.  The answer is I do not know what "Window" is, and there is no db object I know called this.   This is why I was hoping to see the rest of the text for context.  Do you know how/where I can do this?

There is a table column called "Window", but removing this table from the compare, and the database itself, makes no difference to the error.

Otherwise "windows" appears in the Azure SQL server name.  (As is the case with most Azure servers.)

This is an error that appears even after I narrow the comparison down to just one table, with the 'Ignore' option checked for everything.  It appears during the "comparing databases" part.

Peter_Laws

Having dug around I'm pretty sure this is an internal error, I've created a support ticket for you so I can ask for the application logs. If we find a fault I'll share the results here so others can benefit.

GSS

Thanks Peter.  The news is that this error has disappeared as mysteriously as it appeared.   I recently reinstalled Redgate (as part of updating to SSMS v20) so perhaps that fixed it.  Or maybe the version of Azure SQL Server changed to remove this unrecognised token.

Sorry I can't provide a more satisfactory resolution.

Peter_Laws

Not at all, such is life; should it reoccur, please come back to us and I'll resume digging!

GSS

Hi Peter
Sorry report that error is back.  It seems to be almost random.  Some days it does not occur, others it does.  And not related to any particular database.  The error itself is identical whenever it appears.  But once it does appear, nothing works for the remainder of the day.

Where can I upload my log?

Thanks.

GSS

I have raised a support request.