Problem registering server in Enterprise manager

Hi,
I've recently installed SQL Server 2000 on a laptop. The laptop has a
wireless connection to the LAN. I am able to register the other SQL Servers
on the network on the intance on the laptop, but I cannot register the
instance on the laptop from the others; I get the error message "SQL Server
does not existor access denied.|ConnectionOpen (Connect()"
*SQL Server is running on the laptop
*SQL Server agent is also running
*The login and password I use are correct (and I use SQL Server
authentication).
*I have installed SP3a
*I have disabled the Windows XP SP2 firewall and even uninstalled my other
firewall.
*The instance of SQL Server I am trying to register does show up as an
available server in the Register SQL Server Wizard.
What might be the problem? I would also very much appreciate if someone
could point me in the right direction regarding how to troubleshoot this
better, so I can find out where the failure occurs.Try registering the instance of SQL on the laptop FROM the laptop, but do no
t
use the localhost syntax, use the same syntax which is failing from across
the wireless network, whether that's using a netbios name, or rcpip
addresss... What happens then?
"Daniel" wrote:

> Hi,
> I've recently installed SQL Server 2000 on a laptop. The laptop has a
> wireless connection to the LAN. I am able to register the other SQL Server
s
> on the network on the intance on the laptop, but I cannot register the
> instance on the laptop from the others; I get the error message "SQL Serve
r
> does not existor access denied.|ConnectionOpen (Connect()"
> *SQL Server is running on the laptop
> *SQL Server agent is also running
> *The login and password I use are correct (and I use SQL Server
> authentication).
> *I have installed SP3a
> *I have disabled the Windows XP SP2 firewall and even uninstalled my other
> firewall.
> *The instance of SQL Server I am trying to register does show up as an
> available server in the Register SQL Server Wizard.
> What might be the problem? I would also very much appreciate if someone
> could point me in the right direction regarding how to troubleshoot this
> better, so I can find out where the failure occurs.
>|||I am using the Register SQL Server Wizard in Enterprise manager. From the
list of available servers, I choose Laptop3 (the name of the laptop). If I d
o
the same thing FROM the laptop there are no problems. Does this indicate tha
t
the problem is not actually SQL Server related, but rather something with th
e
network? I had the same symptoms a while back when registering other
instances of SQL Server, and that time I solved it by allowing incoming
traffic on ports TCP 1433, UDP 1434 and file and printer sharing in the
Windows XP Firewall. This time that didn't solve the problem and neither did
deactivating the firewall altogether.
Perhaps I should also say that when I installed SQL Server on the laptop, I
had to choose to let SQL Server and SQL Server Agent log in on the local
system account, because for some reason the domain user account I tried coul
d
not be validated. I changed this after the installation so now they both log
in on a domain user account.
The activated protocols are TCP/IP (1433) and named pipes.
"CBretana" wrote:

> Try registering the instance of SQL on the laptop FROM the laptop, but do
not
> use the localhost syntax, use the same syntax which is failing from across
> the wireless network, whether that's using a netbios name, or rcpip
> addresss... What happens then?|||I'd have whoever is responsible for your wireless access point check it out.
Sometimes traffic is filtered either to or from the wireless network for
security reasons. There may be necessary components of the registration
process that aren't allowed to pass through the wireless access point.
"Daniel" <daXniel_kriXstensXen_@.hotmail.com (remove the Xs)> wrote in
message news:26EEB241-9BAA-40D5-8846-DAC1AB702E7D@.microsoft.com...
> Hi,
> I've recently installed SQL Server 2000 on a laptop. The laptop has a
> wireless connection to the LAN. I am able to register the other SQL
Servers
> on the network on the intance on the laptop, but I cannot register the
> instance on the laptop from the others; I get the error message "SQL
Server
> does not existor access denied.|ConnectionOpen (Connect()"
> *SQL Server is running on the laptop
> *SQL Server agent is also running
> *The login and password I use are correct (and I use SQL Server
> authentication).
> *I have installed SP3a
> *I have disabled the Windows XP SP2 firewall and even uninstalled my other
> firewall.
> *The instance of SQL Server I am trying to register does show up as an
> available server in the Register SQL Server Wizard.
> What might be the problem? I would also very much appreciate if someone
> could point me in the right direction regarding how to troubleshoot this
> better, so I can find out where the failure occurs.
>|||When you attempt to register the server, you are logging in. There are two
ways to do this, with a userID and password, or using what is called
"Integrated security" which uses the userID / password of whomever is logged
on to the box you're doing it from. Which of these you are using depends on
how you installed SQL Server. When you installed SQL, did you select
Integrated Secutrity only, or did you choose Itegrated security AND SQL
Server Security ?
When you attempt to register the SQL Server, are you asked to enter a UserID
And Password? My guess is that you are not.. If that's true, then when you
attempt to register from another box, the SQL Server is not recognozing the
UserID of whomever is logged on there as being a valid Login...
Try to actually enter the "sa" and the sa password from the remote
Enterprise manager, AND from the laptop Enterprise Manager, and see if
there's a difference...
"Daniel" wrote:

> I am using the Register SQL Server Wizard in Enterprise manager. From the
> list of available servers, I choose Laptop3 (the name of the laptop). If I
do
> the same thing FROM the laptop there are no problems. Does this indicate t
hat
> the problem is not actually SQL Server related, but rather something with
the
> network? I had the same symptoms a while back when registering other
> instances of SQL Server, and that time I solved it by allowing incoming
> traffic on ports TCP 1433, UDP 1434 and file and printer sharing in the
> Windows XP Firewall. This time that didn't solve the problem and neither d
id
> deactivating the firewall altogether.
> Perhaps I should also say that when I installed SQL Server on the laptop,
I
> had to choose to let SQL Server and SQL Server Agent log in on the local
> system account, because for some reason the domain user account I tried co
uld
> not be validated. I changed this after the installation so now they both l
og
> in on a domain user account.
> The activated protocols are TCP/IP (1433) and named pipes.
>
> "CBretana" wrote:
>
>|||"CBretana" wrote:
> When you attempt to register the server, you are logging in. There are tw
o
> ways to do this, with a userID and password, or using what is called
> "Integrated security" which uses the userID / password of whomever is logg
ed
> on to the box you're doing it from. Which of these you are using depends
on
> how you installed SQL Server. When you installed SQL, did you select
> Integrated Secutrity only, or did you choose Itegrated security AND SQL
> Server Security ?
I chose mixed mode.

> When you attempt to register the SQL Server, are you asked to enter a User
ID
> And Password? My guess is that you are not.. If that's true, then when yo
u
> attempt to register from another box, the SQL Server is not recognozing th
e
> UserID of whomever is logged on there as being a valid Login...
> Try to actually enter the "sa" and the sa password from the remote
> Enterprise manager, AND from the laptop Enterprise Manager, and see if
> there's a difference...
Actually that's precisely what I do, and it only works from the laptop.
Sorry I didn't mention this already.|||Unfortunately, the guy responsible for these things are on vacation. I've
been able to register SQL Servers on laptops connected to the wireless acces
s
point previously. However, I did tamper with the wireless access point to ge
t
the new laptops to be able to connect to it. Pretty stupid of me not to chec
k
whether the SQL Servers on the old laptops are still accesible... That will
be the first thing I'll do on Monday. Even if it doesn't solve the problem i
t
will narrow down the possible causes of it.
"Mike Jansen" wrote:

> I'd have whoever is responsible for your wireless access point check it ou
t.
> Sometimes traffic is filtered either to or from the wireless network for
> security reasons. There may be necessary components of the registration
> process that aren't allowed to pass through the wireless access point.
> "Daniel" <daXniel_kriXstensXen_@.hotmail.com (remove the Xs)> wrote in
> message news:26EEB241-9BAA-40D5-8846-DAC1AB702E7D@.microsoft.com...
> Servers
> Server
>
>|||Ok, sorry, I should have asked this last time but forgot, since I askedit
first time...
From laptop, when you register, are you using "local" or typing the
laptop's server name, or IP Address to specify the server?
If you are using "local", then try using the same thing, on the laptop, that
is failing from over the network...
Say it's ServerName...
If that then also fails, on laptop, same as it fails from over network,
then your problem is related to networking. Try using the IPAddress
directly instead of server name. If that works, then problem is name
resolution (DNS or WINs resolution) issues.
"Daniel" wrote:

> "CBretana" wrote:
> I chose mixed mode.
>
> Actually that's precisely what I do, and it only works from the laptop.
> Sorry I didn't mention this already.

problem opening data connection

Using SS2000, RS2000, VS2003. I'm trying to make changes to some reports that
someone else created. I'm not very familiar with either RS or VS. When I go
into VS and load the solution (someone told me how to find the correct one)
and then in the solution explorer, I double click on the report that I want
to change. Then I click on the "Data" tab and I get this error:
"A connection cannot be made to the database. Set and test the connection
string. SQL Server does not exist or access denied." I double clicked on the
rds file under "Shared Data Sources" and looked on the General tab. This is
the connection string "data source=localhost;initial catalog=SMCLMS_Dev. I
think the contractor developed on his local machine and then deployed to the
development server. I don't have RS on my machine. Will it hurt anything if
I change the connection string to point to the development server?
Thanks,
--
Dan D.No problem check all the parameters and most importantly select the server
and database and user / password. it should work..
Amarnath
"Dan D." wrote:
> Using SS2000, RS2000, VS2003. I'm trying to make changes to some reports that
> someone else created. I'm not very familiar with either RS or VS. When I go
> into VS and load the solution (someone told me how to find the correct one)
> and then in the solution explorer, I double click on the report that I want
> to change. Then I click on the "Data" tab and I get this error:
> "A connection cannot be made to the database. Set and test the connection
> string. SQL Server does not exist or access denied." I double clicked on the
> rds file under "Shared Data Sources" and looked on the General tab. This is
> the connection string "data source=localhost;initial catalog=SMCLMS_Dev. I
> think the contractor developed on his local machine and then deployed to the
> development server. I don't have RS on my machine. Will it hurt anything if
> I change the connection string to point to the development server?
> Thanks,
>
> --
> Dan D.|||Thanks.
If I create a new data source and a new report in the same solution, how do
I deploy it? If I don't use VS2003 to deploy do I take both the rds and rdl
files and upload them to the reports folder? Or is the rds file incorporated
in the rdl file and I just have to upload the rdl file?
Thanks,
--
Dan D.
"Amarnath" wrote:
> No problem check all the parameters and most importantly select the server
> and database and user / password. it should work..
> Amarnath
>
> "Dan D." wrote:
> > Using SS2000, RS2000, VS2003. I'm trying to make changes to some reports that
> > someone else created. I'm not very familiar with either RS or VS. When I go
> > into VS and load the solution (someone told me how to find the correct one)
> > and then in the solution explorer, I double click on the report that I want
> > to change. Then I click on the "Data" tab and I get this error:
> > "A connection cannot be made to the database. Set and test the connection
> > string. SQL Server does not exist or access denied." I double clicked on the
> > rds file under "Shared Data Sources" and looked on the General tab. This is
> > the connection string "data source=localhost;initial catalog=SMCLMS_Dev. I
> > think the contractor developed on his local machine and then deployed to the
> > development server. I don't have RS on my machine. Will it hurt anything if
> > I change the connection string to point to the development server?
> >
> > Thanks,
> >
> >
> > --
> > Dan D.|||If you deploy the rdl from VS2003 it will automatically deploy the rds, if it
hasn't been deployed before. The default is not to allow deployed rds to be
overwritten.
You can also deploy both the rds and rdl by uploading from the Report Manager.
HTH,
magendo_man
"Dan D." wrote:
> Thanks.
> If I create a new data source and a new report in the same solution, how do
> I deploy it? If I don't use VS2003 to deploy do I take both the rds and rdl
> files and upload them to the reports folder? Or is the rds file incorporated
> in the rdl file and I just have to upload the rdl file?
> Thanks,
> --
> Dan D.
>
> "Amarnath" wrote:
> > No problem check all the parameters and most importantly select the server
> > and database and user / password. it should work..
> >
> > Amarnath
> >
> >
> > "Dan D." wrote:
> >
> > > Using SS2000, RS2000, VS2003. I'm trying to make changes to some reports that
> > > someone else created. I'm not very familiar with either RS or VS. When I go
> > > into VS and load the solution (someone told me how to find the correct one)
> > > and then in the solution explorer, I double click on the report that I want
> > > to change. Then I click on the "Data" tab and I get this error:
> > > "A connection cannot be made to the database. Set and test the connection
> > > string. SQL Server does not exist or access denied." I double clicked on the
> > > rds file under "Shared Data Sources" and looked on the General tab. This is
> > > the connection string "data source=localhost;initial catalog=SMCLMS_Dev. I
> > > think the contractor developed on his local machine and then deployed to the
> > > development server. I don't have RS on my machine. Will it hurt anything if
> > > I change the connection string to point to the development server?
> > >
> > > Thanks,
> > >
> > >
> > > --
> > > Dan D.|||If you have VS 2003 that's well and good since it does everything for you,
when you just click "deploy". When you deploy all the details are stored in
tables in an encrypted form so just copying is not the solution.. Other way
is through scripts. using RS.exe
Let me know if you require it or just go to sample.RSS at
\Samples\Reporting Services\Script Samples and select publishsample report.
Just see how to publish a report and you can change accordingly.
Amarnath
"Dan D." wrote:
> Thanks.
> If I create a new data source and a new report in the same solution, how do
> I deploy it? If I don't use VS2003 to deploy do I take both the rds and rdl
> files and upload them to the reports folder? Or is the rds file incorporated
> in the rdl file and I just have to upload the rdl file?
> Thanks,
> --
> Dan D.
>
> "Amarnath" wrote:
> > No problem check all the parameters and most importantly select the server
> > and database and user / password. it should work..
> >
> > Amarnath
> >
> >
> > "Dan D." wrote:
> >
> > > Using SS2000, RS2000, VS2003. I'm trying to make changes to some reports that
> > > someone else created. I'm not very familiar with either RS or VS. When I go
> > > into VS and load the solution (someone told me how to find the correct one)
> > > and then in the solution explorer, I double click on the report that I want
> > > to change. Then I click on the "Data" tab and I get this error:
> > > "A connection cannot be made to the database. Set and test the connection
> > > string. SQL Server does not exist or access denied." I double clicked on the
> > > rds file under "Shared Data Sources" and looked on the General tab. This is
> > > the connection string "data source=localhost;initial catalog=SMCLMS_Dev. I
> > > think the contractor developed on his local machine and then deployed to the
> > > development server. I don't have RS on my machine. Will it hurt anything if
> > > I change the connection string to point to the development server?
> > >
> > > Thanks,
> > >
> > >
> > > --
> > > Dan D.|||Thanks.
--
Dan D.
"magendo_man" wrote:
> If you deploy the rdl from VS2003 it will automatically deploy the rds, if it
> hasn't been deployed before. The default is not to allow deployed rds to be
> overwritten.
> You can also deploy both the rds and rdl by uploading from the Report Manager.
> HTH,
> magendo_man
> "Dan D." wrote:
> > Thanks.
> >
> > If I create a new data source and a new report in the same solution, how do
> > I deploy it? If I don't use VS2003 to deploy do I take both the rds and rdl
> > files and upload them to the reports folder? Or is the rds file incorporated
> > in the rdl file and I just have to upload the rdl file?
> >
> > Thanks,
> > --
> > Dan D.
> >
> >
> > "Amarnath" wrote:
> >
> > > No problem check all the parameters and most importantly select the server
> > > and database and user / password. it should work..
> > >
> > > Amarnath
> > >
> > >
> > > "Dan D." wrote:
> > >
> > > > Using SS2000, RS2000, VS2003. I'm trying to make changes to some reports that
> > > > someone else created. I'm not very familiar with either RS or VS. When I go
> > > > into VS and load the solution (someone told me how to find the correct one)
> > > > and then in the solution explorer, I double click on the report that I want
> > > > to change. Then I click on the "Data" tab and I get this error:
> > > > "A connection cannot be made to the database. Set and test the connection
> > > > string. SQL Server does not exist or access denied." I double clicked on the
> > > > rds file under "Shared Data Sources" and looked on the General tab. This is
> > > > the connection string "data source=localhost;initial catalog=SMCLMS_Dev. I
> > > > think the contractor developed on his local machine and then deployed to the
> > > > development server. I don't have RS on my machine. Will it hurt anything if
> > > > I change the connection string to point to the development server?
> > > >
> > > > Thanks,
> > > >
> > > >
> > > > --
> > > > Dan D.|||I was able to make a change to the report and deploy it using the browser. I
didn't need to make a change to the rds file so I didn't need to redeploy it.
Thanks,
--
Dan D.
"Amarnath" wrote:
> If you have VS 2003 that's well and good since it does everything for you,
> when you just click "deploy". When you deploy all the details are stored in
> tables in an encrypted form so just copying is not the solution.. Other way
> is through scripts. using RS.exe
> Let me know if you require it or just go to sample.RSS at
> \Samples\Reporting Services\Script Samples and select publishsample report.
> Just see how to publish a report and you can change accordingly.
> Amarnath
>
> "Dan D." wrote:
> > Thanks.
> >
> > If I create a new data source and a new report in the same solution, how do
> > I deploy it? If I don't use VS2003 to deploy do I take both the rds and rdl
> > files and upload them to the reports folder? Or is the rds file incorporated
> > in the rdl file and I just have to upload the rdl file?
> >
> > Thanks,
> > --
> > Dan D.
> >
> >
> > "Amarnath" wrote:
> >
> > > No problem check all the parameters and most importantly select the server
> > > and database and user / password. it should work..
> > >
> > > Amarnath
> > >
> > >
> > > "Dan D." wrote:
> > >
> > > > Using SS2000, RS2000, VS2003. I'm trying to make changes to some reports that
> > > > someone else created. I'm not very familiar with either RS or VS. When I go
> > > > into VS and load the solution (someone told me how to find the correct one)
> > > > and then in the solution explorer, I double click on the report that I want
> > > > to change. Then I click on the "Data" tab and I get this error:
> > > > "A connection cannot be made to the database. Set and test the connection
> > > > string. SQL Server does not exist or access denied." I double clicked on the
> > > > rds file under "Shared Data Sources" and looked on the General tab. This is
> > > > the connection string "data source=localhost;initial catalog=SMCLMS_Dev. I
> > > > think the contractor developed on his local machine and then deployed to the
> > > > development server. I don't have RS on my machine. Will it hurt anything if
> > > > I change the connection string to point to the development server?
> > > >
> > > > Thanks,
> > > >
> > > >
> > > > --
> > > > Dan D.sql

problem of connection with sqlserver2005

Hello,

I installed sqlserver2005_express on my PC (localhost) and I try to execute a sql query with ASP.NET.

Here's my page :
Dim mySqlConnection as SqlConnection = new SqlConnection("server=JOE10155\SQLEXPRESS;Trusted_Connection=yes;UID=sa;PWD=xxxx;database=xxxx")
Dim mySqlDataAdapter as SqlDataAdapter = new SqlDataAdapter("SELECT * FROM Entreprise WHERE (EntrepriseNr =999)", mySqlConnection)
Dim myDataSet as DataSet = new DataSet()
mySqlDataAdapter.Fill(myDataSet,"Entreprise")

The problem is :
System.Data.SqlClient.SqlException: Autorisation SELECT refusée sur l'objet 'Entreprise', base de données 'xxxx', schéma dbo'.

if someone have an idea?

Thanks

PS : I use Microsoft SQL Server Management Studio Express.

Hi,

that is French? :-)

I'm not good with it, but sounds as if the user who you connect as (give the credentiuals into connection string) wouldn't have permissions to SELECT fromEntreprise table

Problem ODBC connection....

I have a porblem which windows 2000 couldn't connect to SQL server 2005 through ODBC. But I have no problem with the rest of my windows XP pro. Please help. thanksWhich error do you get ?

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de|||I have done the same step to connect to SQL through ODBC on windows XP pro. But I have 4 other PC which is run under windows 2000 that unable to connect the SQL server. It just counldn't find the server at all.|||

Hi GAN2006,

Like Jens asked, you'll need to post the exact error message that you're receiving. Also, providing your connection string and indicating which driver you're using (SQL Native client, MDAC) would be helpful. Please take a look at this guideline for insight on the type of information that'll make problem determination easier: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=362498&SiteID=1

Thanks,
Il-Sung.

|||

I think I have faced the same problem.

All you need to do is to install MDAC 2.8. This is because SQL 2000 connector in windows 2000 is not there or not working properly. Install MDAC 2.8 and it shall work. For windows xp, you dont have to because by nature it already have mdac 2.8 components.

Problem migrating from sql7 to sql2000 - connection failure

We have an inhouse app written in Delphi which connects to a local server
running SQL7. When we migrated the database to a server running SQL2000 we
ran into problems.
When a user uses the Delphi app to browse data, it seems ok, but when the
user insert records, the app responded "Connection failure".
In the application log of the event viewer, we noticed the following:
Error: 17805, Severity: 20, State: 3
Invalid buffer received from client.
I did a search on support.microsoft.com for this message. It seems there is
some information regarding this on some complicated cause which will be
addressed in service pack 4.
I wonder should I wait for service pack 4 to solve it, or is there something
I can do?LL
From Erland
The message indicates a protocol error in the dialog between client and
server. There are several possible causes for this. The most likely
causes are 1) network problems 2) bug in the client library.
"LL" <LL@.discussions.microsoft.com> wrote in message
news:8A487A41-DE7C-4A5A-B7B7-0397322AD79D@.microsoft.com...
> We have an inhouse app written in Delphi which connects to a local server
> running SQL7. When we migrated the database to a server running SQL2000 we
> ran into problems.
> When a user uses the Delphi app to browse data, it seems ok, but when the
> user insert records, the app responded "Connection failure".
> In the application log of the event viewer, we noticed the following:
> Error: 17805, Severity: 20, State: 3
> Invalid buffer received from client.
> I did a search on support.microsoft.com for this message. It seems there
is
> some information regarding this on some complicated cause which will be
> addressed in service pack 4.
> I wonder should I wait for service pack 4 to solve it, or is there
something
> I can do?|||I dont know how it relates to network problem, because the error condition
only happens when we use a user account to insert/change data via the app.
The only thing that i can say is that the sql 2000 database resides on the
domain controller server, whereas, before the sql 7 database resides on a
workgroup server. i will need to follow up with the programmer to see if
there exist some hardcoded machine name inside the app that causes the
failure.
As for 'bug in client library', i dont know why a failure only happens
during write. but it sounds like i can only try to get the programmer to
check the app or see if there are other compatible versions of delphi that
works with sql2000.
thanks for your reply anyways...
"Uri Dimant" wrote:
> LL
> From Erland
> The message indicates a protocol error in the dialog between client and
> server. There are several possible causes for this. The most likely
> causes are 1) network problems 2) bug in the client library.
>
> "LL" <LL@.discussions.microsoft.com> wrote in message
> news:8A487A41-DE7C-4A5A-B7B7-0397322AD79D@.microsoft.com...
> > We have an inhouse app written in Delphi which connects to a local server
> > running SQL7. When we migrated the database to a server running SQL2000 we
> > ran into problems.
> >
> > When a user uses the Delphi app to browse data, it seems ok, but when the
> > user insert records, the app responded "Connection failure".
> >
> > In the application log of the event viewer, we noticed the following:
> >
> > Error: 17805, Severity: 20, State: 3
> > Invalid buffer received from client.
> >
> > I did a search on support.microsoft.com for this message. It seems there
> is
> > some information regarding this on some complicated cause which will be
> > addressed in service pack 4.
> >
> > I wonder should I wait for service pack 4 to solve it, or is there
> something
> > I can do?
>
>|||Dear LL :
I also got this error when using delphi 7 to update or changing the
record. My database is also migrating from sql7 to sql2k, please send me
some information if you can solve this problem , tkx so much
George

