Software and API Report Codes

The Report Codes that you may receive from our software applications and Developer APIs are given below in their corresponding Topics and Groups.

Success/Intermediate Status

Code Name Explanation Group Notes DNR ?
-15 2Way service created Your new 2Way service has been created. General Final Status. Your 2Way service would have been successfully created. Do test the 2Way service to ensure that it works in the way that you want. DNR
-10 Accepted by Network Your message has been sent to an SMSC, but delivery cannot be confirmed. General Final Status. Some networks do not support delivery receipts. In these instances the final status that can be confirmed is that the message was passed to the SMSC of the mobile network operator. You do not need to handle this report code in sending API's. DNR
-8 Temporary Failure Your message cannot be delivered immediately due to a network or server issue. General Intermediate Status. You do not need to handle this report code in sending API's. DNR
-6 MMS Awaiting Collection The MMS has not yet been collected General Intermediate Status. You do not need to handle this report code in sending API's. DNR
-5 Accepted by Network Your message has been sent to an SMSC, but delivery cannot be confirmed General Final status. You do not need to handle this report code in sending API's but it can be returned in delivery receipts and your message history. DNR
-4 Accepted by Network (queued) The SMSC is attempting to deliver your message General Intermediate status. You do not need to handle this report code in sending API's but it can be returned in delivery receipts and your message history. DNR
-3 Accepted by csoft: delayed Your message has been accepted by CSoft for delayed delivery. General Intermediate Status/API Response. You need to handle this report code in sending API's and you will see it in your message history but it won't be returned in delivery receipts. DNR
-2 Accepted by csoft: queued Your message has been accepted by CSoft for delivery and has been queued for delivery to the network. General Intermediate status/API Response. You need to handle this report code in sending API's and you will see it in your message history but it won't be returned in delivery receipts. DNR
-1 Internal error The service is in an unknown error state. General Final Status/API Response. It is highly unlikely you will ever receive this report code. You should, however, handle this code in sending API's. If you are using an external application to send the messages, exit the program and restart it. If the problem persists, please contact us. DNR
0 Accepted by phone Your message has been delivered to the handset. General Final status. You do not need to handle this report code in sending API's but it can be returned in delivery receipts and your message history. DNR

Failures

