InetLab

Hi,

I just tested your component to send out a bulk SMS.

I received this exception a number of times.

System.NullReferenceException: Object reference not set to an instance of an object.
at Inetlab.SMPP.Common.SmppClientBase.SendPDUAndReturnResponse[TResponse](SmppPDU pdu)
at Inetlab.SMPP.SmppClient.Submit(SubmitSm pdu)
at Inetlab.SMPP.SmppClient.Submit(IList`1 submitSmList)
at Inetlab.SMPP.SmppClient.Submit(IBuilder`1 submitBuilder)
at TOBackend.clsSenderThread.SenderCode() in D:\HostingSpaces2\admin\TOBackend\clsSenderThread.vb:line 414

The code for that line is
SubmitResponse = _SMPPConnection.Submit(SMS.ForSubmit().Coding(DataCodings.Latin1).DeliveryReceipt().From(SourceAddr).Text(ShortMessage).To(DestAddr))

Any ideas what the problem could be?

Thanks
Dan

I also get this

System.NullReferenceException: Object reference not set to an instance of an object.
at Inetlab.SMPP.Common.SmppClientBase.SendPDUAndReturnResponse[TResponse](SmppPDU pdu)
at Inetlab.SMPP.SmppClient.Bind(Bind pdu)
at Inetlab.SMPP.SmppClient.Bind(String systemId, String password, ConnectionMode mode)
at Inetlab.SMPP.SmppClient.Bind(String systemId, String password)
at TOBackend.clsSenderThread.SenderCode() in

Caused by this line..

_SMPPClient.Bind(_SystemID, _Password)

Any feedback?

Please make sure that one of the SourceAddr, ShortMessage and DestAddr is not null

when they are all not null please tell what values they have

Hello,

I have checked and the messages are being delivered, but we still receive a NullReferenceException.

SourceAddr: SEED
ShortMessage: 'SAVE THE DATE' - Sunday 9th March 8:30pm - Mr Steve, international author and lecturer will be doing a pre Fest talk - 'Fest - behind the mask' at 6 Old Hall Road Blackfield. Hope to see you there!
DestAddr: 447902021069

The details have been altered for privacy.

This is part of a large bulk sms and other SMS with the same SourceAddr and ShortMessage are sending without any problems. The fault seems to be random as we can resend using the same settings and there is no issue.

Is it possible to get the source code so we can see where the fault is?
I am not willing to pay for the source code at this point since the fault is random and doesnt appear to be caused by our coding.

Many thanks
Dan

In addition, I have just discovered that one of the messages that received a NullReferenceException was sent twice.

This is quite a bad issue for us.

Correction to my previous post. The message was not sent twice.

It was a concatenated message (2 sms).

Most of the attempts, 2 sms were sent successfully.

When we received NullReferenceException, only 1 of the sms were sent successfully.

Could you please try with latest version 1.1.14.3 ?