Problem migrating from sql7 to sql2000 - connection failure

We have an inhouse app written in Delphi which connects to a local server
running SQL7. When we migrated the database to a server running SQL2000 we
ran into problems.
When a user uses the Delphi app to browse data, it seems ok, but when the
user insert records, the app responded "Connection failure".
In the application log of the event viewer, we noticed the following:
Error: 17805, Severity: 20, State: 3
Invalid buffer received from client.
I did a search on support.microsoft.com for this message. It seems there is
some information regarding this on some complicated cause which will be
addressed in service pack 4.
I wonder should I wait for service pack 4 to solve it, or is there something
I can do?
LL
From Erland
The message indicates a protocol error in the dialog between client and
server. There are several possible causes for this. The most likely
causes are 1) network problems 2) bug in the client library.
"LL" <LL@.discussions.microsoft.com> wrote in message
news:8A487A41-DE7C-4A5A-B7B7-0397322AD79D@.microsoft.com...
> We have an inhouse app written in Delphi which connects to a local server
> running SQL7. When we migrated the database to a server running SQL2000 we
> ran into problems.
> When a user uses the Delphi app to browse data, it seems ok, but when the
> user insert records, the app responded "Connection failure".
> In the application log of the event viewer, we noticed the following:
> Error: 17805, Severity: 20, State: 3
> Invalid buffer received from client.
> I did a search on support.microsoft.com for this message. It seems there
is
> some information regarding this on some complicated cause which will be
> addressed in service pack 4.
> I wonder should I wait for service pack 4 to solve it, or is there
something
> I can do?
|||I dont know how it relates to network problem, because the error condition
only happens when we use a user account to insert/change data via the app.
The only thing that i can say is that the sql 2000 database resides on the
domain controller server, whereas, before the sql 7 database resides on a
workgroup server. i will need to follow up with the programmer to see if
there exist some hardcoded machine name inside the app that causes the
failure.
As for 'bug in client library', i dont know why a failure only happens
during write. but it sounds like i can only try to get the programmer to
check the app or see if there are other compatible versions of delphi that
works with sql2000.
thanks for your reply anyways...
"Uri Dimant" wrote:

