Error when linking new database
Here is the error I get when attempting to create a link to one of my databases.
Failed to update:
oEc.#8Jf: Errors occured whilst parsing file C:\Documents and Settings\cg012463\Local Settings\Application Data\Red Gate\SQL Source Control 0\WorkingBases\e97d34f8-6024-446f-b9b4-fe3a0f345847\Tables\dbo.tblAutomatedWorkSchedulerFileListingExpRRWINEWAT010e129d788c5a4a15b820ae0808880958.sql
'line 3:2: expecting "LPAREN", found ')''
---> #Eyg.#Lyg: Errors occured whilst parsing file C:\Documents and Settings\cg012463\Local Settings\Application Data\Red Gate\SQL Source Control 0\WorkingBases\e97d34f8-6024-446f-b9b4-fe3a0f345847\Tables\dbo.tblAutomatedWorkSchedulerFileListingExpRRWINEWAT010e129d788c5a4a15b820ae0808880958.sql
'line 3:2: expecting "LPAREN", found ')''
---> line 3:2: expecting "LPAREN", found ')'
--- End of inner exception stack trace ---
at #oEc.#7Jf.#t.#B3.#sKf()
at #oEc.#7Jf.#gKf(Action action)
--- End of inner exception stack trace ---
Server stack trace:
at RedGate.SQLSourceControl.Engine.Cancellables.CancellableOperation.#t.#izb.#j5f()
at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(RuntimeMethodHandle md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)
Exception rethrown at [0]:
at RedGate.SQLSourceControl.CommonUI.Forms.ErrorDialog.DoWithObviousExceptionsThrowAll(Action action)
at #JLc.#PLc.#CTc(ICancellableOperation`1 operation, Object token)
Declined this idea as this was a bug that has now been resolved.
-
Our internal reference number is SOC-859. I agree that this will happen in multii-user environments. We'll be looking into this issue soon and will post an update here as we make progress. Thank you!
-
Kevin Greiner commented
I agree that this is what happened. But it is inevitable that this will happen in a multi-user system like a database. Perhaps there is a way to detect this condition.