Connectivity issues

Hi,

I get the following error message trying to connect locally to sql server 2005 dev edition on xp sp2 machine.

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (.Net SqlClient Data Provider)

I have enabled all protocols , the sql browser is running , sql agent and sql database engine not running. All other services like reporting etc are running.

The server is set up to run under local system account. Logging in as administrator, .

This server is installed as default instance . ( I do have sql exp and sql server 200 dev edition installed as named instances)

Beginning to pull my hair out.

Any help would be greatly appreciated.

Regards,

Well, you said the database engine is NOT running? From the looks of things that's what you're trying to connect to...I'll assume a typo maybe? The DB Engine service must be running if you're trying to connect to the SQL engine...

|||

Thank you Chad for the illuminating response.

The problem is precisely that the database engine will not start , I understand that the engine must running order for me to connect to a database , however I have made no mention of trying to connect to a database.

If you have any helpful suggestions I would really appreciate it.

Thank you

Andy

|||

Hi Andy...honestly, everything you wrote in your initial posting was indicating that you were having trouble trying to connect to the server...per your initial post:

"I get the following error message trying to connect locally to sql server 2005 dev edition on xp sp2 machine."

Then, the error message you posted indicates that you are indeed trying to connect to the server from an application:

"An error has occurred while establishing a connection to the server...."

And, it even describes a connection level provider (named pipes)...

So, given your original posting, it seems you are having trouble connecting to the instance, not getting it running. Myself and others would be more than happy to help you debug why you are having trouble getting the engine to start, but we'd need entirely different information.

If you'd like help with why the engine is not able to start, please post any error messages you notice in the application log, sql server error log, and system log related to the SQL Server instance, that's what we'd need to see to help you understand why the engine will not start.

On a final note, bear in mind that folks on the forums are trying to help you, not trying to insult you, and you'll always get more help if you treat myself and others with respect, not by being smart with us. You may notice that I am an administrator of these SQL forums, so please keep posts as civil as possible.

Regards

|||

HI Chad,

My apologies for coming across so curt , having re-read my response it does seem as though I was being rude , not my intention. Perhaps a bit of frustration creeping in, the problem is that my vocabulary and knowledge is lacking and expressing myself in a meaningful way is difficult and perhaps to some one with your knowledge, confusing.

If I am getting an error as described above when trying to get an instance started (i.e. the error is generated when I try and get the engine started) through Management Studio then I assume that error is relevant and that is what I will report on. Having read your second post it is now obvious that the error describes a connection problem rather than an issue regarding the instance running.( which obviously is as result of the engine not running.)

I checked the error log and found a network error which I googled , it seems as though if the via protocol is the culprit , having disabled this protocol the engine started .

The network error in the log:

TDSSNIClient initialization failed with error 0x7e, status code 0x60.

Thank you and my apologies once again.

|||

No worries, I definately understand frustation, we're all quite accustomed to that unfortunately. Glad you were able to get things working,

Regards,

sqlsql

Connection string for MSDE 2000

Hi,
I have a simple asp.net application running ok on my WinXP development
server with SQL Server Express 2005 installed locally. After moving to
the live server (Win 2000 server with MSDE 2000 installed locally),
it's giving me the 'SQL Network Interface Error (error 25): connection
string is not valid'.
So far, i've tried using the following connection string in my
web.config file:
connectionString="Data
Source=.\SQLEXPRESS;AttachDbFilename=|DataDirector y|\registration.mdf;Integrated
Security=True;User Instance=True" providerName="System.Data.SqlClient"
(this works fine on the development server)
connectionString="Data Source=(local);Initial
Catalog=registration;Integrated Security=SSPI"
Does anyone know how to solve this issue? Or is it just not possible to
use Sql Server .NET Data Provider (System.Data.SqlClient) that I used
in the development server to connect to a MSDE 2000 database on the
live server? Originally I wanted to use SQL Server Express 2005 on the
live server, but I didn't enough memory on it, so I figured I tried
MSDE 2000 first to see if I can get the right connection string.
Any help would be appreciated.
THanks,
hfk0
Microsoft SQL Server .NET Data Provider (System.Data.SqlClient) allows
you to connect to a Microsoft SQL Server 7.0, 2000, and 2005 databases
MSDE2000 does not support user instatnce, with which you can attach a
database file (*.mdf) by specifying a file name in connectionString. The
database file (*.mdf) must be attached/installed on the MSDE first before
your ASP.NET app runs.
Also, is the MSDE instance named as "ComputerName\SQLExpress"?
"hfk0" <hery@.infoventures.com> wrote in message
news:1142448305.817752.118520@.j33g2000cwa.googlegr oups.com...
> Hi,
> I have a simple asp.net application running ok on my WinXP development
> server with SQL Server Express 2005 installed locally. After moving to
> the live server (Win 2000 server with MSDE 2000 installed locally),
> it's giving me the 'SQL Network Interface Error (error 25): connection
> string is not valid'.
> So far, i've tried using the following connection string in my
> web.config file:
> connectionString="Data
> Source=.\SQLEXPRESS;AttachDbFilename=|DataDirector y|\registration.mdf;Integrated
> Security=True;User Instance=True" providerName="System.Data.SqlClient"
> (this works fine on the development server)
> connectionString="Data Source=(local);Initial
> Catalog=registration;Integrated Security=SSPI"
> Does anyone know how to solve this issue? Or is it just not possible to
> use Sql Server .NET Data Provider (System.Data.SqlClient) that I used
> in the development server to connect to a MSDE 2000 database on the
> live server? Originally I wanted to use SQL Server Express 2005 on the
> live server, but I didn't enough memory on it, so I figured I tried
> MSDE 2000 first to see if I can get the right connection string.
> Any help would be appreciated.
> THanks,
> hfk0
> Microsoft SQL Server .NET Data Provider (System.Data.SqlClient) allows
> you to connect to a Microsoft SQL Server 7.0, 2000, and 2005 databases
>
|||Hi Norman,
How do I attach/install the *.mdf file on MSDE? Also how do I find out
the MSDE instance name? On the dev server I have SQL Express 2005
installed locally so on the connection string, Data Source=.\SQLEXPRESS
(the dot refers to localhost and SQLEXPRESS the instance name).
Thanks for your help.
hfk0
|||hi,
hfk0 wrote:
> Hi Norman,
> How do I attach/install the *.mdf file on MSDE?
you have to use sp_attach_db system stored procedure,
http://msdn.microsoft.com/library/de...ae-az_52oy.asp
or
http://msdn.microsoft.com/library/de...ae-az_4wrm.asp
...

>Also how do I find out
> the MSDE instance name? On the dev server I have SQL Express 2005
> installed locally so on the connection string, Data
> Source=.\SQLEXPRESS (the dot refers to localhost and SQLEXPRESS the
> instance name).
try having a look at the SQL Server Service Manager in the icon tray.. it
should list the available local instances.. or use oSql.exe command tool
like
c:\>osql.exe -L
(parameters are case sensitive) that will list all available Instances in
you lan... or open the service management applet and seek for MSSQLSERVER
(default instance) or MSSQL$InstanceName (named instance)
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.18.0 - DbaMgr ver 0.62.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi Andrea and Norman,
After trying the following:
- Reconfigured MSDE authentication mode to mixed mode.
- Enabled and configured Named Pipes and TCP/IP protocol using SQL
server network utility.
- Changed connection string on web.config file to
connectionString="Data Source=90.0.0.55,1433;Network
Library=DBMSSOCN;Initial Catalog=registration;User
ID=sa;Password=fmypassword;"
I'm now getting a different error message on the browser:
Cannot open database requested in login 'registration'. Login fails.
Login failed for user 'sa'.
I'm also getting the following message when trying to attach my SQL
database (default instance):
Error 602 Could not find row in sysindexes. run DBCC CHECKTABLE on
sysindexes.
Any clues?
|||hi,
hfk0 wrote:
> Hi Andrea and Norman,
> After trying the following:
> - Reconfigured MSDE authentication mode to mixed mode.
> - Enabled and configured Named Pipes and TCP/IP protocol using SQL
> server network utility.
> - Changed connection string on web.config file to
> connectionString="Data Source=90.0.0.55,1433;Network
> Library=DBMSSOCN;Initial Catalog=registration;User
> ID=sa;Password=fmypassword;"
> I'm now getting a different error message on the browser:
> Cannot open database requested in login 'registration'. Login fails.
> Login failed for user 'sa'.
SQLExpress and MSDE install by default dsabling standard SQL Server
authenticated connections, allowing only truste WinNT connections..
to modify this behavior at "run-time", please have a look at
http://support.microsoft.com/default...b;en-us;285097 in the
section regardin "windows registry" hacking ..

> I'm also getting the following message when trying to attach my SQL
> database (default instance):
> Error 602 Could not find row in sysindexes. run DBCC CHECKTABLE on
> sysindexes.
>
If during the attach process, SQL Server finds the DB to be corrupt, it will
not attach and you can't run DBCC's against it. If this is your problem, you
need to find a valid backup.
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.18.0 - DbaMgr ver 0.62.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||hi,
hfk0 wrote:
> I did changed to windows registry to enable mixed authentication mode
> as well as replaced the seemingly corrupted SQL database, but i'm
> still getting the very same message when attaching the database
> (which is created in Visual Studio.Net 2005) to MSDE:
> Msg 602, Level 21, State 50, Server [name], Line 1
> Couldnot find row in sysindexes for database ID 5, object ID 1, index
> ID 1
> Run DBCC CHECKTABLE on sysindexes
> I wish microsoft would write this error message in plain english
> I'm stuck now and don't know what to do. Perhaps SQL Server Express
> database instance is just not backward compatible with MSDE instance?
SQL Server 2005 database can not be attached to SQL Server 2000 instances..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.18.0 - DbaMgr ver 0.62.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