> LL
> From Erland
> The message indicates a protocol error in the dialog between client and
> server. There are several possible causes for this. The most likely
> causes are 1) network problems 2) bug in the client library.
>
> "LL" <LL@.discussions.microsoft.com> wrote in message
> news:8A487A41-DE7C-4A5A-B7B7-0397322AD79D@.microsoft.com...
> is
> something
>
>
|||Dear LL :
I also got this error when using delphi 7 to update or changing the
record. My database is also migrating from sql7 to sql2k, please send me
some information if you can solve this problem , tkx so much
George

Problem migrating from sql7 to sql2000 - connection failure

We have an inhouse app written in Delphi which connects to a local server
running SQL7. When we migrated the database to a server running SQL2000 we
ran into problems.
When a user uses the Delphi app to browse data, it seems ok, but when the
user insert records, the app responded "Connection failure".
In the application log of the event viewer, we noticed the following:
Error: 17805, Severity: 20, State: 3
Invalid buffer received from client.
I did a search on support.microsoft.com for this message. It seems there is
some information regarding this on some complicated cause which will be
addressed in service pack 4.
I wonder should I wait for service pack 4 to solve it, or is there something
I can do?LL
From Erland
The message indicates a protocol error in the dialog between client and
server. There are several possible causes for this. The most likely
causes are 1) network problems 2) bug in the client library.
"LL" <LL@.discussions.microsoft.com> wrote in message
news:8A487A41-DE7C-4A5A-B7B7-0397322AD79D@.microsoft.com...
> We have an inhouse app written in Delphi which connects to a local server
> running SQL7. When we migrated the database to a server running SQL2000 we
> ran into problems.
> When a user uses the Delphi app to browse data, it seems ok, but when the
> user insert records, the app responded "Connection failure".
> In the application log of the event viewer, we noticed the following:
> Error: 17805, Severity: 20, State: 3
> Invalid buffer received from client.
> I did a search on support.microsoft.com for this message. It seems there
is
> some information regarding this on some complicated cause which will be
> addressed in service pack 4.
> I wonder should I wait for service pack 4 to solve it, or is there
something
> I can do?|||I dont know how it relates to network problem, because the error condition
only happens when we use a user account to insert/change data via the app.
The only thing that i can say is that the sql 2000 database resides on the
domain controller server, whereas, before the sql 7 database resides on a
workgroup server. i will need to follow up with the programmer to see if
there exist some hardcoded machine name inside the app that causes the
failure.
As for 'bug in client library', i dont know why a failure only happens
during write. but it sounds like i can only try to get the programmer to
check the app or see if there are other compatible versions of delphi that
works with sql2000.
thanks for your reply anyways...
"Uri Dimant" wrote:

