Help: Critical Failure.

Help: Critical Failure. SearchSearch
Author Message
Anonymous
 
Posted on Tuesday, June 22, 2004 - 06:00 pm:   

I'm testing NowSms with Sierra Aircard750 for a month. But I have a very very critical problem.
NowSms goes panic, once if it can not send a message. Generally, it happens every three days.
In that case, I have to reboot my PC to restart the service. Without rebooting, I can not send any message any more.

Help me.....

Sim

Following are the error in my SMSOUT.log
======

004-06-21 17:49:20,60A28B68.req,xxx.yyy.xxx.yyy,7775459876,OK -- Sierra Wireless AirCard GPRS Modem,Binary=1;DCS=4;UDH=------
2004-06-21 17:53:02,60A28B69.req,xxx.yyy.xxx.yyy,7775459876,OK -- Sierra Wireless AirCard GPRS Modem,Binary=1;DCS=4;UDH=------
2004-06-21 18:00:06,60A28B6A.req,xxx.yyy.xxx.yyy,7775459876,OK -- Sierra Wireless AirCard GPRS Modem,Binary=1;DCS=4;UDH=0605040B8423F0;Data=------
2004-06-21 18:06:36,60A28B6B.req,xxx.yyy.xxx.yyy,7775459876,Retry Pending - ERROR - Modem Response (2): +CMS ERROR: 500 -- Sierra Wireless AirCard GPRS Modem
2004-06-21 18:06:37,60A28B6B.req,xxx.yyy.xxx.yyy,7775459876,Retry Pending - ERROR - Modem Response (2): +CMS ERROR: 500 -- Sierra Wireless AirCard GPRS Modem
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2890
Registered: 10-2002
Posted on Tuesday, June 22, 2004 - 08:23 pm:   

Hi Sim,

Does restarting the NowSMS service make a difference, or do you have to reboot the PC?

If you have to reboot the PC, it sounds like there is a problem with the Sierra card.

I've noticed that the Sierra card likes to generate "CMS ERROR 500" when it loses its GSM signal, so if you can do anything to strengthen the signal, that would be a good idea.

I've also noticed that "SMS over GPRS" (set under "Properties" for the modem on the SMSC page) works better with the Sierra card, but it depends on whether or not your operator supports this.

-bn
Anonymous
 
Posted on Tuesday, June 22, 2004 - 10:36 pm:   

Hi, Bryce.

Without rebooting the PC, it's hard to fix it.
During the consecutive occurence of ERRORS, I started Airwatcher to check the reception of signal. It was fine.
Personally, I suspect that the interface between NowSMS and Modem might be interfered or disconnected (I means not the problem of modem)

Another awkward thing that I found is that
I switched the mode form "SMS over GSM" to "SMS over GPRS". but the same critical problemed happened again in 5 hours.
At that time, I switched back to "SMS over GSM" and then messages began to be sending out. However I found funny thing.
I tested modem with test button on the "SMSC" folder.
These error messages poped up, even though the NowSMS was able to send messages(it's working)


Help me...


=======
"Unable to initialize modem: Error 80000018 from lineGetID"

and then,

"Unable to access modem, enusre that it is powered on and passes diagnostic tests."

and then

"Modem is not functioning properly. It will be removed from the selected list."

=====




Anonymous
 
Posted on Wednesday, June 23, 2004 - 06:03 pm:   

I can't explain this situation.

If the result of modem test on "SMSC" is fine, NowSMS do not send any message and keep showing error.

Normally, These message are poping up, whenever I test the modem. And NowSMS are keeping working.

=======
"Unable to initialize modem: Error 80000018 from lineGetID"

and then,

"Unable to access modem, enusre that it is powered on and passes diagnostic tests."

and then

"Modem is not functioning properly. It will be removed from the selected list."

=====

Help...


Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2918
Registered: 10-2002
Posted on Friday, June 25, 2004 - 07:26 pm:   

I'm confused too.

If you test the modem in NowSMS, it has to stop the service in order to test the modem.

The "Unable to initialize modem: Error 80000018 from lineGetID" means that Windows refuses to initialise the modem. Unfortunately, this error could mean that the modem is not responding, or it could mean that the modem is already open by another application.

Let me suggest that you try configuring NowSMS to talk to the modem by going to the COM port directly, instead of going through the named modem driver. (With the Sierra card there is no functionality lost by going to the COM port directly.)

Then, enable the debug log by manually editing SMSGW.INI, and under the [SMSGW] section header, add Debug=Yes. Then restart the NowSMS SMS Gateway service. NowSMS will produce an SMSDEBUG.LOG file as it runs.

Let's see what is getting recorded in that file when you start experiencing problems.

Also, are you running v5.50? If not, I would suggest updating to that version. I'm not sure exactly when we implemented the change, but I know that in v5.50, if we receive an error on 5 consecutive attempts to submit a message, we will take action to re-init the modem. This may or may not help your situation, but it would be helpful to see what happens in the SMSDEBUG.LOG when NowSMS attempts to perform this re-init.

The SMSDEBUG.LOG file might be large. If you don't want to post it here, you can e-mail it to nowsms@now.co.uk.