Forum Replies Created

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts

  • stephen.rasey
    Participant

    \\ You can check the next run date for a task by selecting it in the configuration program. //
    That is what I did. I was asking if there was some other way I did not know of deep within the program.

    Maybe there is a hybrid approach. Create the Batch file to run a sequence of OSRun {task} statements, follow up with other Database processing tasks, then finally executing OSRunner to kick off the scheduled rerun.

    Eventually, we may want to move totally to batch or our own database driven runner so that we have frequent updates on databases with high recent activity.

    At the risk of changing the subject, I found this post

    Applying Credit Memo to an Invoice


    Reply #11044, #11050, #13801
    I may be facing a similar issue with a Vendor Credit difficult to find in the tables maintained by Version 2. Is there another thread where this is discussed more recently.


    stephen.rasey
    Participant

    BTW, we are running version 2.0.66.


    stephen.rasey
    Participant

    Perhaps the problem is that the OSRunner wasn’t shut down properly when the Windows Server rebooted?

    Is there a command line Command for Stopping OSRunner.exe.

    Maybe that Batch file of OSRun Tasks may be just the thing bootstrap OpenSync into a condition where OSRunner will execute successfully. Put OSRunner at the end of that sequence of OSRun batches. Worth a try. Thanks for the suggestion.

    How do you verify the next run date except by looking at the Task Properties?
    I verified that the most recent run date displayed in the OpenSync Task properties by looking at the OpenSync Database statistics form and the database history file.

    Here is another possible clue. The Windows Server was down when the first few tasks should have started in a sequence starting at 01:00, staggered every 4 minutes. The Windows Server came up, started OSRunner at 01:42. Task number 12 should have kicked off at 01:44. It did not. None of the remaining tasks did. Further more, at 01:00 the next day, OSRunner did not run the first or any other task until I Stopped and Started the service manually.

    I can see some logic in in setting up the system so that if Task_N doesn’t start, then task N+1 shouldn’t start. But the OpenSync Task Builder does not hint at any dependency between tasks except that they cannot run simultaneously.


    stephen.rasey
    Participant

    The Help file says that the background service is implemented in the OSRunner.EXE.
    In the next paragraph it say that QB API is single threaded, so only one task should run at any one time. ” The background service insures that tasks are sequentially executed. ”

    That implies that OSRun.EXE run via Windows Task manager on dozens of QB files is not as safe as running a sequence of Tasks using the Background Service of OSRunner. Is this correct?

    If I have two Windows Task Sched > OSRun tasks running simultaneously, will I be asking for trouble?

    My Windows Task Scheduler has in it
    “C:\Program Files (x86)\Synergration\OpenSync\OSRunner.exe” Without arguments.
    With a trigger “At Startup”.

    OSRunner does start. But it does not begin to process tasks until the Admin goes to the Home screen > Service Status block, which says “Running”, clicks the Stop, then clicks the Start.

    Is there, perhaps, any other Windows Task Schedule actions we should perform before launching OSRunner? Do we need to kickstart QuickBooks? If so, why do we not need to do that with an manual click Start.

Viewing 4 posts - 1 through 4 (of 4 total)