VirgilTracy
-
Posts
5 -
Joined
-
Last visited
Never
Posts posted by VirgilTracy
-
-
Since update to KSC 12 from KSC 11 keep getting the following runtime error:
Event name Runtime error.
Severity: Functional failure
Application: Kaspersky Security Center 12 Administration Server
Version number: 12.0.0.7734
Task name:
Device: Administration Server <S-OB-FL05>
Group: Application Server
Time: Monday, April 13, 2020 12:17:52 PM
Name of virtual Administration Server:
Description: Runtime error: Database error occurred: #1950 (2601) Generic db error: "2601 'Cannot insert duplicate key row in object 'dbo.hst_tskstates' with unique index 'UX_hst_tskstates_nHostId_strTask'. The duplicate key value is (221, _LOCAL_3F5C4E4855031F020172A898DF5B450B.klt.ctrl).{23000};' LastStatement='hst_tsk_sync'"
Error details: 1950/2601 (Generic db error: "2601 'Cannot insert duplicate key row in object 'dbo.hst_tskstates' with unique index 'UX_hst_tskstates_nHostId_strTask'. The duplicate key value is (221, _LOCAL_3F5C4E4855031F020172A898DF5B450B.klt.ctrl).{23000};' LastStatement='hst_tsk_sync'"), c:\a\b\a_32ba8ed2\s\csadminkit\development2\server\db\ado\db_adoprepstmtimpl.cpp, 408.
.
Does anyone know how to reslove this issue and whether it’s critical or not?Thanks
-
Perfect - many thanks Ravi.
-
Hello Ravi,
I’m not sure what you mean.
When devices are connected to Kaspersky Security Center from out of office I’d like to know from which external IP address they are connecting.
Thanks.
-
Does anyone know if there’s a way to identify the external IP address of machines that are remotely connected to Security Center?
Thanks
Cannot insert duplicate key runtime error
in Kaspersky Endpoint Security for Business
Posted
Tech support has helped resolve this issue now. They identified the managed device that was causing the issue. After removing the device from managed and unassigned devices and blocking it from contacting the server the error wasn't raised anymore. The error still hasn't been raised since unblocking and reassigning it to managed devices. So providing tech support with the GSI log was the solution.