User Tools

Site Tools


troubleshooting_guide

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
troubleshooting_guide [2014/07/01 19:01]
admin created
troubleshooting_guide [2014/08/22 19:50] (current)
Line 15: Line 15:
  
 ===SQL Server=== ===SQL Server===
-  * SQL Server 2005 Express edition [[Configuration Guide]]+  * SQL Server 2005 Express edition [[SQL 2005 Express Configuration|Configuration Guide]]
   * When installing the Evolynx RADIUS Server, if a message appears declaring that SQL server could not be fount or you do not have enough access rights, make sure your SQL Server is configured for mixed mode, not SQL mode authentication. ​   * When installing the Evolynx RADIUS Server, if a message appears declaring that SQL server could not be fount or you do not have enough access rights, make sure your SQL Server is configured for mixed mode, not SQL mode authentication. ​
   * If you see error events in Eventlog with a message like "​...Login failed for user '​EvolynxRadius'​. Reason: Not associated with a trusted SQL Server connection ...", make sure your SQL Server is configured for mixed mode, not SQL mode authentication. ​   * If you see error events in Eventlog with a message like "​...Login failed for user '​EvolynxRadius'​. Reason: Not associated with a trusted SQL Server connection ...", make sure your SQL Server is configured for mixed mode, not SQL mode authentication. ​
   * If you see the error message "SQL Server does not exist or Access Denied",​ make sure your MSDE SQL service is running (chech services). Also make sure SQL server is listening on TCP port 1433. On the same computer running SQL Server, run the command "​SVRNETCN"​ and see if TCP/IP is selected as "​Enabled Protocols"​. Check properties to make sure it is listening on port 1433.    * If you see the error message "SQL Server does not exist or Access Denied",​ make sure your MSDE SQL service is running (chech services). Also make sure SQL server is listening on TCP port 1433. On the same computer running SQL Server, run the command "​SVRNETCN"​ and see if TCP/IP is selected as "​Enabled Protocols"​. Check properties to make sure it is listening on port 1433. 
troubleshooting_guide.txt ยท Last modified: 2014/08/22 19:50 (external edit)