| NowSMS no longer sends SMS text messages |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through January 23, 2007 ⬆ |
◄ ► |
| Author | Message | |||
| Lee Whalen New member Username: Law Post Number: 1 Registered: 12-2006 |
Hello all, I've got a bit of a problem I was hoping you could assist me with. Ever since yesterday, our installation of NowSMS has appeared to not be able to send SMS text messages at all. We generally send it via the web interface, and it has worked well in the past. However, the interface is showing "The message has been sent", but the SMS never hits the phone. I've enabled the debugging log, and there are several messages to the tune of: "2006-12-19 15:24:52,System,,USB Falcom Samba MC75,Modem Failure -- Unable to access modem, ensure that it is powered on and passes diagnostic tests." However, when I stop the NowSMS service, go to the modem via the NowSMS app, and click "test", the app returns "modem successfully tested". I then restart the service but the messages still do not get through. Can someone help me with this issue please? Many thanks, --Lee Whalen | |||
| Malcolm - Now Support New member Username: Malcolm Post Number: 37 Registered: 12-2006 |
Hi Lee, That is very strange. The first thing I would suggest is to try updating to the 2006.10.31 version. More details can be found in the "What's New" section of our web site, but basically if you already have NowSMS 2006, you can just redownload the evaluation version from our web site and install it over your existing copy. This version does have additional logic to try to recover from modem failures. Moving beyond this, it is very unusual for the "Test" button to work, and the actual service to fail. To diagnose this problem, you need to enable the "SMSDEBUG.LOG", which can be enabled on the "Serial #" page of the configuration dialog. Post an excerpt of this log, and that should tell us more about the nature of the problem. -- Malcolm Now Wireless Support | |||
| Lee Whalen New member Username: Law Post Number: 2 Registered: 12-2006 |
Hey Malcom, thanks for getting back to me! Yes, I already enabled the debug log. I also removed the USB extender cable that we were using (per the advice of another thread) to eliminate the possibility of a faulty USB cable. Unfortunately, NowSMS behaves the same. Here's the relevant excerpt from smsdebug.log: 16:40:39:734 [2] ReceiveModemCommand: Error - 3E4 16:41:23:968 [2] HammerNonResponsiveModem: FAILED 16:41:23:968 [2] ThreadProcessModem: Before ModemRelease - USB Falcom Samba MC75 16:41:23:968 [2] ThreadProcessModem: After ModemRelease - USB Falcom Samba MC75 16:46:23:968 [2] ThreadProcessModem: Before ModemAllocate - USB Falcom Samba MC75 16:46:23:968 [2] ThreadProcessModem: After ModemAllocate - USB Falcom Samba MC75 - OK 16:46:23:968 [2] ThreadProcessModem: Re-initializing modem: USB Falcom Samba MC75 ... 16:46:23:968 [2] HammerNonResponsiveModem: Begin 16:46:50:343 [2] ReceiveModemCommand: Error - 3E4 16:47:25:531 [2] ReceiveModemCommand: Error - 3E4 16:47:28:578 [2] ReceiveModemCommand: Error - 3E4 Many thanks! --Lee | |||
| Lee Whalen New member Username: Law Post Number: 3 Registered: 12-2006 |
Also, were I to reinstall over with the latest eval copy, would it automatically redetect my license? --Lee | |||
| Malcolm - Now Support New member Username: Malcolm Post Number: 47 Registered: 12-2006 |
Hi Lee, Yes, the latest eval copy will automatically detect the license (if it does not because it is an older license, it will either present a warning or tell you that it is installing as an eval). The "3E4" error looks ominous, but unfortunately it doesn't mean anything ... it is just a timeout. From the brief snippet of the log, I am puzzled that there are no other errors mentioned before the log says "HammerNonResponsiveModem". Normally there would be some other error reported before this action is triggered ... the message would start with "OpenDevice". It is also strange that "HammerNonResponsiveModem" is triggered immediately (same timestamp), as we begin the process of re-intializing the modem. I would suggest that you try removing the modem from the system (remove the modem from the Phone & Modem options in the Windows Control Panel), and then try re-adding it. If that doesn't work, let me see a longer snippet from the log file, begining with startup and the first attempts to init the modem. -- Malcolm Now Wireless Support | |||
| Lee Whalen New member Username: Law Post Number: 4 Registered: 12-2006 |
Excellent, I'll do that right now. I could send you the full logfiles if you'd like. What's your email address? Mine's law AT nellymoser IHATESPAMDOT com. Feel free to remove and replace the obvious for the 'real' address 8*) Many thanks! --Lee | |||
| Lee Whalen New member Username: Law Post Number: 5 Registered: 12-2006 |
Excellent news! Applying the latest version works like a charm! Thanks again for all your assistance! --Lee | |||
