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 migrating db

I have an access database project that is having problems
since I have migrated the database it connects to. It
connects fine, but all of the server objects show (dbo)
after them. I think the (dbo) issue is related to the
sql user account setup. The user account no longer maps
to a domain account as it had been with the previous
server.
Here is some background information about the migration
and installation of sql server:
I am trying to migrate a database to a new server that is
running windows 2003 and sql server 2000 sp3. I have
copied a backup from the old server to the new server,
and performed a restore. However, when I restore the
database, the users in the database no longer have the
login name (the domain account associated with the user)
mapped. I can delete the accounts and recreate them, all
except the dbo user, which has a lot of objects owned by
it. Is there a way to remap this dbo user to the domain
account that I previously had it mapped to?
During the installation of sql server 2k, I do get an
error stating that sql server sp2 and less is not
supported on the version of windows I am running. I
doubt this is the problem, because I have updated it to
sp3.
Any help you can provide would be greatly appreciated.
Thanks,
Jason
Hi
dbo is the database owner if you do
sp_helpdb dbname
Then it will show the database owner. In general it is usually better to
have dbo as the owner of the objects in the database.
If you want to change the database owner look up the stored procedure
sp_changedbowner in Books Online.
For granting access to the database server check out sp_grantlogin and for
the database see sp_grantdbaccess. It is usually better to grant access to
Windows Groups (which your users belong to) rather than to individual
accounts.
The error message regarding SP3 is normal, upgrading straight away to SP3
means that you will be ok.
John
"jason" <anonymous@.discussions.microsoft.com> wrote in message
news:d9a701c43abb$9b48c770$a601280a@.phx.gbl...
> I have an access database project that is having problems
> since I have migrated the database it connects to. It
> connects fine, but all of the server objects show (dbo)
> after them. I think the (dbo) issue is related to the
> sql user account setup. The user account no longer maps
> to a domain account as it had been with the previous
> server.
> Here is some background information about the migration
> and installation of sql server:
> I am trying to migrate a database to a new server that is
> running windows 2003 and sql server 2000 sp3. I have
> copied a backup from the old server to the new server,
> and performed a restore. However, when I restore the
> database, the users in the database no longer have the
> login name (the domain account associated with the user)
> mapped. I can delete the accounts and recreate them, all
> except the dbo user, which has a lot of objects owned by
> it. Is there a way to remap this dbo user to the domain
> account that I previously had it mapped to?
> During the installation of sql server 2k, I do get an
> error stating that sql server sp2 and less is not
> supported on the version of windows I am running. I
> doubt this is the problem, because I have updated it to
> sp3.
> Any help you can provide would be greatly appreciated.
> Thanks,
> Jason

problem migrating db

