Login Failed

#11

Thanks. Both situations appear to be application related. I'll forward the
information along to our developers.

"Russell Fields" wrote:

Quote:

BigSam,

This was a blog/discussion about 18456:
http://blogs.msdn.com/sql_protocols/...21/536201.aspx

Down in the conversation it says: "Error state 27 signifies the server could
not determine the initial database for the session. Did you specify a
database name in your connection string? Are you sure that the name was
spelled correctly?" So default databases or messed up connection strings
are the most likely here.

Could you have a commonly used default database (other than master) that is
occasionally offline for some reason? (For example, if the default database
is one that is restored periodically, nobody could connect with that default
database until the restore is complete.)

Here is another thread discussing this State 27 failure combined with
connection pooling errors.
http://forums.microsoft.com/TechNet/...8132&SiteID=17

RLF

"BigSam" <BigSam (AT) discussions (DOT) microsoft.com> wrote in message
news:A0C405E1-DD3A-4EC0-ABCD-46D3E02F5BDA (AT) microsoft (DOT) com...
Periodically I'll have these errors in SQL 2k5. Error: 18456, Severity:
14,
State: 27. After a while, they'll stop. What is causing these errors? Why
don't they occurr with every connection attempt?
The database used in the connection is a mirrored database. I do not know
what type connection the developer is using, but believe it to be using an
IP
address rather than named pipes.

#12

Thanks. Both situations appear to be application related. I'll forward the
information along to our developers.

"Russell Fields" wrote:

Quote:

BigSam,

This was a blog/discussion about 18456:
http://blogs.msdn.com/sql_protocols/...21/536201.aspx

Down in the conversation it says: "Error state 27 signifies the server could
not determine the initial database for the session. Did you specify a
database name in your connection string? Are you sure that the name was
spelled correctly?" So default databases or messed up connection strings
are the most likely here.

Could you have a commonly used default database (other than master) that is
occasionally offline for some reason? (For example, if the default database
is one that is restored periodically, nobody could connect with that default
database until the restore is complete.)

Here is another thread discussing this State 27 failure combined with
connection pooling errors.
http://forums.microsoft.com/TechNet/...8132&SiteID=17

RLF

"BigSam" <BigSam (AT) discussions (DOT) microsoft.com> wrote in message
news:A0C405E1-DD3A-4EC0-ABCD-46D3E02F5BDA (AT) microsoft (DOT) com...
Periodically I'll have these errors in SQL 2k5. Error: 18456, Severity:
14,
State: 27. After a while, they'll stop. What is causing these errors? Why
don't they occurr with every connection attempt?
The database used in the connection is a mirrored database. I do not know
what type connection the developer is using, but believe it to be using an
IP
address rather than named pipes.

#13

Thanks. Both situations appear to be application related. I'll forward the
information along to our developers.

"Russell Fields" wrote:

Quote:

BigSam,

This was a blog/discussion about 18456:
http://blogs.msdn.com/sql_protocols/...21/536201.aspx

Down in the conversation it says: "Error state 27 signifies the server could
not determine the initial database for the session. Did you specify a
database name in your connection string? Are you sure that the name was
spelled correctly?" So default databases or messed up connection strings
are the most likely here.

Could you have a commonly used default database (other than master) that is
occasionally offline for some reason? (For example, if the default database
is one that is restored periodically, nobody could connect with that default
database until the restore is complete.)

Here is another thread discussing this State 27 failure combined with
connection pooling errors.
http://forums.microsoft.com/TechNet/...8132&SiteID=17

RLF

"BigSam" <BigSam (AT) discussions (DOT) microsoft.com> wrote in message
news:A0C405E1-DD3A-4EC0-ABCD-46D3E02F5BDA (AT) microsoft (DOT) com...
Periodically I'll have these errors in SQL 2k5. Error: 18456, Severity:
14,
State: 27. After a while, they'll stop. What is causing these errors? Why
don't they occurr with every connection attempt?
The database used in the connection is a mirrored database. I do not know
what type connection the developer is using, but believe it to be using an
IP
address rather than named pipes.

#14

Thanks. Both situations appear to be application related. I'll forward the
information along to our developers.

"Russell Fields" wrote:

Quote:

BigSam,

This was a blog/discussion about 18456:
http://blogs.msdn.com/sql_protocols/...21/536201.aspx

