Service got signal to stop: 22

[qasker]

Hi,

I'm running 3 different 3CX Phone System v12 systems on Windows Server 2012. On one of them the Phone System service sometimes stops. All systems are identical, apart from 3CX configuration. I can't find any leads on why this happens.

• Event log shows: Service got signal to stop: 22
• Service got signal to stop: stop service

After those 2 events there is an APPCRASH event:

Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: 3CXPhoneSystem.exe
P2: 12.0.33463.0
P3: 528e028c
P4: 3CXPhoneSystem.exe
P5: 12.0.33463.0
P6: 528e028c
P7: 40000015
P8: 00000000002c7091
P9:
P10:

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_3CXPhoneSystem.e_9dd94d7dc9cd8e11ed4f905d4ddfcb413481c77_a5e67526

Analysis symbol:
Rechecking for solution: 0
Report Id: f73500ab-92f5-11e3-9408-8ad02cc861e5
Report Status: 4
Hashed bucket:

Our Icinga system alerts me when the service is stopped, and I can start it manually without any problems.

Does anyone know what I can do about these occasional crashes? I have attached the Report.wer file of the APPCRASH event.

 

[cobaltit]

What is your definition of identical? Clearly something is amiss. So it could be a difference in what Windows Updates are installed, or what other software is on the system, or possibly a hardware issue. If the systems are indeed identical, I would probably start with running memtest to make sure you don't have a bad stick of memory.

Also, you didn't make any mention of how long these systems have been running. If these are fresh installs, then perhaps a reinstall is in order.

 

[qasker]

Thank you for your reply.

The systems are running on Windows Server 2012 virtual machines on Citrix XenServer and are provisioned from our Windows Server 2012 templates (gold images). They are all running 3CX dedicated (no other network services) and are at the same Windows and 3CX patch level.

 

[jdhornberger]

Having the same problem here, except I have Windows Server 2012 R2 on Hyper-V environment. Just happened this morning and all I had to do was to start the service again. Would be nice to know why it happens so users don't get cut off in the middle of a phone call.