Forum
See question

Erro sincronização ECHO – Mobile V10   

75 views
0
0

Boa Tarde

No painel echo dá erro na sincronização que é o seguinte:

[1/876] – Failed to process customer 01.
System.Data.SqlClient.SqlException (0x80131904): ‘TRY_CONVERT’ is not a recognized built-in function name.
Incorrect syntax near the keyword ‘ORDER’.
at System.Data.SqlClient.SqlCommand.<>c.<ExecuteDbDataReaderAsync>b__180_0(Task`1 result)
at System.Threading.Tasks.ContinuationResultTaskFromResultTask`2.InnerInvoke()
at System.Threading.Tasks.Task.Execute()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Data.Entity.Core.Objects.ObjectContext.<ExecuteStoreQueryInternalAsync>d__73`1.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Data.Entity.Utilities.TaskExtensions.CultureAwaiter`1.GetResult()
at System.Data.Entity.Core.Objects.ObjectContext.<ExecuteInTransactionAsync>d__3d`1.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Data.Entity.SqlServer.DefaultSqlExecutionStrategy.<ExecuteAsyncImplementation>d__9`1.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Data.Entity.Utilities.TaskExtensions.CultureAwaiter`1.GetResult()
at System.Data.Entity.Core.Objects.ObjectContext.<ExecuteStoreQueryReliablyAsync>d__70`1.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Data.Entity.Utilities.TaskExtensions.CultureAwaiter`1.GetResult()
at System.Data.Entity.Internal.LazyAsyncEnumerator`1.<FirstMoveNextAsync>d__0.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Data.Entity.Infrastructure.IDbAsyncEnumerableExtensions.<ForEachAsync>d__5`1.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
at Primavera.Bot.Mobile.Customers.CustomersInfoHandler.GetAndUploadClientData(Enterprise enterprise, MobileClient client, SalesManager salesManager, CustomersManager customersManager, Clientes customer)
at Primavera.Bot.Mobile.Customers.CustomersInfoHandler.ProcessMessage(IMessage message)
ClientConnectionId:91a18080-5376-4307-bd85-d2a82e270d0e
Error Number:195,State:10,Class:15

 

 

Faça login para poder traduzir
Evolution
Marked as spam
Criado há 1 ano e 2 semanas hldersilva
hldersilva Responsiveness Member
1 answers
0
Private answer

Boa tarde,

Após analisarmos a situação, identificamos que o problema se deve a uma limitação conhecida da aplicação. Infelizmente, em alguns casos, quando há um grande volume de dados para serem sincronizados, a capacidade da resposta do serviço de sincronização é excedida, resultando no erro reportado.
Estamos cientes do impacto que essa limitação pode causar e já criamos uma User Story no nosso backlog para priorizar o desenvolvimento de uma solução que evite esse erro.
No momento, ainda não podemos fornecer uma data precisa para a entrega dessa correção.
Lamentamos sinceramente o transtorno causado por esse problema e agradecemos sua compreensão.
Cumprimentos

Faça login para poder traduzir
Marked as spam
Criado há 1 ano e 2 semanas marcoribeiro
marcoribeiro Loyal Contributor