Difference between revisions of "NextCallRef error on Server Service startup"
Jump to navigation
Jump to search
| Line 6: | Line 6: | ||
# Enter the following via your preferred database query tool: | # Enter the following via your preferred database query tool: | ||
| − | #:< | + | #:<pre>select MAX(callref) from opencall</pre><br\> |
| − | # This will | + | #: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></code> | |
| − | |||
| − | |||
| − | |||
| − | |||
Revision as of 15:14, 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:
select MAX(callref) from opencall
<br\>- 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]<\pre>