and I did not see an answer to this problem there. I have recently been receiving this message on my MetaFrame server. I cannot find anything on it on my TechNet CD's so thought I would check here. Please advise!
EventID.net points to a Microsoft article (Q294326), which leads you to an unpublished hotfix which will fix the problem. According to them: "A corrupted or invalid license is being supplied by the client when it connects to the Terminal Server-based server".
Our event logs were filling up with 1003 errors. I applied the fix and it cleared right up!
Hope this helps - Bill
"You can get anything you want out of life, if you'll just help enough other people get what they want" - Zig Ziglar
Hi, had a look on thinnet re. this message as its something that is affecting our servers too, one of the replies to this problem stated that the user had recieved a "patch" from thinnet forums to sort it but he never elaborated so I dont know where or what this was....???? Another user replied saying that he sorted it by applying a local licence count of one to the server...??? I dont know if this means a "per seat" or "per server" licence...??? Not had time to try this yet and I'm not sure if its possible to "mix" between the two....???
The original Event ID 1003 in this thread had a description of "The description for Event ID ( 1003 ) in Source ( TermService ) could not be found. It contains the following insertion string(s):"
EventID.net provides a fix for the description "Terminal Service Client Has Provided an Invalid License" as well as the reference in the Microsoft article "Q294326". Event though OGI is using Windows 2000, we also have this same issue using TSE40 w/sp6.
Wish we could locate a solution also to this. Thanks.
As Bomberrile states, the Event ID 1003 that I'm getting does not refer to any licensing. Is the hotfix just for a corrupted license or does it fix the original problem which is:
The description for Event ID ( 1003 ) in Source ( TermService ) could
not be found. It contains the following insertion string(s).
Also, what is the icaapi.dll file supposed to fix?
Microsoft's solution in Q294326 states that an update to Icaapi.dll will fix the Event Id 1003 problem (for the Terminal Service client has provided an invalid license message).....I'm not sure if "the insertion string could not be found" message is related...???
see Herne42's post in this thread for the full Microsoft description re the license message.......
Has anyone managed to get a hold of the updated dll and tried it....??? Did it work....???
I was getting the same message for the longest time. It stopped this message from coming back and so far I am having no problems, not sure if it is going to cause any future problems.
So, if I did something stupid please let me know. Thanks
Have you tried to delete the registry key MSLicensing on the client PC? This should fix the problem.
Secondly, make sure you have a licensing server running and your TS can see it. If AD is not in place you may need to force the LS name in the TS registry. Described in the TechNet KB. Cláudio Rodrigues
Microsoft MVP
Windows 2000/NT Server - Terminal Services
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.