Re: Invalid password with ODBC connection

Tech-Archive recommends: Speed Up your PC by fixing your registry

Thank you very much for your very informative reply. I did find my problem
and it had nothing to do with SQL or ODBC. When I wrote the report and
configured for ODBC there was a check box for windows security. I checked it
because at the time I did not want to hassle with the password. However,
when I moved the report to a remote workstation it didnot work. I had to
reconfigure the report to not use windows security and put in the password.
After that all works well.

Again thank you for your assistance I did learn a couple little things from
your links.

Ron Ronhovde

"Sylvain Lafontaine" wrote:

Maybe a permission problem here: connecting to the sql-server doesn't mean
that you have sufficient permission to access a database on this server or
any object inside a database (for reading or reading/writing). There are
other possibilities; for example you didn't save the password with your
connection string and the program that you are using cannot interarctively
ask your for the password if an ODBC call fail. As you have given any
detail on your setup or your report viewer application, it's hard to give
you any other suggestion but you could try changing the protocol; for
example using tcp: instead of np: or vice-versa; for example:

sqlcmd -S tcp:NameOfTheServer\sqlexpress,1433

The use of an alias for the name of the server could also help you in
solving your connection problem. Here are some references on this topic:

http://blogs.msdn.com/sql_protocols/archive/2007/07/19/tcp-provider-no-connection-could-be-made-because-the-target-machine-actively-refused-it.aspx

http://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx

http://blogs.msdn.com/sqlexpress/archive/2004/07/23/192044.aspx

http://msdn2.microsoft.com/en-us/library/ms345318.aspx

http://www.datamasker.com/SSE2005_NetworkCfg.htm

--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)


"Ron Ronhovde" <Ron Ronhovde@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E55F1798-F8A4-436B-9B86-ADB25EFCC284@xxxxxxxxxxxxxxxx
I have SQL 2005 Express running on XP SP2 in a workgroup environment. When
I
attempt to connect to the database, via ODBC, from another workstation in
the
workgroup with our report viewer I get an error of Incorrect password. I
tested the OCBC connection when I created it and it connected.

What could cause an ODBC connection to fail from a program setup to use
the
protocol? I have talked to the software vendor and they do not understand
why it is happening either.

Any suggestions will be greatly appreciated.

Ron Ronhovde



.

Relevant Pages

  • Re: [VW 7.3.1] ODBCConnection
    ... I played around with a few combinations on the connection string and ... with a trusted SQL Server connection. ... there are differences for database connects. ... > any database specific odbc drivers. ...
    (comp.lang.smalltalk)
  • Re: Ada DB bindings and APQ
    ... >>I didn't like the use of handles for database objects. ... > will ensure that the connection will not go away until at least one query ... > things which can be made with a connection. ... That is different to ODBC. ...
    (comp.lang.ada)
  • Re: Mailmerge using a secure database
    ... Database does not have a long path name. ... When I tried re-opening my mail merge documents I get an error message ... Do you need or want specifically to connect with ODBC? ... likely to run into problems where Word truncates the connection string ...
    (microsoft.public.word.mailmerge.fields)
  • Re: Linking Access f/e to Access b/e via ODBC
    ... > Is it possible then to create an ODBC connection to use the ISAM driver ... If I understand your question correctly, the ISAM driver for Jet _is_ what ... you're getting when you create the DSN for an Access database file. ... the ODBC Data Source Administrator can create the DSN to the Access ...
    (microsoft.public.access.externaldata)
  • Re: Trusted Connection
    ... HOWEVER, for one of my users, I will create an ODBC DSN ... for my test database ON THEIR COMPUTER, ... So, when I set up the ODBC DSN connection for this user, ... >> Our SQL Server was set up NOT by me, ...
    (microsoft.public.sqlserver.security)