Showing posts with label client. Show all posts

Tuesday, March 27, 2012

connection problem

Hi, All,
SQL7.0, SP3 on Win2000 server+ sp1
I remote access our client in FL, recently I get error
message [DBNMPNTW] Connection write(writefile()) message
then the connection failed.
What's cause the problem how can I fix it.
Thanks and have a nice day
HawkHi Hawk,
Connection write using the Named Pipes library. There could be a
permission problem with Named Pipes /SMB or a restrictive Security Template
setting. Try connecting using TCP.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Kevin,
Thanks, but how can change it to TCP? Could you tell me
more?
Have a good weekend

>--Original Message--
>Hi Hawk,
> Connection write using the Named Pipes library.
There could be a
>permission problem with Named Pipes /SMB or a
restrictive Security Template
>setting. Try connecting using TCP.
>
>Thanks,
>Kevin McDonnell
>Microsoft Corporation
>This posting is provided AS IS with no warranties, and
confers no rights.
>
>.
>|||Use the SQL Client Network Utility and create a TCP alias. Enter the
actual servername for the alias, this way the client will use sockets
instead.
If you have MDAC 2.6 on the client you can also try this as a test.
osql -Stcp:ServerNameHere -UuserName -Ppassword
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Thank you very much and have a good one
Hawk

Sunday, March 25, 2012

connection problem

Hi, All,
SQL7.0, SP3 on Win2000 server+ sp1
I remote access our client in FL, recently I get error
message [DBNMPNTW] Connection write(writefile()) message
then the connection failed.
What's cause the problem how can I fix it.
Thanks and have a nice day
Hawk
Hi Hawk,
Connection write using the Named Pipes library. There could be a
permission problem with Named Pipes /SMB or a restrictive Security Template
setting. Try connecting using TCP.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
|||Kevin,
Thanks, but how can change it to TCP? Could you tell me
more?
Have a good weekend

>--Original Message--
>Hi Hawk,
> Connection write using the Named Pipes library.
There could be a
>permission problem with Named Pipes /SMB or a
restrictive Security Template
>setting. Try connecting using TCP.
>
>Thanks,
>Kevin McDonnell
>Microsoft Corporation
>This posting is provided AS IS with no warranties, and
confers no rights.
>
>.
>
|||Use the SQL Client Network Utility and create a TCP alias. Enter the
actual servername for the alias, this way the client will use sockets
instead.
If you have MDAC 2.6 on the client you can also try this as a test.
osql -Stcp:ServerNameHere -UuserName -Ppassword
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
|||Thank you very much and have a good one
Hawk

Thursday, March 22, 2012

connection pooling

Hi,
Is there a way to enable connection pooling with SQL Server 2005 with ADO,
OLEDB ? (from c++, not .net)
If client is connecting with the same connection string pooling is
automatically created?
thanksConnection Pooling is implemented by the .NET provider or the OLEDB
provider. AFAIK, the OLEDB provider turns this on by itself. My question is:
why are you using OLE DB to access SQL Server?
____________________________________
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)
----
---
"Andy" <kc2ine@.yahoo.com> wrote in message
news:eEXb6EPIIHA.4296@.TK2MSFTNGP04.phx.gbl...
> Hi,
> Is there a way to enable connection pooling with SQL Server 2005 with ADO,
> OLEDB ? (from c++, not .net)
> If client is connecting with the same connection string pooling is
> automatically created?
> thanks
>

connection pooling

Hi,
Is there a way to enable connection pooling with SQL Server 2005 with ADO,
OLEDB ? (from c++, not .net)
If client is connecting with the same connection string pooling is
automatically created?
thanks
Connection Pooling is implemented by the .NET provider or the OLEDB
provider. AFAIK, the OLEDB provider turns this on by itself. My question is:
why are you using OLE DB to access SQL Server?
____________________________________
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)
------
"Andy" <kc2ine@.yahoo.com> wrote in message
news:eEXb6EPIIHA.4296@.TK2MSFTNGP04.phx.gbl...
> Hi,
> Is there a way to enable connection pooling with SQL Server 2005 with ADO,
> OLEDB ? (from c++, not .net)
> If client is connecting with the same connection string pooling is
> automatically created?
> thanks
>

Tuesday, March 20, 2012

Connection Open (Create File()) /SQL server registration

