Spectrum 9 not able to create file monitor job, not able to get status jobs running

Product Feature: Management Console



Spectrum 9 not able to create file monitor job, not able to get status jobs running


Software: Spectrum Version: 9.0 142 OS: Windows Server 2012

Trying to set up a new file monitor in the Management Console by clicking on the “Add” Button nothing happens.

Also when trying to get information on the history of jobs or running jobs get a “There was problems getting the results from the server” message. The error message is as follows:

An error occurred during an operation of service: the job ------------------ Source: SAL.v2.0 StackTrace: at Group1.ESD.SAL.Services.JobService.listJobs(WebServiceQuery query) at Group1.ESD.Common.Applications.Execution.History.ExecutionHistoryModel.GetJobResults(WebServiceQuery query) ----------------- Inner Exception starts There is an error in XML document (1, 1089). ------------------ Source: System.Xml StackTrace: at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events) at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle) at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at Group1.ESD.WebServiceProxies.Job.JobManagerService.listJobs(WebServiceQuery arg0) at Group1.ESD.SAL.Services.Internal.JobManager.listJobs(WebServiceQuery arg0) at Group1.ESD.SAL.Services.JobService.listJobs(WebServiceQuery query) ----------------- Inner Exception starts '.', hexadecimal value 0x00, is an invalid character. Line 1, position 1089. ------------------ Source: System.Xml StackTrace: at System.Xml.XmlTextReaderImpl.Throw(Exception e) at System.Xml.XmlTextReaderImpl.Throw(String res, String[] args) at System.Xml.XmlTextReaderImpl.ParseText(Int32& startPos, Int32& endPos, Int32& outOrChars) at System.Xml.XmlTextReaderImpl.ParseText() at System.Xml.XmlTextReaderImpl.ParseElementContent() at System.Xml.XmlTextReaderImpl.Read() at System.Xml.XmlTextReader.Read() at System.Xml.XmlReader.ReadElementString() at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderJobService.Read12_JobResult(Boolean isNullable, Boolean checkType) at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderJobService.Read115_listJobsResponse() at Microsoft.Xml.Serialization.GeneratedAssembly.ArrayOfObjectSerializer57.Deserialize(XmlSerializationReader reader) at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events) Inner Exception ends -----------------Inner Exception ends

Restarting the service / server didn’t help.


UPDATED: December 27, 2017
What looks like it might be an OrientDB issue (which is clustered database Spectrum uses for its internal system configuration). After Spectrum 9.0 was released with OrientDB 1.6, Orient Technologies fixed several issues in subsequent releases. The latest is OrientDB 1.6.2. We haven't been able to reproduce the problem you are having, so we don't know if the particular issue you are having is fixed by this latest version, but we suspect it might be. Would you be willing to replace your OrientDB 1.6 artifacts with the attached OrientDB 1.6.2? OrientDB 1.6.2 cannot read OrientDB 1.6 databases, so you would have to delete your existing database. Before replacing the OrientDB 1.6 artifacts with the Orient 1.6.2 artifacts, you could export your dataflows (i.e., subflows, jobs, and services) as .df files and  process flows as .pf files and then re-import those after the replacement is complete. But you would lose all your other Spectrum internal system configuration such as module database resources, notifications, JDBC connections, and your license.
To do the actual replacement, of OrientDB 1.6 with OrientDB 1.6.2:
Export your .df files and .pf files.
Stop your server.
Move your internal system configuration database %G1DCG%\server\app\repository\store\databases\spectrum to a different location not under %G1DCG% (maybe %TMP%?)
Move your 7 old OrientDB artifacts %G1DCG%\server\app\lib\orient*1.6.jar to a different location not in under %G1DCG% (maybe %TMP%?)
Unzip the attached zip file in your %G1DCG% directory to create the 7 new OrientDB 1.6.2 artifacts (like a patch, the directory structure of the attached zip file mirrors the directory structure of your Spectrum installation, so these artifacts will be unzipped to %G1DCG%\server\app\lib).
Restart your server.
Re-import your license.
Manually recreate your internal system configuration such as module database resources, notifications, and JDBC connections.
 OrientDB 1.6.2 are fairly new and have not been fully tested with Spectrum. At some future point in time, we plan to release an updated version if Spectrum with updated OrientDB artifacts.