| Services Stuck "Starting" on Server 2012 R2 |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through April 13, 2018 ⬆ |
◄ ► |
| Author | Message | |||
| Steven McNeese New member Username: Smcneese Post Number: 1 Registered: 03-2018 |
I have installed the trial prior to purchasing licenses. After installation, I added an Android device but could not get it to connect to the NowSMS server. I noticed that the services were stuck in "Starting" and never got to the running state. I assume this is the issue. For grins I installed on a clean Windows 10 machine and the services are stuck "Starting" on this machine also. Anybody come across this and know what to do? Thank you, Steve | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5901 Registered: 08-2008 |
Hi Steve, Can you try uninstalling and rebooting...and confirm the services are no longer present. Then try a fresh install, but do not install to the default location. Instead, manually enter a short path name such as c:\nowsms If this does not fix the problem, uninstall again and try the installer in https://www.nowsms.com/download/nowsms20180221.zip -- Des NowSMS Support | |||
| Steven McNeese New member Username: Smcneese Post Number: 2 Registered: 03-2018 |
When I try to uninstall from the control panel/Programs and Features, I get a dialog that says Could not open INSTALL.LOG file. and it won't uninstall. | |||
| Steven McNeese New member Username: Smcneese Post Number: 3 Registered: 03-2018 |
I installed it originally to d:\program files (x86)\NowSMS. I tried running the UNWISE directly in that directory and it gives the same error message. However, the INSTALL.LOG file is in that directory. Running UNWISE as Administrator results in same error. Did you guys assume people would put it in C:\Program files (x86)\NowSMS? I need to get this uninstalled. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5902 Registered: 08-2008 |
The software used to create the installer is old (and unsupported). And it is having a problem with long directory paths...it converts them to 8.3 short names, and gets confused when 8.3 short name file mapping is disabled in the OS. Manual uninstall instructions to follow... | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5903 Registered: 08-2008 |
Manual uninstall instructions 1.) Remove services Open Command prompt window with run as administrator. Issue the following commands: sc delete nowsms sc delete nowmmsc 2.) If services still are present, reboot or terminate processes smsgwnt.exe and mmscnt.exe. 3.) Delete the directory NowSMS was installed in (default C:\Program files (x86)\NowSMS) 4.) The program shortcuts can be manually deleted -- Des NowSMS Support | |||
| Steven McNeese New member Username: Smcneese Post Number: 4 Registered: 03-2018 |
Des, That installer worked and the services are now starting. Thank you for your help. You should really replace the installer in your trial package with this new one. I had this problem a year ago when i was evaluating your solution and again now. Steve | |||
| Steven McNeese New member Username: Smcneese Post Number: 5 Registered: 03-2018 |
Des, I got my SIM cards in for my android phones. I have tried to configure but cannot get the device to connect to the NowSMS server. I have a working android with a working sim. I can text manually from the phone and it works. I installed the server on a fixed IP address machine at 192.168.1.8. I verified the services were now starting and running (after using custom installer sent by support. I added an android device with the option for remote and set the shared secret to ‘test’, the Route Name to Galaxy1 and phone number to 4693239780. On the Android I installed the software and configured the device for remote direct. It is connected to our wifi on 192.168.2.151 (wireless network, and we have rules on the firewall that move traffic between 192.168.1.* and 192.168.2.* networks) and I added the NowSMS Server address of 192.168.1.8, set the device name to Galaxy1 and set the shared secret to ‘test’. The handheld status says “Connecting….” And then says “ERROR – Invalid device name or secret”. I verified the secret was correct. What would be wrong with the device name? Does it need to machine something on the server? I confirmed that the device can ping the server at 192.168.1.8 and the server can ping the device at 192.168.2.151. No issues there. | |||