Code Name Explanation Group Notes DNR ?
2 Invalid login Your message failed because of an invalid login. General Final Status/API Response. You may get this when using sending API's. Check that the Username and PIN (not Password) are correct including any dots and case. If the problem persists contact us. DNR
3 Invalid number Your message failed because of an invalid DSSN Subscriber number. General Final Status/API Response. You may get this when using sending API's. This is for pager messages only. If the problem persists contact us. DNR
4 Inactive number The message failed because the number you tried to send to is inactive. General Final status. Check the number is currently active. If you can confirm that it is, please contact us. DNR
5 Invalid number The message failed because it was rejected by the network operator. General Final Status/API Response. You may get this when using sending API's. Check that it is a valid number in full international format. e.g. 447700912345 for a UK number. DNR
6 Area code not recognised The message failed because the area code part of the number was not recognised General Final Status/API Response. You may get this when using sending API's. Check that it is a valid number in full international format. e.g. 447700912345 for a UK number. DNR
7 Invalid number The message failed because it was rejected by the network operator. General Final Status/API Response. You may get this when using sending API's. Check that it is a valid number in full international format. e.g. 447700912345 for a UK number. DNR
8 Blacklisted number The message failed because you tried to send to a blacklisted number. General Final Status/API Response. You may get this when using sending API's. DNR
11 Invalid characters The message failed because it contains illegal characters. General Final Status/API Response. You may receive this when using the sending API's. Check the message is valid - If sending non-GSM character set messages, be sure you are using the correct utf-8 encoded characters. DNR
12 Invalid number Your message failed because it was rejected by the network operator as invalid. General Final Status/API Response. You may get this when using sending API's. Check the number is valid DNR
13 Blacklisted number Your message failed because it was rejected by the network operator as a blacklisted number. General Do not retry, the message will not be accepted for this number. DNR
14 SMSC down Your message failed because the network operator is currently down. General Final Status/API Response. You may get this when using sending API's. You should back off for a period and retry again. DNR
15 Out of Credit Your account balance has reached zero/your credit limit.. General Final Status/API Response. You may get this when using sending API's and will see this in your message history. Login to your account online and purchase more credit. You will need to re-send messages marked with this code yourself - they will not be queued up. DNR
16 No message The message failed because it appears to be an empty message. General Final Status/API Response. You may get this when using sending API's. Check that you submitted a message request which actually contained a message to sent. DNR
17 Invalid number The message was failed for security reasons. General Final Status/API Response. You may get this when using sending API's. DNR
18 System error The message failed because of a system error. General Final Status/API Response. You may get this when using sending API's. Retry later. DNR
19 Invalid characters The message failed because the message is unacceptable. General Final status. You may get this when using sending API's. Change the message DNR
20 System error Your message failed for security reasons. General Final status. You may get this when using sending API's. Contact us to discuss why this has occured. DNR
21 System error Message to <number> failed because of a time-out in a server. Retry later. General Final status. You may get this when using sending API's. Contact us to discuss why this has occured. DNR
22 Queue full Your message failed because of a full queue. General Final status. You could get this when using sending API's but it is highly unlikely. Contact us to discuss why this has occured. DNR
23 Rejected by SMSC Your message failed because it was rejected by the network operator. General Final status. You may get this when using sending API's. Check that it is a valid number in full international format. e.g. 447700912345 for a UK number. DNR
24 Unable to route message The message failed because of a route configuration problem. General Final status. You may get this when using sending API's. Please contact us immediately in the highly unlikely event of this occuring. DNR
25 Deleted by SMSC The message failed because it was deleted by the network operator. General Final status. You may see this in a delivery receipt or when viewing your message history. Please contact us immediately in the highly unlikely event of receiving this code. DNR
26 SMSC cannot deliver Message to failed because it could not be delivered. General Final status. You may see this in a delivery receipt or when viewing your message history. Check with the recipient that the number is active and if so, try re-sending the message. If the problem persists, contact us. DNR
27 Expired by SMSC Your message failed because the message expired. General Final status. You may see this in a delivery receipt or when viewing your message history. All messages have a validity period after which they are expired. This is typically 7 days.
28 Abandoned by SMSC Your message failed because the network operator abandoned it. General Final status. You may see this in a delivery receipt or when viewing your message history. DNR
29 System error Your message failed because a connection could not be made to the network operator. Retry later. General Retry later.
30 Protocol error Final status. You message submission fails to conform to the protocol. General You may get this when using sending API's or applications which use those APIs. If you are a developer codingto the API, check the documentation against your implementation for irregularities. If you are an application user, check you have entered valid details for the message you are trying to send. If the problem persists contact the application vendors. DNR
34 Blacklisted account This account has been blacklisted and is no longer available General Accounts are blacklisted when security breaches or fraud is suspected DNR
35 Opted Out You cannot send messages to this number. General The person owning this number has either not opted in to receive messages from you or has opted out. DNR
36 Blacklisted Mobile You are not permitted to send messages to this mobile General DNR
37 System Error Message to failed because of a system error. Retry later. General Do not retry DNR
38 Wrong PIN Each PIN is associated on the server with a particular email program and user at your end. General API Response (Email Only). Either you entered the PIN incorrectly or you are trying to use the same PIN from multiple addresses. You need an additional PIN for a new emailer or email user. Please contact us for more free PIN numbers. DNR
39 Wrong email address You sent an email to the Email to SMS service from an email account which you haved not registered to use with this service. General API Response (Email Only). Login to your account online and register the email address using the menu option Configure Services->Simple Email Input Configuration. DNR
40 Bad MMS URL General DNR
41 Expired MMS The expiration date for the MMS has passed. General DNR
42 MMBox MMS is in your MMBox General DNR
43 OSE Reply Leg General DNR
44 Bad Reply-To You are not permitted to use the ReplyTo number or alpha-tag that you specified. General Final status. You may see this code when using sending API's or when examining your message history. You tried to use a reply-to address which you are not permitted to use. Contact us to discuss your requirements. DNR
46 MO MMS In Library The MO MMS has been uploaded to the library. General Final status. You should get this success code when using the API's to upload MMS content to the library. DNR
47 MO MMS Failed The MO MMS could not be retreived General DNR
48 MMS Repurposing failed The MMS repurposing failed during delivery of the content to the handset. General This could be because we do not know anything about the handset in question or because the MMS content is somehow invalid. Please contact us to investigate further. DNR
49 Bad MMS data The MMS file data (image, mms, java midlet, ringtone, etc) you submitted was found to be invalid when decoded. General Check that the original data is valid using a player/viewer. If submitted using an API, check that the data was correctly hex-encoded and that the content-length is correct so that no characters were added or truncated. There is a free hex encoder available from the Products->Download menu. DNR
54 Mobile Not Subscribed The mobile user has not given you permission to send General DNR
55 Rejected by SMSC General DNR
57 Bad PSMS Parameters You are not configured to use this PSMS service General API Response. Please contact us if you wish to use a premium SMS service. DNR
58 No PSMS Route Cannot deliver PSMS to this operator General API Response. Please contact us if you wish to use a premium SMS service. DNR
59 Deleted by user The message was deleted by the user before it could be sent General DNR
66 Number ported The number is ported to an unsupported network or longer in use General DNR
67 Invalid Originator Address The originator address you are using is not allowed by the destination network. General Check that you are using the correct originator address DNR
69 Must Use HTTPS You must use an HTTPS connection. General API Response. You must use an HTTPS connection when using this API. Change your client code to use HTTPS instead of HTTP. For example https://www.csoft.co.uk/ DNR
70 Insufficient funds in source account When transferring funds the source account did not have enough funds General API Response. You may get this when using API's to transfer funds from one account to another. Top-up the source account or use a different source. DNR
71 Wrong Username The target Username is invalid. General Final Status/API Response. You may get this when using the account management API's. Check that the Username is correct including any dots and case. If the problem persists contact us. DNR
73 Account suspended Final status. Your account has been suspended General You account has been suspended and cannot be accessed. Contact your account manager at Connection Software. www.csoft.co.uk DNR
74 Account Deleted This account has been deleted and no longer exists General DNR
75 Blacklisted Blacklisted General DNR
76 Wrong number of digits The number of digits is not valid for this country. General Verify the number you are sending to is correct. The number has been rejected because it is too short, or to long, to be a valid mobile/cell phone number. DNR
77 Suspended This service has been suspended. General The service has been suspended. Please contact us to discuss why this has occured. DNR
80 Spam MO General DNR
81 Invalid address book group The address book 'group name' that you have specified does not exist. General You may get this when using sending API's. DNR
83 No PSMS Transaction ID You need to receive an MO from this number before you can send a PSMS to it General DNR
84 PSMS Transaction ID Expired You need to receive another MO from this number before you can send PSMS to it again General DNR
85 Unrecognised recipient Could not expand the given Address Book or find a group name. General This error could occur if an address book name or group name could not be found for an account. Make sure that these have been spelt correctly. DNR
86 Unrecognised IM Account The IM Account was not recognised General DNR
87 Disconnected IM Account The IM Account is not connected General DNR
88 Requested delay was more than 2 years You cannot schedule a message for more than 2 years in the future General DNR
89 116SMS service does not exist Your account is not on the 116SMS service and cannot receive messages via this API General DNR
90 Email service is not enabled Your 116SMS account is not enabled to use the email service General DNR
91 Account Deleted This account has been deleted General DNR
92 Message Limit Exceeded You have exceeded the message limit for this account General DNR
93 Group not found The specified group cannot be found in the account holder's address book General DNR
94 Sender not found The sender is not configured to use the SMS to Group service General DNR
95 Secure Number Service Request A request from an end user to opt in or out of a Secure Number Service General DNR
96 Requeue Failed Failed to requeue this message General DNR
97 Invalid PM License You need a valid Pastel Messenger License to use Pastel Messenger General DNR

