Frequently Asked Questions

---

Following installation or upgrade of the Transform Designer application you might receive the following exception when attempting to load a branch file or create a new branch.

"Transform.PinapI.Designer.Documents.PinapIDocument"

This guide helps resolve issues with the Transform Designer exception by refreshing the addon library and verifying proper installation completion.

Step 1: Refresh the Addon Library

Close all Transform applications first - This is important to prevent file conflicts during the refresh process.

• Navigate to your Transform installation directory:
  • Default path: <install_path>\Transform Foundation Server\bin\exe\
  • Look for the file named fsrefreshaolib.exe
• Run the refresh utility with administrator privileges:
  • Right-click on fsrefreshaolib.exe
  • Select "Run as administrator" from the context menu
  • Wait for the process to complete

Purpose: This utility refreshes the addon library files that Transform applications depend on for proper operation.

Step 2: Verify Installation Directory Contents

If Step 1 doesn't resolve the issue, check the installation integrity:

• Navigate to the AddonLibrary folder:
  • Default path: C:\Program Files (x86)\Bottomline Technologies\Transform Foundation Server\AddonLibrary
  • Note: Your path may differ if you used a custom installation directory
• Verify folder contents:
  • Confirm the folder exists and contains files
  • Critical: The folder should NOT be empty
  • If empty, this indicates an incomplete installation

Step 3: Check Folder Name Status

Look for folder naming issues that indicate incomplete installation:

• In the Transform Foundation Server directory, check for:
  • A folder named AddonLibrary (correct, completed installation)
  • A folder named NEWAddonLibrary (incorrect, incomplete installation)

Step 4: Identify Incomplete Installation

If you find a folder named "NEWAddonLibrary":

• This indicates the installation process did not complete successfully
• The final step of the installation is to rename this folder to "AddonLibrary"
• The presence of "NEWAddonLibrary" means this final step failed

Step 5: Complete the Installation Process

Manually complete the installation by renaming the folder:

1. Ensure all Transform applications are closed
2. Rename the folder:
   • Right-click on the NEWAddonLibrary folder
   • Select "Rename" from the context menu
   • Change the name from NEWAddonLibrary to AddonLibrary
   • Press Enter to confirm

Verify the change:

• Confirm the folder is now named AddonLibrary
• Check that all files are still present in the renamed folder

After Completing These Steps

1. Restart the Transform Designer applications and test functionality
2. If issues persist: The problem may be elsewhere in the system and may require additional troubleshooting
3. If successful: The Transform Designer applications should now function properly with the corrected addon library

Important Notes

• Administrator privileges are required for both running the refresh utility and renaming folders in the Program Files directory
• Always close Transform applications before performing these steps to prevent file access conflicts
• Custom installation paths may vary from the default locations shown in this guide
• Keep a backup of your installation directory before making changes, if possible

For any antivirus software on the Transform server, it is strongly recommended that Real-Time Virus Protection is not used as this can interfere with the software being able to create temporary files, can affect performance, and in some cases can result in system instability. If it is not possible to completely disable real-time scanning then the ‘data’ directory, the install directory and all of the directories that the projects reference should be excluded from real-time scanning. 

It is also recommended to disable the real-time scan from the Windows Print Spooler. Example effects of running antivirus software on Transform are: 

• Runtime Server is not shown in the “visible servers” in Administrator’s Config tab. 
• Runtime Server remains "Idle" if added manually and its DNS name in not shown in parenthesis.
• Error “Unable to contact deployment server on port 24501” is returned randomly at a sign-on page of Administrator.
• Error “Unable to synchronise with fsserver.exe; terminating” is logged either in LOGSVR or SYNC system log.
• The number of logs at \TransformFoundationServer\data\logs\\system location is increasing too fast and may reach 100,000 for one day.
• Not all Transform ports are listed when a DOS command “netstat –a” is run. Ports 24500 through 24510 should be shown as LISTENING. 

Possible solutions are: 

1. Disable “File System Auto-Protect” or "real time scanning" option for antivirus software. Restart the antivirus program for the change to take effect. 
2. If using Symantect/Norton, upgrade to version 10.0.2 or higher. 

Some antivirus programs may block ports & non standard executables by default. 

Ports used by Transform are: 

• Customers using the legacy 2.X port for OSA communication to the 2.X Remote Branch. 
• Gateway use port 4038. 

The standard ports for Formscape and Transform are: 

• 24500 - Apache Web Server
• 24501 - Deployment Server
• 24502 - Log Server
• 24503 - BootD (downloads from Deployment Server)
• 24504 - Remote Branch (OSA, SDK, and remote server branch calls)
• 24505 - Cupid (internal system use)
• 24506
• 24507
• 24508
• 24509 

Transform Foundation Server executables are: 

• fdepserver.exe
• fdsbootd.exe
• flogserver.exe
• fscupid.exe
• fsdemail.exe
• fsdisp.exe
• fsdorclupg.exe
• fsdreprintrequest.exe
• fsproc.exe
• fsrbgw.exe
• fsserver.exe
• fssync.exe
• fssync-oneway.exe
• OCRBurstExtractSrv.exe
• OCRSocSrv.exe
• OCRWorkerSrv.exe

