Troubleshooting

This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.

This topic provides information to help you avoid or resolve the most common errors and issues you may encounter when using Microsoft Office Developer Microsoft Access Workflow Designer for Microsoft SQL Server™ tools.

In addition to the tools provided, team solutions and the Access Workflow Designer tools are used in conjunction with Microsoft Windows NT®, Access, SQL Server, and a Microsoft FrontPage® Web site. Because of these dependencies, effective troubleshooting involves isolating where the problem exists. You may want to consult the documentation for additional components.

This section is divided into the following topics:

• Setup and Server Issues

• Database Issues

• Workflow Process and Scripting Issues

• Offline Replication Issues

• Security and Permissions Issues

• Error Messages

Be sure to check the Access Workflow Designer server and developer tools Readmes and the Microsoft Office Developer Web site (http://msdn.Microsoft.com/officedev) for late-breaking information about the product.

As an additional troubleshooting resource, you might consider consulting Microsoft TechNet or the Microsoft Developer Network (MSDN™). These resources include the Microsoft Knowledge Base, as well as other current information. For more information about subscribing to Microsoft TechNet, see http://www.Microsoft.com/technet/. For more information about MSDN, see http://msdn.Microsoft.com/.

To minimize the effects of a server failure or other troubleshooting situation:

• Develop and test a backup and recovery plan.

• Run DBCC CHECKDB occasionally to verify database integrity. For more information, see “DBCC CHECKDB” in the SQL Server Books Online.

• Create Transact-SQL (T-SQL) scripts containing DBCC checks, and use the SQL Server Database Maintenance Plan wizard to schedule the scripts to run during periods of low activity.

• Verify the security permissions and roles you have planned for your databases.

For information about finding the details you require, see Finding Information.