Test Number Success/Failure

Code Name Explanation Group Notes DNR ?
98 Test message failed Your message to a test number failed. Testing Final Status/API Response. Your message to a test number was rejected. Check that you are sending to a valid test number.
99 Test message succeeded Your test message was accepted. Testing Final Status/API Response. Your message was parsed and accepted but as it was sent to a test number it will not be delivered.

Unexpected System Failure

Code Name Explanation Group Notes DNR ?
100 System error An unexpected service-side system failure. System Error You should never experience this, but it could occur in the event of an unexpected server-side system failure. Please contact us if you receive this report code. DNR

Account Management

Code Name Explanation Group Notes DNR ?
104 Account already exists. This account you are trying to create already exists. Account Management You may get this when using the account management API's. If you want to create multiple accounts with our API's please contact us. DNR
105 Permission denied Not allowed to use this service Account Management You may get this when using the account management API's. To use this API please contact us. DNR
106 Unlicenced The handset application is not licensed Account Management Please purchase a licene to use this software on your handset. DNR
107 Undeliverable HLR Your message failed because it was rejected by the network operator Account Management DNR
108 Unknown DR status The delivery receipt had an unknown status Account Management DNR
109 Volume Block You attempted to send too many messages to this number in a short period of time Account Management DNR

Two-way SMS Services

