You have entered your username and password and the program does not allow you access.
There are several reasons why you can't get in, here are some possibilities:
•You've made a mistake when typing your username or password. Retype it correctly.
Password is case-sensitive so check if CAPS LOCK is on, turn it off and retype your password.
If you've forgotten your password, ask your DevMan power-user to give you another.
•It may be something you can't fix yourself i.e. a technical reason such as -
your DevMan database is offline or your network or server may be inaccessible.
•Your account may have been deactivated if you haven't logged on for three months or more.
See Security > Inactive user account to see how to reactivate your user profile.
You've followed all the suggestions and you still cannot get into the program. It's most likely because of some technical problem and you will need to contact your IT department.
Here are some messages where this is true.
(Reasons are given which may help your support person to diagnose and solve the problem).
•KidzNNNNNtion] Cannot open database requested in login ' 'KidzNNNNN'. Login fails. Login failed for user 'KidzNNNNN'.
This problem occurs when the SQL Server security authentication is set to Windows only, and one of the following conditions is true: You are trying to connect to a SQL Server database with a SQL Server login, You are trying to connect to a SQL Server database from a Windows account that does not have sufficient permissions to connect to the server.
•[SqlException] An error has occurred while establishing a connection to the server.
When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server).
•[SQLException] Login failed for user ...Not associated with a trusted SQL Server connection ...
With the above your organisation IT representative may need to consider the following:
If the database has been upgraded or reinstalled or the method of authentication to the database has been altered in some way then it is possible to receive the above message.