The most likely cause of this problem is that there is an issue with one of the database fields in the MessageLog table. I can only repeat the advice I gave in the post that you referred to:
If this error is consistent then there probably is an issue with the layout of the 'MessageOut' database table that you use. To see what happens you can enable the communication logging in the SQL Connector by setting the 'LogCommunicationToFile' property in the advanced settings of the SQL Connector to 'True'. Don't forget to turn off logging after you finished the tests.
The log probably shows a difference in the number of records that are read from the 'MessageOut' table and the number of records that are removed from the table subsequently. If that happens, the SQL Connector rolls back the transaction to make sure that messages are not sent over and over again.
The exact solution for the problem depends on what the issue is with the database table layout but if you look at the logs it should be possible to find out what the problem could be.
i am using the trial basic edition with an SMPP and sql connector.
it works perfectly except the messagelog table is not updating the statues of the sent messages.
it always shows 200 in the statuscode column , Doesn't update even if i waited for a day or two , i tried setting MessageLogRetryOnError to true but that doesn't help.
if i restart the sql connector it shows this error :
SQL Database error, the status of 25 messages could not be updated in the MessageLog table and are removed.
i searched the forum and found this post but the guy wondered off to another error ,
can you tell me what steps i should take to diagnose the problem ,
Most Users Ever Online: 494
Currently Browsing this Page:
Guest Posters: 421
Newest Members:, Henk Helmantel
Administrators: Henk Helmantel: 698