Can anything else causes the “Registration ID, Evaluation ID and Machine ID do not match (134)” error?
Yes, in versions V2.1 and earlier, if your application is properly registered and you instantiate AppSentinel, set the FileMask and RegistrySubKey properties, then set the variable referencing AppSentinel to Nothing or otherwise terminate AppSentinel without calling GetRegistrationInfo. You may get this error the next time your application calls CheckRegistration.
Related Questions
- I converted my application to use a newer version of AppSentinel now it displays the: "Registration ID, Evaluation ID and Machine ID do not match (134)" error, why?
- Can anything else causes the "Registration ID, Evaluation ID and Machine ID do not match (134)" error?
- What else causes the "Registration ID, Evaluation ID and Machine ID do not match (134)" error?