Error 14058: The subscription already exists

Hi,
I've got the error in the Subject when I tried to delete and recreate
manually a pull subscription to a publication.
How can I delete defenitely the subscription from that database?
Thank you.
get your publication name and issue the following command in your
subscription database:
sp_droppullsubscription @.publisher = 'publisher' , @.publisher_db =
'publisher_db' ,[ @.publication = 'publication'
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
"Siu" <Siu@.discussions.microsoft.com> wrote in message
news:7957B486-16ED-498A-BAFC-2755E49555E1@.microsoft.com...
> Hi,
> I've got the error in the Subject when I tried to delete and recreate
> manually a pull subscription to a publication.
> How can I delete defenitely the subscription from that database?
> Thank you.
|||Hi Hilary,
thanks for your answer, but your code still gives the message that the
subscription doesn't exist... I'm also sure that I've written correctly all
the parameter, namely the publisher name, publisher db and the publication
name.
Do you think that there is another problem?
"Hilary Cotter" wrote:

> get your publication name and issue the following command in your
> subscription database:
> sp_droppullsubscription @.publisher = 'publisher' , @.publisher_db =
> 'publisher_db' ,[ @.publication = 'publication'
>
> --
> 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
> "Siu" <Siu@.discussions.microsoft.com> wrote in message
> news:7957B486-16ED-498A-BAFC-2755E49555E1@.microsoft.com...
>
>
|||Hi Hilary,
now I solved the problem: I had to delete the pull subscription manually
from the Publisher database.
I have another question: when I started the syncronitation, I got the
following error:
"The process could not connect to Disctributor 'MYDISTRIBUTOR'. Login failed
for user'
How can I discover which USER NAME failed the login?
"Hilary Cotter" wrote:

> get your publication name and issue the following command in your
> subscription database:
> sp_droppullsubscription @.publisher = 'publisher' , @.publisher_db =
> 'publisher_db' ,[ @.publication = 'publication'
>
> --
> 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
> "Siu" <Siu@.discussions.microsoft.com> wrote in message
> news:7957B486-16ED-498A-BAFC-2755E49555E1@.microsoft.com...
>
>

Error 0: Syntax error or Access violation

Hi,
I'm writing a stored procedure and when I click on the Check Syntax button its giving me the error in the subject. I'm not really sure whats wrong with this. Here is my Stored Procedure code. Any help wud be appreciated.

CREATE PROC CabsSchedule_Insert
{
@.JulianDatesmallint,
@.SiteCodesmallint,
@.CalendarDaysmallint,
@.BillPeriodsmallint,
@.WorkDaysmallint,
@.CalDayBillRcvd varchar(30),
@.Remarksvarchar(50)
}
 AS
INSERT INTO CabsSchedule
(JulianDate, SiteCode, CalendarDay, BillPeriod, WorkDay, CalDayBillRcvd, Remarks)
VALUES
(@.JulianDate, @.SiteCode, @.CalendarDay, @.BillPeriod, @.WorkDay, @.CalDayBillRcvd, @.Remarks)

Thanks,check the datatypes of the columns and the values that you are trying to put into them. other than that i dont see anything else. you might also want tocheck this if you havent already.

hth|||Hi Dinakar,
Thanks for the reply. I got this thing to work. I'm not really sure how SQL Server behaves if I had an extra space inbetween my proc but removing the flower brackets ({) and
adjusting the CabsSchedule in the insert statement right beside the field names did the trick.

CREATE PROC CabsSchedule_Insert
@.JulianDatesmallint,
@.SiteCodesmallint,
@.CalendarDaysmallint,
@.BillPeriodsmallint,
@.WorkDaysmallint,
@.CalDayBillRcvd varchar(30),
@.Remarksvarchar(50)
 AS
INSERT INTO
CabsSchedule(JulianDate, SiteCode, CalendarDay, BillPeriod, WorkDay, CalDayBillRcvd, Remarks)
VALUES
(@.JulianDate, @.SiteCode, @.CalendarDay, @.BillPeriod, @.WorkDay, @.CalDayBillRcvd, @.Remarks)

Thanks again!