Hello,
i have SQL 7.0 servers A, B, C, D
when tryin to register server (mmC) A on B,C,D i get the errormessage
"Client unable to establish connection Connection Open (Create File())"
This worked 2 weeks ago.. and we didn't change anything..
Network wise B,C,D "see" A (ping, net-share..) only "sql-server" wise we
have this problem
THX a lot
PIrmincheck connection with QA
try TCP and NP connection
"Pirmin" wrote:
> Hello,
> i have SQL 7.0 servers A, B, C, D
> when tryin to register server (mmC) A on B,C,D i get the errormessage
> "Client unable to establish connection Connection Open (Create File())"
> This worked 2 weeks ago.. and we didn't change anything..
> Network wise B,C,D "see" A (ping, net-share..) only "sql-server" wise we
> have this problem
> THX a lot
> PIrmin|||Hi,
sorry.. your answer was litl short 4 me..
wht do you mean with "check connection with QA"
Where do i set the connection frm TCP to NamedPipes on the
ServerRegistration..
Thx
Pirmin
"Aleksandar Grbic" wrote:
> check connection with QA
> try TCP and NP connection
> "Pirmin" wrote:
> > Hello,
> >
> > i have SQL 7.0 servers A, B, C, D
> > when tryin to register server (mmC) A on B,C,D i get the errormessage
> > "Client unable to establish connection Connection Open (Create File())"
> >
> > This worked 2 weeks ago.. and we didn't change anything..
> > Network wise B,C,D "see" A (ping, net-share..) only "sql-server" wise we
> > have this problem
> >
> > THX a lot
> > PIrmin|||you can use Query Analyzer (QA - SQL graphical query tool) - isqlw.exe to
check connectivity with sql server
use tcp:<server> to connect with tcp
or
use np:<server> to connect with Named Pipes
later, configure Client Network utility to use one of these protocol and try
connect from mmc
"Pirmin" wrote:
> Hi,
> sorry.. your answer was litl short 4 me..
> wht do you mean with "check connection with QA"
> Where do i set the connection frm TCP to NamedPipes on the
> ServerRegistration..
> Thx
> Pirmin
> "Aleksandar Grbic" wrote:
> > check connection with QA
> > try TCP and NP connection
> >
> > "Pirmin" wrote:
> >
> > > Hello,
> > >
> > > i have SQL 7.0 servers A, B, C, D
> > > when tryin to register server (mmC) A on B,C,D i get the errormessage
> > > "Client unable to establish connection Connection Open (Create File())"
> > >
> > > This worked 2 weeks ago.. and we didn't change anything..
> > > Network wise B,C,D "see" A (ping, net-share..) only "sql-server" wise we
> > > have this problem
> > >
> > > THX a lot
> > > PIrmin|||THX,
well i can't connect via NP nor TCP..
(Pinging works..)
Also checked
"SQL server network config"
TCP and NP are configured..
Anyother idea?
THX
Pirmin
"Aleksandar Grbic" wrote:
> you can use Query Analyzer (QA - SQL graphical query tool) - isqlw.exe to
> check connectivity with sql server
> use tcp:<server> to connect with tcp
> or
> use np:<server> to connect with Named Pipes
> later, configure Client Network utility to use one of these protocol and try
> connect from mmc
>
> "Pirmin" wrote:
> > Hi,
> >
> > sorry.. your answer was litl short 4 me..
> > wht do you mean with "check connection with QA"
> > Where do i set the connection frm TCP to NamedPipes on the
> > ServerRegistration..
> >
> > Thx
> >
> > Pirmin
> >
> > "Aleksandar Grbic" wrote:
> >
> > > check connection with QA
> > > try TCP and NP connection
> > >
> > > "Pirmin" wrote:
> > >
> > > > Hello,
> > > >
> > > > i have SQL 7.0 servers A, B, C, D
> > > > when tryin to register server (mmC) A on B,C,D i get the errormessage
> > > > "Client unable to establish connection Connection Open (Create File())"
> > > >
> > > > This worked 2 weeks ago.. and we didn't change anything..
> > > > Network wise B,C,D "see" A (ping, net-share..) only "sql-server" wise we
> > > > have this problem
> > > >
> > > > THX a lot
> > > > PIrmin|||firewall?
consult your network admin?
can you connect from server A?
server A listen on 1433?
"Pirmin" wrote:
> THX,
> well i can't connect via NP nor TCP..
> (Pinging works..)
> Also checked
> "SQL server network config"
> TCP and NP are configured..
> Anyother idea?
> THX
> Pirmin
> "Aleksandar Grbic" wrote:
> > you can use Query Analyzer (QA - SQL graphical query tool) - isqlw.exe to
> > check connectivity with sql server
> >
> > use tcp:<server> to connect with tcp
> > or
> > use np:<server> to connect with Named Pipes
> >
> > later, configure Client Network utility to use one of these protocol and try
> > connect from mmc
> >
> >
> > "Pirmin" wrote:
> >
> > > Hi,
> > >
> > > sorry.. your answer was litl short 4 me..
> > > wht do you mean with "check connection with QA"
> > > Where do i set the connection frm TCP to NamedPipes on the
> > > ServerRegistration..
> > >
> > > Thx
> > >
> > > Pirmin
> > >
> > > "Aleksandar Grbic" wrote:
> > >
> > > > check connection with QA
> > > > try TCP and NP connection
> > > >
> > > > "Pirmin" wrote:
> > > >
> > > > > Hello,
> > > > >
> > > > > i have SQL 7.0 servers A, B, C, D
> > > > > when tryin to register server (mmC) A on B,C,D i get the errormessage
> > > > > "Client unable to establish connection Connection Open (Create File())"
> > > > >
> > > > > This worked 2 weeks ago.. and we didn't change anything..
> > > > > Network wise B,C,D "see" A (ping, net-share..) only "sql-server" wise we
> > > > > have this problem
> > > > >
> > > > > THX a lot
> > > > > PIrmin

Connection Open (Create File()) /SQL server registration

connection object to client ce

yo ce folks... Anyone had any trouble using a dataset for return values in a datagridview for the client app?

trying to make this work...

' Open the Connection For SQL Compact Edition

Dim cn As New SqlServerCe.SqlCeConnection("Data Source = " & Environment.GetFolderPath(Environment.SpecialFolder.LocalApplicationData) & "\ffgsCRM.sdf")

Dim cmdProduct As SqlServerCe.SqlCeCommand

' create dataset with table

cn.Open()

cmdProduct = cn.CreateCommand

cmdProduct.CommandText = "SELECT ProductDesc AS Description, ProductCost AS Cost, ProductListPrice AS [List Price] FROM Product"

Dim daProduct As New SqlServerCe.SqlCeDataAdapter(cmdProduct)

Dim dtProduct As New Data.DataTable("Product")

daProduct.Fill(dtProduct)

Dim ds As New DataSet

ds.Tables.Add(dtProduct)

'' FILL DATAGRIDVIEW

Me.dbGridProducts.DataSource = ds

I have this working:

' search product description

Dim reqProductSearch As String

reqProductSearch = tstxtSearchDescription.Text

' Open the Connection For SQL Compact Edition

Dim _conn = New SqlCeConnection("Data Source = " & Environment.GetFolderPath(Environment.SpecialFolder.LocalApplicationData) & "\ffgsCRM.sdf")

Dim cmd As New SqlCeCommand()

cmd.Connection = _conn

cmd.CommandText = "select ProductDesc as Description, ProductCost as Cost, ProductListPrice as [List Price] from Product where ProductDesc like '%" & reqProductSearch & "%' ORDER BY ProductDesc"

_conn.Open()

Dim resultSet As SqlCeResultSet

resultSet = cmd.ExecuteResultSet(ResultSetOptions.Scrollable Or ResultSetOptions.Updatable)

'' FILL DATAGRIDVIEW

dbGridProducts.DataSource = resultSet

With dbGridProducts

.Columns("Description").Width = 550

End With

Thanks,

Bill

Hi,
did you try binding the table to the grid rather the dataset ? Did you get an error message on the first solution ? And why are you creating a dataset first just for binding ?
Jens K. Suessmeyer.

http://www.sqlserver2005.de
|||

