We have a Terminal server 2012, recently it report TerminalServices-Licensing error(Event ID 44), please help

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

Log Name:      System
Source:        Microsoft-Windows-TerminalServices-Licensing
Date:          7/20/2015 4:47:55 PM
Event ID:      44
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      tdremote1.twindragonmarketing.com
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="2015-07-20T23:47:55.000000000Z" />
    <EventRecordID>34483</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>tdremote1.twindragonmarketing.com</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>

Hi Eric,

can you please explain the scenario? What are you trying to do? Are you running any app/code that is using  Licensing APIs?

Thank you Silvia for your reply.We just implement a terminal server 2012, and activated the RD licensing server on it. We installed 10 per user CALs. Recently, I found TS server report event error 44 twice, no other related events was found. Looks like it happened after some users renewed their RD license.   Please help me figure it out. Thanks.

Hi Eric,

It seems like that theres problem with the licensing database.

I have seen similar cases which were resolved by rebuilt of the licensing database, which I suggest you try.

Please gather your RDS CAL purchase agreement documentation before rebuilt, since you will need to reinstall RDS CALs onto the license server.

Here is some articles below which might be useful to you:

Event ID 44 Terminal Services License Server Database Availability

https://technet.microsoft.com/en-us/library/cc727345%28v=ws.10%29.aspx?f=255&MSPPError=-2147217396

Rebuild the RD Licensing Database

https://technet.microsoft.com/en-us/library/dd851428.aspx

Best Regards,

Amy

Hi Eric,

It seems like that theres problem with the licensing database.

I have seen similar cases which were resolved by rebuilt of the licensing database, which I suggest you try.

Please gather your RDS CAL purchase agreement documentation before rebuilt, since you will need to reinstall RDS CALs onto the license server.

Here are some articles below which might be useful to you:

Event ID 44 Terminal Services License Server Database Availability

https://technet.microsoft.com/en-us/library/cc727345%28v=ws.10%29.aspx?f=255&MSPPError=-2147217396

Rebuild the RD Licensing Database

https://technet.microsoft.com/en-us/library/dd851428.aspx

Best Regards,

Thank you Amy.

Is the solution apply for server 2012? By the way, the error was just reported twice, and no more errors till now.

• Edited by Eric Cao 6 hours 14 minutes ago

Hi Eric,

Is the solution apply for server 2012?

Yes, it does, despite of GUI differences.

By the way, the error was just reported twice, and no more errors till now.

In that case, I would suggest you monitor event logs, if the error message comes up again, then you may perform rebuilding process to resolve the problem.

Best Regards,

Amy

Thank you Amy.

Is the solution apply for server 2012? By the way, the error was just reported twice, and no more errors till now.

• Edited by Eric Cao Friday, July 24, 2015 12:46 AM

Thank you Amy for your I help.

I will monitor it every day.

Thanks again.

Eric