I have an access database project that is having problems
since I have migrated the database it connects to. It
connects fine, but all of the server objects show (dbo)
after them. I think the (dbo) issue is related to the
sql user account setup. The user account no longer maps
to a domain account as it had been with the previous
server.
Here is some background information about the migration
and installation of sql server:
I am trying to migrate a database to a new server that is
running windows 2003 and sql server 2000 sp3. I have
copied a backup from the old server to the new server,
and performed a restore. However, when I restore the
database, the users in the database no longer have the
login name (the domain account associated with the user)
mapped. I can delete the accounts and recreate them, all
except the dbo user, which has a lot of objects owned by
it. Is there a way to remap this dbo user to the domain
account that I previously had it mapped to?
During the installation of sql server 2k, I do get an
error stating that sql server sp2 and less is not
supported on the version of windows I am running. I
doubt this is the problem, because I have updated it to
sp3.
Any help you can provide would be greatly appreciated.
Thanks,
JasonHi
dbo is the database owner if you do
sp_helpdb dbname
Then it will show the database owner. In general it is usually better to
have dbo as the owner of the objects in the database.
If you want to change the database owner look up the stored procedure
sp_changedbowner in Books Online.
For granting access to the database server check out sp_grantlogin and for
the database see sp_grantdbaccess. It is usually better to grant access to
Windows Groups (which your users belong to) rather than to individual
accounts.
The error message regarding SP3 is normal, upgrading straight away to SP3
means that you will be ok.
John
"jason" <anonymous@.discussions.microsoft.com> wrote in message
news:d9a701c43abb$9b48c770$a601280a@.phx.gbl...
> I have an access database project that is having problems
> since I have migrated the database it connects to. It
> connects fine, but all of the server objects show (dbo)
> after them. I think the (dbo) issue is related to the
> sql user account setup. The user account no longer maps
> to a domain account as it had been with the previous
> server.
> Here is some background information about the migration
> and installation of sql server:
> I am trying to migrate a database to a new server that is
> running windows 2003 and sql server 2000 sp3. I have
> copied a backup from the old server to the new server,
> and performed a restore. However, when I restore the
> database, the users in the database no longer have the
> login name (the domain account associated with the user)
> mapped. I can delete the accounts and recreate them, all
> except the dbo user, which has a lot of objects owned by
> it. Is there a way to remap this dbo user to the domain
> account that I previously had it mapped to?
> During the installation of sql server 2k, I do get an
> error stating that sql server sp2 and less is not
> supported on the version of windows I am running. I
> doubt this is the problem, because I have updated it to
> sp3.
> Any help you can provide would be greatly appreciated.
> Thanks,
> Jason

problem migrating db

I have an access database project that is having problems
since I have migrated the database it connects to. It
connects fine, but all of the server objects show (dbo)
after them. I think the (dbo) issue is related to the
sql user account setup. The user account no longer maps
to a domain account as it had been with the previous
server.
Here is some background information about the migration
and installation of sql server:
I am trying to migrate a database to a new server that is
running windows 2003 and sql server 2000 sp3. I have
copied a backup from the old server to the new server,
and performed a restore. However, when I restore the
database, the users in the database no longer have the
login name (the domain account associated with the user)
mapped. I can delete the accounts and recreate them, all
except the dbo user, which has a lot of objects owned by
it. Is there a way to remap this dbo user to the domain
account that I previously had it mapped to?
During the installation of sql server 2k, I do get an
error stating that sql server sp2 and less is not
supported on the version of windows I am running. I
doubt this is the problem, because I have updated it to
sp3.
Any help you can provide would be greatly appreciated.
Thanks,
JasonHi
dbo is the database owner if you do
sp_helpdb dbname
Then it will show the database owner. In general it is usually better to
have dbo as the owner of the objects in the database.
If you want to change the database owner look up the stored procedure
sp_changedbowner in Books Online.
For granting access to the database server check out sp_grantlogin and for
the database see sp_grantdbaccess. It is usually better to grant access to
Windows Groups (which your users belong to) rather than to individual
accounts.
The error message regarding SP3 is normal, upgrading straight away to SP3
means that you will be ok.
John
"jason" <anonymous@.discussions.microsoft.com> wrote in message
news:d9a701c43abb$9b48c770$a601280a@.phx.gbl...
> I have an access database project that is having problems
> since I have migrated the database it connects to. It
> connects fine, but all of the server objects show (dbo)
> after them. I think the (dbo) issue is related to the
> sql user account setup. The user account no longer maps
> to a domain account as it had been with the previous
> server.
> Here is some background information about the migration
> and installation of sql server:
> I am trying to migrate a database to a new server that is
> running windows 2003 and sql server 2000 sp3. I have
> copied a backup from the old server to the new server,
> and performed a restore. However, when I restore the
> database, the users in the database no longer have the
> login name (the domain account associated with the user)
> mapped. I can delete the accounts and recreate them, all
> except the dbo user, which has a lot of objects owned by
> it. Is there a way to remap this dbo user to the domain
> account that I previously had it mapped to?
> During the installation of sql server 2k, I do get an
> error stating that sql server sp2 and less is not
> supported on the version of windows I am running. I
> doubt this is the problem, because I have updated it to
> sp3.
> Any help you can provide would be greatly appreciated.
> Thanks,
> Jason