hi... on the first solution when i'm getting

(ArgumentException was unhandled) Child list for field ProductDesc cannot be created when i use either ProductDesc or just Description as it would be in a a regular dataset like in SQLExpress... etc...

Dim ds As New DataSet

ds.Tables.Add(dtProduct)

Me.dbGridProducts.DataSource = ds

Me.dbGridProducts.DataMember = "Description"

this fails... i need the dataset for grouping and such and would like to know how it's done with CE...

Thanks,

Bill

|||

got my brain back... DataTable and Dataset examples... :)

'To Open the Connection To Connect to SQLCE

Dim ConsqlCombo As New SqlCeConnection

ConsqlCombo.ConnectionString = "Data Source = " & Environment.GetFolderPath(Environment.SpecialFolder.LocalApplicationData) & "\ffgsCRM.sdf"

'SQL STATEMENT......

Dim reqSQLCombo As New SqlCeCommand

reqSQLCombo.CommandText = "select ProductDesc as Description, ProductCost as Cost, ProductListPrice as [List Price] from Product where ProductMfgID = '" & reqSearch & "'"

reqSQLCombo.CommandType = CommandType.Text

reqSQLCombo.Connection = ConsqlCombo

'CREATE NEW SQL DATA ADAPTER

Dim sqldaCombo As New SqlCeDataAdapter(reqSQLCombo)

Dim sqldsCombo As New DataSet

' FILL DATASET

sqldaCombo.Fill(sqldsCombo, "ProductDesc")

'' FILL DATAGRID

dbGridProducts.DataSource = sqldsCombo.Tables("ProductDesc")

dbGridProducts.DataMember = "ProductDesc"

connection object to client ce

yo ce folks... Anyone had any trouble using a dataset for return values in a datagridview for the client app?

trying to make this work...

' Open the Connection For SQL Compact Edition

Dim cn As New SqlServerCe.SqlCeConnection("Data Source = " & Environment.GetFolderPath(Environment.SpecialFolder.LocalApplicationData) & "\ffgsCRM.sdf")

Dim cmdProduct As SqlServerCe.SqlCeCommand

' create dataset with table

cn.Open()

cmdProduct = cn.CreateCommand

cmdProduct.CommandText = "SELECT ProductDesc AS Description, ProductCost AS Cost, ProductListPrice AS [List Price] FROM Product"

Dim daProduct As New SqlServerCe.SqlCeDataAdapter(cmdProduct)

Dim dtProduct As New Data.DataTable("Product")

daProduct.Fill(dtProduct)

Dim ds As New DataSet

ds.Tables.Add(dtProduct)

'' FILL DATAGRIDVIEW

Me.dbGridProducts.DataSource = ds

I have this working:

' search product description

Dim reqProductSearch As String

reqProductSearch = tstxtSearchDescription.Text

' Open the Connection For SQL Compact Edition

Dim _conn = New SqlCeConnection("Data Source = " & Environment.GetFolderPath(Environment.SpecialFolder.LocalApplicationData) & "\ffgsCRM.sdf")

Dim cmd As New SqlCeCommand()

cmd.Connection = _conn

cmd.CommandText = "select ProductDesc as Description, ProductCost as Cost, ProductListPrice as [List Price] from Product where ProductDesc like '%" & reqProductSearch & "%' ORDER BY ProductDesc"

_conn.Open()

Dim resultSet As SqlCeResultSet

resultSet = cmd.ExecuteResultSet(ResultSetOptions.Scrollable Or ResultSetOptions.Updatable)

'' FILL DATAGRIDVIEW

dbGridProducts.DataSource = resultSet

With dbGridProducts

.Columns("Description").Width = 550

End With

Thanks,

Bill

hi... on the first solution when i'm getting

Dim ds As New DataSet

ds.Tables.Add(dtProduct)

Me.dbGridProducts.DataSource = ds

Me.dbGridProducts.DataMember = "Description"

this fails... i need the dataset for grouping and such and would like to know how it's done with CE...

Thanks,

Bill

|||

got my brain back... DataTable and Dataset examples... :)

'To Open the Connection To Connect to SQLCE

Dim ConsqlCombo As New SqlCeConnection

ConsqlCombo.ConnectionString = "Data Source = " & Environment.GetFolderPath(Environment.SpecialFolder.LocalApplicationData) & "\ffgsCRM.sdf"

'SQL STATEMENT......

Dim reqSQLCombo As New SqlCeCommand

reqSQLCombo.CommandText = "select ProductDesc as Description, ProductCost as Cost, ProductListPrice as [List Price] from Product where ProductMfgID = '" & reqSearch & "'"

reqSQLCombo.CommandType = CommandType.Text

reqSQLCombo.Connection = ConsqlCombo

'CREATE NEW SQL DATA ADAPTER

Dim sqldaCombo As New SqlCeDataAdapter(reqSQLCombo)

Dim sqldsCombo As New DataSet

' FILL DATASET

sqldaCombo.Fill(sqldsCombo, "ProductDesc")

'' FILL DATAGRID

dbGridProducts.DataSource = sqldsCombo.Tables("ProductDesc")

dbGridProducts.DataMember = "ProductDesc"

Monday, March 19, 2012

Connection Manager - No available servers

Windows XP Pro, SQL Server 2005 (Developer) & Visual Studio 2005 (Pro)

New SSIS project (Visual Studio)

New OLE DB/SQL Native client connection.

There's no servers available in the drop down box.

All the services that need to be running are running.

Guess I've missed the obvious here

Cheers

Dave

Hi,

did you try to enter the nae manually ?

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||Yes I did. Will re-try and then post the error.|||

Just tried entering the name manually and it worked...

Any ideas why I can't browse to the instance/server?

|||Do you use another port than the default one 1433 ? If so, you will have to make sure that SQL Server browser is started. What for ? See the link here for more information about the SQL Browser.

http://msdn2.microsoft.com/en-us/library/ms181087.aspx

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

Connection Issues

