Web Service Monitor (WSM) – Error created by network scanner

Formate eVo’s internal webserver is used for the remote lightweight publishing of the eVo event log, and to provide limited remote control functionality.

As an embedded webserver running on an unusual port specified arbitrarily by theSystem Admin at the time of setup, it may appear suspicious to your network monitoring and security software.

Access of the WSM URL, ( example http://Formate-eVoSrv:8080) by third party monitoring software may trigger errors to be recorded in both the Windows and eVo event logs on the server similar to this:

Level ::  Error

Created ::  04/05/2021 09:47:31

Details ::  WebSvcMon.SimpleFile(1150): Could not find file ‘C:\Program Files\Extra Resource Limited\T3\Web\Source\index.html’.

Whilst this may not affect access to the WSM, nor produce an undue overhead on the server*, it will fill the logs with unwanted additional entries, and therefore your network monitoring or security software should be configured by rule to not probe this URL.

*extra entries in the event log may make future diagnostic examination more difficult.

eVo internal ID Association

Ever wondered what the internal id of a form type or revision is?

Underlying configuration files have an an internal unique name of the form


the root of the file name is associated with the machine it was first created on, and the extension identifies the object type, in the above case the actual form type revision. Some of the other extensions identify , Parent Formtype Set, shared value sets, email connections, server tasks, in fact all objects in the Explorer tree have an underlying physical file.

Sometimes this identifiers will turn up in the event log, so it would be useful to be able to link the id back to the item in Explorer. Well to find the association;

Method (1) More Utils|List Config files tool

tool to list all config files

Opening the tool gives you

List Config Files dialog – use refresh button to load content

Method (2) Formtype Sets, Revisions, and Include scripts have the information available in the “info” tab of the properties page for the item.

March/April 2021 – Windows OS Reported Print Problems – Resolution by Microsoft

Further to the previous entry describing print system problems, Microsoft have issued a series of patches to resolve the issues. Exact patch is dependent upon build of windows in use. In simple terms a fully patched ( as up to 07.04.21) windows system should have the fixes installed automatically.

Otherwise cumulative updates from February or March 9th should be either further patched or rolled back, or the following fixes applied


Windows OS 2012R2 KB5001640

Windows 10,2019 (1909 – 0n) KB5001648 & KB5001566

March/April 2021 – Windows OS Reported Print Problems

Whilst most information relates to Windows 10, it appears that a number of recent updates have adversely affected the printing sub-system – it manifests itself with random print job failures, job not reaching the queue, or disappearing from the print queue immediately after appearing but not reaching the printer, and reporting of GDI+ errors. Problems are across Type 3 and Type 4 drivers, with Type 4 being seen to more prone to jobs not reaching the queue.

It seems that versions of the updates have been rolled out to other supported OS. Some of the issues are detailed here

March 15, 2021—KB5001565 (OS Build 17134.2088) Out-of-band (microsoft.com)

Application of the latest Cumulative update for Windows 10 or KB5000842 appears to fix the issue.

Obviously if running a production system on a server OS you will have had significant control over update application, but for a customers choosing to run Formate on a Windows 10 machine in production, the problem updates may have been applied automatically, thus introducing the issues, so please be aware.

Text Formatting

Using tags to apply bold, italic, and colour etc to sections of text.

Take a a required layout output text, such as this (where the line is a single text element, and needs different formatting for parts, bold in this case.)

The items will be available from 01.03.2021:

Firstly the whole line needs to be wrapped in <ft></ft> tags.

Secondly, the date needs to be made bold, using <x=B><x=b> tags to switch bold on and off.

Thirdly, non bold sections still need to be defined as a text item (otherwise they will not show) using the <t></t> tags

So the raw line with formatting control tags would be

<ft><t>The items will be available from</t><t x=”B”>01.03.2021]</t><t x=”b”>:</t></ft>

This line could have the date substituted for a data or server variable, and could either be created in a script, or read in “as is” from an external text file or db. *if added in script the included ” would need to be substituted for \[.

Key things to note. Any text outside of the <ft></ft> tags in this element will make the whole line literal text and no formatting will take place, and format tags are likely to be output instead of converted.

Also all of the below are legitimate, and will not course an error;

<ft></ft>  –  just empty on layout

<ft><t>test</t></ft> should be fine and put test on the layout

<ft>test</ft> – would NOT put test on the layout as it is not within a text tag, so nothing would be put on the layout in this case


Anything in the text element after the final </ft> such as the colon below

<ft><t>The items will be available from</t><t x=”B”>01.03.2021]</t><t x=”b”></t></ft>:

will cause an error as the </ft> is not the last item in the text string.

Whilst an compound line like below, with the start of the text outside the <ft></ft> tags will cause the line to be interpreted as simple text, and the output displayed on the final document will be the literal text.

The items will be available from<ft><t x=”B”>01.03.2021]</t><t x=”b”>:</t></ft>

Much more help can be found at

Release 21 (21.0.21053.11023) Notes on Roll-Back to Previous Release

Although the upgrade from a previous version of eVo to v21 is semi-automated, no equivalent roll-back is available. Should you wish to install a an earlier version to a server with v21 installed already, v21 will need to be fully uninstalled and a completely new installation of the chosen earlier version made.

No configuration, setup, form types or tasks will be transferable as it is a fresh install, other than by use of the standard backup mechanism.