Code Name Explanation Group Notes DNR ?
110 2Way service already exists Your account already has a 2Way service in place. Account Management You may get this when using the create 2Way service API's. If you want to create multiple 2Way services with our API's please contact us. DNR
111 No 2Way numbers available Could not create a new 2Way service because there are no 2Way numbers avaiable. Account Management Please contact us. DNR
112 2Way service charges not configured The 2Way service charges have not been set or configured. Account Management Your new 2Way service was not created. Please contact us. DNR
113 2Way provisioning has failed The creation of a 2Way service has failed. Account Management You may get this when using the create 2Way service API's. Please contact us if you get this error. DNR
114 Repeated Message You attempted to send too many identical messages to this number Account Management DNR

Sending Messages

Code Name Explanation Group Notes DNR ?
150 Logged on to the network operator Reserved. General (Deprecated) Reserved DNR
151 Failed to logon on to the network operator General (Deprecated) DNR
152 Sending Message General (Deprecated) DNR
153 Logged off from the network operator General (Deprecated) DNR
154 Unexpected message General (Deprecated) Exit the program and restart it. If the problem persists, request help from Connection Software DNR
155 Internal error - no protocol This internal error indicates that the output protocol manager attempted to send the message, but there was no protocol to use to send the message to the operator. You should Exit the program and reboot as soon as is practicable. General (Deprecated) Exit the program and restart it. If the problem persists, request help from Connection Software DNR
156 Internal error - no route This is an internal error. It means that the message does not have a route via which to send it out. Please report this error to Connection Software. General (Deprecated) Exit the program and restart it. If the problem persists, request help from Connection Software DNR
157 Internal error - restart program This is an internal error. It means that the message does not have a message body to send (this is not the same as a blank message which is permissible). Please report this error to Connection Software. General (Deprecated) Exit the program and restart it. If the problem persists, request help from Connection Software DNR
158 Message sent The message was successfully sent. General (Deprecated) The message was sent sucessfully. DNR
160 All messages have been queued When sending messages using a multiple recipient enabled version of Mobile Messenger, all messages are queued when sent, even if there is only one to send. This message will be shown to inform you that the messages are being processed and that you can return to the main screen, but that they have not been sent yet. General (Deprecated) You can continue to leave the Message Progress window open and, as the messages are sent, it will be reported. Alternatively, you may close the window and instead check the Message History at some time in the future to see the status of the messages. All queued messages are written to the history and their status updated as it changes. You can also re-open the Message Progress at any time. DNR
161 Message queued Message to ( , ) has been queued. This is a status message and is the first line you will see in the progress log when sending a message. It displays a summary of whom the message is going to be sent, by both name and number, as well as via which Operator the message will be sent. General (Deprecated) No action need be taken. DNR
168 Input Protocol Error Message to failed because of a problem with the remote system. General (Deprecated) Do not retry. DNR
169 System Error Message to failed because of a remote system error. General (Deprecated) Retry later.

Server Errors