Down in the conversation it says: "Error state 27 signifies the server could
not determine the initial database for the session. Did you specify a
database name in your connection string? Are you sure that the name was
spelled correctly?" So default databases or messed up connection strings
are the most likely here.

Could you have a commonly used default database (other than master) that is
occasionally offline for some reason? (For example, if the default database
is one that is restored periodically, nobody could connect with that default
database until the restore is complete.)

Here is another thread discussing this State 27 failure combined with
connection pooling errors.
http://forums.microsoft.com/TechNet/...8132&SiteID=17

RLF

"BigSam" <BigSam (AT) discussions (DOT) microsoft.com> wrote in message
news:A0C405E1-DD3A-4EC0-ABCD-46D3E02F5BDA (AT) microsoft (DOT) com...
Periodically I'll have these errors in SQL 2k5. Error: 18456, Severity:
14,
State: 27. After a while, they'll stop. What is causing these errors? Why
don't they occurr with every connection attempt?
The database used in the connection is a mirrored database. I do not know
what type connection the developer is using, but believe it to be using an
IP
address rather than named pipes.

#15

Thanks. Both situations appear to be application related. I'll forward the
information along to our developers.

"Russell Fields" wrote:

Quote:

BigSam,

This was a blog/discussion about 18456:
http://blogs.msdn.com/sql_protocols/...21/536201.aspx

Down in the conversation it says: "Error state 27 signifies the server could
not determine the initial database for the session. Did you specify a
database name in your connection string? Are you sure that the name was
spelled correctly?" So default databases or messed up connection strings
are the most likely here.

Could you have a commonly used default database (other than master) that is
occasionally offline for some reason? (For example, if the default database
is one that is restored periodically, nobody could connect with that default
database until the restore is complete.)

Here is another thread discussing this State 27 failure combined with
connection pooling errors.
http://forums.microsoft.com/TechNet/...8132&SiteID=17

RLF

"BigSam" <BigSam (AT) discussions (DOT) microsoft.com> wrote in message
news:A0C405E1-DD3A-4EC0-ABCD-46D3E02F5BDA (AT) microsoft (DOT) com...
Periodically I'll have these errors in SQL 2k5. Error: 18456, Severity:
14,
State: 27. After a while, they'll stop. What is causing these errors? Why
don't they occurr with every connection attempt?
The database used in the connection is a mirrored database. I do not know
what type connection the developer is using, but believe it to be using an
IP
address rather than named pipes.

#16

Thanks. Both situations appear to be application related. I'll forward the
information along to our developers.

"Russell Fields" wrote:

Quote:

BigSam,

This was a blog/discussion about 18456:
http://blogs.msdn.com/sql_protocols/...21/536201.aspx

Down in the conversation it says: "Error state 27 signifies the server could
not determine the initial database for the session. Did you specify a
database name in your connection string? Are you sure that the name was
spelled correctly?" So default databases or messed up connection strings
are the most likely here.

Could you have a commonly used default database (other than master) that is
occasionally offline for some reason? (For example, if the default database
is one that is restored periodically, nobody could connect with that default
database until the restore is complete.)

Here is another thread discussing this State 27 failure combined with
connection pooling errors.
http://forums.microsoft.com/TechNet/...8132&SiteID=17

RLF

"BigSam" <BigSam (AT) discussions (DOT) microsoft.com> wrote in message
news:A0C405E1-DD3A-4EC0-ABCD-46D3E02F5BDA (AT) microsoft (DOT) com...
Periodically I'll have these errors in SQL 2k5. Error: 18456, Severity:
14,
State: 27. After a while, they'll stop. What is causing these errors? Why
don't they occurr with every connection attempt?
The database used in the connection is a mirrored database. I do not know
what type connection the developer is using, but believe it to be using an
IP
address rather than named pipes.

#17

Thanks. Both situations appear to be application related. I'll forward the
information along to our developers.

"Russell Fields" wrote:

Quote:

BigSam,

This was a blog/discussion about 18456:
http://blogs.msdn.com/sql_protocols/...21/536201.aspx

Down in the conversation it says: "Error state 27 signifies the server could
not determine the initial database for the session. Did you specify a
database name in your connection string? Are you sure that the name was
spelled correctly?" So default databases or messed up connection strings
are the most likely here.

