Corrupted table causes problems

Hi there;
I have a very strange problem. We are running merge replication for a while
and it just stopped working overnight. I am no longer able to create a
snapshot.It stops with the message: An exception occured in the Snapshot
subsystem.
I browsed the newsgroup and someone suggested to run the snapshot from the
commandline. I did that and it run halfway through und terminated with the
message: Column S1Taxvadue4 not found. Which is correct there is no such
column in the database, it is called S1Taxvalue4!
Further investigation revealed that one columns in on of the conflict_...
has a wrong name. Don't ask me why? Well I tried open the table in design
mode to change the name. I am getting the message:
Table 'conflict_...' could not be loaded.
ODBC Error: Cannot insert the value NULL into column'', table '', column
does not allow nulls. Insert fails
Further investigation of the entries in sysobject revealed that this
particular column has NULL in the column usertype. All other columns of this
table have the value 24 in there.
Any ideas on this?
Thomas BornWe are running SQL Server 2000 with SP3 installed on a Windows 2000 Server
machine.
"Thomas Born" <thomas.born@.setac.net.au> wrote in message
news:%23%23gPUB3rDHA.2432@.TK2MSFTNGP10.phx.gbl...
> Hi there;
> I have a very strange problem. We are running merge replication for a
while
> and it just stopped working overnight. I am no longer able to create a
> snapshot.It stops with the message: An exception occured in the Snapshot
> subsystem.
> I browsed the newsgroup and someone suggested to run the snapshot from the
> commandline. I did that and it run halfway through und terminated with the
> message: Column S1Taxvadue4 not found. Which is correct there is no such
> column in the database, it is called S1Taxvalue4!
>
> Further investigation revealed that one columns in on of the conflict_...
> has a wrong name. Don't ask me why? Well I tried open the table in design
> mode to change the name. I am getting the message:
> Table 'conflict_...' could not be loaded.
> ODBC Error: Cannot insert the value NULL into column'', table '', column
> does not allow nulls. Insert fails
> Further investigation of the entries in sysobject revealed that this
> particular column has NULL in the column usertype. All other columns of
this
> table have the value 24 in there.
> Any ideas on this?
> Thomas Born
>