|
thanks for your reply but it didnt work i try it many times before  do u have any thing else?
|
|
|
|
|
Are you able to connect with SQL Server Management Studio?
|
|
|
|
|
|
What type of application did you connect with SQL Server? ASP.NET or Windows application?
What type of authentication are you using to connect?
|
|
|
|
|
Asp.net and im using mixed mode
my code
string m = "Data Source=./SQLEXPRESS;AttachDbFilename=C:/Program Files/Microsoft SQL Server/MSSQL.1/MSSQL/Data/TestData.mdf;Integrated Security=True;Connect Timeout=30;User Instance=True";
SqlConnection mycon = new SqlConnection(m);
mycon.open();
|
|
|
|
|
|
You are missing DATABASE name in connection string.
|
|
|
|
|
So you are using Windows Authentication.
ASP.NET application will be running under ASPNET account if you open your site from local IIS.
Therefore the ASPNET may not have access to the database. Try to use SQL authentication.
Also the database path should look like C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\TestData.mdf. I am not sure ADO.NET will accept / in a path specification.
|
|
|
|
|
Is your connection string correct?
Post it
|
|
|
|
|
what is wrong with my connecting string????
|
|
|
|
|
|
i add database name but it give me the same result 
what is ment by Verify that the instance name is correct ?????
|
|
|
|
|
Data Source=./SQLEXPRESS
./SQLEXPRESS
This is instance name.
Check in your management studio if this is correct.
HTH
|
|
|
|
|
just do the following steps
goto StartMenu ---->SqlServer----->Configuration Tools-------->SQL Server Configuration Manager
and check in NAMED PIPES protocol is enabled or not 
Best Of Regards,
SOFTDEV
If you have knowledge, let others light their candles at it
|
|
|
|
|
i enabled it and it suggest to restart sql what to do next????
|
|
|
|
|
Restart your pc or restart the SQL services.
Control Panel > Administrative Tools > Services
|
|
|
|
|
ops
it didnt work ido all thing but the same problem occured
|
|
|
|
|
Have you enabled
Client Protocol > Named Pipes ?
|
|
|
|
|
services can be restarted by right clicking your sql server in Management studio and clicking on restart or from windows services (typing services.msc in run will open)
Best Of Regards,
SOFTDEV
If you have knowledge, let others light their candles at it
|
|
|
|
|
sorry for being late.......please tell me how to enable sql browser
|
|
|
|
|
in sql server configuration area
Sql server services
Best Of Regards,
SOFTDEV
If you have knowledge, let others light their candles at it
|
|
|
|
|
nothing else if you are connecting through Named Pipes then you should enable Named Pipes and if you are connecting through TCP/IP then you should enable your tcp/ip protocol , make sure your SQL Browser is also started....
Best Of Regards,
SOFTDEV
If you have knowledge, let others light their candles at it
|
|
|
|
|
Do you trying to connect SQL Server via a proxy server... please let me know.
I will not say I have failed 1000 times; I will say that I have discovered 1000 ways that can cause failure – Thomas Edison.
Don't forget to click [Vote] / [Good Answer] on the post(s) that helped you.
Thanks
Md. Marufuzzaman
|
|
|
|
|
You are using forward slashes throughout your connection string. Change them all to back slashes.
./SQLExpress should be .\SQLExpress
Your AttachDBFileName is C:/whatever/wherever/......... and should be C:\whatever\wherever\.........
If you do that all should work.
When you get an error message you should pay attention to what it says. The error message talked about the SQL Server. The only reference to the server was ./SQLExpress, so that is where you should start looking. Changing it, as I suggest would possibly have caused a different error (for the slashes in your path, although that might have worked, I haven't tested it). Always read your error messages carefully! 
Henry Minute
Do not read medical books! You could die of a misprint. - Mark Twain
Girl: (staring) "Why do you need an icy cucumber?"
“I want to report a fraud. The government is lying to us all.”
|
|
|
|
|
This is the most common problem when Database server couldnt be reached.
Check if you made firewall exemption to the SQL Server browser
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
