14 JUNE 2018
This is an update for Sequence Cora SeQuence v8.4.0, which includes additional tracing capabilities for the issue detailed below.
Enhancements
Detailed plan execution tracing was added to HotOperations.
To Enable the logging:
1. Add the code below to the system diagnostic section (system.diagnostics > sources) in the runtime config file:
<source name="sequence.hotoperations" switchName="sequence.hotoperation.switch" switchType="System.Diagnostics.SourceSwitch">
<listeners>
<add name="hotopseventlog" type="PNMsoft.Sequence.Diagnostics.EventLogTraceListenerEx, PNMsoft.Sequence, Version=8.0.0.0, Culture=neutral, PublicKeyToken=0a1a1b90c1c5dca1" initializeData="Flowtime Stand-alone">
<filter type="System.Diagnostics.EventTypeFilter" initializeData="All" />
</add>
<add name="HostLog"
type="PNMsoft.Sequence.Diagnostics.SvcFormatWorkflowRuntimeTraceListener, PNMsoft.Sequence, Version=8.0.0.0, Culture=neutral, PublicKeyToken=0a1a1b90c1c5dca1"
traceDirectory="C:\temp\logs\hotops"
/>
<remove name="Default" />
</listeners>
</source>
</sources>
2. Change the directory to a valid directory.
3. Add this switch to the switches section
<add name="sequence.hotoperation.switch" value="All" />
Update Steps
Update from 8.4.6:
- Download the files
- Backup your Sequence database.
- Run the PatchSynchronization.sql and PatchSynchronization_Data.sql scripts from the DB Scripts on your Sequence database.
- Run IISRESET.
- Make sure the following files and folders are on the same level in the server.
- Engine
- HotOperations
- SequencePatch.xml
- SequencePatcher.ps1
- Run the SequencePatcer.ps1 on all Sequence servers. (Right click -> Run with PowerShell)
- Press on any key to run as Administrator
- Run IISRESET for the change to take effect.
Rollback Steps (In case of failure)
1. Restore Database to the per patch state
2. Return the old dlls
3. Remove tags from the web.config fil
NOTE: If you are running a Cora SeQuence version earlier than v8.4.6, you must install v8.4.6 before you install v8.4.7.