General Troubleshooting guide

Root Folder
In the immortal words of the Hitchhikers Guide to the Galaxy, we remind you
Like any software installation, there are simply too many environmental factors that are outside of our control in the field. For this reason, we strongly suggest using a clean and fresh installation of Windows 7 with a minimum of Service Pack 1 where possible.
Having said that, we understand that this is not always possible, and have therefore included the following abbreviated troubleshooting guide to assist you with the more common problems that can arise.

Operating System Compatibility Issues

Pertains To
What to Look For
How to Fix It
Operating System Version
Windows 7, Service Pack 1
If you’re not on this version, upgrade or start a fresh installation on a machine that is.
Operating System Version
Windows XP/ Vista
If at all possible, upgrade the machine to Windows 7, SP1. If this is absolutely out of the question, consult your IT expert for ways to override the permissions issues.
Operating System Version
Windows 8.1
You need to be at least on 8.1 to install your application. Due to varying standards of user control, you may find that IQService and IdentityIQ refuse to save/ connect to the database in installations where these products are NOT on the same machine as your application. In this case, downgrade to Windows 7, SP1 to solve the problem, or consult a Windows security expert.


SQL Server on a Network

This guide is NOT designed to help you install and manage a SQL installation over a network.  If you do this, you will need to consult a SQL expert, or at least have the network administrator on hand to assist with any problems that may arise. However, for your guidance, we have included two common problems that affect SQL installations over a network to help reduce the frustration levels.
How to Fix It
Cannot find the SQL Server instance over the network
SQL Browser Service is probably not started if the network connections are fine.
Start the SQL Browser service, and set it to automatic start up if possible to avoid future issues. This can be done either in Windows Services or SQL Configuration Manager.
Can find the SQL Server instance on the network, but cannot connect to it.
Network Access via TCP/IP probably not configured correctly or activated.
In SQL Configuration Manager, you need to enable TCP/IP and named pipes, following which you need to restart the service.
Firewall permissions and other exceptions not correctly set.
Open Port 1433 (SQL default) on the firewall

Adding a Reader Fails to show any Data

How to Fix It
You click on a reader IP, Connect, and get N/A for all the data
IQSuite has timed out for some reason from the connection. This sometimes happens the first time you run the IQSuite Add Reader function on networks that have specific routing tables.
Click Cancel, retype the IP address, Connect again and it should work perfectly.

Add Feedback