Did you check if the account with which the Linked server is set up is not locking out periodically for some reason causing you this error? The problem getting resolved...

Did you check the 'protection level' on the package? I had faced a similar error earlier and it was resolved after I changed the protection level from 'EncryptAllWithPassword' to 'DontSaveSensitive'.

We always do a silent install of the SQL Server instance.

Hope this helps!!

To be run in Cmd prompt (the TempDB, MDF and LDF directories have to be modified)

-------------------------------------------------------------------

Setup.exe /SQLSVCPASSWORD="*****" /AGTSVCPASSWORD="*****"...

Try "update distribution..MSsubscriptions set status=2 where subscriber_db='your DB' ".

The blog here (http://blogs.imeta.co.uk/jwatson/archive/2008/09/22/error-in-replicationsubscriptions-have-been-marked-inactive-and-must-be.aspx) says its is absolutely safe to update the status, I havent personally tried it ever though.

You might need to enable the XP_CMDSHELL option using this:

sp_configure 'xp_cmdshell',1

reconfigure with override

But, be aware that enabling this might make your SQL server vulnerable and if you are using it...

Hi,

As the Tempdb is in simple recovery, the log should be truncated as soon as it reaches 70%, so probably there are open transactions in the database which cannot be...