shopcomputer Posted December 12, 2012 Report Share Posted December 12, 2012 I have noticed that for the past several months on Windows 2008r2 machines, the SnomOne service does not auto start on bootup, probably related to some windows updates. If I manually start it starts up fines, although it does take about 30 seconds to start, longer than it used to. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted December 12, 2012 Report Share Posted December 12, 2012 Thats not good. You should tell the PBX (once that it is running) to write the log to a file and then take a look at it. If there is really nothing in the log that hints at a PBX problem, the PBX service maybe depending on another service. Anything in the Windows event log? Quote Link to comment Share on other sites More sharing options...
shopcomputer Posted December 13, 2012 Author Report Share Posted December 13, 2012 4 servers same error. A timeout was reached (30000 milliseconds) while waiting for the snomONE PBX service to connect. The snomONE PBX service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted December 13, 2012 Report Share Posted December 13, 2012 How many CDR do you have in your cdr* directories??? What do you see when you start it with pbxctrl.exe --dir xxx --log 9? Quote Link to comment Share on other sites More sharing options...
johnlaurenz792 Posted May 5, 2013 Report Share Posted May 5, 2013 I have the same issue and deleting the CDR Directory did not help has anyone else experienced this and found a solution ? Quote Link to comment Share on other sites More sharing options...
Vodia support Posted May 5, 2013 Report Share Posted May 5, 2013 I have the same issue and deleting the CDR Directory did not help has anyone else experienced this and found a solution ? Can you try this article? http://wiki.snomone.com/index.php?title=PBX_Fails_to_Start the cmd line should give you more details on why it failed. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.