I get the following message:
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)
From the following code:
<%@. Page Language="VB" Debug="true" %>
<script runat="server">
Dim ConnectionString As String = "server=
(local);database=ASPExamples"
Dim SelectCommand As String = "SELECT CustomerID, name, phone from
customers"
Dim isEditing As Boolean = False
Dim myConnection As New SqlConnection(ConnectionString)
Dim myCommand As New SqlDataAdapter(SelectCommand, myConnection)
Dim ds As New DataSet()
myCommand.Fill(ds)
DataGrid1.DataSource = ds
DataGrid1.DataBind()
End SubSee:
http://betav.com/blog/billva/2006/0...onnected_1.html
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
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)
----
---
"Roger Halls" <roghalls@.gmail.com> wrote in message
news:Xns992A7925D4244roghallsgmailcom@.19
8.186.190.150...
>I get the following message:
> 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)
> From the following code:
> <%@. Page Language="VB" Debug="true" %>
> <script runat="server">
> Dim ConnectionString As String = "server=
> (local);database=ASPExamples"
> Dim SelectCommand As String = "SELECT CustomerID, name, phone from
> customers"
> Dim isEditing As Boolean = False
> Dim myConnection As New SqlConnection(ConnectionString)
> Dim myCommand As New SqlDataAdapter(SelectCommand, myConnection)
> Dim ds As New DataSet()
> myCommand.Fill(ds)
> DataGrid1.DataSource = ds
> DataGrid1.DataBind()
>
> End Sub
Showing posts with label failure. Show all posts
Showing posts with label failure. Show all posts
Tuesday, March 27, 2012
Sunday, March 25, 2012
connection problem
I get the following message:
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)
From the following code:
<%@. Page Language="VB" Debug="true" %>
<script runat="server">
Dim ConnectionString As String = "server=
(local);database=ASPExamples"
Dim SelectCommand As String = "SELECT CustomerID, name, phone from
customers"
Dim isEditing As Boolean = False
Dim myConnection As New SqlConnection(ConnectionString)
Dim myCommand As New SqlDataAdapter(SelectCommand, myConnection)
Dim ds As New DataSet()
myCommand.Fill(ds)
DataGrid1.DataSource = ds
DataGrid1.DataBind()
End Sub
See:
http://betav.com/blog/billva/2006/06/getting_and_staying_connected_1.html
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
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)
------
"Roger Halls" <roghalls@.gmail.com> wrote in message
news:Xns992A7925D4244roghallsgmailcom@.198.186.190. 150...
>I get the following message:
> 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)
> From the following code:
> <%@. Page Language="VB" Debug="true" %>
> <script runat="server">
> Dim ConnectionString As String = "server=
> (local);database=ASPExamples"
> Dim SelectCommand As String = "SELECT CustomerID, name, phone from
> customers"
> Dim isEditing As Boolean = False
> Dim myConnection As New SqlConnection(ConnectionString)
> Dim myCommand As New SqlDataAdapter(SelectCommand, myConnection)
> Dim ds As New DataSet()
> myCommand.Fill(ds)
> DataGrid1.DataSource = ds
> DataGrid1.DataBind()
>
> End Sub
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)
From the following code:
<%@. Page Language="VB" Debug="true" %>
<script runat="server">
Dim ConnectionString As String = "server=
(local);database=ASPExamples"
Dim SelectCommand As String = "SELECT CustomerID, name, phone from
customers"
Dim isEditing As Boolean = False
Dim myConnection As New SqlConnection(ConnectionString)
Dim myCommand As New SqlDataAdapter(SelectCommand, myConnection)
Dim ds As New DataSet()
myCommand.Fill(ds)
DataGrid1.DataSource = ds
DataGrid1.DataBind()
End Sub
See:
http://betav.com/blog/billva/2006/06/getting_and_staying_connected_1.html
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
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)
------
"Roger Halls" <roghalls@.gmail.com> wrote in message
news:Xns992A7925D4244roghallsgmailcom@.198.186.190. 150...
>I get the following message:
> 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)
> From the following code:
> <%@. Page Language="VB" Debug="true" %>
> <script runat="server">
> Dim ConnectionString As String = "server=
> (local);database=ASPExamples"
> Dim SelectCommand As String = "SELECT CustomerID, name, phone from
> customers"
> Dim isEditing As Boolean = False
> Dim myConnection As New SqlConnection(ConnectionString)
> Dim myCommand As New SqlDataAdapter(SelectCommand, myConnection)
> Dim ds As New DataSet()
> myCommand.Fill(ds)
> DataGrid1.DataSource = ds
> DataGrid1.DataBind()
>
> End Sub
Thursday, March 8, 2012
Connection failure with VIA/GigaNet Protocol
I'm trying to determine if this error
(http://support.microsoft.com/kb/811274/en-us) has been fixed in SQL2000 SP4
or the SP4 cumulative hotfix. I can't find it listed on MSDN, but it's
rather difficult to scroll through the dozens of numbers looking for one
specific fix. Note to Microsoft: Why don't you make the fixed KB numbers
searchable?Hi Ron
I think this was fixed in build 990 which is included in SP4
http://support.microsoft.com/kb/890200/EN-US/
John
"Ron Hinds" wrote:
> I'm trying to determine if this error
> (http://support.microsoft.com/kb/811274/en-us) has been fixed in SQL2000 SP4
> or the SP4 cumulative hotfix. I can't find it listed on MSDN, but it's
> rather difficult to scroll through the dozens of numbers looking for one
> specific fix. Note to Microsoft: Why don't you make the fixed KB numbers
> searchable?
>
>
(http://support.microsoft.com/kb/811274/en-us) has been fixed in SQL2000 SP4
or the SP4 cumulative hotfix. I can't find it listed on MSDN, but it's
rather difficult to scroll through the dozens of numbers looking for one
specific fix. Note to Microsoft: Why don't you make the fixed KB numbers
searchable?Hi Ron
I think this was fixed in build 990 which is included in SP4
http://support.microsoft.com/kb/890200/EN-US/
John
"Ron Hinds" wrote:
> I'm trying to determine if this error
> (http://support.microsoft.com/kb/811274/en-us) has been fixed in SQL2000 SP4
> or the SP4 cumulative hotfix. I can't find it listed on MSDN, but it's
> rather difficult to scroll through the dozens of numbers looking for one
> specific fix. Note to Microsoft: Why don't you make the fixed KB numbers
> searchable?
>
>
Connection Failure to SQL Server 2005
I am trying to connect to a SQL Server 2005 instance from another machine
using Query Analyzer (SQL Server 2000 version) and I am getting the following
error:
Server: Msg 11, Level 16, State 1
[Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error.
I can connect to other SQL Server 2000 versions but not the 2005.
Thanks
Allen
Did you enable the Allow Remote Connections option for the SQL2005 server
instance?
Andrew J. Kelly SQL MVP
"Allen" <Allen@.discussions.microsoft.com> wrote in message
news:7F4792F3-8931-4E92-BEDA-0058D9917CFD@.microsoft.com...
>I am trying to connect to a SQL Server 2005 instance from another machine
> using Query Analyzer (SQL Server 2000 version) and I am getting the
> following
> error:
> Server: Msg 11, Level 16, State 1
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error.
> I can connect to other SQL Server 2000 versions but not the 2005.
> Thanks
> --
> Allen
using Query Analyzer (SQL Server 2000 version) and I am getting the following
error:
Server: Msg 11, Level 16, State 1
[Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error.
I can connect to other SQL Server 2000 versions but not the 2005.
Thanks
Allen
Did you enable the Allow Remote Connections option for the SQL2005 server
instance?
Andrew J. Kelly SQL MVP
"Allen" <Allen@.discussions.microsoft.com> wrote in message
news:7F4792F3-8931-4E92-BEDA-0058D9917CFD@.microsoft.com...
>I am trying to connect to a SQL Server 2005 instance from another machine
> using Query Analyzer (SQL Server 2000 version) and I am getting the
> following
> error:
> Server: Msg 11, Level 16, State 1
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error.
> I can connect to other SQL Server 2000 versions but not the 2005.
> Thanks
> --
> Allen
Connection Failure to SQL Server 2005
I am trying to connect to a SQL Server 2005 instance from another machine
using Query Analyzer (SQL Server 2000 version) and I am getting the followin
g
error:
Server: Msg 11, Level 16, State 1
[Microsoft][ODBC SQL Server Driver][DBNETLIB]General network err
or.
I can connect to other SQL Server 2000 versions but not the 2005.
Thanks
--
AllenDid you enable the Allow Remote Connections option for the SQL2005 server
instance?
Andrew J. Kelly SQL MVP
"Allen" <Allen@.discussions.microsoft.com> wrote in message
news:7F4792F3-8931-4E92-BEDA-0058D9917CFD@.microsoft.com...
>I am trying to connect to a SQL Server 2005 instance from another machine
> using Query Analyzer (SQL Server 2000 version) and I am getting the
> following
> error:
> Server: Msg 11, Level 16, State 1
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]General network e
rror.
> I can connect to other SQL Server 2000 versions but not the 2005.
> Thanks
> --
> Allen|||I've serched high and low for this facility and cannot find it.
I have enabled both client/server tcp/ip named pipes shared memory
and still cannot connect.
"Andrew J. Kelly" wrote:
> Did you enable the Allow Remote Connections option for the SQL2005 server
> instance?
> --
> Andrew J. Kelly SQL MVP
>
> "Allen" <Allen@.discussions.microsoft.com> wrote in message
> news:7F4792F3-8931-4E92-BEDA-0058D9917CFD@.microsoft.com...
>
>|||how does one:
enable the Allow Remote Connections option for the SQL2005 server
> instance?
I've set up ports and enabled tcp/ip, shared memory, pipes and do not see a
Allow Remote Connections option
I've shut off my firewall. I just installed sql server 2005 and am trying to
connect on the SAME MACHINE
"Landon Kelsey" wrote:
[vbcol=seagreen]
> I've serched high and low for this facility and cannot find it.
> I have enabled both client/server tcp/ip named pipes shared memory
> and still cannot connect.
> "Andrew J. Kelly" wrote:
>|||Try running through this quick tutorial to see if you missed anything:
http://msdn2.microsoft.com/en-us/library/ms345318(en-US,SQL.90).aspx
--
Rick Byham
MCDBA, MCSE, MCSA
Documentation Manager,
Microsoft, SQL Server Books Online
This posting is provided "as is" with
no warranties, and confers no rights.
"Landon Kelsey" <landonmkelsey@.hotmail.com> wrote in message
news:D98FEEC7-327F-4079-A971-B8A30A6D8FAE@.microsoft.com...[vbcol=seagreen]
> how does one:
> enable the Allow Remote Connections option for the SQL2005 server
> I've set up ports and enabled tcp/ip, shared memory, pipes and do not see
> a
> Allow Remote Connections option
> I've shut off my firewall. I just installed sql server 2005 and am trying
> to
> connect on the SAME MACHINE
>
> "Landon Kelsey" wrote:
>
using Query Analyzer (SQL Server 2000 version) and I am getting the followin
g
error:
Server: Msg 11, Level 16, State 1
[Microsoft][ODBC SQL Server Driver][DBNETLIB]General network err
or.
I can connect to other SQL Server 2000 versions but not the 2005.
Thanks
--
AllenDid you enable the Allow Remote Connections option for the SQL2005 server
instance?
Andrew J. Kelly SQL MVP
"Allen" <Allen@.discussions.microsoft.com> wrote in message
news:7F4792F3-8931-4E92-BEDA-0058D9917CFD@.microsoft.com...
>I am trying to connect to a SQL Server 2005 instance from another machine
> using Query Analyzer (SQL Server 2000 version) and I am getting the
> following
> error:
> Server: Msg 11, Level 16, State 1
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]General network e
rror.
> I can connect to other SQL Server 2000 versions but not the 2005.
> Thanks
> --
> Allen|||I've serched high and low for this facility and cannot find it.
I have enabled both client/server tcp/ip named pipes shared memory
and still cannot connect.
"Andrew J. Kelly" wrote:
> Did you enable the Allow Remote Connections option for the SQL2005 server
> instance?
> --
> Andrew J. Kelly SQL MVP
>
> "Allen" <Allen@.discussions.microsoft.com> wrote in message
> news:7F4792F3-8931-4E92-BEDA-0058D9917CFD@.microsoft.com...
>
>|||how does one:
enable the Allow Remote Connections option for the SQL2005 server
> instance?
I've set up ports and enabled tcp/ip, shared memory, pipes and do not see a
Allow Remote Connections option
I've shut off my firewall. I just installed sql server 2005 and am trying to
connect on the SAME MACHINE
"Landon Kelsey" wrote:
[vbcol=seagreen]
> I've serched high and low for this facility and cannot find it.
> I have enabled both client/server tcp/ip named pipes shared memory
> and still cannot connect.
> "Andrew J. Kelly" wrote:
>|||Try running through this quick tutorial to see if you missed anything:
http://msdn2.microsoft.com/en-us/library/ms345318(en-US,SQL.90).aspx
--
Rick Byham
MCDBA, MCSE, MCSA
Documentation Manager,
Microsoft, SQL Server Books Online
This posting is provided "as is" with
no warranties, and confers no rights.
"Landon Kelsey" <landonmkelsey@.hotmail.com> wrote in message
news:D98FEEC7-327F-4079-A971-B8A30A6D8FAE@.microsoft.com...[vbcol=seagreen]
> how does one:
> enable the Allow Remote Connections option for the SQL2005 server
> I've set up ports and enabled tcp/ip, shared memory, pipes and do not see
> a
> Allow Remote Connections option
> I've shut off my firewall. I just installed sql server 2005 and am trying
> to
> connect on the SAME MACHINE
>
> "Landon Kelsey" wrote:
>
Connection failure OR General network error OR Timeout
We are running some applications and 3 times a day and every night we get the
following error
Connection failure (Number : -2147467259)
OR
[DBNETLIB][ConnectionRead (recv()).]General network error. Check your
network documentation. (Number : -2147467259)
OR
Timeout expired (Number : -2147467259)
It happens random, has nothing to do with backup,...
This is since we use SQLServer 2005, never had any problems with
SQLServer2000.
Everything else is the same.
Any help would be strongly appreciatedDid you get a solution to your problem? I am having a similar porblem, with
home-based users intermittently losing their connection.
Peter
"Multatuli" wrote:
> We are running some applications and 3 times a day and every night we get the
> following error
> Connection failure (Number : -2147467259)
> OR
> [DBNETLIB][ConnectionRead (recv()).]General network error. Check your
> network documentation. (Number : -2147467259)
> OR
> Timeout expired (Number : -2147467259)
> It happens random, has nothing to do with backup,...
> This is since we use SQLServer 2005, never had any problems with
> SQLServer2000.
> Everything else is the same.
> Any help would be strongly appreciated
>
following error
Connection failure (Number : -2147467259)
OR
[DBNETLIB][ConnectionRead (recv()).]General network error. Check your
network documentation. (Number : -2147467259)
OR
Timeout expired (Number : -2147467259)
It happens random, has nothing to do with backup,...
This is since we use SQLServer 2005, never had any problems with
SQLServer2000.
Everything else is the same.
Any help would be strongly appreciatedDid you get a solution to your problem? I am having a similar porblem, with
home-based users intermittently losing their connection.
Peter
"Multatuli" wrote:
> We are running some applications and 3 times a day and every night we get the
> following error
> Connection failure (Number : -2147467259)
> OR
> [DBNETLIB][ConnectionRead (recv()).]General network error. Check your
> network documentation. (Number : -2147467259)
> OR
> Timeout expired (Number : -2147467259)
> It happens random, has nothing to do with backup,...
> This is since we use SQLServer 2005, never had any problems with
> SQLServer2000.
> Everything else is the same.
> Any help would be strongly appreciated
>
Connection failure on standalone MSDE installtion when network is lost
Scenario -
On a standalone installation i.e client and SQL server are on same
machine, if network connection is lost while preparing SQL server
connection through client application, then SQL connection could not be
established. This was detected only on few machines. The configuration
details are:
OS : Windows 2000 SP 4 with MSDE
Error : MSVC exception occurred. This is not consistent. Some times it
throws error in sql server connectivity DLLs.Check local security policies on client machines that screw up. I had this
probelem recently.
<shridhargune@.hotmail.com> wrote in message
news:1122392145.762770.32950@.g49g2000cwa.googlegroups.com...
> Scenario -
> On a standalone installation i.e client and SQL server are on same
> machine, if network connection is lost while preparing SQL server
> connection through client application, then SQL connection could not be
> established. This was detected only on few machines. The configuration
> details are:
> OS : Windows 2000 SP 4 with MSDE
> Error : MSVC exception occurred. This is not consistent. Some times it
> throws error in sql server connectivity DLLs.
>
On a standalone installation i.e client and SQL server are on same
machine, if network connection is lost while preparing SQL server
connection through client application, then SQL connection could not be
established. This was detected only on few machines. The configuration
details are:
OS : Windows 2000 SP 4 with MSDE
Error : MSVC exception occurred. This is not consistent. Some times it
throws error in sql server connectivity DLLs.Check local security policies on client machines that screw up. I had this
probelem recently.
<shridhargune@.hotmail.com> wrote in message
news:1122392145.762770.32950@.g49g2000cwa.googlegroups.com...
> Scenario -
> On a standalone installation i.e client and SQL server are on same
> machine, if network connection is lost while preparing SQL server
> connection through client application, then SQL connection could not be
> established. This was detected only on few machines. The configuration
> details are:
> OS : Windows 2000 SP 4 with MSDE
> Error : MSVC exception occurred. This is not consistent. Some times it
> throws error in sql server connectivity DLLs.
>
Connection failure on standalone MSDE installtion when network is lost
Scenario -
On a standalone installation i.e client and SQL server are on same
machine, if network connection is lost while preparing SQL server
connection through client application, then SQL connection could not be
established. This was detected only on few machines. The configuration
details are:
OS : Windows 2000 SP 4 with MSDE
Error : MSVC exception occurred. This is not consistent. Some times it
throws error in sql server connectivity DLLs.
Check local security policies on client machines that screw up. I had this
probelem recently.
<shridhargune@.hotmail.com> wrote in message
news:1122392145.762770.32950@.g49g2000cwa.googlegro ups.com...
> Scenario -
> On a standalone installation i.e client and SQL server are on same
> machine, if network connection is lost while preparing SQL server
> connection through client application, then SQL connection could not be
> established. This was detected only on few machines. The configuration
> details are:
> OS : Windows 2000 SP 4 with MSDE
> Error : MSVC exception occurred. This is not consistent. Some times it
> throws error in sql server connectivity DLLs.
>
On a standalone installation i.e client and SQL server are on same
machine, if network connection is lost while preparing SQL server
connection through client application, then SQL connection could not be
established. This was detected only on few machines. The configuration
details are:
OS : Windows 2000 SP 4 with MSDE
Error : MSVC exception occurred. This is not consistent. Some times it
throws error in sql server connectivity DLLs.
Check local security policies on client machines that screw up. I had this
probelem recently.
<shridhargune@.hotmail.com> wrote in message
news:1122392145.762770.32950@.g49g2000cwa.googlegro ups.com...
> Scenario -
> On a standalone installation i.e client and SQL server are on same
> machine, if network connection is lost while preparing SQL server
> connection through client application, then SQL connection could not be
> established. This was detected only on few machines. The configuration
> details are:
> OS : Windows 2000 SP 4 with MSDE
> Error : MSVC exception occurred. This is not consistent. Some times it
> throws error in sql server connectivity DLLs.
>
Connection failure on MSDE 2000/XP installation
We have installed MSDE 2000 on XP For Tablet PC. All
applications that use ODBC to connect to the database work
well, however those applications that use either DBLIB or
E/SQL (embedded SQL built on top of DBLIB) return a "Failed
to get DBPROCESS" error. MSDE was installed with
SQL-Authentication and all apps are started locally on the
server running MSDE. All applications run succesfully under
SQL 2000. Using SQL Profiler to trace application-activity
results in NO events being logged/traced, suggesting that
no SQL commands ever reach the server. Any ideas ?
If they are connecting via tcp/ip, do you have an exception in the firewall
(presuming XP SP2 is installed)?
Is the protocol they are connecting on enabled? (see svrnetcn.exe).
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Fintan" <anonymous@.discussions.microsoft.com> wrote in message
news:074001c5356f$36253fe0$a401280a@.phx.gbl...
> We have installed MSDE 2000 on XP For Tablet PC. All
> applications that use ODBC to connect to the database work
> well, however those applications that use either DBLIB or
> E/SQL (embedded SQL built on top of DBLIB) return a "Failed
> to get DBPROCESS" error. MSDE was installed with
> SQL-Authentication and all apps are started locally on the
> server running MSDE. All applications run succesfully under
> SQL 2000. Using SQL Profiler to trace application-activity
> results in NO events being logged/traced, suggesting that
> no SQL commands ever reach the server. Any ideas ?
>
applications that use ODBC to connect to the database work
well, however those applications that use either DBLIB or
E/SQL (embedded SQL built on top of DBLIB) return a "Failed
to get DBPROCESS" error. MSDE was installed with
SQL-Authentication and all apps are started locally on the
server running MSDE. All applications run succesfully under
SQL 2000. Using SQL Profiler to trace application-activity
results in NO events being logged/traced, suggesting that
no SQL commands ever reach the server. Any ideas ?
If they are connecting via tcp/ip, do you have an exception in the firewall
(presuming XP SP2 is installed)?
Is the protocol they are connecting on enabled? (see svrnetcn.exe).
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Fintan" <anonymous@.discussions.microsoft.com> wrote in message
news:074001c5356f$36253fe0$a401280a@.phx.gbl...
> We have installed MSDE 2000 on XP For Tablet PC. All
> applications that use ODBC to connect to the database work
> well, however those applications that use either DBLIB or
> E/SQL (embedded SQL built on top of DBLIB) return a "Failed
> to get DBPROCESS" error. MSDE was installed with
> SQL-Authentication and all apps are started locally on the
> server running MSDE. All applications run succesfully under
> SQL 2000. Using SQL Profiler to trace application-activity
> results in NO events being logged/traced, suggesting that
> no SQL commands ever reach the server. Any ideas ?
>
connection failure
Hi all,
Everything is fine until today.
I have two instances(both msde databases, but I have enterprise manager and
analyser installed) on my computer one instance is mssql and the other is
mssql$netsdk (asp.net starter kit database)
somehow the connection to mssql$netsdk is failed which display in enterprise
manager.
So I removed the origianl server registration and start a new one, I type
"BETTYPC\NETSDK" as server and using windows authentication when doing the
registration, but the message display at the last step:
sql server registration failed because of connection failure displayed
below:sqldumpexceptionhandler :process 53 generated a fatal exception
c0000005 EXCEPTION_ACCESS_VIOLATION, sql server is terminating this process.
what's the problem?
Can you help and I am desperated
Betty
Hi Bettys,
Welcome to use MSDN Managed Newsgroup!
From your descriptions, I understood you are not able to connect the SQL
Server named instance NETSDK with error message EXCEPTION_ACCESS_VIOLATION.
If I have misunderstood your concern, please feel free to point it out.
AV errors could be caused by various reasons, please perform the steps
below and let me know the result
1. Check the log file of NETSDK instance, make sure whether the instance
was started correctly.
Defautly, the log will be located at C:\Program Files\Microsoft SQL
Server\MSSQL$NETSDK\log, you may paste them here or send to me directly
v-mingqc@.ONLINEmicrosoft.com if you have concerns on security. (Note that
REMOVE ONLINE in my email address before you click SEND)
2. Is it possible to connect the instance via OSQL and Query Analyzer?
3. Is it possible for you to connect via SQL Authentication?
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
================================================== ====
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Hi Michael,
Thank you, this is the first post on this forum. I didn't know what went
wrong. The only thing I can do is googling. Then it came to my mind that I
can stop the mssql@.netsdk sql server then and I restarted. It just started
and stopped again somehow. And then I have to restart the computer. After
that I saw both instances have sqlservr.exe process. This time I register the
server again and it looks fine. Connection is OK.
(I didn't try to use osql and did try to use sql authentication, but when I
supplied one userID and password to this server, this password is set up to a
database on this server, it should be OK right? it didn't work either.)
If you can tell what was going on, that will be great.
Here is the paste from errorLog:
2006-02-02 13:12:54.28 server Microsoft SQL Server 2000 - 8.00.760
(Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 1)
2006-02-02 13:12:54.28 server Copyright (C) 1988-2002 Microsoft
Corporation.
2006-02-02 13:12:54.28 server All rights reserved.
2006-02-02 13:12:54.28 server Server Process ID is 2988.
2006-02-02 13:12:54.28 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL$NETSDK\LOG\ERRORLOG'.
2006-02-02 13:12:54.32 server SQL Server is starting at priority class
'normal'(2 CPUs detected).
2006-02-02 13:12:54.50 server SQL Server configured for thread mode
processing.
2006-02-02 13:12:54.50 server Using dynamic lock allocation. [500] Lock
Blocks, [1000] Lock Owner Blocks.
2006-02-02 13:12:54.52 spid4 Starting up database 'master'.
2006-02-02 13:12:54.57 server Using 'SSNETLIB.DLL' version '8.0.766'.
2006-02-02 13:12:54.57 spid5 Starting up database 'model'.
2006-02-02 13:12:54.57 spid4 Server name is 'BETTYPC\NETSDK'.
2006-02-02 13:12:54.57 spid4 Skipping startup of clean database id 4
2006-02-02 13:12:54.57 spid4 Skipping startup of clean database id 5
2006-02-02 13:12:54.57 spid4 Skipping startup of clean database id 6
2006-02-02 13:12:54.57 spid4 Skipping startup of clean database id 7
2006-02-02 13:12:54.57 spid4 Skipping startup of clean database id 8
2006-02-02 13:12:54.57 spid4 Skipping startup of clean database id 9
2006-02-02 13:12:54.57 spid4 Skipping startup of clean database id 10
2006-02-02 13:12:54.57 spid4 Skipping startup of clean database id 11
2006-02-02 13:12:54.57 spid4 Starting up database 'subway'.
2006-02-02 13:12:54.66 spid5 Clearing tempdb database.
2006-02-02 13:12:55.72 server SQL server listening on .
2006-02-02 13:12:55.72 server Error: 17826, Severity: 18, State: 1
2006-02-02 13:12:55.72 server Could not set up Net-Library 'SSNETLIB'..
2006-02-02 13:12:55.72 server Unable to load any netlibs.
2006-02-02 13:12:55.72 server SQL Server could not spawn FRunCM thread.
Here is the sqldump file
================================================== ===================
BugCheck Dump
================================================== ===================
This file is generated by Microsoft SQL Server 8.00.760
upon detection of fatal unexpected error. Please return this file,
the query or program that produced the bugcheck, the database and
the error log, and any other pertinent information with a Service Request.
Betty
"Michael Cheng [MSFT]" wrote:
> Hi Bettys,
> Welcome to use MSDN Managed Newsgroup!
> From your descriptions, I understood you are not able to connect the SQL
> Server named instance NETSDK with error message EXCEPTION_ACCESS_VIOLATION.
> If I have misunderstood your concern, please feel free to point it out.
> AV errors could be caused by various reasons, please perform the steps
> below and let me know the result
> 1. Check the log file of NETSDK instance, make sure whether the instance
> was started correctly.
> Defautly, the log will be located at C:\Program Files\Microsoft SQL
> Server\MSSQL$NETSDK\log, you may paste them here or send to me directly
>if you have concerns on security. (Note that
> REMOVE ONLINE in my email address before you click SEND)
> 2. Is it possible to connect the instance via OSQL and Query Analyzer?
> 3. Is it possible for you to connect via SQL Authentication?
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> ================================================== ====
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
|||Hi Betty,
It seems your SQL Server is not stable. From the startup log, I believe
something internal is wrong. We may noticed "netlibs" is not loaded and
Dump file were also generated.
Although you could register SQL Server now, I would recommend you backup
all the data in this instnace and perform a reinstallation of NETSDK
instance. You may follow the link below to perform a complete uninstall
How to manually remove SQL Server 2000 default, named, or virtual instance
http://support.microsoft.com/kb/290991
If you have any questions or concerns, don't hesitate to let me know. We
are always here to be of assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
================================================== ====
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
Everything is fine until today.
I have two instances(both msde databases, but I have enterprise manager and
analyser installed) on my computer one instance is mssql and the other is
mssql$netsdk (asp.net starter kit database)
somehow the connection to mssql$netsdk is failed which display in enterprise
manager.
So I removed the origianl server registration and start a new one, I type
"BETTYPC\NETSDK" as server and using windows authentication when doing the
registration, but the message display at the last step:
sql server registration failed because of connection failure displayed
below:sqldumpexceptionhandler :process 53 generated a fatal exception
c0000005 EXCEPTION_ACCESS_VIOLATION, sql server is terminating this process.
what's the problem?
Can you help and I am desperated
Betty
Hi Bettys,
Welcome to use MSDN Managed Newsgroup!
From your descriptions, I understood you are not able to connect the SQL
Server named instance NETSDK with error message EXCEPTION_ACCESS_VIOLATION.
If I have misunderstood your concern, please feel free to point it out.
AV errors could be caused by various reasons, please perform the steps
below and let me know the result
1. Check the log file of NETSDK instance, make sure whether the instance
was started correctly.
Defautly, the log will be located at C:\Program Files\Microsoft SQL
Server\MSSQL$NETSDK\log, you may paste them here or send to me directly
v-mingqc@.ONLINEmicrosoft.com if you have concerns on security. (Note that
REMOVE ONLINE in my email address before you click SEND)
2. Is it possible to connect the instance via OSQL and Query Analyzer?
3. Is it possible for you to connect via SQL Authentication?
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
================================================== ====
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Hi Michael,
Thank you, this is the first post on this forum. I didn't know what went
wrong. The only thing I can do is googling. Then it came to my mind that I
can stop the mssql@.netsdk sql server then and I restarted. It just started
and stopped again somehow. And then I have to restart the computer. After
that I saw both instances have sqlservr.exe process. This time I register the
server again and it looks fine. Connection is OK.
(I didn't try to use osql and did try to use sql authentication, but when I
supplied one userID and password to this server, this password is set up to a
database on this server, it should be OK right? it didn't work either.)
If you can tell what was going on, that will be great.
Here is the paste from errorLog:
2006-02-02 13:12:54.28 server Microsoft SQL Server 2000 - 8.00.760
(Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 1)
2006-02-02 13:12:54.28 server Copyright (C) 1988-2002 Microsoft
Corporation.
2006-02-02 13:12:54.28 server All rights reserved.
2006-02-02 13:12:54.28 server Server Process ID is 2988.
2006-02-02 13:12:54.28 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL$NETSDK\LOG\ERRORLOG'.
2006-02-02 13:12:54.32 server SQL Server is starting at priority class
'normal'(2 CPUs detected).
2006-02-02 13:12:54.50 server SQL Server configured for thread mode
processing.
2006-02-02 13:12:54.50 server Using dynamic lock allocation. [500] Lock
Blocks, [1000] Lock Owner Blocks.
2006-02-02 13:12:54.52 spid4 Starting up database 'master'.
2006-02-02 13:12:54.57 server Using 'SSNETLIB.DLL' version '8.0.766'.
2006-02-02 13:12:54.57 spid5 Starting up database 'model'.
2006-02-02 13:12:54.57 spid4 Server name is 'BETTYPC\NETSDK'.
2006-02-02 13:12:54.57 spid4 Skipping startup of clean database id 4
2006-02-02 13:12:54.57 spid4 Skipping startup of clean database id 5
2006-02-02 13:12:54.57 spid4 Skipping startup of clean database id 6
2006-02-02 13:12:54.57 spid4 Skipping startup of clean database id 7
2006-02-02 13:12:54.57 spid4 Skipping startup of clean database id 8
2006-02-02 13:12:54.57 spid4 Skipping startup of clean database id 9
2006-02-02 13:12:54.57 spid4 Skipping startup of clean database id 10
2006-02-02 13:12:54.57 spid4 Skipping startup of clean database id 11
2006-02-02 13:12:54.57 spid4 Starting up database 'subway'.
2006-02-02 13:12:54.66 spid5 Clearing tempdb database.
2006-02-02 13:12:55.72 server SQL server listening on .
2006-02-02 13:12:55.72 server Error: 17826, Severity: 18, State: 1
2006-02-02 13:12:55.72 server Could not set up Net-Library 'SSNETLIB'..
2006-02-02 13:12:55.72 server Unable to load any netlibs.
2006-02-02 13:12:55.72 server SQL Server could not spawn FRunCM thread.
Here is the sqldump file
================================================== ===================
BugCheck Dump
================================================== ===================
This file is generated by Microsoft SQL Server 8.00.760
upon detection of fatal unexpected error. Please return this file,
the query or program that produced the bugcheck, the database and
the error log, and any other pertinent information with a Service Request.
Betty
"Michael Cheng [MSFT]" wrote:
> Hi Bettys,
> Welcome to use MSDN Managed Newsgroup!
> From your descriptions, I understood you are not able to connect the SQL
> Server named instance NETSDK with error message EXCEPTION_ACCESS_VIOLATION.
> If I have misunderstood your concern, please feel free to point it out.
> AV errors could be caused by various reasons, please perform the steps
> below and let me know the result
> 1. Check the log file of NETSDK instance, make sure whether the instance
> was started correctly.
> Defautly, the log will be located at C:\Program Files\Microsoft SQL
> Server\MSSQL$NETSDK\log, you may paste them here or send to me directly
>if you have concerns on security. (Note that
> REMOVE ONLINE in my email address before you click SEND)
> 2. Is it possible to connect the instance via OSQL and Query Analyzer?
> 3. Is it possible for you to connect via SQL Authentication?
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> ================================================== ====
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
|||Hi Betty,
It seems your SQL Server is not stable. From the startup log, I believe
something internal is wrong. We may noticed "netlibs" is not loaded and
Dump file were also generated.
Although you could register SQL Server now, I would recommend you backup
all the data in this instnace and perform a reinstallation of NETSDK
instance. You may follow the link below to perform a complete uninstall
How to manually remove SQL Server 2000 default, named, or virtual instance
http://support.microsoft.com/kb/290991
If you have any questions or concerns, don't hesitate to let me know. We
are always here to be of assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
================================================== ====
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
Connection failure
When I try to connect one one of our SQL Server databases using SQL Server
2005 client tools I get the following error.
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
inder the default setting SQL Server does not allow remote connections.
(Provider: TCP Provider, erro:0 - No connections could be made because the
target machine actively refused it.) (Microsoft SQL Server, Error: 10061).
I can connect to our other SQL Servers with no problem, and others users can
connect to the one I'm having problems with.
Any ideas?
Problem now solved.
Problem was caused by an alias setup for the previous version of sql server.
Deling the alias solved the problem.
Gary
"Gary Watson" wrote:
> When I try to connect one one of our SQL Server databases using SQL Server
> 2005 client tools I get the following error.
> 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
> inder the default setting SQL Server does not allow remote connections.
> (Provider: TCP Provider, erro:0 - No connections could be made because the
> target machine actively refused it.) (Microsoft SQL Server, Error: 10061).
> I can connect to our other SQL Servers with no problem, and others users can
> connect to the one I'm having problems with.
> Any ideas?
2005 client tools I get the following error.
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
inder the default setting SQL Server does not allow remote connections.
(Provider: TCP Provider, erro:0 - No connections could be made because the
target machine actively refused it.) (Microsoft SQL Server, Error: 10061).
I can connect to our other SQL Servers with no problem, and others users can
connect to the one I'm having problems with.
Any ideas?
Problem now solved.
Problem was caused by an alias setup for the previous version of sql server.
Deling the alias solved the problem.
Gary
"Gary Watson" wrote:
> When I try to connect one one of our SQL Server databases using SQL Server
> 2005 client tools I get the following error.
> 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
> inder the default setting SQL Server does not allow remote connections.
> (Provider: TCP Provider, erro:0 - No connections could be made because the
> target machine actively refused it.) (Microsoft SQL Server, Error: 10061).
> I can connect to our other SQL Servers with no problem, and others users can
> connect to the one I'm having problems with.
> Any ideas?
Connection failure
When I try to connect one one of our SQL Server databases using SQL Server
2005 client tools I get the following error.
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
inder the default setting SQL Server does not allow remote connections.
(Provider: TCP Provider, erro:0 - No connections could be made because the
target machine actively refused it.) (Microsoft SQL Server, Error: 10061).
I can connect to our other SQL Servers with no problem, and others users can
connect to the one I'm having problems with.
Any ideas?Problem now solved.
Problem was caused by an alias setup for the previous version of sql server.
Deling the alias solved the problem.
Gary
"Gary Watson" wrote:
> When I try to connect one one of our SQL Server databases using SQL Server
> 2005 client tools I get the following error.
> 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
> inder the default setting SQL Server does not allow remote connections.
> (Provider: TCP Provider, erro:0 - No connections could be made because the
> target machine actively refused it.) (Microsoft SQL Server, Error: 10061).
> I can connect to our other SQL Servers with no problem, and others users c
an
> connect to the one I'm having problems with.
> Any ideas?
2005 client tools I get the following error.
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
inder the default setting SQL Server does not allow remote connections.
(Provider: TCP Provider, erro:0 - No connections could be made because the
target machine actively refused it.) (Microsoft SQL Server, Error: 10061).
I can connect to our other SQL Servers with no problem, and others users can
connect to the one I'm having problems with.
Any ideas?Problem now solved.
Problem was caused by an alias setup for the previous version of sql server.
Deling the alias solved the problem.
Gary
"Gary Watson" wrote:
> When I try to connect one one of our SQL Server databases using SQL Server
> 2005 client tools I get the following error.
> 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
> inder the default setting SQL Server does not allow remote connections.
> (Provider: TCP Provider, erro:0 - No connections could be made because the
> target machine actively refused it.) (Microsoft SQL Server, Error: 10061).
> I can connect to our other SQL Servers with no problem, and others users c
an
> connect to the one I'm having problems with.
> Any ideas?
connection failure
Hi,
We have just installed sql server 8
while using the enterprise manager, as we clicked on the
server icon the following error was issued:
"An error 1069 (the service did not start due to a logon
failure) ocurred while performing this service operation
on then MSSQL Server Service." In a related dialog we
found out that its default login procedure is by means of
the windows login. Another option was to
provide 'independent' login/password. In older versions I
was always able to login using sa as login with empty
password...
Which one should we use? what is missing?
tia
paco
tia,
FranciscoYour problem is not the login from EM to SQL Server. The problem is that SQL Server didn't event
start. Check out the Service Account for the SQL Server service, and the password specified for
this.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Francisco" <anonymous@.discussions.microsoft.com> wrote in message
news:09dd01c3aec7$002f4a50$a001280a@.phx.gbl...
> Hi,
> We have just installed sql server 8
> while using the enterprise manager, as we clicked on the
> server icon the following error was issued:
> "An error 1069 (the service did not start due to a logon
> failure) ocurred while performing this service operation
> on then MSSQL Server Service." In a related dialog we
> found out that its default login procedure is by means of
> the windows login. Another option was to
> provide 'independent' login/password. In older versions I
> was always able to login using sa as login with empty
> password...
> Which one should we use? what is missing?
> tia
> paco
>
> tia,
> Francisco
>
We have just installed sql server 8
while using the enterprise manager, as we clicked on the
server icon the following error was issued:
"An error 1069 (the service did not start due to a logon
failure) ocurred while performing this service operation
on then MSSQL Server Service." In a related dialog we
found out that its default login procedure is by means of
the windows login. Another option was to
provide 'independent' login/password. In older versions I
was always able to login using sa as login with empty
password...
Which one should we use? what is missing?
tia
paco
tia,
FranciscoYour problem is not the login from EM to SQL Server. The problem is that SQL Server didn't event
start. Check out the Service Account for the SQL Server service, and the password specified for
this.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Francisco" <anonymous@.discussions.microsoft.com> wrote in message
news:09dd01c3aec7$002f4a50$a001280a@.phx.gbl...
> Hi,
> We have just installed sql server 8
> while using the enterprise manager, as we clicked on the
> server icon the following error was issued:
> "An error 1069 (the service did not start due to a logon
> failure) ocurred while performing this service operation
> on then MSSQL Server Service." In a related dialog we
> found out that its default login procedure is by means of
> the windows login. Another option was to
> provide 'independent' login/password. In older versions I
> was always able to login using sa as login with empty
> password...
> Which one should we use? what is missing?
> tia
> paco
>
> tia,
> Francisco
>
Connection failed between PC
Hello, i ahve a problem to connect a pc to another with MSDE installed.
The response message of this failure is:
'Server not exists'
The response message of this failure is:
'Server not exists'
Can help me?
Thanks!Hai,
I dont exactly trap 'What u mentaioned is the os server or sql
server.
Any way if you want to access a machine from u r machine , the
followings must exits.
1. Network among them.
2. if , so u can access other machines from u r command prompt(run).
like, \\node-x\e$
..if it does not work , share the other machine's drives
Raghu|||alessandro_chiodo@.hotmail.com (Alex) wrote in message news:<c7bf0032.0312040727.29186bc9@.posting.google.com>...
> Hello, i ahve a problem to connect a pc to another with MSDE installed.
> The response message of this failure is:
> 'Server not exists'
> Can help me?
> Thanks!
One possibility is that you're using the wrong authentication method:
http://support.microsoft.com/defaul...0&Product=sql2k
Another possibility is that it's MSDE SP3a, which disables network
access to MSDE by default:
http://support.microsoft.com/defaul...for _msde_d3jb
Simon
Subscribe to:
Posts (Atom)