| MessageID intermittently not provided by NowSMS |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through May 19, 2016 ⬆ |
◄ ► |
| Author | Message | |||
| David Balme New member Username: Davidbalme Post Number: 1 Registered: 09-2014 |
Hi Support, I have an intermittent problem with my NowSMS configuration. Intermittently NowSMS is not returning a MessageID when submitting via HTTP. Having browsed the forums I am unable to find a similar issue. Is this something you are familiar with? Apologies for the lack of detail, I am a support engineer fairly new to NowSMS. Many thanks. | |||
| David Balme New member Username: Davidbalme Post Number: 2 Registered: 09-2014 |
The HTML response is returned, but the MessageID value is missing. Any advice please? <HTML> <HEAD><TITLE>Message Submitted</TITLE></HEAD> <BODY bgcolor=#cce8ff> <p> Message Submitted <p> <a href="javascript:history.back()">Continue</a> <p> <pre><small> </small></pre> <p> </BODY> </HTML> | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5297 Registered: 08-2008 |
Hi David, What is the NowSMS version? I can't find any record of a similar problem, but I have a vague memory that I have seen this before. If you check the logs, is there any record of the message being submitted? I seem to recall this happening because of a disk problem...but that we had improved error handling so an error would be returned. By any chance, have you used any advanced settings to move any directories to a network drive? -- Des NowSMS Support | |||
| David Balme New member Username: Davidbalme Post Number: 3 Registered: 09-2014 |
Hi Des, Thank you for your response. We are running version v2012.02.16. We have no mapped network drives being used each NowSMS installation runs on its own server. Yes we do have records of the messages being submitted. Many thanks. David | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 8110 Registered: 10-2002 |
Hi, Unfortunately, we don't have any prior experience with this type of problem. To troubleshoot further, we need to look for any pattern, and collect relevant traces to confirm that the information is indeed missing. That said, we do have two possible theories. Searching back through our archives, we did find one case of this problem being reported previously. Upon further investigation, it was determined that the problem occurred around the same time every day. The customer had a procedure whereby they were restarting the NowSMS services once a day, and this situation would occur if a message was submitted during shutdown. The message was not actually processed. The other theory is speculative, and a long shot. Try adding EnableKeepAlive=No under the [SMSGW] header of SMSGW.INI. This will disable the use of Keep-Alive sockets on the HTTP server side of NowSMS, forcing any submitting client to create a new connection for each submission. This will slow down HTTP submission throughput a little (or a lot depending on the client), so after changing this setting, verify that your HTTP clients are not significantly impacted. -bn Bryce Norwood Now SMS/MMS Support | |||
| David Balme New member Username: Davidbalme Post Number: 4 Registered: 09-2014 |
Hi Des, Thank you for looking into that and highlighting the service restart. We were in fact getting the error at the same time each day, following the service restart. We will be modifying our restart procedure to give NowSMS more time to clear its queued messages before the service gets restarted. Many thanks. David | |||
| David Balme New member Username: Davidbalme Post Number: 5 Registered: 09-2014 |
Apologies, Thank you Bryce! | |||