> LL
> From Erland
> The message indicates a protocol error in the dialog between client and
> server. There are several possible causes for this. The most likely
> causes are 1) network problems 2) bug in the client library.
>
> "LL" <LL@.discussions.microsoft.com> wrote in message
> news:8A487A41-DE7C-4A5A-B7B7-0397322AD79D@.microsoft.com...
> is
> something
>
>|||Dear LL :
I also got this error when using delphi 7 to update or changing the
record. My database is also migrating from sql7 to sql2k, please send me
some information if you can solve this problem , tkx so much
George

Problem Making Sql database Connection in Deployed Site

VWD 2005 Express. Visual Basic. Sql Server 2005. I am trying to establish a connection to a SQL database. The connection (and all other database reads and writes) work fine in debug and in "view in browser" from VWD. I am running the VWD on the same server that hosts the site. When on my server (Windows 2003 Server) under IIS, the connection attempt times out.

Below is the code that is failing (only on the server when deployed):

PrivateSharedSub OpenConn(ByVal cmdAs SqlCommand,ByVal SuccessAsBoolean)

Dim connAsNew SqlConnection(System.Configuration.ConfigurationManager.ConnectionStrings("GoodNews_IntranetConnectionString").ToString)

'The connection string resolves to ("Data Source=HQSERVER\HQSERVER;Initial Catalog=GoodNews_Intranet;Integrated Security=True"

