Greene King
-
Voice messages not written to IWM610
DSPMSG 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 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.
-
Greene King Voice License Key install Guide
This is a guide for installing a New license Key for Greene King Voice into instances.
-
RDT - Unable to force log off
GK reports when their RDT user is unable to reset or force log off from a Resource. To resolve this, we must perform the following steps: Use command WRKUSRJOB (Example: WRKUSRJOB ZTLESNIAB) Enter 5 (Work with), then option 1 to dispaly job status. With this, you'll be able to see since when was the job active. Go back to Work with User Jobs screen. Put 4 (End) under option then press F4. This will display End Job (ENDJOB) screen. In the End Job (ENDJOB) screen, change the 'How to end' field from *CNTRLD into *IMMED Go to Manage Resource and check that option to Force Log off is now available. Note: If user is still unable to force log off from this part, we need to update Active Flag in IWM280 for user from 1 to 0. Sample ticket: INC-19812