connection string does not work for a different server

Hi all,
I currently have an ASP .Net project running locally,
and accessing a local SQL server 2000 database. The
project runs fine since it is able to open the connection to the database,
and perform operations on it locally using
a connection dtata string pointing to the local data source.
However, when I wanted to point to a different server
using the same definitions, the connection did not work.
The only changes have been the name of the data source.
From (local) to SQL9, and the catalog from openhouse to srm. A user with the
same ID, and password was defined
in the target SQl server using the same permissions, and the authentication
is windows and SQL server.
I am able to ping to the server, and access the tables of this database
using enterprise manager using the user
that was defined. At this point I do not know what to
do. Any suggestion is greatly appreciated.
Thanks,
Carlos.
Can you post the error/exception you get?
Vikram Vamshi
Eclipsys Corporation
"Carlos" <chsanin@.earthlink.net> wrote in message
news:u52OyjIGFHA.3824@.TK2MSFTNGP10.phx.gbl...
> Hi all,
> I currently have an ASP .Net project running locally,
> and accessing a local SQL server 2000 database. The
> project runs fine since it is able to open the connection to the database,
> and perform operations on it locally using
> a connection dtata string pointing to the local data source.
> However, when I wanted to point to a different server
> using the same definitions, the connection did not work.
> The only changes have been the name of the data source.
> From (local) to SQL9, and the catalog from openhouse to srm. A user with
> the
> same ID, and password was defined
> in the target SQl server using the same permissions, and the
> authentication
> is windows and SQL server.
> I am able to ping to the server, and access the tables of this database
> using enterprise manager using the user
> that was defined. At this point I do not know what to
> do. Any suggestion is greatly appreciated.
> Thanks,
> Carlos.
>

connection string does not work for a different server

Hi all,
I currently have an ASP .Net project running locally,
and accessing a local SQL server 2000 database. The
project runs fine since it is able to open the connection to the database,
and perform operations on it locally using
a connection dtata string pointing to the local data source.
However, when I wanted to point to a different server
using the same definitions, the connection did not work.
The only changes have been the name of the data source.
From (local) to SQL9, and the catalog from openhouse to srm. A user with the
same ID, and password was defined
in the target SQl server using the same permissions, and the authentication
is windows and SQL server.
I am able to ping to the server, and access the tables of this database
using enterprise manager using the user
that was defined. At this point I do not know what to
do. Any suggestion is greatly appreciated.
Thanks,
Carlos.Can you post the error/exception you get?
Vikram Vamshi
Eclipsys Corporation
"Carlos" <chsanin@.earthlink.net> wrote in message
news:u52OyjIGFHA.3824@.TK2MSFTNGP10.phx.gbl...
> Hi all,
> I currently have an ASP .Net project running locally,
> and accessing a local SQL server 2000 database. The
> project runs fine since it is able to open the connection to the database,
> and perform operations on it locally using
> a connection dtata string pointing to the local data source.
> However, when I wanted to point to a different server
> using the same definitions, the connection did not work.
> The only changes have been the name of the data source.
> From (local) to SQL9, and the catalog from openhouse to srm. A user with
> the
> same ID, and password was defined
> in the target SQl server using the same permissions, and the
> authentication
> is windows and SQL server.
> I am able to ping to the server, and access the tables of this database
> using enterprise manager using the user
> that was defined. At this point I do not know what to
> do. Any suggestion is greatly appreciated.
> Thanks,
> Carlos.
>

Connection remotely gives error.

Hi
When I sign on to my SQL server locally using windows authentication all is
ok.
When I sign on at a client PC I get "Logon failed for user xxx/guest"
Using SQL Authority works ok.
Any suggestions?
TimWhen you connect remotely are you logged into the domain?
Can you map a drive to the SQL Server machine?
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Kevin,
Thanks for the reply.
I have solved the problem now, it was down to permissions.
Tim
"Kevin McDonnell [MSFT]" <kevmc@.online.microsoft.com> wrote in message
news:bPJp2bFkEHA.2632@.cpmsftngxa10.phx.gbl...
> When you connect remotely are you logged into the domain?
> Can you map a drive to the SQL Server machine?
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>