2019-06-09 01:02:11.

411 -05:00 [Debug] Hosting starting

2019-06-09 01:02:11.590 -05:00 [Information] User profile is available. Using
'"C:\Users\wl-ca\AppData\Local\ASP.NET\DataProtection-Keys"' as key repository and
Windows DPAPI to encrypt keys at rest.
2019-06-09 01:02:11.605 -05:00 [Debug] Reading data from file '"C:\Users\wl-
ca\AppData\Local\ASP.NET\DataProtection-Keys\key-429f610c-0634-4611-af8f-
2a3d96d694a2.xml"'.
2019-06-09 01:02:11.634 -05:00 [Debug] Found key {429f610c-0634-4611-af8f-
2a3d96d694a2}.
2019-06-09 01:02:11.664 -05:00 [Debug] Considering key {429f610c-0634-4611-af8f-
2a3d96d694a2} with expiration date 2019-08-26 14:34:12Z as default key.
2019-06-09 01:02:11.684 -05:00 [Debug] Forwarded activator type request from
"Microsoft.AspNetCore.DataProtection.XmlEncryption.DpapiXmlDecryptor,
Microsoft.AspNetCore.DataProtection, Version=2.2.0.0, Culture=neutral,
PublicKeyToken=adb9793829ddae60" to
"Microsoft.AspNetCore.DataProtection.XmlEncryption.DpapiXmlDecryptor,
Microsoft.AspNetCore.DataProtection, Culture=neutral,
PublicKeyToken=adb9793829ddae60"
2019-06-09 01:02:11.686 -05:00 [Debug] Decrypting secret element using Windows
DPAPI.
2019-06-09 01:02:11.689 -05:00 [Debug] Forwarded activator type request from
"Microsoft.AspNetCore.DataProtection.AuthenticatedEncryption.ConfigurationModel.Aut
henticatedEncryptorDescriptorDeserializer, Microsoft.AspNetCore.DataProtection,
Version=2.2.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60" to
"Microsoft.AspNetCore.DataProtection.AuthenticatedEncryption.ConfigurationModel.Aut
henticatedEncryptorDescriptorDeserializer, Microsoft.AspNetCore.DataProtection,
Culture=neutral, PublicKeyToken=adb9793829ddae60"
2019-06-09 01:02:11.690 -05:00 [Debug] Opening CNG algorithm '"AES"' from provider
'null' with chaining mode CBC.
2019-06-09 01:02:11.697 -05:00 [Debug] Opening CNG algorithm '"SHA256"' from
provider 'null' with HMAC.
2019-06-09 01:02:11.705 -05:00 [Debug] Using key {429f610c-0634-4611-af8f-
2a3d96d694a2} as the default key.
2019-06-09 01:02:11.706 -05:00 [Debug] Key ring with default key {429f610c-0634-
4611-af8f-2a3d96d694a2} was loaded during application startup.
2019-06-09 01:02:11.900 -05:00 [Debug] An 'IServiceProvider' was created for
internal use by Entity Framework.
2019-06-09 01:02:12.256 -05:00 [Debug] No relationship from '"CaseFile"' to
'"CaseFileRelated"' has been configured by convention because there are multiple
properties on one entity type "{'InfoCaseFiles', 'InfoCaseFilesRelated'}" that
could be matched with the properties on the other entity type "{'InfoCaseFile',
'InfoCaseFileRelated'}". This message can be disregarded if explicit configuration
has been specified.
2019-06-09 01:02:12.284 -05:00 [Debug] No relationship from '"CaseFileRelated"' to
'"CaseFile"' has been configured by convention because there are multiple
properties on one entity type "{'InfoCaseFile', 'InfoCaseFileRelated'}" that could
be matched with the properties on the other entity type "{'InfoCaseFiles',
'InfoCaseFilesRelated'}". This message can be disregarded if explicit configuration
has been specified.
2019-06-09 01:02:12.410 -05:00 [Debug] No relationship from '"CaseFile"' to
'"CaseFileRelated"' has been configured by convention because there are multiple
properties on one entity type "{'InfoCaseFiles', 'InfoCaseFilesRelated'}" that
could be matched with the properties on the other entity type "{'InfoCaseFile',
'InfoCaseFileRelated'}". This message can be disregarded if explicit configuration
has been specified.
2019-06-09 01:02:12.450 -05:00 [Debug] No relationship from '"CaseFile"' to
'"CaseFileRelated"' has been configured by convention because there are multiple
properties on one entity type "{'InfoCaseFiles', 'InfoCaseFilesRelated'}" that
could be matched with the properties on the other entity type "{'InfoCaseFile',
'InfoCaseFileRelated'}". This message can be disregarded if explicit configuration
has been specified.
2019-06-09 01:02:12.454 -05:00 [Debug] No relationship from '"CaseFileRelated"' to
'"CaseFile"' has been configured by convention because there are multiple
properties on one entity type "{'InfoCaseFile', 'InfoCaseFileRelated'}" that could
be matched with the properties on the other entity type "{'InfoCaseFiles',
'InfoCaseFilesRelated'}". This message can be disregarded if explicit configuration
has been specified.
2019-06-09 01:02:12.515 -05:00 [Debug] No relationship from '"CaseFile"' to
'"CaseFileRelated"' has been configured by convention because there are multiple
properties on one entity type "{'InfoCaseFiles', 'InfoCaseFilesRelated'}" that
could be matched with the properties on the other entity type "{'InfoCaseFile',
'InfoCaseFileRelated'}". This message can be disregarded if explicit configuration
has been specified.
2019-06-09 01:02:12.564 -05:00 [Debug] No relationship from '"CaseFileRelated"' to
'"CaseFile"' has been configured by convention because there are multiple
properties on one entity type "{'InfoCaseFile', 'InfoCaseFileRelated'}" that could
be matched with the properties on the other entity type "{'InfoCaseFiles',
'InfoCaseFilesRelated'}". This message can be disregarded if explicit configuration
has been specified.
2019-06-09 01:02:12.630 -05:00 [Debug] No relationship from '"CaseFile"' to
'"CaseFileRelated"' has been configured by convention because there are multiple
properties on one entity type "{'InfoCaseFiles', 'InfoCaseFilesRelated'}" that
could be matched with the properties on the other entity type "{'InfoCaseFile',
'InfoCaseFileRelated'}". This message can be disregarded if explicit configuration
has been specified.
2019-06-09 01:02:12.634 -05:00 [Debug] No relationship from '"CaseFileRelated"' to
'"CaseFile"' has been configured by convention because there are multiple
properties on one entity type "{'InfoCaseFile', 'InfoCaseFileRelated'}" that could
be matched with the properties on the other entity type "{'InfoCaseFiles',
'InfoCaseFilesRelated'}". This message can be disregarded if explicit configuration
has been specified.
2019-06-09 01:02:12.844 -05:00 [Debug] No relationship from '"CaseFile"' to
'"CaseFileRelated"' has been configured by convention because there are multiple
properties on one entity type "{'InfoCaseFiles', 'InfoCaseFilesRelated'}" that
could be matched with the properties on the other entity type "{'InfoCaseFile',
'InfoCaseFileRelated'}". This message can be disregarded if explicit configuration
has been specified.
2019-06-09 01:02:12.851 -05:00 [Debug] No relationship from '"CaseFile"' to
'"CaseFileRelated"' has been configured by convention because there are multiple
properties on one entity type "{'InfoCaseFiles', 'InfoCaseFilesRelated'}" that
could be matched with the properties on the other entity type "{'InfoCaseFile',
'InfoCaseFileRelated'}". This message can be disregarded if explicit configuration
has been specified.
2019-06-09 01:02:12.859 -05:00 [Debug] No relationship from '"CaseFile"' to
'"CaseFileRelated"' has been configured by convention because there are multiple
properties on one entity type "{'InfoCaseFiles', 'InfoCaseFilesRelated'}" that
could be matched with the properties on the other entity type "{'InfoCaseFile',
'InfoCaseFileRelated'}". This message can be disregarded if explicit configuration
has been specified.
2019-06-09 01:02:12.866 -05:00 [Debug] No relationship from '"CaseFile"' to
'"CaseFileRelated"' has been configured by convention because there are multiple
properties on one entity type "{'InfoCaseFiles', 'InfoCaseFilesRelated'}" that
could be matched with the properties on the other entity type "{'InfoCaseFile',
'InfoCaseFileRelated'}". This message can be disregarded if explicit configuration
has been specified.
2019-06-09 01:02:12.894 -05:00 [Debug] No relationship from '"CaseFileRelated"' to
'"CaseFile"' has been configured by convention because there are multiple
properties on one entity type "{'InfoCaseFile', 'InfoCaseFileRelated'}" that could
be matched with the properties on the other entity type "{'InfoCaseFiles',
'InfoCaseFilesRelated'}". This message can be disregarded if explicit configuration
has been specified.
2019-06-09 01:02:12.900 -05:00 [Debug] No relationship from '"CaseFileRelated"' to
'"CaseFile"' has been configured by convention because there are multiple
properties on one entity type "{'InfoCaseFile', 'InfoCaseFileRelated'}" that could
be matched with the properties on the other entity type "{'InfoCaseFiles',
'InfoCaseFilesRelated'}". This message can be disregarded if explicit configuration
has been specified.
2019-06-09 01:02:12.907 -05:00 [Debug] No relationship from '"CaseFileRelated"' to
'"CaseFile"' has been configured by convention because there are multiple
properties on one entity type "{'InfoCaseFile', 'InfoCaseFileRelated'}" that could
be matched with the properties on the other entity type "{'InfoCaseFiles',
'InfoCaseFilesRelated'}". This message can be disregarded if explicit configuration
has been specified.
2019-06-09 01:02:12.914 -05:00 [Debug] No relationship from '"CaseFileRelated"' to
'"CaseFile"' has been configured by convention because there are multiple
properties on one entity type "{'InfoCaseFile', 'InfoCaseFileRelated'}" that could
be matched with the properties on the other entity type "{'InfoCaseFiles',
'InfoCaseFilesRelated'}". This message can be disregarded if explicit configuration
has been specified.
2019-06-09 01:02:12.915 -05:00 [Debug] No relationship from '"CaseFile"' to
'"CaseFileRelated"' has been configured by convention because there are multiple
properties on one entity type "{'InfoCaseFiles', 'InfoCaseFilesRelated'}" that
could be matched with the properties on the other entity type "{'InfoCaseFile',
'InfoCaseFileRelated'}". This message can be disregarded if explicit configuration
has been specified.
2019-06-09 01:02:13.575 -05:00 [Debug] The property '"CaseFileId"' on entity type
'"FavoriteCaseFile"' was created in shadow state because there are no eligible CLR
members with a matching name.
2019-06-09 01:02:13.575 -05:00 [Debug] The property '"UserId"' on entity type
'"FavoriteCaseFile"' was created in shadow state because there are no eligible CLR
members with a matching name.
2019-06-09 01:02:13.576 -05:00 [Debug] The property '"ClaimCaseFileId"' on entity
type '"MetadataCaseFile"' was created in shadow state because there are no eligible
CLR members with a matching name.
2019-06-09 01:02:13.576 -05:00 [Debug] The property '"DocumentId"' on entity type
'"MetadataDocument"' was created in shadow state because there are no eligible CLR
members with a matching name.
2019-06-09 01:02:13.719 -05:00 [Information] Entity Framework Core "2.2.4-
servicing-10062" initialized '"DocumentaryManagementContext"' using provider
'"Microsoft.EntityFrameworkCore.SqlServer"' with options:
"MigrationsAssembly=Catalejo.Backend.Core "
2019-06-09 01:02:13.807 -05:00 [Debug] Compiling query model: "
"'"(from Role <generated>_1 in DbSet<Role>
select [<generated>_1]).Any()"'
2019-06-09 01:02:13.842 -05:00 [Debug] Optimized query model: "
"'"(from Role <generated>_1 in DbSet<Role>
select [<generated>_1]).Any()"'
2019-06-09 01:02:13.945 -05:00 [Debug] "(QueryContext queryContext) =>
IEnumerable<bool> _InterceptExceptions(
|__ source: IEnumerable<bool> _ToSequence(() => bool GetResult(