SmarterTrack version 14 - Error 500

Problem reported by Yannick Guerdat - 6/24/2018 at 9:00 AM

Resolved

Hi,

Damn I didn't see that the version 14 has been activated and I was planned to install the last version 13. My wrong I didn't read it well, but now my instance is KO :-(

I have error 500 on all the pages and the JS files as well are not working any more.

Has anyone the same issue before I spend my day over this problem ? Actually no JS file is loaded ! All are returning an error 500.

Thanks for your feedback

Artionet.Group - Digital Transformation, eGovernment Solutions

6 Replies

Reply to Thread

Yannick Guerdat Replied

6/24/2018 at 9:12 AM

Some of the errors I get in my logs :

https://MYDOMAIN.COM:443/signalr/reconnect


   at System.Web.Compilation.AssemblyBuilder.Compile()
   at System.Web.Compilation.BuildProvidersCompiler.PerformBuild()
   at System.Web.Compilation.ApplicationBuildProvider.GetGlobalAsaxBuildResult(Boolean isPrecompiledApp)
   at System.Web.Compilation.BuildManager.CompileGlobalAsax()
   at System.Web.Compilation.BuildManager.EnsureTopLevelFilesCompiled()
   at System.Web.Compilation.BuildManager.CallAppInitializeMethod()
   at System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters, PolicyLevel policyLevel, Exception appDomainCreationException)

Artionet.Group - Digital Transformation, eGovernment Solutions

Yannick Guerdat Replied

6/24/2018 at 9:57 PM

Other issue :

Execution Timeout Expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
The statement has been terminated.
System.Data.SqlClient.SqlException (0x80131904): Execution Timeout Expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
The statement has been terminated. ---> System.ComponentModel.Win32Exception (0x80004005): The wait operation timed out
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async, Int32 timeout, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at SmarterTrack.Data.SqlHelperInternal.ExecuteNonQuery(SqlConnection connection, CommandType commandType, String commandText, SqlParameter[] commandParameters)
   at SmarterTrack.Data.SqlHelper.ExecuteNonQuery(SqlConnection connection, CommandType commandType, String commandText, SqlParameter[] commandParameters)
   at SmarterTrack.Data.DataLayerShortcut.ExecuteNonQuery(IDbConnection& conn, String query, SqlParameter[] parameters)
   at SmarterTrack.Data.TicketEntity.PurgeFromDatabase(IDbConnection& connection, List`1 ticketIDs)
   at SmarterTrack.HelperClasses.Threads.AutoPurgeDeletedThread.#0zc()
   at SmarterTrack.HelperClasses.Threads.AutoPurgeDeletedThread.#Zzc()
   at SmarterTrack.HelperClasses.Threads.AutoPurgeDeletedThread.DoWork()
ClientConnectionId:6ec49f95-5d80-4da2-8e77-3d93d4e85e87
Error Number:-2,State:0,Class:11
ClientConnectionId before routing:8963359d-865a-48d5-a56d-5dbe58888424
Routing Destination:dbb508d97ac2.tr11.westeurope1-a.worker.database.windows.net,11050

Artionet.Group - Digital Transformation, eGovernment Solutions

Andrew Barker Replied

6/25/2018 at 7:47 AM

Employee Post

It's difficult to tell what the specific problem is just from the errors you are getting. The SignalR issue could have several underlying causes. The server timeout error generally occurs when the database server is busy performing other tasks, or if there is a network issue. Without more information, it is difficult to say what is going on, or how to resolve it. I would recommend that you submit a support ticket for assistance resolving your issue.

Andrew Barker Software Developer SmarterTools Inc. www.smartertools.com

Yannick Guerdat Replied

6/25/2018 at 8:04 AM

Hello Andrew, thanks for your message. I have already open a support ticket to your team. My staff was today in a blackout day :-(

Artionet.Group - Digital Transformation, eGovernment Solutions

Yannick Guerdat Replied

6/26/2018 at 8:23 AM

Problem fixed !

The issue is regarding the following meta-data in the web.config. Apparently Microsoft Azure already provide this value in the meta-data without to declare it in the web.config :

  175:       <customHeaders>
  176:         <add name="X-UA-Compatible" value="IE=edge" />
  177:       </customHeaders>

Artionet.Group - Digital Transformation, eGovernment Solutions

Employee Replied

6/26/2018 at 10:45 AM

Employee Post

Thanks for providing the resolution, Yannick!

Back to Community Threads

Please leave this box unchecked

6 Replies

Reply to Thread

Tags

Related Knowledge Base Articles