Re: merge repl error invalid parameter

as written this works for me

-Publisher [SQL1] -PublisherDB [CENTRALDB] -Publication
[CENTRAL_BR17] -Subscriber [BR17] -SubscriberDB [BR17Main] -Distributor
[SQL1] -DistributorSecurityMode 1 -Output "c:\BR17.txt" -OutputVerboseLevel
2

Can you try a shorted path name with no spaces?

--
Hilary Cotter

Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html

Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com



"jaylou" <jaylou@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3DC3CB47-2B22-46F1-AD3B-8C87A82AD3DC@xxxxxxxxxxxxxxxx
I have been having a weird situation with this branches replication lately.
For some reason it was failing due to an invalid object on the Branches
database. I added the objects to the data base and the sync worked fine,
but
the step still failed due to "Message The parameter is incorrect. The
step
failed." (it would be nice to know which is incorrect, but that may be
asking
for too much )

I checked the ObjectId and Name in Sysjobs and they are correct
I have no errors in my output file nor do I see this parameter issue.

Here is a copy of my step that is failing. Can anyone see anything that
may
be causing this parameter issue? I also included the extra params from my
ouput file below.

-Publisher [SQL1] -PublisherDB [CENTRALDB] -Publication [CENTRAL_BR17]
-Subscriber [BR17] -SubscriberDB [BR17Main] -Distributor [SQL1]
-DistributorSecurityMode 1 -Output "E:\Microsoft SQL
Server\MSSQL\ReplStepLogs\BR17.txt" -OutputVerboseLevel 2

-XSTEPID 2
-XSUBSYSTEM Merge
-XSERVER SQL1
-XCMDLINE 0
-XCancelEventHandle 000004A4
-XParentProcessHandle 0000049C

Any help or ideas of where to look would be greatly appreciated.
Thanks,
John


.

Relevant Pages

  • Re: c doubt
    ... but the condition is failing always even array size is greater than ... zero. ... The code you have posted does not compile. ... What you have posted here is so incorrect in so many ways that it ...
    (comp.lang.c)
  • Re: Time and Date
    ... Your CMOS/BIOS date and time are incorrect. ... battery is failing. ...
    (microsoft.public.windowsxp.general)
  • GetCommTimeout fails with GetLastError = 87
    ... I have some code that is failing, but I do not know why. ... GetCommTimeouts fails. ... COMMTIMEOUTS address. ... Why would a parameter be incorrect? ...
    (microsoft.public.win32.programmer.kernel)