Re: Impossibly remote connections to SQL 2005 express


One thing that might help you:
When i migrated our application from SQLserver 2000 to 2005, i had a similar issue. That Application can not connect to SQL Server 2005.
SQL Management Studio works fine, but that Application...

The reason for this was:
- SQL Server 2000 uses case insensitive passwords
- SQL Server 2005 interpreted the same passwords with vase sensitivity
- the login dialog of the application was faulty. it converts the passwords to uppercase allways and the connection to SQL Server 2005 never worked (unless you had an uppercase password set). After fixing the App everything works fine.

gregory.white@xxxxxxxxxxxx schrieb:
I have spent the best part of 4 days trying to connect to SQL 2005
express from an winforms app! Yes , I have checked surface config and
TCP/IP blah blah ...

I have trawled the net and spent countless hours on MSDN and many have
tried to help. I have changed the passwords to strongly typed... I have
recreated the login a zillion times,mapped to different databases ,
checked firewall settings, switched off firewall...tried different
database roles, run every possible sp I can find.....attached the
database using the connection string, attached using management studio
and changing the connection string back, tried every possible
connection string I can find, pored through the logs at evry turn ...

Then i did it all again and again and again.

Has anybody managed to connect from an application ever.. (excuse the
cynicysm but I am at wits end)

The best error has to be this one proclaiming success and failure all
at the same time:

2006-11-28 22:00:24.46 Logon Login succeeded for user 'FJUser'.
Connection: non-trusted. [CLIENT: 192.xxx.x.x]
2006-11-28 22:00:24.46 Logon Error: 18456, Severity: 14, State: 16.
2006-11-28 22:00:24.46 Logon Login failed for user 'FJUser'. [CLIENT:
192.xxx.x.x]

Makes my confusion a little more bearable :-)

.

Relevant Pages

  • asp.net 2.0 login control
    ... A database with the same name exists, or specified file cannot be opened, or it is located on UNC share.] ... These problems left me stranded for days, then today, on another machine, I hit a different set of problems I kept getting the following "Failed to generate user instance of SQL Server due to a failure in starting the process for the user instance. ... (Basically this is a new option in the connection string that allows you to point out where the ..mdf file resides eliminating the need to create database in some SQL instance.) ... Beware that the windows account of the user that first creates the connection in this databaseless manner, becomes exclusive user for this file and no other windows account will be able to create a connection to this file. ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Newbie question on SQL connection
    ... database on my developer machine. ... > to develop databases away from the live SQL server - that way in the ... > domain SQL Server. ... Does your connection string contain a typo? ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: .NET and SQL Server on Separate Machines
    ... add this domain account as a valid login to your sql server. ... Everything was running correctly when the database ... > The connection string in our web.config file originally looked like this: ...
    (microsoft.public.sqlserver.connect)
  • Re: .NET and SQL Server on Separate Machines
    ... add this domain account as a valid login to your sql server. ... Everything was running correctly when the database ... > The connection string in our web.config file originally looked like this: ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: FP2003 fails to validate data connection
    ... The connection string is not correct or DSN are not correct. ... The machine is running XP Pro with IIS 5.1 and SQL Server 2000 both running. ... > The FP2003 Database Results Wizard and Database Interface Wizard have no problem locating the active DSNs on the machine, ... Other apps I have written have no problem using these DSNs. ...
    (microsoft.public.frontpage.programming)
Loading