Jump to content
Telis Ltd

Windows pbxctrl.exe crashes immediately

Recommended Posts

Hi,

 

This a new install on a new server. The server is running Windows 2008 R2 Foundation 64bit and is running AD, DNS and DHCP. SnomOne 64bit is the only non-Microsoft software on the server. The snomOne PBX services starts but crashes immediately, the following is logged to the application event log. I completely rebuilt the server, reinstalled AD, DNS and DHCP and it is still happening.

 

If someone tell me where the logs should be I'll post those as well. Any ideas.

 

Log Name: Application

Source: Application Error

Date: 25/01/2011 11:12:32

Event ID: 1000

Task Category: (100)

Level: Error

Keywords: Classic

User: N/A

Computer: Server-MDH.mdh.local

Description:

Faulting application name: pbxctrl.exe, version: 0.0.0.0, time stamp: 0x4cb886f2

Faulting module name: pbxctrl.exe, version: 0.0.0.0, time stamp: 0x4cb886f2

Exception code: 0xc0000005

Fault offset: 0x000000000027243f

Faulting process id: 0x6ac

Faulting application start time: 0x01cbbc80c1b6ab6c

Faulting application path: C:\Program Files\snom\snomONE\pbxctrl.exe

Faulting module path: C:\Program Files\snom\snomONE\pbxctrl.exe

Report Id: 007f1273-2874-11e0-b312-b8ac6f992400

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

<System>

<Provider Name="Application Error" />

<EventID Qualifiers="0">1000</EventID>

<Level>2</Level>

<Task>100</Task>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime="2011-01-25T11:12:32.000000000Z" />

<EventRecordID>430</EventRecordID>

<Channel>Application</Channel>

<Computer>Server-MDH.mdh.local</Computer>

<Security />

</System>

<EventData>

<Data>pbxctrl.exe</Data>

<Data>0.0.0.0</Data>

<Data>4cb886f2</Data>

<Data>pbxctrl.exe</Data>

<Data>0.0.0.0</Data>

<Data>4cb886f2</Data>

<Data>c0000005</Data>

<Data>000000000027243f</Data>

<Data>6ac</Data>

<Data>01cbbc80c1b6ab6c</Data>

<Data>C:\Program Files\snom\snomONE\pbxctrl.exe</Data>

<Data>C:\Program Files\snom\snomONE\pbxctrl.exe</Data>

<Data>007f1273-2874-11e0-b312-b8ac6f992400</Data>

</EventData>

</Event>

Share this post


Link to post
Share on other sites

I also tried running the 32bit snomONE software on the same server with exactly the same result.

 

I could really use some help otherwise I'm going to have one unhappy customer on my hands!

Share this post


Link to post
Share on other sites

Thanks!

 

I had already tried that since my last post. I get a message on the command line

 

Starting up

 

And then I immediately get a dialog saying pbxctrl.exe has stopped working.

 

Problem signature:

Problem Event Name: APPCRASH

Application Name: pbxctrl.exe

Application Version: 0.0.0.0

Application Timestamp: 4cb886f2

Fault Module Name: pbxctrl.exe

Fault Module Version: 0.0.0.0

Fault Module Timestamp: 4cb886f2

Exception Code: c0000005

Exception Offset: 000000000027243f

OS Version: 6.1.7600.2.0.0.272.33

Locale ID: 2057

Additional Information 1: c6fa

Additional Information 2: c6fa2117ce5efaa27981222b8ff557f7

Additional Information 3: 5f2d

Additional Information 4: 5f2de1d9670c32d34830fe6103767e83

 

Also no log is generated. I also edited the pbx.xml file with a different log file name containing a $ as detailed at the bottom of this page http://wiki.snomone.com/index.php?title=Quick_Installation.

 

One thing I did this time and last time (I installed this server twice due to this issue) was use Windows updates to install .net4 and the client profile .net4 before I did the snomONE install, could this be the issue?? Also the server is Windows 2008R2 Foundation edition, maybe that is the issue (seems unlikely). The other thing is it's 64bit.

Share this post


Link to post
Share on other sites

No, the PBX is not using .net (at all). Maybe you are a CRLF victim or something went wrong with the download.

 

I downloaded http://www.pbxnsip.com/snomone/beta/win32/pbxctrl-2011-4.2.0.3979.exe and I get this:

 

PBX>dir
...
01/24/2011  02:32 PM         9,672,704 pbxctrl-2011-4.2.0.3979.exe
PBX>.\pbxctrl-2011-4.2.0.3979.exe --dir . --no-daemon --log 9 --no-check-ports

 

Then the PBX starts up. I also have a couple of ports blocked (5060 for my soft phone), so the --no-check-ports was neccessary on my system. OF course for a real server operation, I would have to make sure that noone else takes the SIP port.

 

Also check if you have the same size, if the size is different there must be a problem with the download.

Share this post


Link to post
Share on other sites

OK, I think fixed this :)

 