Code Name Explanation Group Notes DNR ?
171 Invalid login Message to failed because of an unknown Grade of Service. General (Deprecated) If the problem persists contact Connection Software DNR
172 Invalid login Message to failed because of an invalid login. General (Deprecated) Check your login details DNR
173 Invalid number Message to failed because of an invalid DSSN Subscriber number. General (Deprecated) If the problem persists contact Connection Software DNR
174 Inactive number Message to failed because the number is inactive. General (Deprecated) Check the number DNR
175 Invalid number Message to failed because it was rejected by the network operator General (Deprecated) Check the number DNR
176 Unknown number Message to failed because the pager/mobile/cell phone is not recognised General (Deprecated) Check the number DNR
177 Invalid number Message to failed because it was rejected by the network operator General (Deprecated) Check the number DNR
178 Blacklisted number Message to failed because too many messages have been sent. General (Deprecated) DNR
179 Message limit exceeded Message to failed because too many messages have been sent. General (Deprecated) DNR
180 Message limit exceeded Message to failed because too many messages have been sent. General (Deprecated) DNR
181 Invalid characters Message to failed because it contained an illegal character General (Deprecated) Check the message DNR
182 Invalid number Message to failed because it was rejected by the network operator General (Deprecated) Check the number DNR
183 Blacklisted number Message to failed because it was rejected by the network operator General (Deprecated) Check the number DNR
184 Can't reach remote server Unable to connect to the remote server.. General (Deprecated) Either the remote servers are down or unreachable. Check the network and firewall as well as the remote servers DNR
185 Out of Credit Message to failed because it was rejected by the network operator General (Deprecated) Check the number DNR
186 No message Message to failed because it was rejected by the network operator. General (Deprecated) Check the number DNR
187 Invalid number Message to failed for security reasons. General (Deprecated) DNR
188 System error Message to failed because of a system error. Retry later. General (Deprecated) Retry later.
189 Invalid characters Message to failed because the message is unacceptable. General (Deprecated) Change the message DNR
190 System error Message to failed for security reasons. General (Deprecated) DNR
191 System error Message to failed because of a time-out in a server. Retry later. General (Deprecated) Retry later.
192 Queue full Message to failed because of a full queue. Retry later. General (Deprecated) Retry later.
193 Rejected by SMSC Message to failed because it was rejected by the network operator General (Deprecated) DNR
194 Unable to route message Message to failed because of a configuration or database problem. General (Deprecated) DNR
195 Deleted by SMSC Message to failed because it was deleted by the service provider. General (Deprecated) Check the message DNR
196 SMSC cannot deliver Message to failed because it could not be delivered. The recipients pager or mobile was unavailable and the message expired General (Deprecated) Check with the recipient - or re-send the message. DNR
197 Expired by SMSC Message to failed because the message expired. General (Deprecated) DNR
198 Abandoned by SMSC Message to failed because the service provider abandoned it. The recipients pager or mobile was unavailable and the message expired General (Deprecated) DNR
199 System error Message to failed because a connection could not be made to the network operator. Retry later. General (Deprecated) Retry later.

Address Book

Code Name Explanation Group Notes DNR ?
200 Address book not found Windows Address Book cannot be found. Mobile Messenger It is supplied with Internet Explorer and you need to install it before you can use this program. Detailed help is available in the online Help system and in the Installation Guide. See the ""Start"" menu => Program Files => Connection Software => Mobile Messenger => Installation Guide. DNR
201 Address book not found Currently, Mobile Messenger only supports the reading of the Windows Address Book (WAB) which is supplied free with Windows 98/98 Second Edition/Windows 2000 and Windows ME and also with Internet Explorer/Outlook Express v4.0 or greater. It does not at present support other address books such as Outlook or Eudora (this is planned for a future version). If you do not have the Windows Address Book, you will always receive these messages at startup and you can only send messages to recipients you type in directly using their mobile/cellular/pager number. These messages can appear, even after WAB has been installed, if you have not actually run the Windows Address Book (wab.exe) program prior to starting Mobile Messenger. This is a fault with WAB and not Mobile Messenger but can be fixed by running the program once and then closing it. You will need to use the address book program to store your contacts for Mobile Messenger anyway. Mobile Messenger Mobile Messenger reserved code. Windows Address Book cannot be found. It is supplied with Internet Explorer and you need to install it before you can use this program. Detailed help is available in the online Help system and in the Installation Guide. See the ""Start"" menu => Program Files => Connection Software => Mobile Messenger => Installation Guide. DNR
202 Address book empty There are no entries in your address book. Mobile Messenger Mobile Messenger reserved code. In order to use the program easily, you should add recipients to your address book. You can easily import Address Book entries from another program - see the online Hlep. DNR
203 Too many recipients specified Mobile Messenger has a limit to the number of recipients that a message can be sent to at any one time. If you exceed this limit, you will receive this message. Mobile Messenger Mobile Messenger reserved code. You can work around this limitation by sending the message to a group of recipients in blocks. Do this by selecting all the recipients that you can from the group, typing the message, and then sending the message. If you de-select the recipients, then select the next block, the message will not be deleted and you can send it to the next block. Continue this until you have sent the required message to the group. Please contact the supplier of your version of Mobile Messenger, or alternatively, contact Connection Software. DNR
204 Number not recognised The pager, mobile or cell phone number of this person has not been recognised. Mobile Messenger Mobile Messenger reserved code. If you are sure the number is correct, then this indicates that the database supplied with the program needs to be updated. Please request help from Connection Software. DNR

