Release notes Indicium 2023.1.11

Related products: Indicium Service Tier
Release notes Indicium 2023.1.11

Hello everyone,

In this sprint, we have added support for downloading reports directly when using resource staging, and fixed some minor issues.

You can read more about Indicium's features in the Indicium user manual. We will keep you updated regularly about Indicium's progress.

 

About Indicium

Two types of the Thinkwise Indicium Application Tier are available:

Contents of this release

 

Indicium - New

Download reports directly when using resource staging

Indicium Indicium Basic

When using resource staging, you can now download a report. This means it will be returned directly on the call to /commit the resource. You can force this by adding
?direct_download=true to the URL.

Previously, Indicium would return a response with a location header containing the location to download the report.

 

Minor fixes and tasks

  • We have added support for exporting a table when running Indicium on Linux.
  • Some specific logs did not show up in AWS CloudWatch and Azure ApplicationInsights. This has been fixed.
  • The ‘Enable local accounts’ setting on the ‘Global settings’ screen in IAM, which can be used to turn off authentication via local accounts, was ignored by Indicium. This has been fixed.

Hello,

Anyone else has issue upgrading to this version?

There is nothing in the log file and for sure there is no new configuration introduced as per above. 

Our IAM version however is 2022.2 could that be the problem ? isn’t it backwards compatible ?


Hello mperrot,

Since you said that the log file is empty, it sounds like Indicium isn’t even starting, which points to an issue with deployment or system requirements.

I have a few questions to pinpoint the issue:

  1. Are you using Indicium Universal or Indicium Basic?
  2. What was your previous version of Indicium?
  3. Are you deploying on premises or in Azure/AWS?

Hello mperrot,

Since you said that the log file is empty, it sounds like Indicium isn’t even starting, which points to an issue with deployment or system requirements.

I have a few questions to pinpoint the issue:

  1. Are you using Indicium Universal or Indicium Basic?
  2. What was your previous version of Indicium?
  3. Are you deploying on premises or in Azure/AWS?

Hi @Vincent Doppenberg ,

When I say there is nothing in the logs I do not mean it is empty, I mean it just does not have any errors. Indicium seems to have started as normal.

2023-01-24T06:36:05.7059825+00:00  [wrn] No persistent storage location for dataprotection is configured. The Encrypt and Decrypt process actions are disabled.
See the Thinkwise documentation on how to configure dataprotection. (cecad728)
2023-01-24T06:36:07.2369599+00:00 [inf] Initiating startup license check (a070e428)
2023-01-24T06:36:07.2938466+00:00 [inf] Reading license from IAM. (d4563d62)
2023-01-24T06:36:07.3301829+00:00 [inf] License successfully read from IAM. (66b06fb5)
2023-01-24T06:36:07.4121117+00:00 [inf] Loading model for application his_office from meta source 490 (SQLSERVER_IAM - 2022.2) (d00a4927)
2023-01-24T06:36:07.4282680+00:00 [inf] Loading model for application master from meta source 490 (SQLSERVER_IAM - 2022.2) (237444fa)
2023-01-24T06:36:07.4298415+00:00 [inf] Loading model for application his_mobile_app from meta source 490 (SQLSERVER_IAM - 2022.2) (4efba725)
2023-01-24T06:36:17.9057528+00:00 [inf] Loaded model of application 652 (DEV_TEST - 1.10) (374b993b)
2023-01-24T06:36:18.0014856+00:00 [inf] Loaded model of application 657 (HIS - 1.04.38) (3c045c7e)
2023-01-24T06:36:18.0020399+00:00 [inf] Loaded model of application 658 (HIS - 1.04.38) (f770ece5)
2023-01-24T06:36:19.4880169+00:00 [inf] License refresh not required. Current license state: Valid. "License valid until 2023-04-20T08:11:35" (6a3d1cf0)
2023-01-24T06:36:19.4958240+00:00 [inf] License refresh scheduled for 2023-01-27 08:11:35. (09ff7cde)

 

Answering to your questions:

  1. We are deploying the Indicium Universal.
  2. The Indicium Previous version of Indicium 2023.1.10 (Currently reverted back to this version)
  3. The deployment is on Azure.

Thanks


Hello mperrot,

That log file and screenshot cannot be from the same Indicium at the same moment. The screenshot indicates that Indicium has not started and the log file indicates that it has. It’s possible that the log entries are older or newer than the screenshot and that Indicium had restarted before or after. Another option is that the screenshot and log files are from different instances of Indicium.

