Invalid Descriptor Index

Hi,
I have setup snapshot pull replication between SQL2000 (publisher) and
MSDE2000 (subscriber).
The following error "Invalid Descriptor Index" is occuring on the
subscriber. Would someone please tell me what this error means and how to
get around it?
Thanks
reapply sp3 on the subscriber.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"mm" <postto@.news.com> wrote in message
news:u8luytqlEHA.2492@.TK2MSFTNGP15.phx.gbl...
> Hi,
> I have setup snapshot pull replication between SQL2000 (publisher) and
> MSDE2000 (subscriber).
> The following error "Invalid Descriptor Index" is occuring on the
> subscriber. Would someone please tell me what this error means and how to
> get around it?
> Thanks
>

Invalid column name 'rowguiedcol' - error number 207

"The process could not deliver the snapshot to the Subscriber"
I added a new database to the same server as the publisher and distributor.
The error ocurred when pushing a new subscription to it.
I did indicate that the subscriber already has the schema and data.
Any ideas for correcting?
thanks,
bob
Sounds like the table you are replicating to has an extra column in it which
is not in the publisher. Look for a column called rowguidcol and delete it.
If you get an error message complaining that this table is published for
replication or a similar message, verify that this table is not published,
or published to.
If it is you might have to do the following:
exec sp_configure N'allow updates', 1
go
reconfigure with override
go
UPDATE syscolumns set colstat = colstat & ~4096 WHERE colstat &4096 <>0
GO
UPDATE sysobjects set replinfo=0
GO
and then issue a sp_MSunmarkreplinfo against the problem table
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Robert A. DiFrancesco" <bob.difrancesco@.comcash.com> wrote in message
news:umf1ACevEHA.2520@.TK2MSFTNGP15.phx.gbl...
> "The process could not deliver the snapshot to the Subscriber"
> I added a new database to the same server as the publisher and
distributor.
> The error ocurred when pushing a new subscription to it.
> I did indicate that the subscriber already has the schema and data.
> Any ideas for correcting?
> thanks,
> bob
>

'Invalid Column Name' on initial snapshot

Building a second merge publication from a db, I'm getting an error 'Invalid
Column Name XXXXX' on gernerating the initial snapshot. The column
definitely exists. Anyone seen this behaviour before and maybe offer some
guidance?
Looks like this issue may be fixed in SP4
http://support.microsoft.com/kb/821535
"Tony Toker" <xyzzy@.identic.co.uk> wrote in message
news:crdj1r$rn3$1$8302bc10@.news.demon.co.uk...
> Building a second merge publication from a db, I'm getting an error
'Invalid
> Column Name XXXXX' on gernerating the initial snapshot. The column
> definitely exists. Anyone seen this behaviour before and maybe offer some
> guidance?
>
>
|||Thanks again for the help Paul, looks like we were posting simultaneously.
"Tony Toker" <xyzzy@.identic.co.uk> wrote in message
news:crduu6$f5i$1$830fa795@.news.demon.co.uk...[vbcol=seagreen]
> Looks like this issue may be fixed in SP4
> http://support.microsoft.com/kb/821535
>
>
> "Tony Toker" <xyzzy@.identic.co.uk> wrote in message
> news:crdj1r$rn3$1$8302bc10@.news.demon.co.uk...
> 'Invalid
some
>

invalid cab file after snapshot via FTP

I was able to successfuly retrieve a snapshot via FTP but the subscriber says
the snapshot .cab within the folder is invalid. What would make the file
invalid?
Jeffrey, this looks rather strange indeed. Which version of SQL server are
you running? Is the cab file marked read-only by any chance? Can you browse
the content of snapshot.cab directly in Explorer? Were there any strange
error messages in the snapshot agent history table? Does the problem go away
if you regenerate the snapshot?
-Raymond
"Jeffrey K. Ericson" wrote:

> I was able to successfuly retrieve a snapshot via FTP but the subscriber says
> the snapshot .cab within the folder is invalid. What would make the file
> invalid?