Category Archives: SMS

How to Solve “ERROR [HYT00][Microsoft][ODBC SQL Server Driver]Query timeout expired”

PROBLEM: ERROR [HYT00][Microsoft][ODBC SQL Server Driver]Query timeout expired

POSSIBLE CAUSE: Database too large, too many records in tables

SOLUTION: Create an index for “outbox” table:-

  1. Stop the SMS Engine service of MobiGATE
  2. Using SQL Management Studio, go to “indexes” of “dbo.outbox”, right-clickm select “New Index…”
  3. For “index name”, enter “To solve query timeout”
  4. Select “Nonclustered”
  5. Click “Add” to add 2 columns “datetime_queued” and “sent_status” (refer to red boxes below):
  6. Click “OK” button and a new index will be created:
  7. Start the SMS Engine service of MobiGATE
  8. Observe in log if this eror message still appear “ERROR [HYT00][Microsoft][ODBC SQL Server Driver]Query timeout expired
  9. If it appears again, please fill-in the table below:
    QUESTIONS ANSWERS (provide screen shot if available) REMARK
    Date of index created (as shown above)
    Take a screen capture of the SQL Management Studio showing:

    1. the new index
    2. the columns in the new index
    Date of the error message “ERROR [HYT00][Microsoft][ODBC SQL Server Driver]Query timeout expired” first appear
    Total number of records in “outbox” table when the error first appears
    Please send us:

    • the log file of the date when the error appear
    • “config.xml” file

Renaming “Sierra Wireless” in COM Ports

Objective: to use AT command to rename “Sierra Wireless” to “MOBITEK” so that all the 4 COM ports will display “MOBITEK”

 

Result: after using the “AT+WUSB” to change name to “MOBITEK”, the 4 COM ports in device manager still show  as “Sierra Wireless” .

 

In addition, there is no AT command to remove the other 3 COM ports, “CNS”, ‘DM” & “NMEA”

USB Drivers of FX30 and MOBITEK S80 Have Conflict — Bad_pool_caller

Problem: the USB Drivers for both FX30 and MOBITEK S80 cannot be installed in the same machine. Otherwise the below blue screen error will appear when trying to connect MOBITEK S80 3G Modem to the PC/machine.

 

