Scenario 1: Timeout Behavior
Resolution: This scenario existed only in SEE 12.0.0 and has been resolved with SEE 12.0.1 release and above.
1. SEE Web Console not accessible with an error "The server is currently inaccessible. Retry Later"
2. SEE 12.0 Clients have issues connecting to the server
EPG-35659
Scenario 2: The following appears:
The SEE Web Console login is successful if the admin is added as a single user.
When adding the admin to a Security Group that has permissions to login, the user is not granted access.
Resolution: This may be due to the Database authentication mode being set to "SQL Authentication", rather than Windows Authentication.
When SQL Authentication is used, the App Pools identity will be set to a generic account called "Network Service".
Network Service is a valid account, but is a generic account that may not have read-only access to the Active Directory.
If you do not allow Network Service to read AD objects, it will be better to use a different account to accommodate this.
The account that you use needs to be a valid domain account, but read-only access is all that is needed.
You can assign this to the SEEMS Configuration screen under the "Database" tab.
Then, where "SQL server authentication" is selected, click "Change" next to the "Web application pool identity" and select the account you would like to use.
This account need only be read-only and does not require any special permissions to the directory.
Once this is done, click Save.
Scenario 3: MS SQL server services not running or disabled.
Make sure that SQL services are running and started.
1. SQL Server Service
2. SQL Browser