Product

Platform

Operating system

Windows 2000

Error

None.

Symptoms

When the rule engine (AutomationApp.exe) starts up, it will fail. Then 20 seconds later it will restart and fail again. Ad infinitum.

With each failure, something like this is output to the diagnostic log:

E 08May06 18:29:08.298-PDT [9620.9300] MERCURY AraxiLab AutomationApp.Startup ?(?) Creo.PWS.Automation.BaseDataModel.DMAction():Exception message: Parse Error, no type associated with Xml key a4 Creo.PWS.Automation.PrinergyDataModelTypes.InputFileKind PrinergyDataModelTypes, Version=31.2.650.0, Culture=neutral, PublicKeyToken=c98cd755506f628c

E 08May06 18:29:08.345-PDT [9620.9300] MERCURY AraxiLab AutomationApp.Startup ?(?) Creo.PWS.Automation.BaseDataModel.DMAction(): at System.Runtime.Serialization.Formatters.Soap.SoapHandler.ProcessGetType(String value, String xmlKey, String& assemblyString)

at System.Runtime.Serialization.Formatters.Soap.SoapHandler.ProcessType(ParseRecord pr, ParseRecord objectPr)

at System.Runtime.Serialization.Formatters.Soap.SoapHandler.ProcessAttributes(ParseRecord pr, ParseRecord objectPr)

at System.Runtime.Serialization.Formatters.Soap.SoapHandler.EndElement(String prefix, String name, String urn)

at System.Runtime.Serialization.Formatters.Soap.SoapParser.ParseXml()

at System.Runtime.Serialization.Formatters.Soap.SoapParser.Run()

at System.Runtime.Serialization.Formatters.Soap.ObjectReader.Deserialize(HeaderHandler handler, ISerParser serParser)

at System.Runtime.Serialization.Formatters.Soap.SoapFormatter.Deserialize(Stream serializationStream, HeaderHandler handler)

at System.Runtime.Serialization.Formatters.Soap.SoapFormatter.Deserialize(Stream serializationStream)

at Creo.PWS.Automation.BaseDataModel.DMAction.Deserialize(Byte[] buf)

at Creo.PWS.Automation.BaseDataModel.DMAction.GetPersistedActiveActions()

E 08May06 18:29:08.360-PDT [9620.9300] MERCURY AraxiLab AutomationApp.Startup ?(?) Creo.PWS.Automation.AutomationApp.UnhandledExceptionHandler():Got unhandled exception from sender Name: AutomationApp.exe

There are no context policies.

E 08May06 18:29:08.376-PDT [9620.9300] MERCURY AraxiLab AutomationApp.Startup ?(?) Creo.PWS.Automation.AutomationApp.UnhandledExceptionHandler():Exception message: Parse Error, no type associated with Xml key a4 Creo.PWS.Automation.PrinergyDataModelTypes.InputFileKind PrinergyDataModelTypes, Version=31.2.650.0, Culture=neutral, PublicKeyToken=c98cd755506f628c

E 08May06 18:29:08.392-PDT [9620.9300] MERCURY AraxiLab AutomationApp.Startup ?(?) Creo.PWS.Automation.AutomationApp.UnhandledExceptionHandler(): at System.Runtime.Serialization.Formatters.Soap.SoapHandler.ProcessGetType(String value, String xmlKey, String& assemblyString)

at System.Runtime.Serialization.Formatters.Soap.SoapHandler.ProcessType(ParseRecord pr, ParseRecord objectPr)

at System.Runtime.Serialization.Formatters.Soap.SoapHandler.ProcessAttributes(ParseRecord pr, ParseRecord objectPr)

at System.Runtime.Serialization.Formatters.Soap.SoapHandler.EndElement(String prefix, String name, String urn)

at System.Runtime.Serialization.Formatters.Soap.SoapParser.ParseXml()

at System.Runtime.Serialization.Formatters.Soap.SoapParser.Run()

at System.Runtime.Serialization.Formatters.Soap.ObjectReader.Deserialize(HeaderHandler handler, ISerParser serParser)

at System.Runtime.Serialization.Formatters.Soap.SoapFormatter.Deserialize(Stream serializationStream, HeaderHandler handler)

at System.Runtime.Serialization.Formatters.Soap.SoapFormatter.Deserialize(Stream serializationStream)

at Creo.PWS.Automation.BaseDataModel.DMAction.Deserialize(Byte[] buf)

at Creo.PWS.Automation.BaseDataModel.DMAction.GetPersistedActiveActions()

at Creo.PWS.Automation.RuleEngine.Engine.StartupPhase2()

at Creo.PWS.Automation.RuleEngine.Engine.DelayedStart()

i 08May06 18:29:08.407-PDT [9620.11348] MERCURY AraxiLab AutomationApp ?(?) Creo.PWS.Automation.RuleEngine.Engine():Rule engine stopping.

Cause

2. The site upgrades to 3.1.0.2.

3. The site creates and enables some new rule sets that use new-for-3.1.0.2 types of actions and/or events.

4. At least one of these new rule sets is executing (waiting in a timer action) when the system is shut down.

5. The site rolls back to 3.1.0.1. When the rule engine starts up, it will fail. Then start up 20 seconds later and fail. Ad infinitum.

Solution

Contact PD. This is fixed by writing and executing an SQL statement that updates the state of the relevant persisted actions in the database.

Permanent fix:

See also

Keywords

Automation

Technical contact(s)

Ken Boyle

Submitted by

Ken Lew

Date submitted

12 May 2006