Since you’re deploying on Azure, the cause of your issue could be that the Indicium App Service was not stopped before the files were replaced. This could cause files that were in use to not be replaced. Can you retry deploying version 2023.1.11 with the following steps?

  • Stop the Indicium App Service in the Azure Portal.
  • Delete all existing Indicium files, excluding perhaps the appsettings.json file. In this specific case it’s okay to keep the old web.config as well, since we have not changed that file in this version.
  • Deploy the 2023.1.11 files
  • Start the Indicium App Service in the Azure Portal
  • Try navigating to Indicium in your browser
  • If you get the same error, take note of the current time
  • Check Indicium’s error log (I would expect the Logs folder to be absent)

Fresh
  1. I have cleaned the directory completely. to be empty.
  2. Redeployed a fresh Indicium 2023.1.11 using kudu as always
  3. Started the server which created the Logs Directory

     

  4. got a new Log file

 

Timestamp is UTC time.

Log Content:

 

The Error persists.

 

The Web.config, appsettings.json is not changed and it is using the default coming from Thinkwise .

Our configuration is part of the Azure App service configuration and not in appsettings.json.

Thank you

 


@mperrott @Vincent Doppenberg we have had this particular error while Indicium was actually running with a few earlier upgrades too. This issue was client-side and the solution back then was to clear the user’s browser cache for the specific Indicium URL (not the Universal GUI cache).

Does this work for you? You could also test with Incognito browser. If so, there is something buggy in the latest Indicium.