Solutions: there are 3 solutions to choose:

  1. reboot Windows into “last known good configuration” (source: https://support.microsoft.com/en-my/help/4026863/windows-fix-error-0xc2-badpoolcaller);
  2. run system restore to restore Windows to the a date before FX30 USB driver was installed; or
  3. uninstall FX30 USB driver.

Test Result of MOBITEK SMS Engine — Enterprise Edition with TLS 1.2

 

TEST DATE SMS ENGINE VERSION TLS 1.2 SSL 2.0 OS MS SQL SERVER ODBC DRIVER 64-BIT ODBC DRIVER 32-BIT .NET FRAMEWORK TEST RESULT
2020-05-14 8.3 Enabled Disabled by default Windows Server 2012 64 bit MS SQL Server 2017 Express ODBC Driver 13 for SQL Server v. 2017.140.1000.169 ODBC Driver 13 for SQL Server v. 2017.140.1000.169 4.7.2 16:50:30 SMS Engine Enterprise Edition service (8.3.0) started
16:50:35 Modem ID 8 : initialized
2020-05-20 7.1 Enabled Disabled by default Windows Server 2012 64 bit MS SQL Server 2017 Express ODBC Driver 13 for SQL Server v. 2017.140.1000.169 ODBC Driver 13 for SQL Server v. 2017.140.1000.169 4.7.2 09:47:04 SMS Engine Enterprise Edition service (7.1.0) started
09:47:09 Modem ID 8 : initialized
2020-05-20 8.3 Enabled Disabled by default Windows Server 2012 64 bit MS SQL Server 2017 Express ODBC Driver 13 for SQL Server v. 2017.140.1000.169 ODBC Driver 13 for SQL Server v. 2017.140.1000.169 4.7.2 10:29:17 SMS Engine Enterprise Edition service (8.3.0) started
10:29:22 Modem ID 8 : initialized
10:31:39 SMS Engine Enterprise Edition service (8.3.0) stopped
2020-05-21 5.8 Enabled Disabled by adding  DWORD: “Enabled” with value 0
in registry
Windows Server 2012 64 bit MS SQL Server 2017 Express ODBC Driver 13 for SQL Server v. 2017.140.1000.169 ODBC Driver 13 for SQL Server v. 2017.140.1000.169 4.6 16:10:25 SMS Engine Enterprise Edition service (version 5.8.1) started
16:10:29 Modem ID 8 : initialized
16:10:49 SMS Engine Enterprise Edition service (version 5.8.1) stopped

Conclusion: MOBITEK SMS Engine — Enterprise Edition starting from version 5.8 until 8.x supports TLS 1.2

ERROR [HY000] [MySQL][ODBC 5.1 Driver]Host ‘175.xxx.xxx.xx’ is blocked because of many connection errors; unblock with ‘mysqladmin flush-hosts’

Problem: when using MOBITEK SMS Engine — Enterprise Edition v. 7.1 with MySQL database server in remote server (Exabytes), this error will appear after 2 days.

MOBITEK® SMS Engine — Enterprise Edition

 

SMS Engine was started on 23-Aug-2019, non-stop, until these error messages were received on 25-Aug-2019, Sunday, 1:41 am

01:42:21 ERROR [08S01] [MySQL][ODBC 5.1 Driver]Lost connection to MySQL server at 'reading initial communication packet', system error: 0
01:42:25 ERROR [HY000] [MySQL][ODBC 5.1 Driver]Host '175.xxx.xxx.xx' is blocked because of many connection errors; unblock with 'mysqladmin flush-hosts'
01:42:28 ERROR [HY000] [MySQL][ODBC 5.1 Driver]Can't connect to MySQL server on '72.xx.xxx.xx' (10055)
ERROR [HY000] [MySQL][ODBC 5.1 Driver]Can't connect to MySQL server on '72.18.132.28' (10055)

 

Trouble Shooting: The SMS Engine does not hold the database connection. It always close it after every execution of database query otherwise the engine would have failed long time ago.  Any other applications connecting to this database ? This error can also happen when there are too many connections issued to the database. Default concurrent connection for mysql is 151.

 

Conclusion: MOBITEK SMS Engine — Enterprise Edition only uses 1 database connection.

 

Control Panel for MobiGATE SMS Engine — Enterprise Edition version 2.6 is Released

List of  Fixes in Version 2.6

  • Engine cannot start because service is still stopping (after “Stop” button is clicked). CP shows “Stopped” but in fact service is showing “Stopping”;
  • Engine cannot stop because service is still starting (after “Start” button is clicked). CP shows “Started” bt in fact service is showing “Starting”;
  • “Modem Status” is tab “Modem 9 to 16” is not showing colours, it is showing “5” or “0” instead. Happens in MS SQL Server only (does not happen in MySQL);
  • Error message when connecting the “modem.state” table – “Location: CheckModemStatusVersion2_MSSQL Error message: Login failed. The login is from an untrusted domain and cannot be used with Windows authentication”;
  • Error message when connecting the “modem.state” table – “Location: CheckModemStatusVersion2_MSSQL Error message: Login failed. The login is from an untrusted domain and cannot be used with Integrated authentication”;
  • Conversion from string “” to type ‘Double’ is not valid. Caused by null or empty value in “Modem_State.Status”;
  • After stop monitoring, modem ID 9 to 16 still showing modem status.By right, there should be no colour status and should be all grey colour;
  • Set the application to run as administrator automatically.

 

Download

Existing customers of MobiGATE with valid warranty period or with valid annual support programme could download version 2.6 from here … (https://www.mobitek.my/download/MOBITEK%20MOBIGATE/Setup%20–%20Control%20Panel%20v.%202.6.zip)

 

More Information

 

How to Configure Windows Server and MS SQL Server Express to Allow Control Panel of MobiGATE to Remotely Connect

SETTING WHAT ERROR WILL APPEAR IF THE SETTING IS NOT DONE
Windows Firewall: allow “SQL Server Windows NT – 64 Bit”

If firewall is not opened for SQL Sever then this error will appear:

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error:40 – Could not open a connection to SQL Server)

SQL Server Configuration Manager:

  1. Enable Named Pipes and TCP/IP:
    – Go to SQL Server Network Configuration -> Protocols for <instance name> -> right click on Named Pipes and TCP/IP -> choose Enable
  2. Set port 1433 in TCP/IP Properties:
    – Go to SQL Server Network Configuration -> Protocols for <instance name> -> right-click on TCP/IP -> choose Properties
    – in IP Addresses tab -> scroll until the end until find IPAII -> set TCP Dynamic Ports to empty and TCP Port to 1433
If “Named Pipes” and “TCP/IP” are not enabled in MS SQL Server then this error will appear:

“A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error:40 – Could not open a connection to SQL Server) ”

If the SQL Server is using instance e.g. “./SQLEXPRESS”:

  1. In Windows Firewall, open port number 1434:
  2. In SQL Server Configuration Manager: Start “SQL Server Browser” in “SQL Server Configuration Manager”:
If TCP/UDP Port no. 1434 is not opened, then this error will appear:

“A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 – Error Locating Server/Instance Specified) ”

Remote connection must be enabled to connect to databases remotely. Connect to SQL Server Instance in SSMS. Right click on SQL Server instance name in SSMS and choose Properties. You will get Server properties window. Click on Connections from left side pane and tick the check box on Allow remote connections to this server option from right side pane.

MORE INFORMATION