- 23 Apr 2024
- 1 Minute to read
- Print
- DarkLight
- PDF
Blueprint: Unable to release Secure Print jobs. The terminal returns "A licensing error occurred. The Secure Release Here feature is not licensed or the license has expired" but the license on the Analyst is current.
- Updated on 23 Apr 2024
- 1 Minute to read
- Print
- DarkLight
- PDF
Environment
Pharos Blueprint v5.0.7078
Pharos Blueprint v5.0.7085
Hewlett-Packard iMFP Terminal
Konica-Minolta iMFP Terminal
Canon iMFP Terminal
Ricoh iMFP Terminal
Sharp iMFP Terminal
Lexmark eDAS Terminal
Omega PS150 Terminal
Omega PS200 Terminal
Omega PS60 Terminal
Xerox PSX Terminal
Symptoms
ERROR: "A licensing error occurred. The Secure Release Here feature is not licensed or the license has expired"
Can't log in to release print jobs
All Blueprint and terminal connectivity tests pass
Change
The Blueprint license had expired, and a new license had been applied at the Analyst.
Cause
Microsoft Internet Information Server (IIS), which hosts the Pharos EDI Service for terminal functions (authentication, job display and management, and job release), did not completely terminate all open sessions upon application of the new Blueprint license. Therefore, some Pharos terminals did not receive an updated configuration and were behaving as though the license was still invalid.
Resolution
When a license is updated on the Blueprint Analyst, it is immediately replicated to all Blueprint Collectors, which in turn engages a change control within the Pharos EDI Service, and is supposed to affect all Pharos terminals registered to the Collector. However, since Microsoft IIS did not terminate all current sessions (as it should have), the most effective course of action is to reset Microsoft IIS.
1. Open a command prompt with an administrative credential.
2. Type iisreset at the prompt and press the [Enter] key on the keyboard.
This has the effect of expiring all current EDI sessions, and the Pharos terminals receive the new license information as well.
Please note that this is no longer an issue with Pharos Blueprint Enterprise 5.1 SP1 and higher.