The Transform Web request object works in Transform Designer but returns the following error when deployed to a Runtime Server:

(The request was aborted. Could not create SSL/TLS secure channel)

The following registry settings enable TLS 1.2 support for .NET Framework applications, which resolves connection errors that occur when trying to make web requests to servers that require secure TLS 1.2 connections. Without these settings, older .NET applications may default to less secure protocols like SSL 3.0 or TLS 1.0, causing connection failures.

Make sure you backup the registry before making the change

The Windows Registry is a critical database that stores low-level settings for the operating system and applications. Making incorrect changes can cause system instability, boot failures, or application malfunctions. A backup allows you to restore the registry to its previous working state if something goes wrong.

Registry Settings required on the Transform Runtime Server/s

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft.NETFramework\v4.0.30319]

• This registry key targets .NET Framework version 4.0.30319 applications running on 64-bit systems
• The path points to the main .NET Framework configuration location in the Windows registry

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft.NETFramework\v4.0.30319]

• This key targets the same .NET Framework version but for 32-bit applications running on 64-bit Windows systems
• The "Wow6432Node" is Windows' compatibility layer that allows 32-bit applications to run on 64-bit systems

If the Transform Web Server and Runtime Server computers are located in different subnets.

it may be necessary to configure the Branch Inter-Process Communication (IPC) Broker process to enable communication between Transform processes on these two machines.To configure the Branch IPC process when dealing with different subnets:

1. Access the Administrator application
2. Navigate to the Runtime Servers tab
3. Select the relevant Runtime Server, and click Show
4. On the Runtime Server page, click the Process Config link
5. Click Advanced 
6. In the list of processes, select fscupid and click Modify Selected
7. Within the Command Line, locate the -f argument. The hash (#) characters in this argument indicate that the corresponding numbers in the IP address must match. For any parts of the IP addresses of the Web server and Runtime Server computers that do not match, you must change the hash (#) character to an asterisk (*). 

The -f argument uses a pattern-matching system where you specify which parts of IP addresses should match exactly and which parts can vary. This is done using two special characters:

• The # character indicates that octets (the four number groups in an IP address) must match exactly.
• The * character indicates that octets can be different.

Let's walk through the example with IP addresses 77.78.9.2 and 77.78.8.4:

When you examine these two addresses octet by octet:

• First octet: 77 matches 77 ✓
• Second octet: 78 matches 78 ✓
• Third octet: 9 does not match 8 ✗
• Fourth octet: 2 does not match 4 ✗

Since the first two octets are identical between both IP addresses, you use the # character to indicate they must match. Since the last two octets are different, you use the * character to indicate they can vary.

Therefore, the -f argument should be set to #.#.*.*, which tells the system: "Match IP addresses where the first two octets are exactly the same (77.78), but the last two octets can be anything."

This pattern would match IP addresses like 77.78.1.1, 77.78.50.200, or 77.78.255.255, but would not match addresses like 76.78.1.1 or 77.79.1.1.

For connection from AX2012 set the -f argument to *.*.*.*

FROM: "$(BINDIR)\fscupid.exe" -hn $(DEFAULTGROUP) -f #.#.#.* -dp "$(DATAPATH)"

TO: "$(BINDIR)\fscupid.exe" -hn $(DEFAULTGROUP) -f *.*.*.* -dp "$(DATAPATH)"

Firewall Ports

Additionally, it is crucial to ensure that traffic is allowed across the firewall between the Runtime Server and Transform Web Server computers on specific ports

Ports 24501 and 24502 for the Administrator application

Port 24505 for the Transform Content Center application

To increase throughput you can tune the number of One-way branch files that can run concurrently. To change the number of Branch Execution Workers complete the following steps:

1. Access the Administrator application
2. Navigate to the Runtime Servers tab
3. Select the relevant Runtime Server, and click Show
4. Click Process Config

Branch Execution Workers

This shows, the maximum number of remote branch requests that can be processed at the same time, by process group. The default value is 4. Increasing the value of this setting improves throughput, but can impose additional load on the server.

Changing the Settings

After changing a setting, click Modify to implement the change.

Advanced Settings

fsdisp.exe has a number of parameters that can be added to the Command that control the behavior of one-way requests.

-mcc n to specify the number of concurrent fssysnc

-mls nnnn to specify that each fssync process restarts after nnnn seconds

-mr nn to specify that each fssync process restarts after processing nn requests

To update the one-way requests parameters.

1. From the Process Config page, click Advanced.
2. Select fsdisp, and then Modify selected.
3. Select the the Command line field
4. Add the required parameter, in this example we specify that each fssync process should restart after processing 10 requests, using the -mr parameter.
   For example, "$(BINDIR)\fsdisp.exe" -cp $(CUPIDPORT) -sn $(SERVERNAME) -dp "$(DATAPATH)" -mr 10.
5. Click Modify.

Please note when tuning the number of Document Execution Workers you need to ensure your system hardware can facilitate the increase in concurrent processes.