The information in this article applies to:
Moderate: Requires basic macro, coding, and interoperability skills. This article applies only to a Microsoft Access project (.adp). SYMPTOMSIf your Access Workflow Designer server computer hosts two or more solutions and one or more of the solution databases is either renamed or deleted, the database becomes suspect in Microsoft SQL Server. Because the database is suspect, when you try to synchronize the user list for any of the hosted solution databases, the following error message appears:
CAUSEWhen the Access Workflow Designer attempts to synchronize the user list for a solution database, it cycles through and opens all databases stored on the server. If one or more databases are damaged, when the Access Workflow Designer opens the damaged database, no databases can be synchronized. RESOLUTIONEither restore and re-attach a copy of the suspect database (if it was deleted), or rename the .mdf and .ldf files back to their original file names. After the database appears as it did before all Microsoft SQL Server services were stopped, you can synchronize the user list for all solution databases. MORE INFORMATIONSteps to Reproduce Behavior
Additional query words: prb userlist exception synchronizeuserlist cannot open database requested
Keywords : kbdta modWFDesigner |
Last Reviewed: November 23, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |