Dropping the publication doesn't have to delete any article. can you tell us wich article is that?

execute sp_helptrigger tblDelete.

Check the owner of the trigger.

Also check that the trigger is enabled, and you could also add some prints inside the trigger to check if it is running

...

to drop a publication, first delete all the subscription...

run sp_helpmergesubscription from the published db. Then drop those subscriptions with sp_dropmergesubscription.

Once all the subscriptions have been deleted, drop the publication with...

I don't understand...are you trying to remove the table that was published?

Droping replicacion is just deleting the records in all the system tables referencing that publication or configuration, not its...

You might consider placing the distributor on a separate server, or even in the subscriber.

But to minimize workload, you shoudn't create the distributor on the publisher.

If you want to fix the problem, if you still have the nominal (810046) in the publisher, try inserting that value into the subscriber with the error. If you deleted...

I've compressed snapshot files into cab files letting the snapshot agent to do it, but also didn't compress the snapshot and then manually compressed all the snapshot files with rar...

That login is created during creation of the distributor. You should first, reconfigure your distributor and drop and recreate all your publications if any.

Instead of searching the db, you should check what process in consuming the sql resources, and then if necesary find out from what db that process is connected.

You can run...

Yes you add Andy's parameters on the second step of the log reader agent job... or you can also run the log reader from the command line with the logread.exe...

If you have a slow link between the databases, running queries to know the differences can be too slow. So you can export to files the tables that you want...

You can run profiler to check what is executing in the server or in a specific database.

You should also run sp_who2 to know what proceses are running and with dbcc...

Is the MSDTC service started on the remote server?

For me it is always better to use the stored procedures to do anything with replication.

The sp sp_dropMergeSubscription must be run on the publisher DB on the publisher.

If you...

Are you using Transactional replication?

It seems like a problem in your db, do you have any option in dbcc to try to fix the db, like REPAIR_REBUILD in 6.5?