Hi,
I am working with a client whose primary software for their firm uses
MS SQL. They have been experiencing frequent issues with data missing
from query windows, or old data that has been deleted or archived
reappearing; the client closes the program and things are back to
normal. In talking with the support staff for the vendor, they assure
me that we have "an ideal enviroment" for running their software, but
are insisisting that the problems the client is experiencing are
"connection issues" and can't have not been able to point me in any
directions to check other than looking at the hardware environment
which they have said is "ideal". Can someone possibly explain what
other places we might look for connection issues? The client is
running SBS 2003 Premium, which includes SQL 2000. We have all
service packs installed on the server and the workstations.
If more info is needed please feel free to ask.
Thanks,
Mike Garoutte
Milwaukee, WII would look for transactions that are not being committed. In
general it is a Bad Thing for a transaction to remain open during any
user activity. It sounds like that is happening, and the connection
is being broken before or without the user doing whatever has to be
done to make the change final.
An alternate explanation would be that they application stages
transactions in other tables before updating the main tables, and the
user is not taking whatever final step there is that applies the data.
Roy Harvey
Beacon Falls, CT
On Tue, 29 Apr 2008 07:03:07 -0700 (PDT), Mike G <mgaroutte@.gmail.com>
wrote:
>Hi,
>I am working with a client whose primary software for their firm uses
>MS SQL. They have been experiencing frequent issues with data missing
>from query windows, or old data that has been deleted or archived
>reappearing; the client closes the program and things are back to
>normal. In talking with the support staff for the vendor, they assure
>me that we have "an ideal enviroment" for running their software, but
>are insisisting that the problems the client is experiencing are
>"connection issues" and can't have not been able to point me in any
>directions to check other than looking at the hardware environment
>which they have said is "ideal". Can someone possibly explain what
>other places we might look for connection issues? The client is
>running SBS 2003 Premium, which includes SQL 2000. We have all
>service packs installed on the server and the workstations.
>If more info is needed please feel free to ask.
>Thanks,
>Mike Garoutte
>Milwaukee, WI|||Hi Ron,
Thanks for your reply. I have to be honest that I am not sure how to
check for uncommitted transactions. When the record is saved, I would
assume it
would be updated in the database. One thing that frequently happens
while editing a record the
staff at the clients office will click the "Save & Close" button to
save the changes to the record and they get a message that the record
has
been deleted by another user, even though the record has not been
deleted. We are putting a gigabit nic in the server Thursday night.
Thanks for your help.
Mike
On Apr 29, 11:52=A0am, "Roy Harvey (SQL Server MVP)"
<roy_har...@.snet.net> wrote:
> I would look for transactions that are not being committed. =A0In
> general it is a Bad Thing for a transaction to remain open during any
> user activity. =A0It sounds like that is happening, and the connection
> is being broken before or without the user doing whatever has to be
> done to make the change final.
> An alternate explanation would be that they application stages
> transactions in other tables before updating the main tables, and the
> user is not taking whatever final step there is that applies the data.
> Roy Harvey
> Beacon Falls, CT
> On Tue, 29 Apr 2008 07:03:07 -0700 (PDT), Mike G <mgarou...@.gmail.com>
> wrote:
>
> >Hi,
> >I am working with a client whose primary software for their firm uses
> >MS SQL. =A0They have been experiencing frequent issues with data missing
> >from query windows, or old data that has been deleted or archived
> >reappearing; the client closes the program and things are back to
> >normal. =A0In talking with the support staff for the vendor, they assure
> >me that we have "an ideal enviroment" for running their software, but
> >are insisisting that the problems the client is experiencing are
> >"connection issues" and can't have not been able to point me in any
> >directions to check other than looking at the hardware environment
> >which they have said is "ideal". =A0Can someone possibly explain what
> >other places we might look for connection issues? =A0The client is
> >running SBS 2003 Premium, which includes SQL 2000. =A0We have all
> >service packs installed on the server and the workstations.
> >If more info is needed please feel free to ask.
> >Thanks,
> >Mike Garoutte
> >Milwaukee, WI- Hide quoted text -
> - Show quoted text -|||DBCC OPENTRAN can be used to find open transactions.
Roy Harvey
Beacon Falls, CT
On Wed, 30 Apr 2008 06:49:22 -0700 (PDT), Mike G <mgaroutte@.gmail.com>
wrote:
>Hi Ron,
>Thanks for your reply. I have to be honest that I am not sure how to
>check for uncommitted transactions. When the record is saved, I would
>assume it
>would be updated in the database. One thing that frequently happens
>while editing a record the
>staff at the clients office will click the "Save & Close" button to
>save the changes to the record and they get a message that the record
>has
>been deleted by another user, even though the record has not been
>deleted. We are putting a gigabit nic in the server Thursday night.
>Thanks for your help.
>Mike
>
>On Apr 29, 11:52 am, "Roy Harvey (SQL Server MVP)"
><roy_har...@.snet.net> wrote:
>> I would look for transactions that are not being committed. In
>> general it is a Bad Thing for a transaction to remain open during any
>> user activity. It sounds like that is happening, and the connection
>> is being broken before or without the user doing whatever has to be
>> done to make the change final.
>> An alternate explanation would be that they application stages
>> transactions in other tables before updating the main tables, and the
>> user is not taking whatever final step there is that applies the data.
>> Roy Harvey
>> Beacon Falls, CT
>> On Tue, 29 Apr 2008 07:03:07 -0700 (PDT), Mike G <mgarou...@.gmail.com>
>> wrote:
>>
>> >Hi,
>> >I am working with a client whose primary software for their firm uses
>> >MS SQL. They have been experiencing frequent issues with data missing
>> >from query windows, or old data that has been deleted or archived
>> >reappearing; the client closes the program and things are back to
>> >normal. In talking with the support staff for the vendor, they assure
>> >me that we have "an ideal enviroment" for running their software, but
>> >are insisisting that the problems the client is experiencing are
>> >"connection issues" and can't have not been able to point me in any
>> >directions to check other than looking at the hardware environment
>> >which they have said is "ideal". Can someone possibly explain what
>> >other places we might look for connection issues? The client is
>> >running SBS 2003 Premium, which includes SQL 2000. We have all
>> >service packs installed on the server and the workstations.
>> >If more info is needed please feel free to ask.
>> >Thanks,
>> >Mike Garoutte
>> >Milwaukee, WI- Hide quoted text -
>> - Show quoted text -

Connection issue with named instance

Hi all,
Since the replacement of new client workstation I've trouble for connection
of these new machines ot My different SQL Servers. On this configuration we
only speak of client/server connected on the same LAN without any antivirus
enabled.
When my users hae their new PC's (W2K - MDAC 2.6 SP1), they try to connect
to my server via for example ODBC and in this case when they browse network
they can't see named instance (only default instance is displayed (port 1433)
!). Next to it if they force the name in the connection string they still
can't connect ot the server, because of the port resolution. My workaround
today is to force the port in the connection string of each client (quite
heavy, 2500 workstations !!!) On my servers I have TCP/IP and Named Pipes
enable.
I've performed different test of connection (telnet 1433 work, PortQRY
return that 1433 and 1434 are working (but it didn't return all the instances
name), ping OK, tracert ok,...)
Any help would be appreciated, thanks in advance
SylvainCan you please follow below links and let us know if it was helpful for you.
http://sqljunkies.com/How%20To/2E1101E0-D5C1-4DBD-A398-FE485DFA439B.scuk
&
http://support.microsoft.com/default.aspx?scid=kb;en-us;287932
Regards
Surajit
"Sylvain" wrote:
> Hi all,
> Since the replacement of new client workstation I've trouble for connection
> of these new machines ot My different SQL Servers. On this configuration we
> only speak of client/server connected on the same LAN without any antivirus
> enabled.
> When my users hae their new PC's (W2K - MDAC 2.6 SP1), they try to connect
> to my server via for example ODBC and in this case when they browse network
> they can't see named instance (only default instance is displayed (port 1433)
> !). Next to it if they force the name in the connection string they still
> can't connect ot the server, because of the port resolution. My workaround
> today is to force the port in the connection string of each client (quite
> heavy, 2500 workstations !!!) On my servers I have TCP/IP and Named Pipes
> enable.
> I've performed different test of connection (telnet 1433 work, PortQRY
> return that 1433 and 1434 are working (but it didn't return all the instances
> name), ping OK, tracert ok,...)
> Any help would be appreciated, thanks in advance
> Sylvain|||Thanks for your reply.
Concerning the first link, after checking all cases the result is the same
than before, the only workaround is to create an alias (force port number).
All my clients even set on dynamically determine port, can't find an instance
other than the default except if I set manually the expected port by the
server.
For the second link, after checking with my network team we have validate
that no firewall are placed between clients and servers.
Thanks for your help
Sylvain
"surajits" wrote:
> Can you please follow below links and let us know if it was helpful for you.
> http://sqljunkies.com/How%20To/2E1101E0-D5C1-4DBD-A398-FE485DFA439B.scuk
> &
> http://support.microsoft.com/default.aspx?scid=kb;en-us;287932
>
> Regards
> Surajit
>
>
> "Sylvain" wrote:
> > Hi all,
> >
> > Since the replacement of new client workstation I've trouble for connection
> > of these new machines ot My different SQL Servers. On this configuration we
> > only speak of client/server connected on the same LAN without any antivirus
> > enabled.
> > When my users hae their new PC's (W2K - MDAC 2.6 SP1), they try to connect
> > to my server via for example ODBC and in this case when they browse network
> > they can't see named instance (only default instance is displayed (port 1433)
> > !). Next to it if they force the name in the connection string they still
> > can't connect ot the server, because of the port resolution. My workaround
> > today is to force the port in the connection string of each client (quite
> > heavy, 2500 workstations !!!) On my servers I have TCP/IP and Named Pipes
> > enable.
> > I've performed different test of connection (telnet 1433 work, PortQRY
> > return that 1433 and 1434 are working (but it didn't return all the instances
> > name), ping OK, tracert ok,...)
> >
> > Any help would be appreciated, thanks in advance
> > Sylvain

Connection issue with named instance

Hi all,
Since the replacement of new client workstation I've trouble for connection
of these new machines ot My different SQL Servers. On this configuration we
only speak of client/server connected on the same LAN without any antivirus
enabled.
When my users hae their new PC's (W2K - MDAC 2.6 SP1), they try to connect
to my server via for example ODBC and in this case when they browse network
they can't see named instance (only default instance is displayed (port 1433)
!). Next to it if they force the name in the connection string they still
can't connect ot the server, because of the port resolution. My workaround
today is to force the port in the connection string of each client (quite
heavy, 2500 workstations !!!) On my servers I have TCP/IP and Named Pipes
enable.
I've performed different test of connection (telnet 1433 work, PortQRY
return that 1433 and 1434 are working (but it didn't return all the instances
name), ping OK, tracert ok,...)
Any help would be appreciated, thanks in advance
Sylvain
Can you please follow below links and let us know if it was helpful for you.
http://sqljunkies.com/How%20To/2E110...85DFA439B.scuk
&
http://support.microsoft.com/default...b;en-us;287932
Regards
Surajit
"Sylvain" wrote:

> Hi all,
> Since the replacement of new client workstation I've trouble for connection
> of these new machines ot My different SQL Servers. On this configuration we
> only speak of client/server connected on the same LAN without any antivirus
> enabled.
> When my users hae their new PC's (W2K - MDAC 2.6 SP1), they try to connect
> to my server via for example ODBC and in this case when they browse network
> they can't see named instance (only default instance is displayed (port 1433)
> !). Next to it if they force the name in the connection string they still
> can't connect ot the server, because of the port resolution. My workaround
> today is to force the port in the connection string of each client (quite
> heavy, 2500 workstations !!!) On my servers I have TCP/IP and Named Pipes
> enable.
> I've performed different test of connection (telnet 1433 work, PortQRY
> return that 1433 and 1434 are working (but it didn't return all the instances
> name), ping OK, tracert ok,...)
> Any help would be appreciated, thanks in advance
> Sylvain
|||Thanks for your reply.
Concerning the first link, after checking all cases the result is the same
than before, the only workaround is to create an alias (force port number).
All my clients even set on dynamically determine port, can't find an instance
other than the default except if I set manually the expected port by the
server.
For the second link, after checking with my network team we have validate
that no firewall are placed between clients and servers.
Thanks for your help
Sylvain
"surajits" wrote:
[vbcol=seagreen]
> Can you please follow below links and let us know if it was helpful for you.
> http://sqljunkies.com/How%20To/2E110...85DFA439B.scuk
> &
> http://support.microsoft.com/default...b;en-us;287932
>
> Regards
> Surajit
>
>
> "Sylvain" wrote:

