locked
sftrbt.exe error 53259 during stop monitoring process in the sequencer RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    hi

    using app-v sequencer 4.6 x64 and trying to sequence project beta 2010.

    After the installation has been done, I stop monitoring and get this message:

    error: there was a problem processing reboot tasks. please refer to the reboot.log

    and this error message

    error during task execution (error code 53259)

    Nothing has been captured.

    sft-seq-log

    [04/08/2010 14:41:38 VRB RTSK] sftrbt process failed - return code 2.
    [04/08/2010 14:41:38 ERR RTSK] Error during task execution (error code 53259).

    any idea?

    thx

    Thursday, April 8, 2010 12:45 PM

Answers

  • Question
    Sign in to vote
    1
    Sign in to vote
    For me, just as an FYI, I logged off and logged on as an administrator and it worked.  I initially selected the program and set it to Run As, and selected an Domain Network Administrator account, but that gave the error, when I logged on, as that Domain Administrator account, with local administrator permissions, I was able to get it to work.
    • Marked as answer by Oli D. _ Tuesday, September 6, 2011 3:19 PM
    Friday, June 4, 2010 5:43 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello,

    There are additional log-files addressing problems with reboot problems. See this technet-page;

    http://technet.microsoft.com/en-us/library/cc843645.aspx

    You can probably from there see more specifically what happens and perhaps be able to determine what causes the issue.

    /Znack

    Thursday, April 8, 2010 12:52 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    hi

    I've checked all log files and I did not found any hints.

     

    But the application does not want a reboot....

     

    strange

    Thursday, April 8, 2010 12:58 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    any hints?
    Tuesday, April 13, 2010 5:51 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello,

    Inorder to resolve this I would want to try to locate what it tries todo when rebooting.

    /Znack

    • Marked as answer by Oli D. _ Friday, April 30, 2010 8:03 AM
    • Unmarked as answer by Oli D. _ Tuesday, September 6, 2011 3:19 PM
    Tuesday, April 13, 2010 8:28 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello,

    Inorder to resolve this I would want to try to locate what it tries todo when rebooting.

    /Znack

    Hi

     

    The app does not want to reboot. That is the strange point. After finishing the capture, I get this error message.

    It happens when I tried to sequence project 2010 or visio 2010 beta.

    Tuesday, April 13, 2010 8:38 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hello,

    I have no idea if the application tries to do something during a reboot - but if you say it doesn't, it probably doesn't.

    The sequencer thinks there is a pending reboot and pending tasks - my recommendation was to identify what those are.

    /Znack
    Tuesday, April 13, 2010 9:30 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Update:

     

    I have on my sequencing machine the SCCM Agent running. Stopping this agent before starting the monitoring seems to solve my error.

     

    I'll test that out with other apps.

     

    Cheers

    • Proposed as answer by znack Tuesday, April 20, 2010 2:18 PM
    • Unproposed as answer by Oli D. _ Tuesday, September 6, 2011 3:19 PM
    Tuesday, April 20, 2010 2:01 PM
  • Question
    Sign in to vote
    1
    Sign in to vote
    For me, just as an FYI, I logged off and logged on as an administrator and it worked.  I initially selected the program and set it to Run As, and selected an Domain Network Administrator account, but that gave the error, when I logged on, as that Domain Administrator account, with local administrator permissions, I was able to get it to work.
    • Marked as answer by Oli D. _ Tuesday, September 6, 2011 3:19 PM
    Friday, June 4, 2010 5:43 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    @Matthew:

     

    that THE solution: logged on as a local user, not a domain user, solved that problem.

     

    Thx!

    • Marked as answer by Oli D. _ Tuesday, September 6, 2011 3:18 PM
    • Unmarked as answer by Oli D. _ Tuesday, September 6, 2011 3:19 PM
    Tuesday, September 6, 2011 3:18 PM