SAP Knowledge Base Article - Preview

2459326 - IQ Cockpit always records ID 4625 in Windows security log - SAP IQ


When IQ cockpit is used on Windows, event ID 4625 is always recorded in Windows security log.
This is the Audit Failure event.
However, this security log is recorded as a failure even if the user successfully logs on to the IQ server.

There are two problems.

  1. There is no reason for cockpit to record this security log.
  2. This security log is always Audit Failure.

For example, if a user who does not exist in the IQ database fails login via cockipit, the same log is recorded.
Even if login succeeds using dba / sql, Audit Failure is recorded.

And this problem is environment independent.
Windows Server 2012 R2 will be reproduced on both domain members and workstations.
Creating dba user for local users will also reproduce the problem.

Event Log
Log Name:      Security
 Source:        Microsoft-Windows-Security-Auditing
 Date:          2017/04/05 6:09:23
 Event ID:      4625
 Task Category: Logon
 Level:         Information
 Keywords:      Audit Failure
 User:          N/A
 Computer:      hostname
 An account failed to log on.

  Security ID:  SYSTEM
  Account Name:  hostname$
  Account Domain:  LOCAL
  Logon ID:  0x3E7

Logon Type:   3

Account For Which Logon Failed:
  Security ID:  NULL SID
  Account Name:  <identity>
   <parameter key="ResourceGUID" value="32D8FD3EBEDF491B86AA114CD1859C3D"/>
   <parameter key="ResourceName" value="iqdemo"/>
   <parameter key="Username" value="dba"/>
  Account Domain:  local

Failure Information:
  Failure Reason:  Unknown user name or bad password.
  Status:   0xC000006D
  Sub Status:  0xC0000064

Process Information:
  Caller Process ID: 0x158c
  Caller Process Name: C:\sap\COCKPIT-4\bin\amd64\cockpitsvc.exe

Network Information:
  Workstation Name: hostname
  Source Network Address: -
 Source Port:  -

Detailed Authentication Information:
  Logon Process:  Advapi
  Authentication Package: Negotiate
  Transited Services: -
 Package Name (NTLM only): -
 Key Length:  0

This event is generated when a logon request fails. It is generated on the computer where access was attempted.

The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.

The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).

The Process Information fields indicate which account and process on the system requested the logon.

The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.

The authentication information fields provide detailed information about this specific logon request.
  - Transited services indicate which intermediate services have participated in this logon request.
  - Package name indicates which sub-protocol was used among the NTLM protocols.
  - Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
 Event Xml:
 <Event xmlns="">
     <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" />
     <TimeCreated SystemTime="2017-04-05T06:09:23.254066500Z" />
     <Correlation />
     <Execution ProcessID="624" ThreadID="2364" />
     <Security />
     <Data Name="SubjectUserSid">S-1-5-18</Data>
     <Data Name="SubjectUserName">hostname$</Data>
     <Data Name="SubjectDomainName">LOCAL</Data>
     <Data Name="SubjectLogonId">0x3e7</Data>
     <Data Name="TargetUserSid">S-1-0-0</Data>
     <Data Name="TargetUserName"><identity>
   <parameter key="ResourceGUID" value="32D8FD3EBEDF491B86AA114CD1859C3D"/>
   <parameter key="ResourceName" value="iqdemo"/>
   <parameter key="Username" value="dba"/>
     <Data Name="TargetDomainName">local</Data>
     <Data Name="Status">0xc000006d</Data>
     <Data Name="FailureReason">%%2313</Data>
     <Data Name="SubStatus">0xc0000064</Data>
     <Data Name="LogonType">3</Data>
     <Data Name="LogonProcessName">Advapi  </Data>
     <Data Name="AuthenticationPackageName">Negotiate</Data>
     <Data Name="WorkstationName">hostname</Data>
     <Data Name="TransmittedServices">-</Data>
     <Data Name="LmPackageName">-</Data>
     <Data Name="KeyLength">0</Data>
     <Data Name="ProcessId">0x158c</Data>
     <Data Name="ProcessName">C:\sap\COCKPIT-4\bin\amd64\cockpitsvc.exe</Data>
     <Data Name="IpAddress">-</Data>
     <Data Name="IpPort">-</Data>

Agent Log
2017-04-05 06:14:02,219 [INFO ] [adapter.UAFLoginCommand                      ] [scc-ui::1752] - Authenticating web login dba
2017-04-05 06:14:02,685 [INFO ] [security.IQLoginModule                       ] [RMI TCP Connection(20)-] - Validating credentials



  • SAP IQ 16.0 SP10 and later
  • Windows Server 2012 R2
  • Cockpit Server 4


SAP Sybase IQ 15.4


IQ, Cockpit, security log, event, event log, 4625 , KBA , BC-SYB-IQ , Sybase IQ , Bug Filed

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.