Connection issue with named instance

Hi all,
Since the replacement of new client workstation I've trouble for connection
of these new machines ot My different SQL Servers. On this configuration we
only speak of client/server connected on the same LAN without any antivirus
enabled.
When my users hae their new PC's (W2K - MDAC 2.6 SP1), they try to connect
to my server via for example ODBC and in this case when they browse network
they can't see named instance (only default instance is displayed (port 1433
)
!). Next to it if they force the name in the connection string they still
can't connect ot the server, because of the port resolution. My workaround
today is to force the port in the connection string of each client (quite
heavy, 2500 workstations !!!) On my servers I have TCP/IP and Named Pipes
enable.
I've performed different test of connection (telnet 1433 work, PortQRY
return that 1433 and 1434 are working (but it didn't return all the instance
s
name), ping OK, tracert ok,...)
Any help would be appreciated, thanks in advance
SylvainCan you please follow below links and let us know if it was helpful for you.
http://sqljunkies.com/How%20To/2E11...485DFA439B.scuk
&
http://support.microsoft.com/defaul...kb;en-us;287932
Regards
Surajit
"Sylvain" wrote:

> Hi all,
> Since the replacement of new client workstation I've trouble for connectio
n
> of these new machines ot My different SQL Servers. On this configuration w
e
> only speak of client/server connected on the same LAN without any antiviru
s
> enabled.
> When my users hae their new PC's (W2K - MDAC 2.6 SP1), they try to connect
> to my server via for example ODBC and in this case when they browse networ
k
> they can't see named instance (only default instance is displayed (port 14
33)
> !). Next to it if they force the name in the connection string they still
> can't connect ot the server, because of the port resolution. My workaround
> today is to force the port in the connection string of each client (quite
> heavy, 2500 workstations !!!) On my servers I have TCP/IP and Named Pipes
> enable.
> I've performed different test of connection (telnet 1433 work, PortQRY
> return that 1433 and 1434 are working (but it didn't return all the instan
ces
> name), ping OK, tracert ok,...)
> Any help would be appreciated, thanks in advance
> Sylvain|||Thanks for your reply.
Concerning the first link, after checking all cases the result is the same
than before, the only workaround is to create an alias (force port number).
All my clients even set on dynamically determine port, can't find an instanc
e
other than the default except if I set manually the expected port by the
server.
For the second link, after checking with my network team we have validate
that no firewall are placed between clients and servers.
Thanks for your help
Sylvain
"surajits" wrote:
[vbcol=seagreen]
> Can you please follow below links and let us know if it was helpful for yo
u.
> http://sqljunkies.com/How%20To/2E11...485DFA439B.scuk
> &
> http://support.microsoft.com/defaul...kb;en-us;287932
>
> Regards
> Surajit
>
>
> "Sylvain" wrote:
>

connection issue from our developer

Hi,
SQL 2005 EE is installed on W2k3 box and firewall is off in this server.
From my client machine, my window account and that developer window account
all can login into this server with ODBC, sql client, telent to 1433 or VS
connection. But, this developer can't login to SQL server from him machine
with any appliction. He is in the same domain as server and my machine. I
don't know what's the reason to cause this issue now.
Please advise. Thank you.
Lynn
Best Regards,
Lynn
What is the exact error message and error number he gets
when he tries to log into SQL Server?
-Sue
On Thu, 22 Mar 2007 10:33:45 -0700, Lynn
<Lynn@.discussions.microsoft.com> wrote:

>Hi,
>SQL 2005 EE is installed on W2k3 box and firewall is off in this server.
>From my client machine, my window account and that developer window account
>all can login into this server with ODBC, sql client, telent to 1433 or VS
>connection. But, this developer can't login to SQL server from him machine
>with any appliction. He is in the same domain as server and my machine. I
>don't know what's the reason to cause this issue now.
>Please advise. Thank you.
>Lynn
|||We only enable Shared Memory and TCP/IP protocal in server side. And, those
are the error they are getting.
osql -- SQL server doesn't exist or access denied
Query Analyzer -- General network error. Check your network documentation
VS 2005 -- (without specifing TCP protocal in connection) A connection was
succssfully established with the server, but then an error occured during the
pre-login handshake. When connecting ....(provider: Named Pipes provider,
error: 0 - No process is on the ther end of the pipe)
VS 2005 -- (specify TCP protocal in connection) 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 ...
(provider: TCP provider: 0 -- A connection attempt failed because the
connected party didn't not properly respond after a period of tiem, or
established connection failed because connected host has failed to respond.)
Again, this developer is able to login by using my machine with his WIN
account.
After I enable Named Pipes in server. This developer is able to connect to
server on his machine by using Named Pipe.
Firewall is off in the server, so I can't think of the issue for TCP
connection on developer's machine.
Please advise. Thank you.
Best Regards,
Lynn
"Sue Hoegemeier" wrote:

> What is the exact error message and error number he gets
> when he tries to log into SQL Server?
> -Sue
> On Thu, 22 Mar 2007 10:33:45 -0700, Lynn
> <Lynn@.discussions.microsoft.com> wrote:
>
>
|||Check the following article in Books Online:
http://msdn2.microsoft.com/en-us/library/ms175496.aspx
-Sue
On Fri, 23 Mar 2007 09:15:08 -0700, Lynn
<Lynn@.discussions.microsoft.com> wrote:

