Invalid compiler output

Invalid compiler output

  
Olá,
Estou tentando publicar meu eSpace mas ocorre ERRO, porém outros eSpaces
estou conseguindo publicar normalmente, este erro ocorre apenas neste eSpace.
Tentei publicar em outras máquinas, mas o problema continua.
O que pode estar causando este erro de publicação? 

Desde já agradeço.

mensagem de erro:

Internal Error
 
Invalid compiler output.
Connection Timeout Expired.  The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement.  
 
This could be because the pre-login handshake failed or the server was unable to respond back in time.  The duration spent while attempting to connect to this server was - 
[Pre-Login] initialization=197; handshake=14802; 
 
Exception Details:
[1] Internal Error: Invalid compiler output.
Connection Timeout Expired.  The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement.  
 
This could be because the pre-login handshake failed or the server was unable to respond back in time.  The duration spent while attempting to connect to this server was - 
[Pre-Login] initialization=197; handshake=14802; 
at OutSystems.HubEdition.Compiler.Compiler.<>c__DisplayClass2.<Compile>b__1()
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()
[2] System.Data.SqlClient.SqlException (0x80131904): Connection Timeout Expired.  The timeout period elapsed while attempting to consume the pre-login handshake 
acknowledgement.  This could be because the pre-login handshake failed or the server was unable to respond back in time.  The duration spent while attempting to 
connect to this server was - [Pre-Login] initialization=197; handshake=14802;  ---> System.ComponentModel.Win32Exception (0x80004005): O tempo limite de espera foi atingido
   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error)
   at System.Data.SqlClient.TdsParserStateObject.ReadSniSyncOverAsync()
   at System.Data.SqlClient.TdsParserStateObject.TryReadNetworkPacket()
   at System.Data.SqlClient.TdsParser.ConsumePreLoginHandshake(Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, Boolean& marsCapable)
   at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, 
Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, Boolean withFailover)
   at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean ignoreSniOpenTimeout, 
TimeoutTimer timeout, Boolean withFailover)
   at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance,
 SqlConnectionString connectionOptions, SqlCredential credential, TimeoutTimer timeout)
   at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer timeout, SqlConnectionString connectionOptions, SqlCredential credential, String newPassword,
 SecureString newSecurePassword, Boolean redirectedUserInstance)
   at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, 
Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions, 
SessionData reconnectSessionData)
   at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, 
DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)
   at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnectionPool pool, DbConnection owningObject, DbConnectionOptions options, 
DbConnectionPoolKey poolKey, DbConnectionOptions userOptions)
   at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)
   at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)
   at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate,
 Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection)
   at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions,
 DbConnectionInternal& connection)
   at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, 
DbConnectionInternal oldConnection, DbConnectionInternal& connection)
   at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, 
TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
   at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)
   at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)
   at System.Data.SqlClient.SqlConnection.Open()
   at OutSystems.HubEdition.Extensibility.Data.TransactionService.BaseTransactionService.GetConnection()
   at OutSystems.HubEdition.Extensibility.Data.TransactionService.BaseTransactionService.CreateConnection(Int32 numRetries)
   at OutSystems.HubEdition.DatabaseProvider.SqlServer.DatabaseObjects.DatabaseObjectFactory.ParseQualifiedTableName(String qualifiedName, 
String& linkedServer, String& catalog, String& schema, String& table)
   at OutSystems.HubEdition.DatabaseProvider.SqlServer.DatabaseObjects.DatabaseObjectFactory.CreateTableSourceInfo(String qualifiedName)
   at OutSystems.HubEdition.Compiler.AbstractEntity.get_TableInfo()
   at OutSystems.HubEdition.Compiler.AbstractEntityAction.#C1c()
   at #03b.#gdb.#O1c.#L1c(TextWriter writer, String sqlVarName, String outputParameterName, RetrieveIdMethod& retrieveIdMethod)
   at #03b.#gdb.#O1c.#N1c(TextWriter writer, String transactionVarName)
   at #03b.#gdb.#Q1c.DumpBody(TextWriter writer, Boolean& outputIsRefParmHolder)
   at #03b.#FJc.DumpDecl(TextWriter writer)
   at OutSystems.HubEdition.Compiler.ESpace.DumpExtendedActions(TextWriter writer, IEnumerable`1 extendedActions, Boolean addExtendedActionsClass)
   at OutSystems.HubEdition.Compiler.ESpace.DumpEntitiesCSharp()
   at OutSystems.HubEdition.Compiler.ESpace.DumpEntities()
   at OutSystems.HubEdition.Compiler.ESpace.Dump()
   at OutSystems.HubEdition.Compiler.Compiler.InnerCompile(CompilationContext context)
   at OutSystems.HubEdition.Compiler.Compiler.Compile(CompilationContext context)
ClientConnectionId:3c951e2a-3d7a-4d81-a710-e4a8955fdf8e
[3] System.ComponentModel.Win32Exception (0x80004005): O tempo limite de espera foi atingido

Hi Agno,

The problem seems to be a timeout in the database while matching the eSpace entities with the existing database tables.

Are you using a personal environment? How many entities does the eSpace have?

Cheers,
Miguel
Ola Miguel, obrigado pela atenção.

Sobre suas perguntas, não estou usando a área pessoa, e tenho 101 entities neste eSpace.

obrigado novamente.
Ola novamente, 

Problema resolvido, o que estava causando o erro era uma falha de conexão com servidor externo que uso em uma extension, porém o erro mostrado pelo service center não deixava claro o motivo do problema.
Para resolver esre problema eu mudei a conexão do servidor da extension e ficou tudo OK, publicando
normalmente.

abraço.
Olá Agno,

Ainda bem que o problema ficou resolvido!

Cumprimentos,
Miguel
Hi everybody, 

Right now I am having a similar issue:

Message:
Invalid compiler output.
Sequence contains no matching element
Environment Information  
Stack:
Exception Details:
[1] Internal Error: Invalid compiler output.
Sequence contains no matching element
at OutSystems.HubEdition.Compiler.Compiler.<>c__DisplayClass2.<Compile>b__1()
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()
[2] System.InvalidOperationException: Sequence contains no matching element
   at System.Linq.Enumerable.Single[TSource](IEnumerable`1 source, Func`2 predicate)
   at #V3b.#K6b.#U6b.#8bb1.#9Yd(#jic groupByAttr)
   at #V3b.#K6b.#U6b.#O6b(Action`1 applyToGroupByAttribute, Action`1 applyToAggregateAttribute)
   at #V3b.#K6b.#U6b.WriteReadDBStatement(TextWriter writer, AnonymousStructure elementType)
   at OutSystems.HubEdition.Compiler.Nodes.DataSet.DumpReadDBMethod(TextWriter writer, QueryInstance instance)
   at OutSystems.HubEdition.Compiler.Nodes.AbstractQuery.InnerDump(TextWriter writer, QueryInstance instance)
   at OutSystems.HubEdition.Compiler.Nodes.AbstractQuery.Dump(TextWriter writer)
   at OutSystems.HubEdition.Compiler.Interfaces.ScreenFlowNodeUtils.#0ld(IScreenFlowNode screenFlowNode, TextWriter writer)
   at OutSystems.HubEdition.Compiler.Nodes.WebScreen.Dump(TextWriter writer)
   at OutSystems.HubEdition.Compiler.Nodes.AbstractContentNode.Dump()
   at OutSystems.HubEdition.Compiler.Flows.WebFlow.Dump()
   at OutSystems.HubEdition.Compiler.WebFlows.WebHandler.Dump(IEnumerable`1 webFlows)
   at OutSystems.HubEdition.Compiler.ESpace.Dump()
   at OutSystems.HubEdition.Compiler.Compiler.InnerCompile(CompilationContext context)
   at OutSystems.HubEdition.Compiler.Compiler.Compile(CompilationContext context)

This is happening after i renamed the "IsActive" attribute of several tables to homogenize tha name. The name was changed from "Enabled" to "IsActive". I have a module with all entities (Core) and a web module with the interfaces and logic which references the other one.

any idea?
Hi Johannes,

In your case it looks like there is an Aggregate that did not get the attribute correctly renamed.
If you could do a Submit Feedback in Service Studio including the oml with the problem we can look at the problem.

Just reply here after you send it.

Regards,
João Rosado
Joao, Thanks a lot for your answer. I have just sent the feedbak in Service Studio. Hope you can help me


João Rosado wrote:
Hi Johannes,

In your case it looks like there is an Aggregate that did not get the attribute correctly renamed.
If you could do a Submit Feedback in Service Studio including the oml with the problem we can look at the problem.

Just reply here after you send it.

Regards,
João Rosado
 
 
Joao. I did something that look really strange to me: i cut and paste all web elements I had in my application, tried to publish and worked fine. Do you have any explanation to this?
Hi Johannes,

Yes, that is a way to fix it.
When something in a eSpace is changed it updates all usages with the correct values. For some reason that did not happen with a usage in an aggregate.
Cut and Pasting causes all objects to be recreated and revalidated, fixing your problem.

Good to know that you got it fixed.

Regards,
João Rosado
Hi Joao. I have just read your answer. 

 I have to say that this "rare" behaviour can be so ofuscating that made me lost half day of work... :-P Now speaking more seriously, should i post an idea with this as an improvement? 
Hi Johannes,

If when any error occurs someone does a submit the problem using the Submit Feeback feature (or oppening a ticket in OutSystems Support depending on the severity and client support level), these feedbacks are added automatically to our maintnance backlog.

Then is a question of frequency and severity to determine when they are fixed.
That is why it is very important for everyone to ALWAYS submit the errors ...even if no message is written.


<rant mode>

I really feel sad about this because noone does it!!!
I've been here helping for years now and can probably still count with the fingers of my hands the number of topic replies of crashes/errors where I did not have to ask explicitly for a Submit Feedback.

</rant mode>


Regards,
João Rosado
Thanks Joao. I promise I will be more proactive sendind Feedback when any error ocurs in the platform.