Conflict procedures gone weird...

I am using SQLServer7 with SP4 merge replicating to PocketPC devices. Everything works fine EXCEPT conflict resolution...

After publishing I noticed that the conflict_tablename tables and sp_cft_ storedprocedures didn't get created. So I picked up the .cft files created in the ReplData/unc/... directory and ran them myself through Query Analyser.

Now the conflict resolution procedure are called when a conflict occurs BUT they return the following errors....

Message: The process could not log conflict information
Source: Merge Replication Provider

followed by...

Message: {[call sp_cft_59....](?,?,?,?,0x00)}
Source: ServerMachineName

followed by...

Message: Too many parameter arguments were supplied for procedure sp_cft_59...
Source: ServerMachineName

Ok, it seems the addition of the 0x00 in the call is incorrect so can someone please help me out with this. Please note that I'm only Enterprise Manager proficient in SQLServer.

Thank you,
jhAwww please!! Someone out there must know something about this. Or can anybody point me at another resource that might be useful?

Thnx

configuring a publishing and distribution wizard

I am having a problem with configuring publiushed and distributor .i am
selecting the option to make the local server its own distibutor.
After competing the task, I am getting an enterprise manager error stating
that
Sql server manager could not configure the "SQLSERVER' as distibutore for
"SQLSERVER'
error 18483 could not connect th the server 'SQLSERVER' becouse
Distibutor_admin' is ot defined as a remote login at the server...
Need help!!
what happens if you do a select @.@.servername on the local server?
"Sam" <Sam@.discussions.microsoft.com> wrote in message
news:7B19D769-EFF7-4DB6-A2F0-9CBEE75BCC6D@.microsoft.com...
>I am having a problem with configuring publiushed and distributor .i am
> selecting the option to make the local server its own distibutor.
> After competing the task, I am getting an enterprise manager error stating
> that
> Sql server manager could not configure the "SQLSERVER' as distibutore for
> "SQLSERVER'
> error 18483 could not connect th the server 'SQLSERVER' becouse
> Distibutor_admin' is ot defined as a remote login at the server...
> Need help!!
|||As Hilary is alluding to, the @.@.servername valiable is probably incorrect.
If this is the case, you will need to run the sp_addserver procedure with
the local parameter to set it correctly. You may also need to run
sp_dropserver as well.
After doing this, you will need to stop and restart SQL Server for the
change to take effect.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Hi Guys,
I have tried the sp_addserver and sp_dropserver procedure, restarted the
server and i still have the sa me issue
"Rand Boyd [MSFT]" wrote:

> As Hilary is alluding to, the @.@.servername valiable is probably incorrect.
> If this is the case, you will need to run the sp_addserver procedure with
> the local parameter to set it correctly. You may also need to run
> sp_dropserver as well.
> After doing this, you will need to stop and restart SQL Server for the
> change to take effect.
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>
|||what happens when you issue a select @.@.servername now
Hilary Cotter
Looking for a SQL Server replication book?
Now available for purchase at:
http://www.nwsu.com/0974973602.html
"Sam" <Sam@.discussions.microsoft.com> wrote in message
news:E443C6F1-24E8-4074-98CD-388AA6529D0E@.microsoft.com...[vbcol=seagreen]
> Hi Guys,
> I have tried the sp_addserver and sp_dropserver procedure, restarted the
> server and i still have the sa me issue
>
> "Rand Boyd [MSFT]" wrote:
incorrect.[vbcol=seagreen]
with[vbcol=seagreen]
rights.[vbcol=seagreen]