OpenSync

Home Forums OpenSync OSRunner will not start after latest Win 10 update

This topic contains 4 replies, has 3 voices, and was last updated by  Yudel Rosales 5 hours, 20 minutes ago.

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #67454

    jkieburtz
    Participant

    I just wanted to hop on the thread about OSRunner not starting up but somehow my Reply ended up creating illegal HTML (sorry about that). Here are a couple of additional notes. This happened right after I upgraded to Win 10 Build 2004 so I also think it’s related to that. In particular Event Viewer shows .NET Runtime error Event ID 1023:

    Application: OSRunner.Exe Framework Version: v4.0.30319 Description: The process was terminated due to an internal error in the .NET Runtime at IP 749698D6 (74650000) with exit code 80131506.

    Followed by Application Error Event ID 1000:

    OSRunner.Exe
    3.0.0.1
    5da4d144
    clr.dll
    4.8.4220.0
    5f03aaa0
    80131506
    003198d6
    2364
    01d6867871890e16
    C:\Program Files (x86)\Synergration\OpenSync\OSRunner.Exe
    C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
    609c3cc9-1438-4a94-a1f7-3c44bd35d169

    #67455

    Yudel Rosales
    Keymaster

    We will update the .net framework and release a new version.

    #67479

    jkieburtz
    Participant

    Any idea when the compile will happen? I end up having to do a manual refresh about 10 times per day.

    Thanks, Jim

    #67502

    Patricia
    Participant

    Reporting the same problem: OSRunner not loading.
    Will this fix be expedited? Our users also have to run the Tasks manually every 15 minutes or so….

    #67510

    Yudel Rosales
    Keymaster

    Sorry about that. You can use the windows scheduler along with OSRun.exe and you can put the task name on the argument of the task windows scheduler and it will run it for you.

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

You must be logged in to reply to this topic.