Database Access

Code Name Explanation Group Notes DNR ?
250 Database out of date The database supplied with the program needs to be updated. Mobile Messenger Mobile Messenger reserved code. Please request help from Connection Software. DNR
251 Database out of date The database supplied with the program needs to be updated. Please request help from Connection Software. Mobile Messenger Mobile Messenger reserved code. The global database is version stamped internally. Mobile Messenger knows the minimum version of the database that it can work correctly with and will check this when starting up. If there is an inconsistency, you will see this warning. If the database is not too old, MM may run but operability will be affected and you should seek to upgrade your database immediately to ensure the database integrity. DNR
252 Can't open database There is a problem opening the database. It may have been deleted, corrupted, or moved or is in use by another program. Mobile Messenger DNR
253 Can't access database There is a problem accessing the database. It may have been deleted, corrupted, or moved or is in use by another program. Mobile Messenger DNR
254 Database entry no found One of the databases entries could not be found or is incorrect. Would you like to try automatically recreating the entry so that the program can continue to send messages? Mobile Messenger When Mobile Messenger attempts to use the ODBC entries to locate the databases at startup, it may discover that they are incorrect. If this happens you will receive this error message. Unless you know have good reason not to, you should allow the program to try and repair the ODBC entries it refers to. If the database files are not where they are expected to be or have been renamed then the automatic recreation will fail and you will be presented with a file selector window from which you can locate the database files yourself. If you select Cancel, Mobile Messenger will start up but you will constantly receive database error messages and it will not function properly. If your databases are kept on a server, such as might be the case if you share a global routing database, then it is possible that the reason for this error might be a network problem. In which case, you should NOT let Mobile Messenger amend your ODBC entries, but instead consult your Network Administrator. DNR
255 Can't access database There is a problem accessing the database. It may have been deleted, corrupted, or moved or is in use by another program. Mobile Messenger Re-install the program to re-create the database DNR
256 Can't close database There is a problem closing the database. It may have been deleted, corrupted, or moved or is in use by another program. Mobile Messenger Re-install the program to re-create the database DNR
257 Can't open database If the database cannot be closed it implies that there is something wrong internal to Mobile Messenger or with the connection to the database. If the database is on another machine, check that it is still accessible. If so, then safest option is to close down the program as soon as possible and reboot the machine. If upon restarting Mobile Messenger, the problem persists, then you should contact Connection Software. Mobile Messenger There is a problem opening the database. It may have been deleted, corrupted, or moved or is in use by another program. DNR
258 Can't close database There is a problem closing the database. It may have been deleted, corrupted, or moved or is in use by another program. Mobile Messenger Mobile Messenger can automatically fix some ODBC entry problems. If you have agreed to allow it to do so, always after seeing a previous error, and it cannot do so them you will see this message. You may be able to fix this problem by closing down Mobile Messenger and then deleting the ODBC entries using the ODBC Data Sources Control Panel applet. Start the applet that can be found under Start/Settings/Control Panel. Select the System DSN tab. Select the MOBILE_MESSAGE_GLOBAL entry in the System Data Sources list. Press the Remove button and click on Yes when it asks if you are sure. Repeat steps 3 & 4 for the MOBILE_MESSAGE_LOCAL entry. After doing this, you should be able to restart Mobile Messenger and allow it to recreate the ODBC entries for you. If your global database is not in the standard location, then you may not to help MM find it using the directory window that will be displayed in this case. If this is the first time that you have run Mobile Messenger, it may be that you do not have ODBC installed on your system. You should have been warned about this and given a means to obtain it during installation. You can check that you have ODBC installed by looking for the applet called ODBC Data Sources under Start/Settings/Control Panel. If you do, also check that under the Drivers tab there is an entry for the Microsoft Access Driver. DNR
259 Can't close database Mobile Messenger There is a problem closing the database. It may have been deleted, corrupted, or moved or is in use by another program. DNR
260 Can't open database When Mobile Messenger tries to repair the ODBC entries it knows where to expect to find the databases it uses. If however, they are not there, or have been renamed, then it cannot automatically fix the ODBC entries to point to the databases. In this situation you will see this error and will be offered the chance to point MM at the database, should you know where it is or that it is now called. We strongly discourage you from renaming or moving the databases when there is no need, but if you have good reason then you can fix the ensuing problem here. Mobile Messenger There is a problem opening the database. It may have been deleted, corrupted, or moved or is in use by another program. DNR
261 Can't open database There is a problem opening the database. It may have been deleted, corrupted, or moved or is in use by another program. Mobile Messenger The most common cause of this problem is not having ODBC installed. During installation you will have been warned about this and told how to get ODBC onto your system. If you have not done this then do so now. You may need a support package from your software provider. DNR
262 Can't open database There is a problem opening the database. Mobile Messenger You may need to install ODBC on your system, and then reinstall this program in order to fix the problem. DNR

