PRB: Expired Subscription Cleanup Agent Fails if the First Published Database is Deleted (296792)
The information in this article applies to:
- Microsoft SQL Server 2000 (all editions)
- Microsoft SQL Server 7.0
This article was previously published under Q296792 SYMPTOMS
If the first database that is published is then unpublished and dropped, and there are databases that are published, the Expired Subscription Cleanup Agent fails and the following error message occurs:
Unable to connect to SQL Server '(local)'. The step failed.
The error is also reported in the SQLServerAgent error log:
[298] SQLServer Error: 4060, Cannot open database requested in login '%.*ls'. Login fails. [SQLSTATE 42000]
CAUSE
The Expired Subscription Cleanup job executes the sp_expired_subscription_cleanup stored procedure within the context of the first database that was published. The sp_expired_subscription_cleanup stored procedure tries to run under the context of the database that was dropped but the procedure fails.
WORKAROUND
To work around this problem, follow these steps:
- Open the SQL Enterprise Manager, and then navigate to the server that has the failed job.
- Open the Miscellaneous Agents folder under the Replication Monitor folder. In the details window right-click the Expired Subscription Cleanup Agent, and then click Agent Properties.
- To open the edit job step window, click the Steps tab, and then double-click the Run agent step.
- Under the database option, you will see the first database (in alphabetical order) to be the database context under which the agent executes the stored procedure.
- Select an existing database (preferably choose the master), and then click OK.
- Close all the open windows. Click OK, and then start the agent. The agent now runs successfully.
| Modification Type: | Major | Last Reviewed: | 10/16/2003 |
|---|
| Keywords: | kbCodeSnippet kbprb KB296792 |
|---|
|