Try

conn.Open()

cmd.Connection = conn

Success =True

Catch exAs Exception

Success =False

EndTry

EndSub

It would be great if you could post the error message that you are getting.

And in a hosted environment, it is advisable to protect your database by providing a username and password.

|||

That may be the ticket. The database does require windows authentication, so how may I make the connection (in vb code) providing a username and password? Perhaps when I am in debug, the sql calls use my windows login, however, when on the server, there is not password being passed?

|||

Please visitwww.connectionstrings.com to know the syntax for creating a connection string for your backend with user name and password.

If you think, this resolves your problem, please mark the post as "Answer". by this way we all know your issue is resolved

|||

Thank you. I found the answer on the page. I put the User Id and Password in the web.config file where the connection is defined. How can I ensure that this will not be readable when the web site is deployed?

|||

It won't be readable to a normal user, but for added security, if its not already in web.confing, then put it there. You can then use encryption to encrypt the connectionstring section (which is much easier than it sounds).

This might help:

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

|||

WEB.CONFIG file is a secure one. No one can read that file outside of your application. In other words, web.config can only be read by the pages within application.

every body uses the web.config to store connection strings and is safe so far.

read the following article to know more about web.config.

http://www.aspdev.org/articles/web.config/

also, please do not forget to mark my post as answer so that we will know for sure that your issue has been resolved.