Login Failed error 18456

I was reviewing our logs from yesterday and today and I have probably 100
errors:
12/21/2005 08:30:26,Logon,Unknown,Login failed for user 'ApplicationUser'.
[CLIENT: 1.1.1.119]
12/21/2005 08:30:26,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State:
16.
This is the login that we are using for our application login. We haven't
had any reports of anyone not being able to log on or anything but there are
over 100 errors in the error logs. The user has a server role of dbcreator,
and is mapped to several databases with a role membership of db_datareader,
db_datawrite, and public. Our application uses this account to login to SQL
Server.
We are using SQL Server version 2005.
What are the possible causes to this error? It seems like it is a simple
login failure, but trust me when i tell you...if people were not able to
logon we would hear about it.
Thanks for any insight you might be able to provide.
RonCould It be that the Standarddatabase of the user is not present
anymore ? This usally happens when you moved a database and scripted
out the users with their original database which isn=B4t present on the
destination system. Try to check that in Dev Studio.
HTH, Jens Suessmeyer.|||Pardon my newbe question...but what is the StandardDatabase? is it a
database that they were given rights to but then the database was removed?
Your response sounds right in the fact that we added the user to the Model
database so that they were given rights based on that database when every
new database was converted. We had a problem with the application and one
of the databases that was converted and ended up removing it temporarily to
fix the problem in the application...could that be the culprit?
Thanks!
Ron
"Jens" <Jens@.sqlserver2005.de> wrote in message
news:1135176452.767970.33270@.g47g2000cwa.googlegroups.com...
Could It be that the Standarddatabase of the user is not present
anymore ? This usally happens when you moved a database and scripted
out the users with their original database which isnt present on the
destination system. Try to check that in Dev Studio.
HTH, Jens Suessmeyer.