| Knowledgebase Home | Contact |
 Search the Knowledgebase |
 Jump to ID |
 Browse by Category |
| Licensing error when Audium Call Services is started | ||||||||||||
| Categories: Audium Call Services 3.4.x and 3.5 | ||||||||||||
This article describes what to check if, when Audium Call Services is started, an error message is logged that mentions the license files. SYMPTOMS An error similar to the following is generated when Audium Call Services is started: javax.servlet.ServletException: An error occurred during initialization of the server. The error was: The license file could not be authenticated. Please verify information or contact support. Audium Call Services will not process incoming requests, and so attempting to call into your application will likely result in a voice browser-specific error message. RESOLUTION This error message is produced when there is a problem authenticating the license files installed on Audium Call Services. There are several possible fixes, please check the following: - Make sure that both the License and Signature files are in the ...\Audium\CallServices\license directory. - Check the access rights for both files. The user running Tomcat should have rights to read the license file. - Have you made any modifications to either License or Signature file? Note that some email clients, such as Outlook, might modify binary files and thus cause them to be corrupted. We strongly suggest sending files in a compressed format, either as a ZIP or TAR archive, and unzipping them on the target server. - If the license files were transferred via FTP, please ensure that the transfer mode of your FTP client has been set to binary. The signature file is a binary file and transferring it through ASCII mode could corrupt it and thus lead to the lack of authentication. |
Print this page
Post a comment
| Visitor Comments |
| No visitor comments posted. Post a comment |
| Related Questions |
| Attachments |
| No attachments were found. |