>We only enable Shared Memory and TCP/IP protocal in server side. And, those
>are the error they are getting.
>osql -- SQL server doesn't exist or access denied
>Query Analyzer -- General network error. Check your network documentation
>VS 2005 -- (without specifing TCP protocal in connection) A connection was
>succssfully established with the server, but then an error occured during the
>pre-login handshake. When connecting ....(provider: Named Pipes provider,
>error: 0 - No process is on the ther end of the pipe)
>VS 2005 -- (specify TCP protocal in connection) 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 ...
>(provider: TCP provider: 0 -- A connection attempt failed because the
>connected party didn't not properly respond after a period of tiem, or
>established connection failed because connected host has failed to respond.)
>Again, this developer is able to login by using my machine with his WIN
>account.
>After I enable Named Pipes in server. This developer is able to connect to
>server on his machine by using Named Pipe.
>Firewall is off in the server, so I can't think of the issue for TCP
>connection on developer's machine.
>Please advise. Thank you.
|||Sue,
The developer's client protocol order is TCP and NP. We didn't enable Named
Pipe in server at the beginning, that's why the first message is NP message
due to client will try to connect in the protocol order in the client. As I
menetioned, after I turn on Named Pipes in server, user's machine is able to
connect to server. But, the issue our developers had is that they couldn't
connect with TCP protocol from their machine. (I can connect by TCP protocol
from my machine. The developer login to my machine and his win account can
connect to the server as well). His machine is able to connect to our SQL
2000 with TCP protocol, but just can't connect to 2005 with TCP protocol. I
was thinging is firewall in server to caused this issue, but firewall didn't
enable in the server at all. So, I don't know what cause the issue.
Please advise.
Best Regards,
Lynn
"Sue Hoegemeier" wrote:

> Check the following article in Books Online:
> http://msdn2.microsoft.com/en-us/library/ms175496.aspx
> -Sue
> On Fri, 23 Mar 2007 09:15:08 -0700, Lynn
> <Lynn@.discussions.microsoft.com> wrote:
>
>
|||When you get symptoms like this where it only affects the
user on a particular PC then you need to look at that PC.
You'd probably start by testing basic connectivity to the
server from the PC: Can the user ping the server by name,
can the user ping the server by IP, what network related
issues are found in the Event logs on the PC, can the user
connect to the server using sqlcmd, etc. Also, have you
tried logging in from that users PC?
If you find that the issue is comes up only with Management
Studio, have the user increase the connect timeout in SSMS:
When logging on, click on the options button in the Connect
to Server window and increase the connection timeout to
something greater than the 15 second default.
It would also be worth checking the users MDAC installation
using the component checker. You can download this from:
http://msdn2.microsoft.com/en-us/data/aa937730.aspx
You may also want to look at applying the latest SQL Server
service pack to the client on that PC having problems.
-Sue
On Thu, 29 Mar 2007 15:38:05 -0700, Lynn
<Lynn@.discussions.microsoft.com> wrote:

>Sue,
>The developer's client protocol order is TCP and NP. We didn't enable Named
>Pipe in server at the beginning, that's why the first message is NP message
>due to client will try to connect in the protocol order in the client. As I
>menetioned, after I turn on Named Pipes in server, user's machine is able to
>connect to server. But, the issue our developers had is that they couldn't
>connect with TCP protocol from their machine. (I can connect by TCP protocol
>from my machine. The developer login to my machine and his win account can
>connect to the server as well). His machine is able to connect to our SQL
>2000 with TCP protocol, but just can't connect to 2005 with TCP protocol. I
>was thinging is firewall in server to caused this issue, but firewall didn't
>enable in the server at all. So, I don't know what cause the issue.
>Please advise.
|||Sue,
Thank you again. Definitely, we already checked the network connect from
those developers machine. The connection issue happens to all related
developers. The developers were able to ping the server by name and IP from
their machine. But, the issue only happened on connecting to SQL 2005 with
TCP protocol. We tested through ODBC (with TCP/IP), osql, telnet to 1433
port, VS, but all connection were failed.
One developer already reinstall SQL 2005 client, but the problem is still
resisted. Will ask them to update to sp2 and go from there.
Best Regards,
Lynn
"Sue Hoegemeier" wrote:

> When you get symptoms like this where it only affects the
> user on a particular PC then you need to look at that PC.
> You'd probably start by testing basic connectivity to the
> server from the PC: Can the user ping the server by name,
> can the user ping the server by IP, what network related
> issues are found in the Event logs on the PC, can the user
> connect to the server using sqlcmd, etc. Also, have you
> tried logging in from that users PC?
> If you find that the issue is comes up only with Management
> Studio, have the user increase the connect timeout in SSMS:
> When logging on, click on the options button in the Connect
> to Server window and increase the connection timeout to
> something greater than the 15 second default.
> It would also be worth checking the users MDAC installation
> using the component checker. You can download this from:
> http://msdn2.microsoft.com/en-us/data/aa937730.aspx
> You may also want to look at applying the latest SQL Server
> service pack to the client on that PC having problems.
> -Sue

Sunday, March 11, 2012

Connection is busy with results for another command

We are migrating our databases from MS Access to SQL Server 2005 and using the SQL Native Client ODBC driver.

We also use a reporting tool called Actuate. Some of our Actuate reports use multiple datastreams to build the report.

When I run an Actuate report having multiple datastreams I get the following error message from SQL Server:

Error generated by the connected data source. Connection is busy with results for another command.

Is there a configuration setting in SQL Server to enable processing of multiple result sets?

Thanks.

sqlserver can handle thousands of connections. The error reported sounds like your application error/limitation. I suggest you take a look at the application configuration (i.e. connection or command method).

|||Thanks, oj.

I think what's happening is that Actuate is attempting to execute multiple queries simultaneously against the same db connection. The error I'm getting looks to be an ODBC error generated from SQL Server.|||

It's typically the data access provider (odbc, .net, etc.) that the application uses that throws the error. For example, you cannot execute another sqlcommand on the same connection that is being used/processed by a sqldatareader.

http://msdn2.microsoft.com/en-us/library/system.data.sqlclient.sqldatareader.aspx

|||

SQL Server introduced MARS which allows multiactive resultssets. have a look in the BOL and see have you can enabled it within your conenctionstring at www.connectionstrings.com

Jens K Suessmeyer

http://www.sqlserver2005.de

Connection is busy with results for another command

We are migrating our databases from MS Access to SQL Server 2005 and using the SQL Native Client ODBC driver.

We also use a reporting tool called Actuate. Some of our Actuate reports use multiple datastreams to build the report.

When I run an Actuate report having multiple datastreams I get the following error message from SQL Server:

Error generated by the connected data source. Connection is busy with results for another command.

Is there a configuration setting in SQL Server to enable processing of multiple result sets?

Thanks.

|||Thanks, oj.

http://msdn2.microsoft.com/en-us/library/system.data.sqlclient.sqldatareader.aspx

|||

SQL Server introduced MARS which allows multiactive resultssets. have a look in the BOL and see have you can enabled it within your conenctionstring at www.connectionstrings.com

