ADO Error Code:0x80040e4d

[Do Park via SQLMonster.com]

Hello all,
I use Crystal Report v9, SQL server 2000.
When I try to connect to a Database via ADO, I got the following error.

Login failed.
Details :ADO Error Code:0x80040e4d
Source:Microsoft OLE DB Provider for SQL Server
Description:Login failed for use’xxxxxxx’
SQL State: 42000
Native Error:18456

Is there anyone how has this problem?
How can I fix this?

Thanks in advance,
Do.

--
Message posted via http://www.sqlmonster.com

[Simon Hayes]

"Do Park via SQLMonster.com" <fo***@nospam.SQLMonster.com> wrote in message
news:9c******************************@SQLMonster.c om...

Hello all,
I use Crystal Report v9, SQL server 2000.
When I try to connect to a Database via ADO, I got the following error.

Login failed.
Details :ADO Error Code:0x80040e4d
Source:Microsoft OLE DB Provider for SQL Server
Description:Login failed for use'xxxxxxx'
SQL State: 42000
Native Error:18456

Is there anyone how has this problem?
How can I fix this?

Thanks in advance,
Do.

--
Message posted via http://www.sqlmonster.com

"Login failed" suggests that you need to check the login you're using to
connect with - is it a SQL login, or a Windows account; are you using a DSN
or a connection string; can you connect from osql.exe or Query Analyzer
using the same account (or another account) etc.

Simon

[Do Park via SQLMonster.com]

I use Windows authentication. I can access other databases via the same way
(Crystal Report). I connected this database via ADO successfully two or
three days ago. There was no change in my environment and SQL Server.

Best regards,
Do.

--
Message posted via http://www.sqlmonster.com

[Erland Sommarskog]

Do Park via SQLMonster.com (fo***@SQLMonster.com) writes:

I use Windows authentication. I can access other databases via the same
way (Crystal Report). I connected this database via ADO successfully two
or three days ago. There was no change in my environment and SQL
Server.

Probably there was. Unfortunately, it is impossible for us who don't
have access to your environment to tell what is going on. You will
have to see your local admin to sort it out.
--
Erland Sommarskog, SQL Server MVP, es****@sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp