OpenSync

Home › Forums › OpenSync › WVD Windows 10 Task Scheduler Invalid OLEVERB structure (0x80040000)

This topic contains 4 replies, has 2 voices, and was last updated by  Yudel Rosales 6 months, 3 weeks ago.

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • August 5, 2020 at 2:48 pm #67362

    rferrilli
    Premium Member

    I am a support client and I am stuck. Any advice would be appreciated.

    The sync works when I manually run it from Open Sync Configuration screen.
    When I manually execute the .bat file that contains the following command
    “C:\Program Files (x86)\Synergration\OpenSync\OSRun.exe” RefreshQuickBooks
    the sync works.
    When I configure the WVD Windows 10 Task Scheduler to run the .bat file with this command
    “C:\Program Files (x86)\Synergration\OpenSync\OSRun.exe” RefreshQuickBooks
    the Task Scheduler gives this error
    Invalid OLEVERB structure (0x80040000)
    Open Sync Logs give this error
    20020-08-05 18:37:54 0 OpenSync:Runner OSRun – RefreshQuickBooks
    2020-08-05 18:37:54 0 OpenSync:Runner Runner: Start task RefreshQuickBooks
    2020-08-05 18:37:54 0 WorkTracker Init
    2020-08-05 18:37:54 0 WorkTracker Starting task: RefreshQuickBooks
    2020-08-05 18:37:54 0 BackWorker ExecuteBackground Begin
    2020-08-05 18:38:03 -2147220472 BackWorker MakeQbConnection Error: Could not start QuickBooks. Retrying connection
    2020-08-05 18:38:41 -2147220472 BackWorker MakeQbConnection Error: Could not start QuickBooks. Retrying connection
    2020-08-05 18:39:19 -2147220472 BackWorker MakeQbConnection Error: Could not start QuickBooks.
    2020-08-05 18:39:19 -1 WorkTracker Could not start QuickBooks.: -2147220472
    2020-08-05 18:39:19 0 OpenSync:Runner ErrorExit: Could not start QuickBooks.: -2147220472

    August 6, 2020 at 11:20 am #67363

    rferrilli
    Premium Member

    This is the log using the OSRunner Scheduler which failed too. Manual run task sync under the same user seems to be working fine. Any advice is appreciated.

    2020-08-05 19:11:22 0 OSRunner Startup
    2020-08-06 03:00:01 0 WorkTracker Run Task RefreshQuickBooksToFERRAZ-SQL-DataLake
    2020-08-06 03:00:01 0 WorkTracker Starting task: RefreshQuickBooksToFERRAZ-SQL-DataLake
    2020-08-06 03:00:01 0 BackWorker ExecuteBackground Begin
    2020-08-06 03:00:24 0 BackWorker MakeQbConnection: Connection Opened
    2020-08-06 03:00:39 -2147467259 BackWorker ExecuteBackground Error: Login timeout expired
    2020-08-06 03:00:41 0 BackWorker CloseQbConnection: Close Connection
    2020-08-06 03:00:41 -1 WorkTracker Login timeout expired:-2147467259
    2020-08-06 06:00:01 0 WorkTracker Run Task TransactionDetail_All
    2020-08-06 06:00:01 0 WorkTracker Starting task: TransactionDetail_All
    2020-08-06 06:00:01 0 BackWorker ExecuteBackground Begin
    2020-08-06 06:00:11 0 BackWorker MakeQbConnection: Connection Opened
    2020-08-06 06:00:12 0 BackWorker GetReport
    2020-08-06 06:00:27 -2147467259 BackWorker ExecuteBackground Error: Login timeout expired
    2020-08-06 06:00:28 0 BackWorker CloseQbConnection: Close Connection
    2020-08-06 06:00:29 -1 WorkTracker Login timeout expired:-2147467259

    August 6, 2020 at 11:24 am #67364

    rferrilli
    Premium Member

    Actually refresh from WVD to Azure Serverless SQL ended in this error.
    2020-08-06 15:17:51 0 OSRunner OSRunner Terminating
    2020-08-06 15:17:59 0 OpenSync:Runner Runner: Start task RefreshQuickBooksToFERRAZ-SQL-DataLake
    2020-08-06 15:17:59 0 WorkTracker Init
    2020-08-06 15:17:59 0 WorkTracker Starting task: RefreshQuickBooksToFERRAZ-SQL-DataLake
    2020-08-06 15:17:59 0 BackWorker ExecuteBackground Begin
    2020-08-06 15:18:15 0 BackWorker MakeQbConnection: Connection Opened
    2020-08-06 15:18:15 0 BackWorker Refresh All
    2020-08-06 15:18:15 0 BackWorker Processing table: Account
    2020-08-06 15:18:36 0 BackWorker Processing table: Bill
    2020-08-06 15:18:37 0 BackWorker Processing table: Bill Payment
    2020-08-06 15:18:38 0 BackWorker Processing table: Charge
    2020-08-06 15:18:39 0 BackWorker Processing table: Check
    2020-08-06 15:18:48 0 BackWorker Processing table: Class
    2020-08-06 15:18:48 0 BackWorker Processing table: Credit Card Charge
    2020-08-06 15:18:49 0 BackWorker Processing table: Credit Card Credit
    2020-08-06 15:18:49 0 BackWorker Processing table: Credit Memo
    2020-08-06 15:18:56 0 BackWorker Processing table: Customer Message
    2020-08-06 15:18:56 0 BackWorker Processing table: Customer Type
    2020-08-06 15:18:57 0 BackWorker Processing table: Terms
    2020-08-06 15:18:57 0 BackWorker Processing table: Deposit
    2020-08-06 15:19:12 0 BackWorker Processing table: Entity
    2020-08-06 15:19:13 0 BackWorker Processing table: Employee
    2020-08-06 15:23:13 -2147467259 BackWorker ExecuteBackground Error: Login timeout expired employeepayrollinfo err#:-2147467259 field:ListID vbcrlf & (Please reconnect to your database server and try again.)
    2020-08-06 15:23:14 0 BackWorker CloseQbConnection: Close Connection
    2020-08-06 15:23:14 -1 WorkTracker Login timeout expired employeepayrollinfo err#:-2147467259 field:ListID vbcrlf & (Please reconnect to your database server and try again.):-2147467259
    2020-08-06 15:23:14 0 OpenSync:Runner ErrorExit: Login timeout expired employeepayrollinfo err#:-2147467259 field:ListID vbcrlf & (Please reconnect to your database server and try again.):-2147467259

    August 6, 2020 at 11:47 am #67365

    rferrilli
    Premium Member

    (Please reconnect to your database server and try again.):-2147467259 – This may be related to an Azure health event. Please focus on the original issue. Identified an Azure issue happening at the same time as the refresh.

    August 13, 2020 at 11:26 am #67380

    Yudel Rosales
    Keymaster

    increase time out in your azure database

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

You must be logged in to reply to this topic.

Copyright © 2013 Synergration Inc