Jens K Suessmeyer

http://www.sqlserver2005.de

Connection is busy with results for another command

We are migrating our databases from MS Access to SQL Server 2005 and using the SQL Native Client ODBC driver.

We also use a reporting tool called Actuate. Some of our Actuate reports use multiple datastreams to build the report.

When I run an Actuate report having multiple datastreams I get the following error message from SQL Server:

Error generated by the connected data source. Connection is busy with results for another command.

Is there a configuration setting in SQL Server to enable processing of multiple result sets?

Thanks.

|||Thanks, oj.

http://msdn2.microsoft.com/en-us/library/system.data.sqlclient.sqldatareader.aspx

|||

SQL Server introduced MARS which allows multiactive resultssets. have a look in the BOL and see have you can enabled it within your conenctionstring at www.connectionstrings.com

Jens K Suessmeyer

http://www.sqlserver2005.de

Connection is busy with results for another command

We are migrating our databases from MS Access to SQL Server 2005 and using the SQL Native Client ODBC driver.

We also use a reporting tool called Actuate. Some of our Actuate reports use multiple datastreams to build the report.

When I run an Actuate report having multiple datastreams I get the following error message from SQL Server:

Error generated by the connected data source. Connection is busy with results for another command.

Is there a configuration setting in SQL Server to enable processing of multiple result sets?

Thanks.

|||Thanks, oj.

http://msdn2.microsoft.com/en-us/library/system.data.sqlclient.sqldatareader.aspx

|||

SQL Server introduced MARS which allows multiactive resultssets. have a look in the BOL and see have you can enabled it within your conenctionstring at www.connectionstrings.com

Jens K Suessmeyer

http://www.sqlserver2005.de

Connection from XP SP2 to Windows 2003 R2 with SQL Server 2005 failed

I cannot make named pipe connection with client by ODBC DSA.

Here is information. Refering to http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=362498&SiteID=1.

[1] Client side:

1. What is the connection string in you app or DSN? (please specify) ODBC \\[SERVER_NAME]\pipe\sql\guery

2. If client fails to connect, what is the client error messages? (please specify) Connection failed: SQLState: ’01000’ SQL ServerError: 1326 [Microsoft][ODBC SQL Server Driver][Named Pipes]connectionOpen (Connect()) Connection failed: SQLState: ’08001’ SQL Server Error: 17 [Microsoft][ODBC SQL Server Driver][Named Pipes]SQL Server does not exist or access denied.

3. Is the client remote or local to the SQL server machine? [Remote | Local]

4. Can you ping your server? [YES | NO ]

In cmd.exe console, type “ping -a <server_name>”.

5. Can you telnet to your SQL Server? [YES | NO, please specify the error message ]

In cmd.exe console, type “telnet <server name> port, where port can be 135, 445 or sql_server_tcp_port. If your cmd.exe console turns into a complete black screen with a cursor flushing on top left corner, you are connected. Type ctrl+’[‘ to bring up telnet prompt and type “quit” <enter>.

7. Is your client computer in the same domain as the Server computer? (Same domain | Different domains | WorkGroup)

8. What protocol the client enabled? [Shared Memory | TCPIP | Named Pipes].

9. Do you have aliases configured that match the server name portion of your connection string? If so, please check if it is correct. You can use cliconfg.exe (SS 2000) or SQL Server Configuration Manager (SS 2005) to configure the alias. [NO]

10. Do you select force encryption on server and/or client? [NO]

I was able to connect with TCP/IP settings.

[2] Server side:

1. What is the MS SQL version? [SQL Server 2005]

2. What is the SKU of MS SQL? [Enterprise | Standard | Workgroup | Express (or MSDE) | other (please specify)].

3. What is the SQL Server Protocol enabled? [Shared Memory | TCPIP | Named Pipes ]. Use SQL Server Configuration Manager to configure it and check ERRORLOG or event log to confirm.

4. Does the server start successfully? [YES | NO] If not what is the error messages in the SQL server ERRORLOG?

5. If SQL Server is a named instance, is the SQL browser enabled? [YES | NO]

6. What is the account that the SQL Server is running under?[Local System | Network Service | Domain Account]

7. Do you make firewall exception for your SQL server TCP port if you want connect remotely through TCP provider? [YES | NO | not applicable | not enabled]

8. Do you make firewall exception for SQL Browser UDP port 1434? In SQL2000, you still need to make firewall exception for UDP port 1434 in order to support named instance.[YES | NO | not applicable | not enabled]

I could connect locally with named pipes.

Do I have to make some file shares manually?

[2a] Tool Used to Connect

What tool or Application are you using to connect to SQL Server (eg: Visual Studio, SQL Server Management Studio, SQLCmd.exe, OSQL, etc) and especially the version of SQL Server (Express, Workgroup, Standard, Enterprise, Developer)

[3] Platform:

1. What is the OS version? [Windows XPSP2 | Windows 2003 | Windows 2000 | Windows 98 | others (please specify ) ].

1. Server [Windows Server 2003 R2]

2. Client [Windows XP SP2]

2. Do you have third party antivirus, anti-spareware software installed? [Symantec | Norton | other (please specify) ? NO].

[4] Misc:

1. If you have certificate configuration issue: Please use “certutil.exe –v –store my” to dump certificate specific info and post it in your question. [NO]

What happens if you execute
net use \\[server_name]\ipc$
from the client?

Tuesday, March 27, 2012

connection problem

Sunday, March 25, 2012

connection problem

Thursday, March 22, 2012

connection pooling

connection pooling

Tuesday, March 20, 2012

Connection Open (Create File()) /SQL server registration

Connection Open (Create File()) /SQL server registration

Connection Open (Create File()) /SQL server registration

connection object to client ce

connection object to client ce

Monday, March 19, 2012

Connection Manager - No available servers

Connection Issues

Connection issue with named instance

Connection issue with named instance

Connection issue with named instance

connection issue from our developer

Sunday, March 11, 2012

Connection is busy with results for another command

Connection is busy with results for another command

Connection is busy with results for another command

Connection is busy with results for another command

Connection from XP SP2 to Windows 2003 R2 with SQL Server 2005 failed

Do I have to make some file shares manually?

asp sql server

Blog Archive

About Me