Difference between revisions of "NextCallRef error on Server Service startup"
Jump to navigation
Jump to search
| (4 intermediate revisions by the same user not shown) | |||
| Line 6: | Line 6: | ||
# Enter the following via your preferred database query tool: | # Enter the following via your preferred database query tool: | ||
| − | #:< | + | #:<pre>USE swdata</pre> |
| − | # This will | + | #:<pre>SELECT MAX(callref) FROM opencall</pre> |
| − | + | #:This will return the last call reference number used, please make a note of it. | |
| − | + | #Using the Interactive SQL tool, enter the the following, replacing the "####" with the callref value returned above: | |
| − | + | #:<pre>USE sw_systemdb; [RETURN]</pre> | |
| − | + | #:<pre>UPDATE system_counters SET count = #### WHERE name = 'nextcallreference'; [RETURN]</pre> | |
| − | |||
| − | |||
| − | |||
Latest revision as of 16:13, 20 July 2015
You may find that the Supportworks Server service is unable to start and the following error is displayed in the swserver logs:
[ERROR]:[5972] Invalid callref: an entry in opencall is greater than nextcallref!
To resolve this issue the following steps should be completed on the Supportworks Application database:<br\>
- Enter the following via your preferred database query tool:
USE swdata
SELECT MAX(callref) FROM opencall
- This will return the last call reference number used, please make a note of it.
- Using the Interactive SQL tool, enter the the following, replacing the "####" with the callref value returned above:
USE sw_systemdb; [RETURN]
UPDATE system_counters SET count = #### WHERE name = 'nextcallreference'; [RETURN]