Skip to main content
A
Arun5E3A
Participant
July 13, 2021
Question

Adobe Framemaker 2019 stops processing when we minimize the RDP session window

  • July 13, 2021
  • 2 replies
  • 210 views
We have installed the application Adobe FrameMaker 2019 to a server(Windows 2012 R2) which we use periodically to process large number of .cgm files (16000 - 35000).
When we start the conversion, we could see the processing through application's GUI screen.
The conversion process is carried out without any problem if we keep of RDP screen open but when we minimize or close(X) the RDP screen(not log out) then the application enters idle state and the conversion process is paused. The conversion process continues again when we maximize the RDP screen or when we login again.
 
We would like to how to make the Frame maker to continue processing even when we minimize or close(not log out) the RDP screen.
    This topic has been closed for replies.

    2 replies

    pulkitn
    Adobe Employee
    pulkitn
    Adobe Employee
    July 14, 2021

    As far as I know, FrameMaker doesn't stop processing things even if you close or minimize the RDP session.
    I had  used FM on the remote machine many times and haven't seen this 
    The culprit could be a script or in some enterprises, a virtual system that sleeps when we close the RDP session, Contact your IT to know more about it 

    A
    Arun5E3AAuthor
    Participant
    July 16, 2021

    Hi Pulktin,

     

    Thanks for your comments

     

    The other applications and programs is running fine even if the RDP screen is minimized or closed but only Framemaker becomes Idle.

     

    On the script part we are executing a .fsl script in which there is section which does an operation using the document object of each .cgm file. I'm not sure if this section is demanding the RDP GUI to be open.

     

    Open Document File(vXML)
    NewVar(docobj)
    FileIsInUse(ResetLockAndContinue)
    FontChangedMetric(OK)
    AlertUserAboutFailure(True)
    MakeVisible(TRUE)
    FontNotFoundInDoc(OK)
    MakeIconic(FALSE);
    Save Document DocObject(docobj)
    File(vXML)
    FileType(SaveFmtXml)
    ReturnStatus(vErrorList);
    Close Document DocObject(docobj) IgnoreMods;

    Bob_Niland
    Community Expert
    Bob_NilandCommunity Expert
    Community Expert
    July 13, 2021

    Is this Adobe Framemaker or Framemaker Publishing Server that's installed?

    Regular (single-user) FM isn't officially supported on Windows Server, and even if it installs and runs, it isn't licenced for use by multiple users (so if that's the scenario, and this is a bug, it's not likely to get fixed).

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices