The following general database error has occurred: "ESE error -1003 JET_errInvalidParameter, Invalid API parameter. "

We are seeing the following on a Windows 2012 R2 Domain Controller:

Log Name:      System
Source:        Microsoft-Windows-TerminalServices-Licensing
Date:          08/01/2019 14:30:12
Event ID:      44
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      %computername%. domain.suffix
Description:
The following general database error has occurred: "ESE error -1003 JET_errInvalidParameter, Invalid API parameter.
"
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-TerminalServices-Licensing" Guid="{4D99F017-0EB1-4B52-8419-14AEBD13D770}" EventSourceName="TermServLicensing" />
    <EventID Qualifiers="0">44</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2019-01-08T14:30:12.000000000Z" />
    <EventRecordID>120322</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>%computername%. domain.suffix</Computer>
    <Security />
  </System>
  <UserData>
    <EventXML xmlns:auto-ns3="http://schemas.microsoft.com/win/2004/08/events" xmlns="Event_NS">
      <param1>ESE error -1003 JET_errInvalidParameter, Invalid API parameter.
</param1>
    </EventXML>
  </UserData>
</Event>


It is the terminal server licensing machine also...

Any ideas?

Well the ESE jet engine is the file level ntds.dit database in the windows\folder that stores information pertaining to Active Directory, but is also used for the Terminal Server licensing database in Windows 2012 R2, and we think this may be the latter.

1003 error means it was interrupted whilst creating a log file but if your licensing database is still up and running the error should disappear once the log file is overwritten.