FlexLink YOUTILIZE - Manual (Page 98)

Providing production efficiency
Page 98 of 125
Troubleshooting
SQL Server
Unable to Connect to the Database
When the software throws this error, it indicates that there was some kind of problem when
attempting to connect to the SQL Server Express database. When the software starts up, it attempts
to connect to the database. If the database does not respond, it simply returns this error. The
system has no ability to diagnose why. This error is kind of like the "Service Engine" light on your
vehicle. When the service engine light starts flashing, it means something is wrong, but it is a very
general warning that does not give you much information on what is wrong, just that something is
wrong. The cause of it could be anything from a loose gas cap to a failed spark plug to some bad
sensor.
When it comes to the cannot connect error, it can range from the long file path issue to interference
from UAC, to permissions issues, to a conflict with an existing installation of SQL Server, to registry
entries, to the location of the installation file on your computer. The list is long. Here is a
troubleshooting guide to try and help you diagnose what particular problem is vexing you and how
to repair it. If the troubleshooting is getting you nowhere, the full manual install is another method
that may be more effective, as you take things into your own hands and have better visibility to
errors.
As a potential source of more information to diagnose the problem with, you could always look for
connection errors in both
C:\Program Files (x86)\Microsoft SQL
Server\MSSQL10_50.IMONITOREXPRESS\MSSQL\Log\ERRORLOG
and
You may have to use an administrator account to read this file. As an example ERRORLOG entry:
2011-01-02 11:32:15.08 Logon Error: 18456, Severity: 14, State: 38.
2011-01-02 11:32:15.08 Logon Login failed for user 'EXAMPLE\Example'.
Reason: Failed to open the explicitly specified database. [CLIENT: <named
pipe>]