Skip to content
CCMForge
Exstream Field Archive

Exstream F1062 invalid Service Storage during StoryTeller export

Current releasesCommunications Server lineage through Exstream 25.3

By Tomas Hajek, working with Exstream since 2008. Published 2026-02-26

Applies to: StreamServe 5.6.1-5.6.2 and Exstream 25.3 Communications Builder StoryTeller export on Windows.

Symptom

Export fails with:

Fatal F1062: The Service Export for the service "MYSERVICE" could not be completed because the process seems to have an invalid Service Storage.

The export may succeed after restarting the project or the machine, then fail again. Opening every process and saving a harmless change sometimes helps and sometimes does not, especially after upgrading to 25.3 (Build 16.6.71). The inconsistency is what makes this one frustrating: the process opens normally, so the project content looks fine.

Cause

The authoritative mechanism is an incomplete or incorrect Windows Registry registration for Strs.Tools.StoryTeller.ExportConfigurator.

Two things can be wrong: the registry value can point to the wrong Classes\CLSID\{CLSID} entry, or the referenced InprocServer32 key can have a missing or stale CodeBase path for StoryTellerExportConfigurator.dll. Either way, the process service storage is invalid at export time even though authoring works normally. This typically happens after a client installation or upgrade that left an older registration behind.

Fix

On the machine that performs the export, open regedit with administrative privileges.

  1. Find Strs.Tools.StoryTeller.ExportConfigurator and follow its Classes\CLSID\{CLSID} reference.
  2. Verify the referenced Export Configurator matches the installed 16.6.x version.
  3. Under InprocServer32, verify that CodeBase exists and points to the correct StoryTellerExportConfigurator.dll.
  4. If the path is stale, repair the installation or re-register, then restart Communications Builder and retry the export.

Saving each process is at best a diagnostic, not a fix. If the problem began after an upgrade, compare the registry entries and DLL paths between a working and a failing Windows account before touching any project content.

Compare the machine before changing the project

Registration problems follow the machine and the Windows account, not the project. When an export defect survives a project restore but disappears on a colleague's machine, stop debugging the project.

Related notes

Related Exstream notes.

Ask about your case

Resolve can check the pattern against your environment.

Resolve searches your approved sources and shows its citations. If the evidence is weak, the same case reaches an experienced Exstream specialist with the evidence attached.

Discuss your Exstream problem See how Resolve works
These articles describe field experience and identify the Exstream versions they cover. They are not official vendor guidance. CCMForge is independent and is not affiliated with or endorsed by OpenText. OpenText and Exstream are trademarks of their respective owner.