Voice messages not written to IWM610
Modified on: Mon, 15 Apr 2024 6:54 PMDSPMSG QSYSOPR
Checking IWM610, records for 1 user were the last added to the file and no further records were being added when I refreshed my SQL search
Notes from Ian Spottiswood:
When this problem happens (malformed IWM610.DATA610, where the string of data is corrupt or incomplete), we need to delete the message from the Voice SQL Server database.
- Log onto the “RDP – VMWWMSVOICELIVE” tile in Greene King’s portal.
Click the Start button, then the “down” arrow to show all apps:
Open SQL Server Management Studio:
Ensure that “SQL Server Authentication” is selected and login using credentials below (see VPN Profiles/Greene King folder in Sharepoint for details):
User: sa
Password: 1nd1g0v0!ce
Password: 1nd1g0v0!ce
Expand Databases – System Databases – RenovotecIndigoDatabase – Tables – click dbo.IndigoInterfaceMessages.
The results panel (bottom middle) is usually blank, but if a persistent record is continually passing through to WMS, it will show in that panel. Note the Id and type a “delete” sql command into the top panel, e.g.
Delete from dbo.IndigoInterfaceMessages where Id = xxxxxxx
This should stop that message from continually being pushed to WMS.
MSGW will need answering in WMS though, but the next valid Voice message should come through ok.