Remember that when you work with the link server, it is entered in the list of services in Windows. Since all services must be unique, you cannot insert the link server twice with the same name.

When you generate an instance of a link server (start_link_server method), the system checks whether a link server with the same name is already registered. If this is the case, the call fails, and the system returns an error message.

This means that problems can arise with the link server if a user is using several transactions at once that use SAP Desktop Office Integration (and hence the link server).

When you call the method start_link_server, always use the parameter link_server_mode = link_server->link_server_custname and assign an application-related parameter <server_name_suffix>.

This solution has the restriction that the user cannot run the same transaction twice simultaneously, since in this case, the same name would be assigned to the memory area twice.

When you call the method start_link_server, always use the parameter link_server_mode = link_server->link_server_custname and assign a unique name (for example, GUID or ID of the document in the central repository) to the parameter server_name_suffix.

This solution has the disadvantage that existing links in an initial document must be adapted: {LINK SAP.OLELinkServer.ItemObject.<n> "SAPOLELinkServer<GUID>" "<field>" \<format>}.

The unique name must also be saved with the document, since the same suffix must be used when you subsequently restart the link server to display the document again.