Re: Problem connecting to an SQL 2005 Express Instance in RANU mod

Remember that I'm working in RANU mode with the AttachDbFileName keyword in
the connection string.
Again, everything works fine with Windows XP. So this may be tied to the new
security model under VISTA, and I'm wondering where to search to find the
real problem here.
TIA.

"William Vaughn" wrote:

I expect you're missing the "Initial Catalog" or "Default Database" key in
the ConnectionString.
The error means you don't have access to the default database for the
selected user.


--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
-----------------------------------------------------------------------------------------------------------------------

"Olivier MATROT" <olivier.matrot.rte@xxxxxxxxxxxxx> wrote in message
news:59979870-E887-48A6-9A58-684730CED2F9@xxxxxxxxxxxxxxxx
I should have looked in the error log to know more.
Today I encountered the same problem on a Vista box.

The error log shows :
2007-09-27 15:28:04.37 Logon Error: 18456, Severity: 14, State: 11.
2007-09-27 15:28:04.37 Logon Login failed for user
'VistaEnt\rtefaxmfp'. [CLIENT: <named pipe>]

State 11 means "Login is valid but server access failed".
Where should I look to get more information about this issue ?
TIA.


"William Vaughn" wrote:

Ah, sort of. If a user is logged on to the domain then yes, you need a
visible (and functioning) domain controller to validate the credentials
(each time you execute Open). In some cases you can get away with not
having
a functioning domain controller for N hours but after that it will insist
on
reauthenticating with the DC.

However, if the user logs on to the MACHINE (and not the domain), the
machine registered User credentials are used when using SSPI
authentication.

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no
rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
-----------------------------------------------------------------------------------------------------------------------

"Olivier MATROT" <olivier.matrot.rte@xxxxxxxxxxxxx> wrote in message
news:F46A8F26-2271-4471-8CF5-D5A49819D0B5@xxxxxxxxxxxxxxxx
Solved the problem.
When a computer is a domain member, only domain users are valid with
SQL
Integrated Security.

"Olivier MATROT" wrote:

Hello,
I'm using SQL2005 Express User Instance Feature.
The OS is Windows XPSP2 up to date with updates.
I have a problem connecting to the SQL 2005 Express instance when it
is
installed while the computer is a domain member.
The user instance is accessed by a local user (as opposed to a domain
user)
attaching an MDB file with the following connection string :
"Data source=.\RTEFAXMFP;Trusted_Connection=yes;Application
Name=RTEFCDDBXP.DLL;AttachDbFileName='C:\Documents and Settings\All
Users\Application Data\RTE\RTE
FAX\SQLExpressDatabase\RTEFAXMFP.mdf';User
Instance=True".
The error is "Login failed for user 'SETUPRTEFAXEX\rtefaxmfp'.".

When the SQL Express Instance is installed while the computer is in a
workgroup, there is no problem at all.
TIA.




.

Relevant Pages

  • Re: Problem connecting to an SQL 2005 Express Instance in RANU mod
    ... I expect you're missing the "Initial Catalog" or "Default Database" key in the ConnectionString. ... Hitchhiker's Guide to Visual Studio and SQL Server ... and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook) ... >> I'm using SQL2005 Express User Instance Feature. ...
    (microsoft.public.sqlserver.connect)
  • Re: Any harm in using Async=true to sql server 2005 for non-async db calls
    ... Hitchhiker's Guide to Visual Studio and SQL Server ... and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook) ... Processing=True" in my connection string to a sql server 2005 database ... for both async db calls and non async calls? ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Connection issues between .Net framwok and SQl Express 2005
    ... the simplest way is to not use USER INSTANCE. ... simply attach the ASPNETDB.mdf to SQL Server permenantly, ... Study on SQL Server Epxress USER INSTANCE is always good if you are to use ... With regards to your suggested connection string solution, ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Connection issues between .Net framwok and SQl Express 2005
    ... Look up sp_attachdb in the books online with SQL Server Express. ... You will no longer need the database MDF file name in the connection string. ... the simplest way is to not use USER INSTANCE. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: How migrate from SQL Express to SQL Server
    ... Would I have had to explicitly used User Instance? ... Hitchhiker's Guide to Visual Studio and SQL Server ... and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook) ...
    (microsoft.public.dotnet.framework.adonet)