Applies to these products:-
- MOBITEK MobiGATE model: SG-4-U
- MOBITEK MobiGATE model: SG-4-E
- MOBITEK Q24 STK Modem Hub model: STKMH-US401-C
- MOBITEK Q24 STK Modem Hub model: STKMH-EP432-C
Applies to these products:-
When connecting to a VNC Server (applies to both RealVNC and TightVNC), the VNC client (applies to both RealVNC and TightVNC) is unable to connect, and shows this message, “Connection closed unexpectedly”.
The followings settings are properly configured and they are not the issues:-
However, the log file of TightVNC server shows:-
[ 2132/ 4332] 2016-06-15 13:23:30 ! write() function stopped because transport has not been initialized yet.
[ 2132/ 4332] 2016-06-15 13:23:32 ! AnonymousPipe::read() failed (m_hRead = 000000000000030C)
[ 2132/ 4332] 2016-06-15 13:23:32 ! The Pipe's read function failed after ReadFile calling (The pipe has been ended. (109))
[ 2132/ 4332] 2016-06-15 13:23:32 ! Exception during DesktopClientImpl creaion:
[ 2132/ 4332] 2016-06-15 13:23:32 ! Error during RFB initialization:
[ 2132/ 4332] 2016-06-15 13:23:32 ! Connection will be closed:
[ 4500/ 4420] 2016-06-15 13:23:42 ! Desktop server application failed with error: The desktop server time out expired
The root caused is “RFB” on the VNC server.
Solution:-
Another reason for “Connection closed unexpectedly” is that RealVNC version 4.x does not work in Windows 7. For Windows 7, it requires Real VNC version 5 and above.
This error will appear if you copy the “dll” file from your development PC over to your production PC without running the “setup.exe” file on the production PC.
Solution:-
Step 1: Click Start and type command or cmd in the search box. It will depend on what Windows version you have. We will use Windows 8.1 x64 bit for this example.
Step 2: A command prompt will appear. Navigate the command prompt to C:\Windows\SysWOW64
Step 3: Type “regsvr32 [path of dl]” at the command prompt. In this case, I will use MobitekSMSAPI7.dll file, so the command will be:
C:\Windows\SysWow64\regsvr32 “MobitekSMSAPI7.dll”
Press enter to execute.
Step 4: A dialog box will pop out, indicating that the dll file is successfully registered into your system.
Allow “Full Control” to “Users” to the folder of the application. In this example, itis “C:\Program Files (x86)\SMS Engine Enterprise Edition”
(note: for updated post, please refer to https://mobitek-system.com/blog/2017/07/how-to-insert-sim-card-into-mobitkek-mobigate/)
[iframe src=”http://www.mobitek.com.my/Support/MobiGATE/Driver/Virtual%20Serial%20COM%20Port%20for%20SG-B-8-L-x/Installation%20Guide%20for%20MobiGATE%20SG-B-8.html” width=”100%” height=”500″]
PROBLEM: the STK ENGINE has problem submitting “OK” to STK. Refer below for the log in “ini” file:
Confirm reload to 0173737692 with RM 10.00 now > OK STK status is unknown. > STK status is unknown. STK status is unknown. STK status is unknown. STK status is unknown. STK is deactivated! 12/21/2015 4:25:58 AM
SOLUTION: bug fixed in MOBITEK STK ENGINE version 4.4
Applies to: MOBITEK® SMS360 — E-Mail Edition
Solution: http://sms360.com.my/main/index.php/2015/09/20/run-time-error-13-type-mismatch/
Applies to: MOBITEK® SMS360 — E-Mail Edition
Solution: http://sms360.com.my/main/index.php/2016/01/04/why-do-i-received-duplicate-sms/