If Geo SCADA is installed and configured correctly, yet the connection is not working, this article will assist in helping the user check the configuration and collect the relevant information required to troubleshoot this issue.
Items to Check
Firstly, the Geo SCADA Mobile companion needs to be installed and running on the Geo SCADA server where data is being accessed from (i.e. the Geo SCADA Server that the Geo SCADA mobile server is connecting to). To verify, collect a screen shot of the Windows Services that are running on the Geo SCADA Server PC (Geo SCADA services). It should look similar to the image below:
Next, check to see if a secure connection is being used. When first configuring Geo SCADA Mobile, it is recommended to disable the secure connection during the initial testing (to prove functionality). Secure connections may then be enabled after. To check this, look at the following:
- On the Geo SCADA Server PC, look at the Geo SCADA Server configuration tool (Configuration | system configuration | Mobile dialog). Ensure the ‘Use SSL connection’ box is unchecked
- On the Geo SCADA Mobile Server PC, look at the ‘Global Setting’ dialog of the Geo SCADA Mobile Configurator. Ensure that the ‘Use Secure Companion Connections’ box is unchecked
If this box is checked on the GS Server PC, uncheck it, apply the changes and restart the GS server.
If this box is checked on the GS Mobile Server PC, uncheck it and restart both Geo SCADA Services. (see last bullet point in section immediately below)
Next, check the items below. If the connection is still not working, follow the Information Needed steps below that.
- Ensure firewall in router, and local Windows firewalls allow port 8008 bidirectional traffic
- Ensure the proper version of ASP.Net is installed – v4.0 needs to be used, not 2.0 (see note about ASP.Net below)
- Ensure the local firewall (GS Mobile server PC) is not blocking incoming traffic on the IIS port (i.e. 443 – or whichever port is configured for GS Mobile in IIS)
- On the Geo SCADA server PC, in the 'Configure Connections' dialog, ensure the 'Workstation' name field is blank
- Ensure that the following services are running (Windows Control Panel | Windows Tools | Services):
- Geo SCADA Expert Mobile Companion Server
- Geo SCADA Mobile Settings
The screen shot below shows that Geo SCADA is using ASP.NET v4.0. Launch IIS and click on ‘Application Pools’ to see this view:
Information Needed
Test the connection from the mobile device to the IIS server (running on the Geo SCADA Mobile server) by opening a web browser on the mobile device and entering the following URL:
https://<address/name>/mobile/service.svc/v1/admin/pin
(where <address/name> is the name or IP address of the Geo SCADA Mobile Server PC)
If the connection is successful, the browser should return a single word, ‘true’.
Example
The Geo SCADA developers have provided a URL to a Geo SCADA Mobile server in the UK for users to connect to as a test. Open a web browser and enter the following URL:
https://saurbaum.uk/mobile/service.svc/v1/admin/pin
The browser should return a screen that looks similar to the screen shot below. If you do not see a result of ‘true’, then the connection is not valid and further troubleshooting will be required.
(Note: the word ‘true’ will appear in a very tiny font in the top left of the screen. It may be difficult to see)
(Alternatively, you should also be able to perform a ping test in both directions (I.E. pinging the mobile device from the GS Mobile Server PC and pinging the GS Mobile Server PC from the mobile device. This requires the user installing a ping app on the mobile device.)
If the test above (to the production server) is successful, then open the Geo SCADA Mobile app on the mobile device and try to connect to the Geo SCADA Mobile server. Note the time of the connection attempt and then collect the following:
- the names and IP addresses of the servers in question (where the Geo SCADA Mobile server and Geo SCADA server are installed) so that we can correlate information with the log files. If both the GS server and GS Mobile server are running on the same PC, then just that PC's IP address and name are needed.
- the name and IP address of any redundant GS server(s) (if configured - so that we can identify these in the log files)
- log files from both the mobile server and the mobile companion (see bullet list below). These are described in the Diagnostics sections of the GS mobile admin guide (there is a section for both the mobile server and the mobile companion). These logs should be in the C:\ProgramData\Schneider Electric\ClearSCADA\Logs folder. The MobileCompanion.log file may be in a sub folder named 'DB'. (I.E. C:\ProgramData\Schneider Electric\ClearSCADA\Logs\DB)
- WebServer.log
- MobileServer.log
- MobileCompanion.log
- Note: the WebServer.log file is only created when the mobile device connects to the Geo SCADA Mobile server. If this connection does not occur, then the WebServer.log file is not created. To check if the connection occurred, look at the following Windows directory:
C:\inetpub\logs\LogFiles
There will be one or more folders which will contain files named u_ex####.log.
These log files can provide some insight into the mobile connection attempt.
- Copies of the corresponding DB_### and DBSnapshot_### log files from the following folder on the Geo SCADA server PC: C:\ProgramData\Schneider Electric\ClearSCADA\Logs\DB
Note: Please ensure that all log files (WebServer, MobileServer, MobileSompanion, DB, DBSnapshot) cover the time of the connection attempt. All log files may be opened using Windows Notepad and the timestamp can be seen in the left-hand column. All logs are shown in UTC time, so they may appear to be different to local time by several hours
- A copy of the MobileServer.exe (or ClearSCADAMobileServer.exe) configuration file from the following folder on the Geo SCADA Mobile server PC: C:\ProgramData\Schneider Electric\ ClearSCADA (The ‘Type’ column shows this as a ‘SQL Server Compact Edition Database’ file or as a ‘JSON’ file)
- A copy of the MobileConfig.sdf file or MobileServerConfig.json file (whichever one is present) from the following folder on the Geo SCADA Mobile server PC: C:\Program Files\Schneider Electric\EcoStruxure Geo SCADA Mobile\Server
- A screen shot of the error that is being seen on the mobile device
- The time of the error (if this is not shown in the screen shot from the mobile device, as per above)
- A screen shot of the ‘Mobile’ page from the Geo SCADA server configuration tool on the Geo SCADA Server PC (Configuration | System Configuration | Mobile dialog)
- Screen shots of the WebX dialog (all of it) from the Geo SCADA server configuration tool on the Geo SCADA Server PC (Configuration | System Configuration | WebX dialog)
- A screen shot of the ‘Configure Connections’ dialog on the Geo SCADA Server PC (‘Client Configuration’ dialog – showing the details of the connection)
- Screen shots of all branch dialogs of the Geo SCADA Mobile Configurator on the Geo SCADA Mobile Server PC. Ensure that screen shots of all sub branches are also collected. Screen shots required are:
- Global Settings
- Licensing
- Systems
- System name
- Devices
- Device 1 serial number
- Device 1 user
- Device 1 serial number
(It is assumed that the Device1 user, above, is the user who is attempting to connect. If a different device/user is trying to connect, please send the relevant screen shots for that device/user)
- The version of iOS or Android that is running on the mobile device
- Screen shots of IIS (Internet Information Services) – ClearSCADAMobile branch, showing:
- Bindings dialog (right-side column)
- Advanced Settings dialog (right-side column)
- Basic settings dialog (right-side column) and the resulting dialog that pops up after pressing the 'Test Settings' button from this dialog
Further information on troubleshooting Geo SCADA Mobile issues may be found at the link below:
Common Issues in Geo SCADA Mobile - Schneider Electric Community
This article should be reviewed to ensure that your system is configured accordingly.
Once this information has been collected, please reach out to the Geo SCADA Technical Support team to start troubleshooting this issue. A case will be automatically created by emailing the support group at: