V9.1 Debugger won't run - "Access is denied" - SOLVED - Forum - OpenEdge Development - Progress Community

V9.1 Debugger won't run - "Access is denied" - SOLVED

 Forum

V9.1 Debugger won't run - "Access is denied" - SOLVED

  • We have a client still on V9.1 (sigh) and whom we access via Windows' remote desktop.  When attempting to start the Progress Debugger we see the splash screen briefly, followed by a Windows error to the effect of "Access is denied".  My theory is that the Debugger is attempting to write temp files somewhere on disk and is running into security restrictions.  Can anyone confirm or debunk that theory, and maybe details that will help us solve this?

  • Which version of Windows are they running?
     
    James Palmer |Application Developer
    Tel: 01253 785103 | Fax: 01253 785001 | Web: www.inenco.com | Twitter : @inenco
    footer
     
    From: keithg [mailto:bounce-keithg@community.progress.com]
    Sent: 16 May 2014 15:28
    To: TU.OE.Development@community.progress.com
    Subject: V9.1 Debugger won't run - "Access is denied"
     
    Thread created by keithg

    We have a client still on V9.1 (sigh) and whom we access via Windows' remote desktop.  When attempting to start the Progress Debugger we see the splash screen briefly, followed by a Windows error to the effect of "Access is denied".  My theory is that the Debugger is attempting to write temp files somewhere on disk and is running into security restrictions.  Can anyone confirm or debunk that theory, and maybe details that will help us solve this?

    Stop receiving emails on this subject.

    Flag this post as spam/abuse.

     

    Click here to report this email as spam.



    Inenco, Ribble House, Ballam Road, Lytham, FY8 4TS. Company Reg No: 2435678 For further information on the Inenco Group Ltd please visit our web site at www.inenco.com

    NOTE: This email and any information contained within or attached in a separate file is confidential and intended solely for the Individual to whom it is addressed. The information or data included is solely for the purpose indicated or previously agreed. Any information or data included with this e-mail remains the property of Inenco Group Ltd. and the recipient will refrain from utilising the information for any purpose other than that indicated and upon request will destroy the information and remove it from their records. Whilst this e-mail or attached documents may contain market information, this information is not provided as advice. Inenco do not accept any liability for any damages or losses of any kind suffered as a result of any action(s) taken as a result of the content of this e-mail or attachments. Any views or opinions presented are solely those of the author and do not necessarily represent those of Inenco Group Ltd. If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. No warranties or assurances are made in relation to the safety and content of this e-mail and any attachments. No liability is accepted for any consequences arising from it. If you have received this email in error please notify the sender by telephone on +44 (0)1253 785000.
  • Hello,

    You can use Process Monitor or File Monitor from Windows Sysinternals to see the file access including the status of the operations.

    I hope this helps,
    Edsel
    P.S.: The link to the attachment does not seem to work.
  • The machine we connect to is running Windows Server 2003 R2.

  • SOLVED:

    I found that the INI file was missing the "Java" section required for the Debugger to instantiate.