2025-11-23 18:14:54.3458||DEBUG|PaymentSystem.Program|init main function 2025-11-23 18:14:58.0106||INFO|Hangfire.SqlServer.SqlServerObjectsInstaller|Start installing Hangfire SQL objects... 2025-11-23 18:14:58.4644||INFO|Hangfire.SqlServer.SqlServerObjectsInstaller|Hangfire SQL objects installed. 2025-11-23 18:14:58.4860||INFO|Hangfire.BackgroundJobServer|Starting Hangfire Server using job storage: 'SQL Server: VLIV-EFTDB01@RCPaySL-Live' 2025-11-23 18:14:58.4860||INFO|Hangfire.BackgroundJobServer|Using the following options for SQL Server job storage: Queue poll interval: 00:00:00. 2025-11-23 18:14:58.4860||INFO|Hangfire.BackgroundJobServer|Using the following options for Hangfire Server: Worker count: 20 Listening queues: 'default' Shutdown timeout: 00:00:15 Schedule polling interval: 00:00:15 2025-11-23 18:14:58.5989||INFO|Hangfire.Server.BackgroundServerProcess|Server vliv-eftapp01:18288:d7b5f7b1 successfully announced in 93.4681 ms 2025-11-23 18:14:58.6059||INFO|Hangfire.Server.BackgroundServerProcess|Server vliv-eftapp01:18288:d7b5f7b1 is starting the registered dispatchers: ServerWatchdog, ServerJobCancellationWatcher, ExpirationManager, CountersAggregator, Worker, DelayedJobScheduler, RecurringJobScheduler... 2025-11-23 18:14:58.6234||INFO|Hangfire.Server.BackgroundServerProcess|Server vliv-eftapp01:18288:d7b5f7b1 all the dispatchers started 2025-11-23 18:15:00.1088|30000|WARN|Microsoft.EntityFrameworkCore.Model.Validation|No type was specified for the decimal column 'Amount' on entity type 'BlackList'. This will cause values to be silently truncated if they do not fit in the default precision and scale. Explicitly specify the SQL server column type that can accommodate all the values using 'HasColumnType()'. 2025-11-23 18:15:00.1216|30000|WARN|Microsoft.EntityFrameworkCore.Model.Validation|No type was specified for the decimal column 'Amount' on entity type 'FeeReversal'. This will cause values to be silently truncated if they do not fit in the default precision and scale. Explicitly specify the SQL server column type that can accommodate all the values using 'HasColumnType()'. 2025-11-23 18:15:00.1216|30000|WARN|Microsoft.EntityFrameworkCore.Model.Validation|No type was specified for the decimal column 'FeeAmount' on entity type 'FeeTransactionLog'. This will cause values to be silently truncated if they do not fit in the default precision and scale. Explicitly specify the SQL server column type that can accommodate all the values using 'HasColumnType()'. 2025-11-23 18:15:00.1216|30000|WARN|Microsoft.EntityFrameworkCore.Model.Validation|No type was specified for the decimal column 'Amount' on entity type 'FeeTransactionLogStaging'. This will cause values to be silently truncated if they do not fit in the default precision and scale. Explicitly specify the SQL server column type that can accommodate all the values using 'HasColumnType()'. 2025-11-23 18:15:00.1216|30000|WARN|Microsoft.EntityFrameworkCore.Model.Validation|No type was specified for the decimal column 'FeeAmount' on entity type 'PaymentBatch'. This will cause values to be silently truncated if they do not fit in the default precision and scale. Explicitly specify the SQL server column type that can accommodate all the values using 'HasColumnType()'. 2025-11-23 18:15:00.1216|30000|WARN|Microsoft.EntityFrameworkCore.Model.Validation|No type was specified for the decimal column 'TotalAmount' on entity type 'PaymentBatch'. This will cause values to be silently truncated if they do not fit in the default precision and scale. Explicitly specify the SQL server column type that can accommodate all the values using 'HasColumnType()'. 2025-11-23 18:15:00.1216|30000|WARN|Microsoft.EntityFrameworkCore.Model.Validation|No type was specified for the decimal column 'Amount' on entity type 'PaymentItem'. This will cause values to be silently truncated if they do not fit in the default precision and scale. Explicitly specify the SQL server column type that can accommodate all the values using 'HasColumnType()'. 2025-11-23 18:15:00.1216|30000|WARN|Microsoft.EntityFrameworkCore.Model.Validation|No type was specified for the decimal column 'CorporateFeeAmount' on entity type 'PaymentItem'. This will cause values to be silently truncated if they do not fit in the default precision and scale. Explicitly specify the SQL server column type that can accommodate all the values using 'HasColumnType()'. 2025-11-23 18:15:00.1382|30000|WARN|Microsoft.EntityFrameworkCore.Model.Validation|No type was specified for the decimal column 'CreditAmount' on entity type 'PaymentItem'. This will cause values to be silently truncated if they do not fit in the default precision and scale. Explicitly specify the SQL server column type that can accommodate all the values using 'HasColumnType()'. 2025-11-23 18:15:00.1382|30000|WARN|Microsoft.EntityFrameworkCore.Model.Validation|No type was specified for the decimal column 'CustomerFeeAmount' on entity type 'PaymentItem'. This will cause values to be silently truncated if they do not fit in the default precision and scale. Explicitly specify the SQL server column type that can accommodate all the values using 'HasColumnType()'. 2025-11-23 18:15:00.1382|30000|WARN|Microsoft.EntityFrameworkCore.Model.Validation|No type was specified for the decimal column 'CorporateFeeAmount' on entity type 'PaymentItemStaging'. This will cause values to be silently truncated if they do not fit in the default precision and scale. Explicitly specify the SQL server column type that can accommodate all the values using 'HasColumnType()'. 2025-11-23 18:15:00.1382|30000|WARN|Microsoft.EntityFrameworkCore.Model.Validation|No type was specified for the decimal column 'CreditedAmount' on entity type 'PaymentItemStaging'. This will cause values to be silently truncated if they do not fit in the default precision and scale. Explicitly specify the SQL server column type that can accommodate all the values using 'HasColumnType()'. 2025-11-23 18:15:00.1382|30000|WARN|Microsoft.EntityFrameworkCore.Model.Validation|No type was specified for the decimal column 'CustomerFeeAmount' on entity type 'PaymentItemStaging'. This will cause values to be silently truncated if they do not fit in the default precision and scale. Explicitly specify the SQL server column type that can accommodate all the values using 'HasColumnType()'. 2025-11-23 18:15:00.1382|30000|WARN|Microsoft.EntityFrameworkCore.Model.Validation|No type was specified for the decimal column 'Amount' on entity type 'PaymentReversal'. This will cause values to be silently truncated if they do not fit in the default precision and scale. Explicitly specify the SQL server column type that can accommodate all the values using 'HasColumnType()'. 2025-11-23 18:15:00.1382|30000|WARN|Microsoft.EntityFrameworkCore.Model.Validation|No type was specified for the decimal column 'Amount' on entity type 'PaymentSummaryByBank'. This will cause values to be silently truncated if they do not fit in the default precision and scale. Explicitly specify the SQL server column type that can accommodate all the values using 'HasColumnType()'. 2025-11-23 18:15:00.1382|30000|WARN|Microsoft.EntityFrameworkCore.Model.Validation|No type was specified for the decimal column 'Credit' on entity type 'Statement'. This will cause values to be silently truncated if they do not fit in the default precision and scale. Explicitly specify the SQL server column type that can accommodate all the values using 'HasColumnType()'. 2025-11-23 18:15:00.1382|30000|WARN|Microsoft.EntityFrameworkCore.Model.Validation|No type was specified for the decimal column 'Debit' on entity type 'Statement'. This will cause values to be silently truncated if they do not fit in the default precision and scale. Explicitly specify the SQL server column type that can accommodate all the values using 'HasColumnType()'. 2025-11-23 18:15:00.1543|30000|WARN|Microsoft.EntityFrameworkCore.Model.Validation|No type was specified for the decimal column 'TotalAmount' on entity type 'UploadStaging'. This will cause values to be silently truncated if they do not fit in the default precision and scale. Explicitly specify the SQL server column type that can accommodate all the values using 'HasColumnType()'. 2025-11-23 18:15:00.1945|10403|INFO|Microsoft.EntityFrameworkCore.Infrastructure|Entity Framework Core 3.1.10 initialized 'AppDbContext' using provider 'Microsoft.EntityFrameworkCore.SqlServer' with options: using lazy-loading proxies 2025-11-23 18:15:00.1945|10403|INFO|Microsoft.EntityFrameworkCore.Infrastructure|Entity Framework Core 3.1.10 initialized 'AppDbContext' using provider 'Microsoft.EntityFrameworkCore.SqlServer' with options: using lazy-loading proxies 2025-11-23 18:15:00.1945|10403|INFO|Microsoft.EntityFrameworkCore.Infrastructure|Entity Framework Core 3.1.10 initialized 'AppDbContext' using provider 'Microsoft.EntityFrameworkCore.SqlServer' with options: using lazy-loading proxies 2025-11-23 18:15:00.1945|10403|INFO|Microsoft.EntityFrameworkCore.Infrastructure|Entity Framework Core 3.1.10 initialized 'AppDbContext' using provider 'Microsoft.EntityFrameworkCore.SqlServer' with options: using lazy-loading proxies 2025-11-23 18:15:00.1945|10403|INFO|Microsoft.EntityFrameworkCore.Infrastructure|Entity Framework Core 3.1.10 initialized 'AppDbContext' using provider 'Microsoft.EntityFrameworkCore.SqlServer' with options: using lazy-loading proxies 2025-11-23 18:15:01.0966|20101|INFO|Microsoft.EntityFrameworkCore.Database.Command|Executed DbCommand (13ms) [Parameters=[], CommandType='Text', CommandTimeout='30'] SELECT 1 2025-11-23 18:15:01.1158|20101|INFO|Microsoft.EntityFrameworkCore.Database.Command|Executed DbCommand (10ms) [Parameters=[], CommandType='Text', CommandTimeout='30'] SELECT OBJECT_ID(N'[__EFMigrationsHistory]'); 2025-11-23 18:15:01.1219|20101|INFO|Microsoft.EntityFrameworkCore.Database.Command|Executed DbCommand (2ms) [Parameters=[], CommandType='Text', CommandTimeout='30'] SELECT 1 2025-11-23 18:15:01.1219|20101|INFO|Microsoft.EntityFrameworkCore.Database.Command|Executed DbCommand (24ms) [Parameters=[@__defaultDate_0='?' (DbType = DateTime2), @__today_1='?' (DbType = DateTime2), @__today_2='?' (DbType = DateTime2)], CommandType='Text', CommandTimeout='30'] SELECT [p].[Id], [p].[ApprovalStatus], [p].[BatchDescription], [p].[BatchReference], [p].[CorporateId], [p].[CreatedBy], [p].[CurrencyId], [p].[DateCreated], [p].[DateModified], [p].[Fee], [p].[FeeAmount], [p].[FinalResponseCode], [p].[FinalResponseDescription], [p].[InProgress], [p].[InitialResponseCode], [p].[InitialResponseDescription], [p].[IsActive], [p].[IsDeleted], [p].[IsReversed], [p].[LastReQueryDate], [p].[ModifiedBy], [p].[PaymentMode], [p].[PaymentReference], [p].[PaymentStatus], [p].[PaymentTypeId], [p].[RetryCount], [p].[SourceAccount], [p].[SourceAccountName], [p].[SuspenseAccount], [p].[TotalAmount], [p].[TotalItem], [p].[TransactionDate], [p].[TransactionRef], [p].[TransactionStatus], [p].[UploadStagingId], [p].[UserType], [p].[UserTypeId] FROM [PaymentBatch] AS [p] WHERE ([p].[TransactionStatus] = 5) AND ((([p].[TransactionDate] > @__defaultDate_0) AND ([p].[TransactionDate] < @__today_1)) OR ([p].[DateCreated] < @__today_2)) 2025-11-23 18:15:01.1219|20101|INFO|Microsoft.EntityFrameworkCore.Database.Command|Executed DbCommand (1ms) [Parameters=[], CommandType='Text', CommandTimeout='30'] SELECT OBJECT_ID(N'[__EFMigrationsHistory]'); 2025-11-23 18:15:01.1219|20101|INFO|Microsoft.EntityFrameworkCore.Database.Command|Executed DbCommand (44ms) [Parameters=[@__xDate_0='?' (DbType = DateTime2)], CommandType='Text', CommandTimeout='30'] SELECT [p].[Id], [p].[ApprovalStatus], [p].[BatchDescription], [p].[BatchReference], [p].[CorporateId], [p].[CreatedBy], [p].[CurrencyId], [p].[DateCreated], [p].[DateModified], [p].[Fee], [p].[FeeAmount], [p].[FinalResponseCode], [p].[FinalResponseDescription], [p].[InProgress], [p].[InitialResponseCode], [p].[InitialResponseDescription], [p].[IsActive], [p].[IsDeleted], [p].[IsReversed], [p].[LastReQueryDate], [p].[ModifiedBy], [p].[PaymentMode], [p].[PaymentReference], [p].[PaymentStatus], [p].[PaymentTypeId], [p].[RetryCount], [p].[SourceAccount], [p].[SourceAccountName], [p].[SuspenseAccount], [p].[TotalAmount], [p].[TotalItem], [p].[TransactionDate], [p].[TransactionRef], [p].[TransactionStatus], [p].[UploadStagingId], [p].[UserType], [p].[UserTypeId] FROM [PaymentBatch] AS [p] WHERE ([p].[TransactionStatus] = 9) AND ([p].[TransactionDate] <= @__xDate_0) 2025-11-23 18:15:01.1847|20101|INFO|Microsoft.EntityFrameworkCore.Database.Command|Executed DbCommand (31ms) [Parameters=[], CommandType='Text', CommandTimeout='30'] SELECT [MigrationId], [ProductVersion] FROM [__EFMigrationsHistory] ORDER BY [MigrationId]; 2025-11-23 18:15:01.1999|20405|INFO|Microsoft.EntityFrameworkCore.Migrations|No migrations were applied. The database is already up to date. 2025-11-23 18:15:01.6622||INFO|Microsoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManager|User profile not available. Using 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ASP.NET\4.0.30319.0\AutoGenKeys\S-1-5-82-405065765-51968188-4129435083-1865239232-3978796933\DataProtection' as key repository and Windows DPAPI to encrypt keys at rest. 2025-11-23 18:15:02.0348|1|INFO|Microsoft.AspNetCore.Hosting.Diagnostics|Request starting HTTP/1.1 OPTIONS http://rcpayapi.mof.gov.sl/PaymentService/api/Payment/Statistics?CorporateId=207&Days=30 2025-11-23 18:15:02.7639|4|INFO|Microsoft.AspNetCore.Cors.Infrastructure.CorsService|CORS policy execution successful. 2025-11-23 18:15:02.7639|2|INFO|Microsoft.AspNetCore.Hosting.Diagnostics|Request finished in 738.4124ms 204 2025-11-23 18:15:02.8297|1|INFO|Microsoft.AspNetCore.Hosting.Diagnostics|Request starting HTTP/1.1 GET http://rcpayapi.mof.gov.sl/PaymentService/api/Payment/Statistics?CorporateId=207&Days=30 2025-11-23 18:15:03.0384|1|INFO|Microsoft.AspNetCore.Authentication.JwtBearer.JwtBearerHandler|Failed to validate the token. Microsoft.IdentityModel.Tokens.SecurityTokenExpiredException: IDX10223: Lifetime validation failed. The token is expired. ValidTo: 'System.DateTime', Current time: 'System.DateTime'. at Microsoft.IdentityModel.Tokens.Validators.ValidateLifetime(Nullable`1 notBefore, Nullable`1 expires, SecurityToken securityToken, TokenValidationParameters validationParameters) at System.IdentityModel.Tokens.Jwt.JwtSecurityTokenHandler.ValidateLifetime(Nullable`1 notBefore, Nullable`1 expires, JwtSecurityToken jwtToken, TokenValidationParameters validationParameters) at System.IdentityModel.Tokens.Jwt.JwtSecurityTokenHandler.ValidateTokenPayload(JwtSecurityToken jwtToken, TokenValidationParameters validationParameters) at System.IdentityModel.Tokens.Jwt.JwtSecurityTokenHandler.ValidateToken(String token, TokenValidationParameters validationParameters, SecurityToken& validatedToken) at Microsoft.AspNetCore.Authentication.JwtBearer.JwtBearerHandler.HandleAuthenticateAsync() 2025-11-23 18:15:03.0568|7|INFO|Microsoft.AspNetCore.Authentication.JwtBearer.JwtBearerHandler|Bearer was not authenticated. Failure message: IDX10223: Lifetime validation failed. The token is expired. ValidTo: 'System.DateTime', Current time: 'System.DateTime'. 2025-11-23 18:15:03.0612|4|INFO|Microsoft.AspNetCore.Cors.Infrastructure.CorsService|CORS policy execution successful. 2025-11-23 18:15:03.0612|2|INFO|Microsoft.AspNetCore.Authorization.DefaultAuthorizationService|Authorization failed. 2025-11-23 18:15:03.0612|12|INFO|Microsoft.AspNetCore.Authentication.JwtBearer.JwtBearerHandler|AuthenticationScheme: Bearer was challenged. 2025-11-23 18:15:03.0755|2|INFO|Microsoft.AspNetCore.Hosting.Diagnostics|Request finished in 245.8011ms 401 2025-11-23 18:15:13.9803|1|INFO|Microsoft.AspNetCore.Hosting.Diagnostics|Request starting HTTP/1.1 OPTIONS http://rcpayapi.mof.gov.sl/PaymentService/api/Payment/Statistics?CorporateId=207&Days=30 2025-11-23 18:15:13.9899|4|INFO|Microsoft.AspNetCore.Cors.Infrastructure.CorsService|CORS policy execution successful. 2025-11-23 18:15:13.9899|2|INFO|Microsoft.AspNetCore.Hosting.Diagnostics|Request finished in 14.5784ms 204 2025-11-23 18:15:14.0246|10403|INFO|Microsoft.EntityFrameworkCore.Infrastructure|Entity Framework Core 3.1.10 initialized 'AppDbContext' using provider 'Microsoft.EntityFrameworkCore.SqlServer' with options: using lazy-loading proxies 2025-11-23 18:15:14.0246|10403|INFO|Microsoft.EntityFrameworkCore.Infrastructure|Entity Framework Core 3.1.10 initialized 'AppDbContext' using provider 'Microsoft.EntityFrameworkCore.SqlServer' with options: using lazy-loading proxies 2025-11-23 18:15:15.1060|1|INFO|Microsoft.AspNetCore.Hosting.Diagnostics|Request starting HTTP/1.1 GET http://rcpayapi.mof.gov.sl/PaymentService/api/Payment/Statistics?CorporateId=207&Days=30 2025-11-23 18:15:15.1060|1|INFO|Microsoft.AspNetCore.Authentication.JwtBearer.JwtBearerHandler|Failed to validate the token. Microsoft.IdentityModel.Tokens.SecurityTokenExpiredException: IDX10223: Lifetime validation failed. The token is expired. ValidTo: 'System.DateTime', Current time: 'System.DateTime'. at Microsoft.IdentityModel.Tokens.Validators.ValidateLifetime(Nullable`1 notBefore, Nullable`1 expires, SecurityToken securityToken, TokenValidationParameters validationParameters) at System.IdentityModel.Tokens.Jwt.JwtSecurityTokenHandler.ValidateLifetime(Nullable`1 notBefore, Nullable`1 expires, JwtSecurityToken jwtToken, TokenValidationParameters validationParameters) at System.IdentityModel.Tokens.Jwt.JwtSecurityTokenHandler.ValidateTokenPayload(JwtSecurityToken jwtToken, TokenValidationParameters validationParameters) at System.IdentityModel.Tokens.Jwt.JwtSecurityTokenHandler.ValidateToken(String token, TokenValidationParameters validationParameters, SecurityToken& validatedToken) at Microsoft.AspNetCore.Authentication.JwtBearer.JwtBearerHandler.HandleAuthenticateAsync() 2025-11-23 18:15:15.1060|7|INFO|Microsoft.AspNetCore.Authentication.JwtBearer.JwtBearerHandler|Bearer was not authenticated. Failure message: IDX10223: Lifetime validation failed. The token is expired. ValidTo: 'System.DateTime', Current time: 'System.DateTime'. 2025-11-23 18:15:15.1060|4|INFO|Microsoft.AspNetCore.Cors.Infrastructure.CorsService|CORS policy execution successful. 2025-11-23 18:15:15.1060|2|INFO|Microsoft.AspNetCore.Authorization.DefaultAuthorizationService|Authorization failed. 2025-11-23 18:15:15.1060|12|INFO|Microsoft.AspNetCore.Authentication.JwtBearer.JwtBearerHandler|AuthenticationScheme: Bearer was challenged. 2025-11-23 18:15:15.1060|2|INFO|Microsoft.AspNetCore.Hosting.Diagnostics|Request finished in 13.3964ms 401 2025-11-23 18:20:14.1708|10403|INFO|Microsoft.EntityFrameworkCore.Infrastructure|Entity Framework Core 3.1.10 initialized 'AppDbContext' using provider 'Microsoft.EntityFrameworkCore.SqlServer' with options: using lazy-loading proxies 2025-11-23 18:20:14.1708|10403|INFO|Microsoft.EntityFrameworkCore.Infrastructure|Entity Framework Core 3.1.10 initialized 'AppDbContext' using provider 'Microsoft.EntityFrameworkCore.SqlServer' with options: using lazy-loading proxies 2025-11-23 18:25:14.3590|10403|INFO|Microsoft.EntityFrameworkCore.Infrastructure|Entity Framework Core 3.1.10 initialized 'AppDbContext' using provider 'Microsoft.EntityFrameworkCore.SqlServer' with options: using lazy-loading proxies 2025-11-23 18:25:14.3590|10403|INFO|Microsoft.EntityFrameworkCore.Infrastructure|Entity Framework Core 3.1.10 initialized 'AppDbContext' using provider 'Microsoft.EntityFrameworkCore.SqlServer' with options: using lazy-loading proxies 2025-11-23 18:30:14.4807|10403|INFO|Microsoft.EntityFrameworkCore.Infrastructure|Entity Framework Core 3.1.10 initialized 'AppDbContext' using provider 'Microsoft.EntityFrameworkCore.SqlServer' with options: using lazy-loading proxies 2025-11-23 18:30:14.4807|10403|INFO|Microsoft.EntityFrameworkCore.Infrastructure|Entity Framework Core 3.1.10 initialized 'AppDbContext' using provider 'Microsoft.EntityFrameworkCore.SqlServer' with options: using lazy-loading proxies 2025-11-23 18:35:14.6794|10403|INFO|Microsoft.EntityFrameworkCore.Infrastructure|Entity Framework Core 3.1.10 initialized 'AppDbContext' using provider 'Microsoft.EntityFrameworkCore.SqlServer' with options: using lazy-loading proxies 2025-11-23 18:35:14.6909|10403|INFO|Microsoft.EntityFrameworkCore.Infrastructure|Entity Framework Core 3.1.10 initialized 'AppDbContext' using provider 'Microsoft.EntityFrameworkCore.SqlServer' with options: using lazy-loading proxies 2025-11-23 18:35:53.0982|1|INFO|Microsoft.AspNetCore.Hosting.Diagnostics|Request starting HTTP/1.1 POST http://127.0.0.1:30054/PAYMENTSERVICE/iisintegration 0 2025-11-23 18:35:53.0982|2|INFO|Microsoft.AspNetCore.Hosting.Diagnostics|Request finished in 3.9128ms 202 2025-11-23 18:35:53.0982||INFO|Hangfire.Server.BackgroundServerProcess|Server vliv-eftapp01:18288:d7b5f7b1 caught stopping signal... 2025-11-23 18:35:53.1119||INFO|Hangfire.Server.BackgroundServerProcess|Server vliv-eftapp01:18288:d7b5f7b1 caught stopped signal... 2025-11-23 18:35:54.1858||INFO|Hangfire.Server.BackgroundServerProcess|Server vliv-eftapp01:18288:d7b5f7b1 All dispatchers stopped 2025-11-23 18:35:54.2031||INFO|Hangfire.Server.BackgroundServerProcess|Server vliv-eftapp01:18288:d7b5f7b1 successfully reported itself as stopped in 6.7515 ms 2025-11-23 18:35:54.2031||INFO|Hangfire.Server.BackgroundServerProcess|Server vliv-eftapp01:18288:d7b5f7b1 has been stopped in total 1096.1202 ms