2024-07-24 09:49:00 466-->>>S7采集异常===>>Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling 'Dispose' on the context instance, or wrapping it in a using statement. If you are using dependency injection, you should let the dependency injection container take care of disposing context instances. Object name: 'ApplicationDbContext'. 2024-07-24 09:49:05 082-->>>S7采集异常===>>Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling 'Dispose' on the context instance, or wrapping it in a using statement. If you are using dependency injection, you should let the dependency injection container take care of disposing context instances. Object name: 'ApplicationDbContext'. 2024-07-24 09:49:10 049-->>>S7采集异常===>>Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling 'Dispose' on the context instance, or wrapping it in a using statement. If you are using dependency injection, you should let the dependency injection container take care of disposing context instances. Object name: 'ApplicationDbContext'. 2024-07-24 09:49:15 058-->>>S7采集异常===>>Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling 'Dispose' on the context instance, or wrapping it in a using statement. If you are using dependency injection, you should let the dependency injection container take care of disposing context instances. Object name: 'ApplicationDbContext'. 2024-07-24 09:50:45 504-->>>S7采集异常===>>Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling 'Dispose' on the context instance, or wrapping it in a using statement. If you are using dependency injection, you should let the dependency injection container take care of disposing context instances. Object name: 'ApplicationDbContext'. 2024-07-24 09:50:50 063-->>>S7采集异常===>>Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling 'Dispose' on the context instance, or wrapping it in a using statement. If you are using dependency injection, you should let the dependency injection container take care of disposing context instances. Object name: 'ApplicationDbContext'. 2024-07-24 09:50:55 048-->>>S7采集异常===>>Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling 'Dispose' on the context instance, or wrapping it in a using statement. If you are using dependency injection, you should let the dependency injection container take care of disposing context instances. Object name: 'ApplicationDbContext'. 2024-07-24 09:57:30 287-->>>S7采集异常===>>Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling 'Dispose' on the context instance, or wrapping it in a using statement. If you are using dependency injection, you should let the dependency injection container take care of disposing context instances. Object name: 'ApplicationDbContext'. 2024-07-24 09:57:30 312-->>>S7采集异常===>>Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling 'Dispose' on the context instance, or wrapping it in a using statement. If you are using dependency injection, you should let the dependency injection container take care of disposing context instances. Object name: 'ApplicationDbContext'. 2024-07-24 09:57:35 050-->>>S7采集异常===>>Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling 'Dispose' on the context instance, or wrapping it in a using statement. If you are using dependency injection, you should let the dependency injection container take care of disposing context instances. Object name: 'ApplicationDbContext'. 2024-07-24 09:57:40 039-->>>S7采集异常===>>Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling 'Dispose' on the context instance, or wrapping it in a using statement. If you are using dependency injection, you should let the dependency injection container take care of disposing context instances. Object name: 'ApplicationDbContext'. 2024-07-24 09:57:45 048-->>>S7采集异常===>>Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling 'Dispose' on the context instance, or wrapping it in a using statement. If you are using dependency injection, you should let the dependency injection container take care of disposing context instances. Object name: 'ApplicationDbContext'. 2024-07-24 09:57:50 050-->>>S7采集异常===>>Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling 'Dispose' on the context instance, or wrapping it in a using statement. If you are using dependency injection, you should let the dependency injection container take care of disposing context instances. Object name: 'ApplicationDbContext'. 2024-07-24 09:57:55 039-->>>S7采集异常===>>Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling 'Dispose' on the context instance, or wrapping it in a using statement. If you are using dependency injection, you should let the dependency injection container take care of disposing context instances. Object name: 'ApplicationDbContext'. 2024-07-24 09:58:00 043-->>>S7采集异常===>>Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling 'Dispose' on the context instance, or wrapping it in a using statement. If you are using dependency injection, you should let the dependency injection container take care of disposing context instances. Object name: 'ApplicationDbContext'. 2024-07-24 12:33:21 803-->>>S7采集异常===>>Object reference not set to an instance of an object. 2024-07-24 12:39:04 533-->>>S7采集异常===>>Object reference not set to an instance of an object. 2024-07-24 12:41:34 787-->>>S7采集异常===>>Object reference not set to an instance of an object. 2024-07-24 12:49:34 308-->>>S7采集异常===>>Object reference not set to an instance of an object. 2024-07-24 12:51:12 048-->>>S7采集异常===>>Object reference not set to an instance of an object. 2024-07-24 12:51:12 079-->>>S7采集异常===>>Object reference not set to an instance of an object. 2024-07-24 12:51:13 241-->>>S7采集异常===>>Object reference not set to an instance of an object. 2024-07-24 12:51:14 221-->>>S7采集异常===>>Object reference not set to an instance of an object. 2024-07-24 12:51:14 249-->>>S7采集异常===>>Object reference not set to an instance of an object. 2024-07-24 12:51:16 165-->>>S7采集异常===>>Object reference not set to an instance of an object. 2024-07-24 12:51:16 190-->>>S7采集异常===>>Object reference not set to an instance of an object. 2024-07-24 13:19:11 341-->>>S7采集异常===>>Object reference not set to an instance of an object. 2024-07-24 13:22:07 816-->>>S7采集异常===>>Unable to cast object of type 'System.DBNull' to type 'System.String'. 2024-07-24 13:26:56 849-->>>S7采集异常===>> Unable to cast object of type 'System.DBNull' to type 'System.String'. Stack Trace: at MySqlConnector.Core.Row.GetString(Int32 ordinal) in /_/src/MySqlConnector/Core/Row.cs:line 355 at MySqlConnector.MySqlDataReader.GetString(Int32 ordinal) in /_/src/MySqlConnector/MySqlDataReader.cs:line 293 at lambda_method71(Closure, QueryContext, DbDataReader, ResultContext, SingleQueryResultCoordinator) at Microsoft.EntityFrameworkCore.Query.Internal.SingleQueryingEnumerable`1.Enumerator.MoveNext() at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection) at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source) at WCS.Repository.WcsTagValueRepository.GetList(WcsTagValue vo) in C:\Users\admin\Source\Repos\wcs\WCS\Repository\WcsTagValueRepository.cs:line 44 at WCS.Services.WcsTagValueService.GetList(WcsTagValue vo) in C:\Users\admin\Source\Repos\wcs\WCS\Service\Impl\WcsTagValueService.cs:line 19 at WCS.Service.Impl.TaskService.DataCollectS7Job() in C:\Users\admin\Source\Repos\wcs\WCS\Service\Impl\TaskService.cs:line 147 2024-07-24 13:27:23 222-->>>S7采集异常===>> Unable to cast object of type 'System.DBNull' to type 'System.String'. Stack Trace: at MySqlConnector.Core.Row.GetString(Int32 ordinal) in /_/src/MySqlConnector/Core/Row.cs:line 355 at MySqlConnector.MySqlDataReader.GetString(Int32 ordinal) in /_/src/MySqlConnector/MySqlDataReader.cs:line 293 at lambda_method71(Closure, QueryContext, DbDataReader, ResultContext, SingleQueryResultCoordinator) at Microsoft.EntityFrameworkCore.Query.Internal.SingleQueryingEnumerable`1.Enumerator.MoveNext() at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection) at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source) at WCS.Repository.WcsTagValueRepository.GetList(WcsTagValue vo) in C:\Users\admin\Source\Repos\wcs\WCS\Repository\WcsTagValueRepository.cs:line 44 at WCS.Services.WcsTagValueService.GetList(WcsTagValue vo) in C:\Users\admin\Source\Repos\wcs\WCS\Service\Impl\WcsTagValueService.cs:line 19 at WCS.Service.Impl.TaskService.DataCollectS7Job() in C:\Users\admin\Source\Repos\wcs\WCS\Service\Impl\TaskService.cs:line 147 2024-07-24 13:28:41 115-->>>S7采集异常===>> Value cannot be null. (Parameter 'value') Stack Trace: at Newtonsoft.Json.Utilities.ValidationUtils.ArgumentNotNull(Object value, String parameterName) at Newtonsoft.Json.JsonConvert.DeserializeObject(String value, Type type, JsonSerializerSettings settings) at Newtonsoft.Json.JsonConvert.DeserializeObject[T](String value, JsonSerializerSettings settings) at Newtonsoft.Json.JsonConvert.DeserializeObject[T](String value) at WCS.Service.Impl.TaskService.DataCollectS7Job() in C:\Users\admin\Source\Repos\wcs\WCS\Service\Impl\TaskService.cs:line 161 2024-07-24 13:28:43 804-->>>S7采集,Ip:192.168.10.202 地址:DB2.4,值:0,发生变化 2024-07-24 13:29:06 735-->>>S7采集,Ip:192.168.10.202 地址:DB2.4,值:3,发生变化