Unable to run IDXACTIVATE online if remote server process present

Unable to run IDXACTIVATE online when ABL remote servers are present.

Connections with timestamps older than  <dbtimestamp> exist. (13246)
Do you wish to continue waiting..... Type y to continue (y/n). (13247)

The Connections referred are Remote server processes are currently connected to the database.
No remote ABL clients are currently connected to the database.
 

SQL remote servers do not prevent IDXACTIVATE from running.

IDXACTIVATE online will not run while a remote server process is connected to the database, even if there are no active remote ABL clients.

Upgrade to OpenEdge 10.1C or later, where remote ABL Servers are not considered in the active timestamp check. 

While the IDXACTIVATE feature was introduced in OpenEdge 10.1A, OpenEdge 10.2B08, 11.2.1, 11.3.0 or later are recommended. Previously there were issues where interrupting an IDXACTIVATE during the key build phase, leaves the index as active (but it's not built) and another that left admin locks behind when interrupted. Otherwise please refer to the Articles referenced below for additional considerations.

If all remote ABL users are disconnected and no exclusive locks or latches are held, terminate the remote server process through PROMON to the IDXACTIVATE session to continue:

$   promon R&D -> 4. Administrative Options -> 7. Terminate Server

For further information please refer to Article: P39432, How to terminate a remote server process?   

Progress Articles: 

P129256, Error 1422 after backing out of online IDXACTIVATE   
IDXACTIVATE / IDXFIX leave index admin locks after being interupted   
Index becomes active after interrupting an IDXACTIVATE session