.BAD file extension Need Help and Some Slution I found

.BAD file extension Need Help and Some Slution I found SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through June 21, 2007 » .BAD file extension Need Help and Some Slution I found « Previous || Next »
Author Message
zeeshan rasheed
New member
Username: Sakaz

Post Number: 3
Registered: 03-2007
Posted on Thursday, March 29, 2007 - 11:16 pm:   

Hi Bryce.
I have already write two times but no body response to my message but i have solved my problem myself and find out the problems. Now i am getting the problem with one thing. sometime when i received message through my GSM Mobile Modem (T68i) and process the received message with HTTP script they go to the SMS-IN Directory with .BAD extension. I need to know why but i have gone through the forum and checked SMSDEBUG and LOG files and found the error 500 series. So means it is communication problem with the Modem.

But i found the point where is the exact problem. When i receive SMS more then 50 Char then it goes to SMS-IN directory with .BAD exantion and if i receive SMS message with 10 or 20 chars. then it goes well in the Q Driectory with .REQ Extension.

Can you or anybody help me how i can resolve the problem or if there is any upgrade version of Nowsms i am using v2006. But i checked many time with short message and it does work fine.

I hope this time anybody will reply me

Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 7039
Registered: 10-2002
Posted on Wednesday, April 04, 2007 - 08:40 pm:   

Hi Shan,

If you have messages in the SMS-IN directory with a ".BAD" extension, this means that we posted them to your 2-way command, but the 2-way command returned an HTTP error response.

So if you notice that there is messages of particular lengths encounter a problem, it is likely a problem with your 2-way command script handling longer messages.

You can rename the ".BAD" file to a ".IN" file to force it to be reprocessed.

Also, I'd suggest enabling the SMSDEBUG.LOG ... then you can look at this log to see the exact HTTP request that NowSMS is making when it passes the message to your script. That way you can make some tests by issuing the similar requests to your script outside of NowSMS for troubleshooting.


Login Login / Register Logout Logout Search Last 30 Days Topics Topics