@mperrott, in this case the error will probably appear in your eventlog.xml. You can find startup errors like this by opening Azure Kudu (you can find this in the Azure Portal for your App Service under "Advanced Tools”).

There you press "Debug console” and in my case I used “PowerShell”. In the new screen you can see the folder "Logfiles” and there should be an eventlog.xml.

If by any change you added an OpenID client recently (I don't know if this is the case, but I've seen this startup error a few times due to this), you this topic might help you: 

If it contains another type of error, it would be interesting to see this log. A new topic on the community might be better suited for this in that case!

I hope the eventlog will give us some insight! 

The error @Arie V mentions, is already fixed in Indicium and happened due to some stale cookies. It might still be interesting to try out though.

 


@mperrott @Vincent Doppenberg we have had this particular error while Indicium was actually running with a few earlier upgrades too. This issue was client-side and the solution back then was to clear the user’s browser cache for the specific Indicium URL (not the Universal GUI cache).

Does this work for you? You could also test with Incognito browser. If so, there is something buggy in the latest Indicium.

Hi @Arie V ,

I have tried it but that does not seem to work.

@mperrott, in this case the error will probably appear in your eventlog.xml. You can find startup errors like this by opening Azure Kudu (you can find this in the Azure Portal for your App Service under "Advanced Tools”).

There you press "Debug console” and in my case I used “PowerShell”. In the new screen you can see the folder "Logfiles” and there should be an eventlog.xml.

If by any change you added an OpenID client recently (I don't know if this is the case, but I've seen this startup error a few times due to this), you this topic might help you: 

If it contains another type of error, it would be interesting to see this log. A new topic on the community might be better suited for this in that case!

I hope the eventlog will give us some insight! 

The error @Arie V mentions, is already fixed in Indicium and happened due to some stale cookies. It might still be interesting to try out though.

 

Hi @Dick van den Brink ,

Indeed we have OpenID configured some time now and was working, I was missing point 2 from the topic you mentioned for the WEBSITE_LOAD_CERTIFICATES : *.

I do not get the Cruptographic error anymore in the EventLog.

See the EventLog attached on timestamp: 2023-01-25T09:03

 

<Event>
<System>
<Provider Name=".NET Runtime"/>
<EventID>1026</EventID>
<Level>1</Level>
<Task>0</Task>
<Keywords>Keywords</Keywords>
<TimeCreated SystemTime="2023-01-25T09:03:41Z"/>
<EventRecordID>317847765</EventRecordID>
<Channel>Application</Channel>
<Computer>RD0003FFDBE9AE</Computer>
<Security/>
</System>
<EventData>
<Data>Application: w3wp.exe CoreCLR Version: 6.0.1122.52304 .NET Version: 6.0.11 Description: The process was terminated due to an unhandled exception. Exception Info: System.AggregateException: One or more errors occurred. (The daemon process has indicated that it has failed to start properly and has sent the following error: System.IO.FileNotFoundException: Could not load file or assembly 'System.Runtime, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. File name: 'System.Runtime, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' Server stack trace: at System.Reflection.RuntimeAssembly.GetExportedTypes(RuntimeAssembly assembly, ObjectHandleOnStack retTypes) at System.Reflection.RuntimeAssembly.GetExportedTypes() at Prockees.Runtime.PluginServer.LoadAndStart(Assembly assembly) at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs) at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg) Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at Prockees.Runtime.PluginServer.LoadAndStart(Assembly assembly) at Prockees.PluginDomain.Load() in P:\git\Prockees\src\Prockees\PluginDomain.cs:line 56 WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog]. ) (The daemon process has indicated that it has failed to start properly and has sent the following error: System.IO.FileNotFoundException: Could not load file or assembly 'System.Runtime, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. File name: 'System.Runtime, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' Server stack trace: at System.Reflection.RuntimeAssembly.GetExportedTypes(RuntimeAssembly assembly, ObjectHandleOnStack retTypes) at System.Reflection.RuntimeAssembly.GetExportedTypes() at Prockees.Runtime.PluginServer.LoadAndStart(Assembly assembly) at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs) at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg) Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at Prockees.Runtime.PluginServer.LoadAndStart(Assembly assembly) at Prockees.PluginDomain.Load() in P:\git\Prockees\src\Prockees\PluginDomain.cs:line 56 WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog]. ) ---> Prockees.Bootstrapper.DaemonStartException: The daemon process has indicated that it has failed to start properly and has sent the following error: System.IO.FileNotFoundException: Could not load file or assembly 'System.Runtime, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. File name: 'System.Runtime, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' Server stack trace: at System.Reflection.RuntimeAssembly.GetExportedTypes(RuntimeAssembly assembly, ObjectHandleOnStack retTypes) at System.Reflection.RuntimeAssembly.GetExportedTypes() at Prockees.Runtime.PluginServer.LoadAndStart(Assembly assembly) at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs) at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg) Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at Prockees.Runtime.PluginServer.LoadAndStart(Assembly assembly) at Prockees.PluginDomain.Load() in P:\git\Prockees\src\Prockees\PluginDomain.cs:line 56 WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog]. at Prockees.Bootstrapper.PluginBootstrapper.Start() at Prockees.Bootstrapper.BootstrapManager`1.<>c__DisplayClass9_0.<Start>b__0(Int32 i) at System.Threading.Tasks.Parallel.<>c__DisplayClass19_0`1.<ForWorker>b__1(RangeWorker& currentWorker, Int32 timeout, Boolean& replicationDelegateYieldedBeforeCompletion) --- End of stack trace from previous location --- at System.Threading.Tasks.Parallel.<>c__DisplayClass19_0`1.<ForWorker>b__1(RangeWorker& currentWorker, Int32 timeout, Boolean& replicationDelegateYieldedBeforeCompletion) at System.Threading.Tasks.TaskReplicator.Replica.Execute() --- End of inner exception stack trace --- at System.Threading.Tasks.TaskReplicator.Run[TState](ReplicatableUserAction`1 action, ParallelOptions options, Boolean stopOnFirstFailure) at System.Threading.Tasks.Parallel.ForWorker[TLocal](Int32 fromInclusive, Int32 toExclusive, ParallelOptions parallelOptions, Action`1 body, Action`2 bodyWithState, Func`4 bodyWithLocal, Func`1 localInit, Action`1 localFinally) --- End of stack trace from previous location --- at System.Threading.Tasks.Parallel.ThrowSingleCancellationExceptionOrOtherException(ICollection exceptions, CancellationToken cancelToken, Exception otherException) at System.Threading.Tasks.Parallel.ForWorker[TLocal](Int32 fromInclusive, Int32 toExclusive, ParallelOptions parallelOptions, Action`1 body, Action`2 bodyWithState, Func`4 bodyWithLocal, Func`1 localInit, Action`1 localFinally) at System.Threading.Tasks.Parallel.For(Int32 fromInclusive, Int32 toExclusive, Action`1 body) at Prockees.Bootstrapper.BootstrapManager`1.Start(Action`1 onStarted) at Prockees.Bootstrapper.BootstrapManager`1.Start() at Indicium.Reporting.DevExpress.DevExpressReportDependency.<>c__DisplayClass6_0.<.ctor>b__0() in C:\azp\agent\_work\1\s\src\Reporting\Indicium.Reporting.DevExpress\DevExpressReportDependency.cs:line 84 at System.Lazy`1.ViaFactory(LazyThreadSafetyMode mode) at System.Lazy`1.ExecutionAndPublication(LazyHelper executionAndPublication, Boolean useDefaultConstructor) at System.Lazy`1.CreateValue() at Indicium.Reporting.DevExpress.DevExpressReportDependency.Preload() in C:\azp\agent\_work\1\s\src\Reporting\Indicium.Reporting.DevExpress\DevExpressReportDependency.cs:line 95 at Indicium.BackgroundServices.ReportPluginPreloadService.addPreloadTaskForReportType(IDependencyContainer`2 dependencyContainer, ReportType reportType, List`1 preloadTasks) in C:\azp\agent\_work\1\s\src\Indicium\BackgroundServices\ReportPluginPreloadService.cs:line 47 at Indicium.BackgroundServices.ReportPluginPreloadService.ExecuteAsync(CancellationToken stoppingToken) in C:\azp\agent\_work\1\s\src\Indicium\BackgroundServices\ReportPluginPreloadService.cs:line 32 at Microsoft.Extensions.Hosting.BackgroundService.StartAsync(CancellationToken cancellationToken) at Microsoft.AspNetCore.Hosting.HostedServiceExecutor.<>c__DisplayClass3_0.<StartAsync>b__0(IHostedService service) at Microsoft.AspNetCore.Hosting.HostedServiceExecutor.ExecuteAsync(Func`2 callback, Boolean throwOnFirstFailure) at Microsoft.AspNetCore.Hosting.WebHost.StartAsync(CancellationToken cancellationToken) at Microsoft.AspNetCore.Hosting.WebHostExtensions.RunAsync(IWebHost host, CancellationToken token, String startupMessage) at Microsoft.AspNetCore.Hosting.WebHostExtensions.RunAsync(IWebHost host, CancellationToken token, String startupMessage) at Microsoft.AspNetCore.Hosting.WebHostExtensions.RunAsync(IWebHost host, CancellationToken token) at Microsoft.AspNetCore.Hosting.WebHostExtensions.Run(IWebHost host) at Indicium.Program.Main(String[] args) in C:\azp\agent\_work\1\s\src\Indicium\Program.cs:line 30 ---> (Inner Exception #1) Prockees.Bootstrapper.DaemonStartException: The daemon process has indicated that it has failed to start properly and has sent the following error: System.IO.FileNotFoundException: Could not load file or assembly 'System.Runtime, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. File name: 'System.Runtime, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' Server stack trace: at System.Reflection.RuntimeAssembly.GetExportedTypes(RuntimeAssembly assembly, ObjectHandleOnStack retTypes) at System.Reflection.RuntimeAssembly.GetExportedTypes() at Prockees.Runtime.PluginServer.LoadAndStart(Assembly assembly) at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs) at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg) Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at Prockees.Runtime.PluginServer.LoadAndStart(Assembly assembly) at Prockees.PluginDomain.Load() in P:\git\Prockees\src\Prockees\PluginDomain.cs:line 56 WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog]. at Prockees.Bootstrapper.PluginBootstrapper.Start() at Prockees.Bootstrapper.BootstrapManager`1.<>c__DisplayClass9_0.<Start>b__0(Int32 i) at System.Threading.Tasks.Parallel.<>c__DisplayClass19_0`1.<ForWorker>b__1(RangeWorker& currentWorker, Int32 timeout, Boolean& replicationDelegateYieldedBeforeCompletion) --- End of stack trace from previous location --- at System.Threading.Tasks.Parallel.<>c__DisplayClass19_0`1.<ForWorker>b__1(RangeWorker& currentWorker, Int32 timeout, Boolean& replicationDelegateYieldedBeforeCompletion) at System.Threading.Tasks.TaskReplicator.Replica.Execute()<--- </Data>
</EventData>
</Event>
<Event>
<System>
<Provider Name="IIS AspNetCore Module V2"/>
<EventID>1018</EventID>
<Level>1</Level>
<Task>0</Task>
<Keywords>Keywords</Keywords>
<TimeCreated SystemTime="2023-01-25T09:03:42Z"/>
<EventRecordID>317848390</EventRecordID>
<Channel>Application</Channel>
<Computer>RD0003FFDBE9AE</Computer>
<Security/>
</System>
<EventData>
<Data>Application '/LM/W3SVC/129889330/ROOT/indicium' with physical root 'D:\home\site\indicium\' hit unexpected managed exception, exception code = '0xe0434352'. First 30KB characters of captured stdout and stderr logs: warn: General[0] No persistent storage location for dataprotection is configured. The Encrypt and Decrypt process actions are disabled. See the Thinkwise documentation on how to configure dataprotection. info: Licensing[0] Initiating startup license check info: Licensing[0] Reading license from IAM. info: Licensing[0] License successfully read from IAM. info: Licensing[0] License refresh not required. Current license state: Valid. License valid until 2023-04-19T08:25:08 info: Licensing[0] License refresh scheduled for 2023-01-26 08:25:08. Unhandled exception. System.AggregateException: One or more errors occurred. (The daemon process has indicated that it has failed to start properly and has sent the following error: System.IO.FileNotFoundException: Could not load file or assembly 'System.Runtime, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. File name: 'System.Runtime, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' Server stack trace: at System.Reflection.RuntimeAssembly.GetExportedTypes(RuntimeAssembly assembly, ObjectHandleOnStack retTypes) at System.Reflection.RuntimeAssembly.GetExportedTypes() at Prockees.Runtime.PluginServer.LoadAndStart(Assembly assembly) at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs) at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg) Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at Prockees.Runtime.PluginServer.LoadAndStart(Assembly assembly) at Prockees.PluginDomain.Load() in P:\git\Prockees\src\Prockees\PluginDomain.cs:line 56 WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog]. ) (The daemon process has indicated that it has failed to start properly and has sent the following error: System.IO.FileNotFoundException: Could not load file or assembly 'System.Runtime, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. File name: 'System.Runtime, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' Server stack trace: at System.Reflection.RuntimeAssembly.GetExportedTypes(RuntimeAssembly assembly, ObjectHandleOnStack retTypes) at System.Reflection.RuntimeAssembly.GetExportedTypes() at Prockees.Runtime.PluginServer.LoadAndStart(Assembly assembly) at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs) at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg) Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at Prockees.Runtime.PluginServer.LoadAndStart(Assembly assembly) at Prockees.PluginDomain.Load() in P:\git\Prockees\src\Prockees\PluginDomain.cs:line 56 WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog]. ) ---> Prockees.Bootstrapper.DaemonStartException: The daemon process has indicated that it has failed to start properly and has sent the following error: System.IO.FileNotFoundException: Could not load file or assembly 'System.Runtime, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. File name: 'System.Runtime, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' Server stack trace: at System.Reflection.RuntimeAssembly.GetExportedTypes(RuntimeAssembly assembly, ObjectHandleOnStack retTypes) at System.Reflection.RuntimeAssembly.GetExportedTypes() at Prockees.Runtime.PluginServer.LoadAndStart(Assembly assembly) at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs) at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg) Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at Prockees.Runtime.PluginServer.LoadAndStart(Assembly assembly) at Prockees.PluginDomain.Load() in P:\git\Prockees\src\Prockees\PluginDomain.cs:line 56 WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog]. at Prockees.Bootstrapper.PluginBootstrapper.Start() at Prockees.Bootstrapper.BootstrapManager`1.<>c__DisplayClass9_0.<Start>b__0(Int32 i) at System.Threading.Tasks.Parallel.<>c__DisplayClass19_0`1.<ForWorker>b__1(RangeWorker& currentWorker, Int32 timeout, Boolean& replicationDelegateYieldedBeforeCompletion) --- End of stack trace from previous location --- at System.Threading.Tasks.Parallel.<>c__DisplayClass19_0`1.<ForWorker>b__1(RangeWorker& currentWorker, Int32 timeout, Boolean& replicationDelegateYieldedBeforeCompletion) at System.Threading.Tasks.TaskReplicator.Replica.Execute() --- End of inner exception stack trace --- at System.Threading.Tasks.TaskReplicator.Run[TState](ReplicatableUserAction`1 action, ParallelOptions options, Boolean stopOnFirstFailure) at System.Threading.Tasks.Parallel.ForWorker[TLocal](Int32 fromInclusive, Int32 toExclusive, ParallelOptions parallelOptions, Action`1 body, Action`2 bodyWithState, Func`4 bodyWithLocal, Func`1 localInit, Action`1 localFinally) --- End of stack trace from previous location --- at System.Threading.Tasks.Parallel.ThrowSingleCancellationExceptionOrOtherException(ICollection exceptions, CancellationToken cancelToken, Exception otherException) at System.Threading.Tasks.Parallel.ForWorker[TLocal](Int32 fromInclusive, Int32 toExclusive, ParallelOptions parallelOptions, Action`1 body, Action`2 bodyWithState, Func`4 bodyWithLocal, Func`1 localInit, Action`1 localFinally) at System.Threading.Tasks.Parallel.For(Int32 fromInclusive, Int32 toExclusive, Action`1 body) at Prockees.Bootstrapper.BootstrapManager`1.Start(Action`1 onStarted) at Prockees.Bootstrapper.BootstrapManager`1.Start() at Indicium.Reporting.DevExpress.DevExpressReportDependency.<>c__DisplayClass6_0.<.ctor>b__0() in C:\azp\agent\_work\1\s\src\Reporting\Indicium.Reporting.DevExpress\DevExpressReportDependency.cs:line 84 at System.Lazy`1.ViaFactory(LazyThreadSafetyMode mode) at System.Lazy`1.ExecutionAndPublication(LazyHelper executionAndPublication, Boolean useDefaultConstructor) at System.Lazy`1.CreateValue() at Indicium.Reporting.DevExpress.DevExpressReportDependency.Preload() in C:\azp\agent\_work\1\s\src\Reporting\Indicium.Reporting.DevExpress\DevExpressReportDependency.cs:line 95 at Indicium.BackgroundServices.ReportPluginPreloadService.addPreloadTaskForReportType(IDependencyContainer`2 dependencyContainer, ReportType reportType, List`1 preloadTasks) in C:\azp\agent\_work\1\s\src\Indicium\BackgroundServices\ReportPluginPreloadService.cs:line 47 at Indicium.BackgroundServices.ReportPluginPreloadService.ExecuteAsync(CancellationToken stoppingToken) in C:\azp\agent\_work\1\s\src\Indicium\BackgroundServices\ReportPluginPreloadService.cs:line 32 at Microsoft.Extensions.Hosting.BackgroundService.StartAsync(CancellationToken cancellationToken) at Microsoft.AspNetCore.Hosting.HostedServiceExecutor.<>c__DisplayClass3_0.<StartAsync>b__0(IHostedService service) at Microsoft.AspNetCore.Hosting.HostedServiceExecutor.ExecuteAsync(Func`2 callback, Boolean throwOnFirstFailure) at Microsoft.AspNetCore.Hosting.WebHost.StartAsync(CancellationToken cancellationToken) at Microsoft.AspNetCore.Hosting.WebHostExtensions.RunAsync(IWebHost host, CancellationToken token, String startupMessage) at Microsoft.AspNetCore.Hosting.WebHostExtensions.RunAsync(IWebHost host, CancellationToken token, String startupMessage) at Microsoft.AspNetCore.Hosting.WebHostExtensions.RunAsync(IWebHost host, CancellationToken token) at Microsoft.AspNetCore.Hosting.WebHostExtensions.Run(IWebHost host) at Indicium.Program.Main(String[] args) in C:\azp\agent\_work\1\s\src\Indicium\Program.cs:line 30 ---> (Inner Exception #1) Prockees.Bootstrapper.DaemonStartException: The daemon process has indicated that it has failed to start properly and has sent the following error: System.IO.FileNotFoundException: Could not load file or assembly 'System.Runtime, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. File name: 'System.Runtime, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' Server stack trace: at System.Reflection.RuntimeAssembly.GetExportedTypes(RuntimeAssembly assembly, ObjectHandleOnStack retTypes) at System.Reflection.RuntimeAssembly.GetExportedTypes() at Prockees.Runtime.PluginServer.LoadAndStart(Assembly assembly) at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs) at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg) Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at Prockees.Runtime.PluginServer.LoadAndStart(Assembly assembly) at Prockees.PluginDomain.Load() in P:\git\Prockees\src\Prockees\PluginDomain.cs:line 56 WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog]. at Prockees.Bootstrapper.PluginBootstrapper.Start() at Prockees.Bootstrapper.BootstrapManager`1.<>c__DisplayClass9_0.<Start>b__0(Int32 i) at System.Threading.Tasks.Parallel.<>c__DisplayClass19_0`1.<ForWorker>b__1(RangeWorker& currentWorker, Int32 timeout, Boolean& replicationDelegateYieldedBeforeCompletion) --- End of stack trace from previous location --- at System.Threading.Tasks.Parallel.<>c__DisplayClass19_0`1.<ForWorker>b__1(RangeWorker& currentWorker, Int32 timeout, Boolean& replicationDelegateYieldedBeforeCompletion) at System.Threading.Tasks.TaskReplicator.Replica.Execute()<--- </Data>
<Data>Process Id: 5156.</Data>
<Data>File Version: 16.0.22296.11. Description: IIS ASP.NET Core Module V2 Request Handler. Commit: 617d594f2bf75a8904d3d0e7d68a0bacf8e6763a</Data>
</EventData>
</Event>
<Event>
<System>
<Provider Name="IIS AspNetCore Module V2"/>
<EventID>1007</EventID>
<Level>1</Level>
<Task>0</Task>
<Keywords>Keywords</Keywords>
<TimeCreated SystemTime="2023-01-25T09:03:42Z"/>
<EventRecordID>317848625</EventRecordID>
<Channel>Application</Channel>
<Computer>RD0003FFDBE9AE</Computer>
<Security/>
</System>
<EventData>
<Data>Application '/LM/W3SVC/129889330/ROOT/indicium' with physical root 'D:\home\site\indicium\' failed to load coreclr. Exception message: CLR worker thread exited prematurely</Data>
<Data>Process Id: 5156.</Data>
<Data>File Version: 16.0.22296.11. Description: IIS ASP.NET Core Module V2 Request Handler. Commit: 617d594f2bf75a8904d3d0e7d68a0bacf8e6763a</Data>
</EventData>
</Event>

 


@Vincent Doppenberg @Dick van den Brink We have another issue with the latest Indicium 2023.1.11 regarding DevExpress reports: the Process Action ‘Generate report’ throws this error (which I also see in above log from @mperrott). The Process Action does still work in Indicium 2023.1.10.

Could this be related?

[err] Process action "generate_report_generate_freight_invoice" in processflow "save_s3_file_as_link" in application 7145 threw an exception. (571360e4) System.AggregateException: One or more errors occurred. (The daemon process has indicated that it has failed to start properly and has sent the following error: System.IO.FileNotFoundException: Could not load file or assembly 'System.Runtime, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. File name: 'System.Runtime, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'

 


Hello Arie,

Yes, this is the same issue. The only difference is that @mperrott  appears to have report preloading configured in the appsettings.json, which causes the problem to occur during startup, which crashes Indicium. We are investigating what happened between 2023.1.10 and 2023.1.11 that would explain this issue.


Hello Arie,

Yes, this is the same issue. The only difference is that @mperrott  appears to have report preloading configured in the appsettings.json, which causes the problem to occur during startup, which crashes Indicium. We are investigating what happened between 2023.1.10 and 2023.1.11 that would explain this issue.

Hi @Vincent Doppenberg ,

I remove my settings related to Dev Express and now it works:

 {
    "name": "Reporting__DevExpress__Preload",
    "value": "True",
    "slotSetting": true
  },
  {
    "name": "Reporting__DevExpress__WorkerCount",
    "value": "10",
    "slotSetting": true
  },

 

Thank you 

Please Let me know once the issue is resolved to apply back the configuration for DevExpress.


Hello @mperrott,

This does fix your startup problem, but please note that your reports will not work. I will keep you updated on the status of this issue.


Hello @mperrott,

This does fix your startup problem, but please note that your reports will not work. I will keep you updated on the status of this issue.

Hi @Vincent Doppenberg ,

Noted on this, we will not go into this version for our UAT and PROD env yet, until we get a fix for the above issue.


Hello @mperrott and @Arie V,

The issue has been resolved. Due to a problem on our build server, the 2023.1.11 version was not built correctly. One of our DevExpress libraries was not targeting the correct version of .NET.

Our apologies for the inconvenience caused by this issue. If you redownload version 2023.1.11 from TCP, the problem should disappear. The version number has remained the same because there was no need to make any changes, we’ve just rebuilt the same version.

Thank you for both of your input on this issue, it has helped us pinpoint the cause.