Sending Multimedia Messages

Code Name Explanation Group Notes DNR ?
333 No valid multimedia message found Your message appears to be a multimedia message but does not contain a valid multimedia message specification. Multimedia Ensure that you have included all the essential components for a multimedia message. Check the specification for the API you are using.
334 Unknown error while constructing message Multimedia
335 General failure, format :[defaults]: wrong Multimedia DNR
336 Format not matched Multimedia DNR
337 Default parameter is not d, o, b, s or l Multimedia DNR
338 Value for duration not allowed Multimedia DNR
339 Value for scale not allowed Multimedia DNR
340 Value for style not allowed Multimedia
341 Value for loop not allowed Multimedia DNR
342 Value for d, o, b or l is not an integer Multimedia DNR
343 Format [duration][#][scale][.] wrong Multimedia DNR
344 Note value not allowed Multimedia DNR
345 Ringtone unsuitable for this phone Multimedia DNR
346 Library contains no valid data Multimedia DNR
347 Invalid library number Multimedia DNR
348 No MNC/MCC given for operator logo Multimedia DNR
349 Phone type not supported Multimedia DNR
351 Checksum error Multimedia DNR
352 Syntax error Multimedia DNR
353 Operation not supported by system Multimedia DNR
354 Operation not allowed Multimedia DNR
355 Call barring active Multimedia DNR
356 Invalid originator address Multimedia DNR
357 Authentication failure Multimedia DNR
358 Legitimisation code for all calls, failure Multimedia DNR
359 GA not valid Multimedia DNR
360 Repetition not allowed Multimedia DNR
361 Legitimisation code for standard text, failure Multimedia DNR
362 Priority call not allowed Multimedia DNR
363 Legitimisation code for priority call, failure Multimedia DNR
364 Urgent message not allowed Multimedia DNR
365 Legitimisation code for urgent message, failure Multimedia DNR
366 Reverse charging not allowed Multimedia DNR
367 Legitimisation code for reverse charging, failure Multimedia DNR
368 Deferred delivery not allowed Multimedia DNR
369 New authentication code not valid Multimedia DNR
370 New legitimisation code not valid Multimedia DNR
371 Standard text not valid Multimedia DNR
372 Time period not valid Multimedia DNR
373 Message type not supported by system Multimedia DNR
374 Message too long Multimedia DNR
375 Requested standard text not valid Multimedia DNR
376 Message type not valid for the pager type Multimedia DNR
377 Error code 27 Multimedia DNR
378 Invalid character set Multimedia DNR
379 Unrecognised error Multimedia DNR

Your session is about to expire

You will be logged out in seconds.

Do you want to stay signed in?

Yes, keep me signed in     No, Sign me out