Automation Point Notification Manager SQL DB Errors

Products

• Automation Point

Issue/Introduction

After recently upgrading Automation Point APP to 11.5.3.3, the client started receiving VOX5666E, VOX5626E, VOX6124E, and VOX6129E errors, when attempting to use Notification Manager:

VOX 155716 CAAPDA01 VOX5660I TAPI dispatch thread is active.
VOX 155716 CAAPDA01 VOX5666E TAPI function lineInitializeEx error=0x80000048.
VOX 155716 CAAPDA01 VOX5122I Automation Point Notification Server started successfully.
VOX 142618 CAAPDA01 VOX5125I Command started: NMLOG. Cmd#: 1.
VOX 142618 CAAPDA01 VOX5630I Command finished: NMLOG. Cmd#: 1.
VOX 142618 CAAPDA01 VOX6126I nmfind.rex 00851977809 0000 Starting with parms: NAME('Name Surname') TELL('Testing from OPS to AP')
VOX 142618 CAAPDA01 VOX5125I Command started: NMIADDITEM. Cmd#: 2.
VOX 142618 CAAPDA01 VOX5626E NMIADDITEM command did not execute successfully. RC: 6056.
VOX 142618 CAAPDA01 VOX5630I Command finished: NMIADDITEM. Cmd#: 2.
VOX 142618 CAAPDA01 VOX6124E nmfind.rex 00851977809 0000 RC= 6056 Error= Could not get an item number from the database: VOX6056E SQL error: 17a8. See trace messages for details.
VOX 142618 CAAPDA01 VOX5125I Command started: NMLOG. Cmd#: 3.
VOX 142618 CAAPDA01 VOX5630I Command finished: NMLOG. Cmd#: 3.
VOX 142618 CAAPDA01 VOX6129E nmfind.rex 00851977809 0000 EXEC RETURNED RC= 6056 Started with parms: NAME('Name Surname') TELL('Testing from OPS to AP')
 

Resolution

Here are matters to consider upon occurrences of messages VOX5666E, VOX5626E, VOX6124E, and VOX6129E:
 . Was the NMFIND.rex changed?
 . Is this the first time that Notification Manager was used?
 . Was the AP server rebooted after an upgrade to patch 3?

In this instance, the client responded:
 . NMFIND.rex was not changed.
 . Notification Manager has been used on a limited basis prior to the last patch install.
 . The cycling of the AP DB server enabled Notification Manager to run.

So, the cycling of the AP DB server was needed to get Notification Manager to run.