Video Screencast Help

EV 10 Indexing No Vivisimo License??? Anyone seen this please?

Created: 26 Sep 2012 • Updated: 29 Oct 2012 | 3 comments
EV 10 Indexing No Vivisimo License??? Anyone seen this please?
It came from rebuild task report
24/09/2012 11:08:04 The rebuild paused as it encountered an error.
24/09/2012 11:08:11 The rebuild has resumed its processing.
24/09/2012 11:08:11 The rebuild subtask has failed. 
Error Code: 57
Description:Indexing engine unreachable. The content type text/html; charset=utf-8 of the response message does not match the content type of the binding (text/xml; charset=utf-8). If using a custom encoder, be sure that the IsContentTypeSupported method is implemented properly. The first 1024 bytes of the response were: '<html>
        <title><br><br>error (0 ms) - **** No Vivisimo License **** Please try to install your license through the Velocity Administration Tool. For assistance, please contact &nbsp;&nbsp;(ID: CORE_LICENSE_NO_KEY)</title>
         body {font-family:"Verdana";font-weight:normal;font-size: .7em;color:black;} 
         p {font-family:"Verdana";font-weight:normal;color:black;margin-top: -5px}
         b {font-family:"Verdana";font-weight:bold;color:black;margin-top: -5px}
         H1 { font-family:"Verdana";font-weight:normal;font-size:18pt;color:red }
         H2 { font-family:"Verdana";font-weight:normal;font-size:14pt;color:maroon }
         pre {font-family:"Lucida Console";font-size: .9em}
         .marker {font-weight: bold; color: black;text-decoration: none;}
         .version {color: gray;}
         .error {margin-bottom: 10px;}
         .expandable { text-decoration:underline; font-weight:bold; color:navy; cursor:hand; }
        </sty'. The remote server returned an error: (500) Internal Server Error.
For more information, see the online index troubleshooting technical note at:




We had to reset EV Indexing and the error disappeared.

Comments 3 CommentsJump to latest comment

CareFreeX's picture

If you have an issue like this you should call support. Based on the amount of questions you had asked on the forum, you may want to engage Symantec partners for training or health check.

Dan Holzrichter's picture

I just got the same error message today when the server was upgrading some exchange journals.