Do you have any question about this error?
Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now →
Message type: E = Error
Message class: TD - SAPscript: Text editor, composer, forms, styles and fonts
Message number: 364
Message text: Link chain is endless or too long (& links)
The fontmetrics file (AFM file) contains an endless or too long chain
of links. If an AFM file referred to by a link also contains a link to
another AFM file and the link chain continues in this way, the search
for the final AFM file is terminated at a specific length of the link
chain.
The system sends an error message.
Correct the link in the fontmetrics by editing the fontmetrics file and
correcting the link. Enter the key of an available fontmetrics file.
Make sure this AFM file does not also contain a link. A correct link
appears as follows:
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
sapLinkToAFM HPLJIIID HELVE 120 false trueError message extract from SAP system. Copyright SAP SE.
TD364
- Link chain is endless or too long (& links) ?The SAP error message TD364, which states "Link chain is endless or too long (& links)," typically occurs in the context of transport requests and the transport management system (TMS) in SAP. This error indicates that there is a problem with the transport links, which can lead to an infinite loop or an excessively long chain of transport requests.
Cause:
- Circular Dependencies: The most common cause of this error is circular dependencies between transport requests. This means that one transport request is dependent on another, which in turn is dependent on the first, creating a loop.
- Long Dependency Chains: If there are too many transport requests linked together, the system may exceed the maximum allowed length for a chain of dependencies.
- Incorrect Transport Configuration: Misconfiguration in the transport routes or incorrect settings in the transport management system can also lead to this error.
Solution:
- Analyze Transport Requests: Use transaction codes like
SE01
(Transport Organizer) orSE09
(Workbench Organizer) to analyze the transport requests and their dependencies. Look for circular references or excessively long chains.- Remove Circular Dependencies: If you identify circular dependencies, you will need to break the loop by adjusting the transport requests. This may involve removing or modifying the dependencies.
- Limit Chain Length: If the chain is too long, consider breaking it into smaller, more manageable transport requests. This can help avoid hitting the limits set by the system.
- Check Transport Routes: Review the transport routes in TMS (transaction
STMS
) to ensure they are correctly configured and do not create unnecessary dependencies.- Consult SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide guidance on best practices for managing transport requests.
Related Information:
SE01
, SE09
, STMS
, and SE10
for managing transport requests and analyzing dependencies.If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP Basis team or reach out to SAP support for further assistance.
Get instant SAP help. Sign up for our Free Essentials Plan.
TD363
Link to nonexistent font metrics &
What causes this issue? The fontmetrics file (AFM file) contains a link to another fontmetrics file. However, the latter does not exist.System Respon...
TD362
Data was not saved
What causes this issue? The user has cancelled the current operation.System Response The system sends an information message. The data from the curr...
TD365
Font metrics must be applied from a different printer font
What causes this issue? You tried to create a fontmetrics file (AFM file) by using an existing fontmetrics file as a template. The key of the printer...
TD366
Output cannot be redirected to this printer (see long text)
What causes this issue? You tried to output a SAPscript spool request to an output device to which another device type is assigned than that for whic...
Click on this link to search all SAP messages.