Could you have a commonly used default database (other than master) that is
occasionally offline for some reason? (For example, if the default database
is one that is restored periodically, nobody could connect with that default
database until the restore is complete.)

Here is another thread discussing this State 27 failure combined with
connection pooling errors.
http://forums.microsoft.com/TechNet/...8132&SiteID=17

RLF

"BigSam" <BigSam (AT) discussions (DOT) microsoft.com> wrote in message
news:A0C405E1-DD3A-4EC0-ABCD-46D3E02F5BDA (AT) microsoft (DOT) com...
Periodically I'll have these errors in SQL 2k5. Error: 18456, Severity:
14,
State: 27. After a while, they'll stop. What is causing these errors? Why
don't they occurr with every connection attempt?
The database used in the connection is a mirrored database. I do not know
what type connection the developer is using, but believe it to be using an
IP
address rather than named pipes.

#18

Thanks. Both situations appear to be application related. I'll forward the
information along to our developers.

"Russell Fields" wrote:

Quote:

BigSam,

This was a blog/discussion about 18456:
http://blogs.msdn.com/sql_protocols/...21/536201.aspx

Down in the conversation it says: "Error state 27 signifies the server could
not determine the initial database for the session. Did you specify a
database name in your connection string? Are you sure that the name was
spelled correctly?" So default databases or messed up connection strings
are the most likely here.

Could you have a commonly used default database (other than master) that is
occasionally offline for some reason? (For example, if the default database
is one that is restored periodically, nobody could connect with that default
database until the restore is complete.)

Here is another thread discussing this State 27 failure combined with
connection pooling errors.
http://forums.microsoft.com/TechNet/...8132&SiteID=17

RLF

"BigSam" <BigSam (AT) discussions (DOT) microsoft.com> wrote in message
news:A0C405E1-DD3A-4EC0-ABCD-46D3E02F5BDA (AT) microsoft (DOT) com...
Periodically I'll have these errors in SQL 2k5. Error: 18456, Severity:
14,
State: 27. After a while, they'll stop. What is causing these errors? Why
don't they occurr with every connection attempt?
The database used in the connection is a mirrored database. I do not know
what type connection the developer is using, but believe it to be using an
IP
address rather than named pipes.

#19

Thanks. Both situations appear to be application related. I'll forward the
information along to our developers.

"Russell Fields" wrote:

Quote:

BigSam,

This was a blog/discussion about 18456:
http://blogs.msdn.com/sql_protocols/...21/536201.aspx

Down in the conversation it says: "Error state 27 signifies the server could
not determine the initial database for the session. Did you specify a
database name in your connection string? Are you sure that the name was
spelled correctly?" So default databases or messed up connection strings
are the most likely here.

Could you have a commonly used default database (other than master) that is
occasionally offline for some reason? (For example, if the default database
is one that is restored periodically, nobody could connect with that default
database until the restore is complete.)

Here is another thread discussing this State 27 failure combined with
connection pooling errors.
http://forums.microsoft.com/TechNet/...8132&SiteID=17

RLF

"BigSam" <BigSam (AT) discussions (DOT) microsoft.com> wrote in message
news:A0C405E1-DD3A-4EC0-ABCD-46D3E02F5BDA (AT) microsoft (DOT) com...
Periodically I'll have these errors in SQL 2k5. Error: 18456, Severity:
14,
State: 27. After a while, they'll stop. What is causing these errors? Why
don't they occurr with every connection attempt?
The database used in the connection is a mirrored database. I do not know
what type connection the developer is using, but believe it to be using an
IP
address rather than named pipes.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Login Failed

microsoft.public.sqlserver.connect microsoft.public.sqlserver.connect

Re: Login Failed - 06-10-2008 , 10:15 AM

Re: Login Failed - 06-10-2008 , 10:15 AM

Re: Login Failed - 06-10-2008 , 10:15 AM

Re: Login Failed - 06-10-2008 , 10:15 AM

Re: Login Failed - 06-10-2008 , 10:15 AM

Re: Login Failed - 06-10-2008 , 10:15 AM

Re: Login Failed - 06-10-2008 , 10:15 AM

Re: Login Failed - 06-10-2008 , 10:15 AM

Re: Login Failed - 06-10-2008 , 10:15 AM