SYSTEM_LICENSE_VIOLATION

[Steve Wagner]

I know my question has probably been around a long time, but I didn't see
any postings for it, so here it is again.

We have installed a fully authenticated Windows Embedded IDE with SP2,
bought and paid for. We built our image, deployed it as a temporary image,
and it runs fine. Finally, we became an Microsoft OEM and bought two runtime
licenses. We patched in the 25-character license (including the dashes after
every 5 characters) in Settings->Run-time Image Licensing. We fail when the
first boot agent reboots the system with a license violation, 0x009A. So,
what might be happening?

Thanks much,

Steve Wagner

 

[Guest]

I had same error and same problem once.
After all I've find out that if image was originally made on the evaluated
version of TD and then rebuilded in the authenticated TD, the
SYSTEM_LICENSE_VIOLATION error will appear. So I was forced to recreated the
image from zero in the authenticated Windows Embedded IDE.

 

[Steve Wagner]

Wow. Seems like a not-too-friendly bug in the IDE. In my case, however, I
started with an authenticated IDE, non evaluation copy. So I'm still stuck.

Steve

 

[Martin Grossen, eMVP [AVNET Silica]]

Hi Steve

Try to set the "Boot Partition Size" to 1024 and
"Partition Cluster Size" to 4069. (standard)
(Under Target Device Settings)

Do a dependency check and a rebuild.

Also check your PID number in the filed "Run-time Image Licensing"
it should be in the format "11111-22222-33333-44444-55555" and the
code have to be out of a license sticker envelope. (Yellow sticker with PID)
NOT the Target Designer Toolkit Box.


--

Martin Grossen, eMVP

AVNET EMG Silica
Franchise Manager Microsoft Embedded Europe

Your competent partner for Microsoft Embedded licencing

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~