Error when trying to update

Hi All
I get this error when i open a specific table from enterprise manager and
try to update values in it.
Data has changed since the results pane was last updated. Do you want to
save your changes now?
Click Yes to save your chnages and update the database.
Click No to discard your changes and refresh the results pane.
Click Cancel to continue editing.
If i click Yes which is of course what i wnated to do from the begining i
get this error:
Row cannot be located for updating.Some values may have been changed since
it was last Read.
So i was wonderring if anybody can give me some help with that.
Thanks in Advance
Naderseems like someone else already made a change to your data or that you are
trying to make a change to a key value that is used by em to locate the
record you want to update
Regards,
Dandy Weyn
MCSE, MCSA, MCDBA, MCT
www.dandyman.net
"Nader Galal" <ngalal@.health-insights.com> wrote in message
news:uNxO%23CD1DHA.3224@.tk2msftngp13.phx.gbl...

quote:

---

> Hi All
> I get this error when i open a specific table from enterprise manager and
> try to update values in it.
> Data has changed since the results pane was last updated. Do you want to
> save your changes now?
> Click Yes to save your chnages and update the database.
> Click No to discard your changes and refresh the results pane.
> Click Cancel to continue editing.
> If i click Yes which is of course what i wnated to do from the begining i
> get this error:
> Row cannot be located for updating.Some values may have been changed since
> it was last Read.
> So i was wonderring if anybody can give me some help with that.
> Thanks in Advance
> Nader
>

---

sql

Error when starting Incremental Population

Hi all
I have a very large FT catalog on a table.
I have tried to initiate an incremental population
Exec sp_fulltext_catalog 'FT_PATCLAIMS','start_incremental'
and I got the following error :
"Execution of a full-text operation failed. The Gatherer
is shutting down."
I have found no reference to this error on the microsof
site. Has anyone seen this problem before. I would hate to
have to recreate this catalog. It can take a number of
weeks !!!
Thanks
Michael.
Are there any error messages logged in the event log from MSSearch or mssci?
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
|||We had the same issue, it was solved by restarting the 'Microsoft Search'
service.
Cheers
Paul Bell,
DBA UnisysWest
Perth, Western Australia.
"Hilary Cotter" wrote:

> Are there any error messages logged in the event log from MSSearch or mssci?
>
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
|||Paul,
What issue was that? What error did you get that was resolved by just
restarting the 'Microsoft Search' service?
Thanks,
John
"Paul Bell" <Paul Bell@.discussions.microsoft.com> wrote in message
news:BC409C32-C77E-4CBC-9BEF-CEC58E6A79BB@.microsoft.com...[vbcol=seagreen]
> We had the same issue, it was solved by restarting the 'Microsoft Search'
> service.
> Cheers
> Paul Bell,
> DBA UnisysWest
> Perth, Western Australia.
> "Hilary Cotter" wrote:
mssci?[vbcol=seagreen]

Error when running Agent in Merge Replication!

Hi All:
I am trying to setup a Merge Replication over Internet. Snapshot runs
successfully, but when it tries to run sycronize the data for ther first
time, it gives the following error in the end:
The Subscription to Publication 'xxxx' is invalid
'xxxx' is the Database Name
The connectivity to the remote DB is working.
One of the reasons for this swich I found was the the remote server's name
was changed after SQL server was installed. Therefore the old name was
dropeed b y using these:
sp_dropserver <server name>
go
sp_addserver <new server name> , LOCAL
go
After doing this, we still get the same message "The Subscription to
Publication 'xxxx' is invalid"
Please suggest the remedy for this.
Thanks,
Anukul
anukul,
Just for grins, check that the publisher is aware of the new server name. If not you can either drop the subscription in both places and re-create or alter the subscription in both places to utilize the new machine name.
Give it a shot. Worst case it doesn't work...|||If you changed the server name after configuring the Subscriber, the
Publisher doesn't know about the new server name. You need to drop and
recreate the subscription at the Subscriber and re-register the Subscriber
with the Publisher, using the following stored procedures:
? sp_dropmergepullsubscription at the Subscriber (only if the Merge Agent
runs at the Subscriber, a pull subscription).
? sp_dropmergesubscription at the Publisher.
? sp_dropsubscriber at the Publisher.
You should also be able to do this from Enterprise Manager.
Then you must re-register the Subscriber using sp_addsubscriber or (from
Enterprise Manager) and recreate the subscription using either Enterprise
Manager or executing sp_addmergesubscription at the Publisher and
sp_addmergepullsubscription (only if the Merge Agent runs at the Subscriber,
a pull subscription).
Best wishes,
Glenn Gailey
SQL Server User Education
This posting is provided "AS IS" with no warranties, and confers no rights.
"Anukul" wrote:

> Hi All:
> I am trying to setup a Merge Replication over Internet. Snapshot runs
> successfully, but when it tries to run sycronize the data for ther first
> time, it gives the following error in the end:
> The Subscription to Publication 'xxxx' is invalid
> 'xxxx' is the Database Name
> The connectivity to the remote DB is working.
> One of the reasons for this swich I found was the the remote server's name
> was changed after SQL server was installed. Therefore the old name was
> dropeed b y using these:
> sp_dropserver <server name>
> go
> sp_addserver <new server name> , LOCAL
> go
> After doing this, we still get the same message "The Subscription to
> Publication 'xxxx' is invalid"
> Please suggest the remedy for this.
> Thanks,
> Anukul
>
>

Error trying to connect

Hello all
I am getting an error 8198 when trying to replicate from one server. It
says Could not obtain informaion about Windows NT user/group and username
problem is the user it cannot obtain information about does not exist on
either server. What else can cause this error
Warren,
as this is a validation issue, the most likely issue is the job owner - pls
try changing the job owner to sa.
The other possibility is the sql server agent account. Please make sure that
the sql server agent is run by a windows account that is in the sysadmin
role on each server.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)