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.
Hello, sorry for the delay! this error happens when a customer places an sms shipping
Error: Diafaan event log: Not all records from the table Send SMS Could be removed or updated. Send SMS operation rolled back
What should I do to fix the error.
I am sorry but I don't understand the question. Can you provide more details about the problem?
How do I work it already does not know what else to do.
The error 'Not all records from the Send SMS table could be removed or updated. Send SMS operation rolled back.' occurs when your SQL database throws an error when Diafaan SMS Server tries to remove the messages it loaded from the 'MessageOut' database table. Diafaan SMS Server then rolls back the database transaction and discards the SMS messages that are already loaded from your database.
The SQL Connector will try to load the messages in the next batch process, normally this error is nothing to be worried about but if the error occurs regularly it might be an indication of problems with your SQL database.
Not all records from the Send SMS table could be removed or updated. Send SMS operation rolled back.
This error is generated when the SQL Connector in Diafaan SMS Server is not able to update the status of previously sent messages in the 'MessageLog' table of your SQL database after a delivery report for these messages is received. It can happen when the Diafaan SMS Server service is stopped, or the SQL Connector settings are changed, while the SQL Connector has unhandled update requests in memory.
If you set the 'MessageLogRetryOnError' property to 'True' in the advanced settings of the SQL Connector, it is also possible that this error is generated when there is a problem with the database and when there are too much update requests waiting to be handled. When the list of unhandled update requests is getting too large, Diafaan SMS Server will remove the oldest ones to prevent memory leaks.
In a stable system, where you do not normally stop and start the Diafaan SMS Server service or SQL Connector, this error should not occur and if you see this error it might be an indication that there is a problem with the SQL database settings.
hello, I am using a trial license diafaan for application testing before buying the license.
however I have been running into this error.
I have 10 modem, each modem programmed to send only 600 sms day.
SQL Database error, the status of 255 messages could not be updated in the MessageLog table and are removed.
Most Users Ever Online: 494
Currently Browsing this Page:
Guest Posters: 545
Newest Members:, Henk Helmantel
Administrators: Henk Helmantel: 1088