I manually started the Microsoft .NET Framework NGEN v4.0.30319_X64 service (which should normally start and then stop). After doing this the snomONE service started to work. I guess something was wring with the JIT'er?

 

Anyway no doubt this will be useful to someone.

Share this post


Link to post
Share on other sites

No, it's not a fix. Even after the service appeared to start I got no logs or response on from a web browser on 127.0.0.1. The service was running in the sense that pressing the refresh button in the services applet reported it as running.

 

After a reboot the problem returned exactly as before.

 

Hmmm...

 

What are the exe's dependencies?

Share this post


Link to post
Share on other sites

OK, I used dependency walker to find the exe's dependencies (it deosn't have many!) and I was missing only one which was also missing on a working machine. So it's not that.

 

However I now get output from the exe, which looks as if it's not binding to a the right IP/ports. Can someone help me interpret this please.

 

C:\Program Files\snom\snomONE>pbxctrl.exe --dir . --no-daemon --log 9 --no-check

-ports

Starting up

[7] 20110125152227: syslog is disabled on the PBX

[1] 20110125152227: Starting up version 2011-4.2.0.3958

[8] 20110125152227: Found interface on 192.168.160.1 with netmask 255.255.255.0

[8] 20110125152227: Found interface on 127.0.0.1 with netmask 255.0.0.0

[8] 20110125152227: Found interface on fe80::f451:5da9:ab93:b9bb with netmask ::

 

[8] 20110125152227: Found interface on ::1 with netmask ::

[7] 20110125152227: Found time zones HST AKDT AKST PDT PST MDT MST CDT CST2 EDT

EST ADT AST NDT NST BST CET GMT+2 TUR GMT+3 GMT+4 GMT+5 GMT+6 GMT+7 GMT+8 GMT+9

CST CAT IST AUS1 AUS2 AUS3 AUS4 AUS5 AUS6 NZST CHAST GMT

[8] 20110125152227: Timer frequency is 500 us

[1] 20110125152227: Working Directory is C:\Program Files\snom\snomONE

[7] 20110125152227: UDP: Opening socket on 0.0.0.0

[7] 20110125152227: UDP: Opening socket on [::]

[8] 20110125152227: No from address for sending text email

[5] 20110125152227: Starting threads

[7] 20110125152227: TCP: Opening socket on 0.0.0.0:80

[7] 20110125152227: TCP: Opening socket on [::]:80

[7] 20110125152227: TCP: Opening socket on 0.0.0.0:443

[7] 20110125152227: TCP: Opening socket on [::]:443

[0] 20110125152227: Could not bind socket to port 389 on IP 0.0.0.0

[0] 20110125152227: FATAL: Could not open TCP port 389 for HTTP/HTTPS

[0] 20110125152227: Could not bind socket to port 389 on IP [::]

[0] 20110125152227: FATAL: Could not open TCP port 389 for HTTP/HTTPS

[7] 20110125152227: UDP: Opening socket on 0.0.0.0:161

[7] 20110125152227: UDP: Opening socket on [::]:161

[7] 20110125152227: UDP: Opening socket on 0.0.0.0:69

[7] 20110125152227: UDP: Opening socket on [::]:69

[7] 20110125152227: UDP: Opening socket on 0.0.0.0

[5] 20110125152227: Set thread affinity to 1

[9] 20110125152227: Resolve 1: discover 1.2.3.4

[7] 20110125152227: UDP: Opening socket on [::]

[8] 20110125152227: Trunk 1 (PSTN Gateway) is associated with the following addr

esses: 1.2.3.4

[7] 20110125152227: UDP: Opening socket on 0.0.0.0:5060

[8] 20110125152227: Joined multicast group 224.0.1.75

[7] 20110125152227: UDP: Opening socket on [::]:5060

[7] 20110125152227: TCP: Opening socket on 0.0.0.0:5060

[7] 20110125152227: TCP: Opening socket on [::]:5060

[7] 20110125152227: TCP: Opening socket on 0.0.0.0:5061

[7] 20110125152227: TCP: Opening socket on [::]:5061

Share this post


Link to post
Share on other sites

Looks like the LDAP port (389) is in use

 

Solutions:

  • Either you make sure that this port is not in use before starting the PBX. Or
  • Open the pbx.xml file(in the PBX install folder), search for 389, change it, save the file and restart the service.

Share this post


Link to post
Share on other sites

It doesn't use .NET at all?? But it asks you to download the .NET4 framework client profile if you don't have it when you install it!

 

Strange. You never know what kind of libraries are sucked in, obviously... Anyway, good to know!

Share this post


Link to post
Share on other sites
Looks like the LDAP port (389) is in use

 

Solutions:

Either you make sure that this port is not in use before starting the PBX. Or

Open the pbx.xml file(in the PBX install folder), search for 389, change it, save the file and restart the service.

 

Thank you, it is now working. The server is running AD (i.e. is a domain controller) and these use 389 LDAP by default. I moved the port used by snomONE to 8389 using the pbx.xml file.

Share this post


Link to post
Share on other sites
Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...