Troubleshooting Workflow Applications for SQL Server

  • Article

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.

Because workflow applications and the Workflow Designer are used in conjunction with Microsoft® Windows® 2000, Microsoft® Access, Microsoft® SQL Server™, and a Microsoft® FrontPage® Web site, effective troubleshooting involves isolating where the problem exists. You might want to consult the documentation for these additional products.

Be sure to check the Workflow Designer server and developer tools Readmes and the Microsoft® Office XP Developer Web site (http://www.microsoft.com/office/developer) 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 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.

See Also

Troubleshooting Setup and Server Issues | Troubleshooting Database Issues | Troubleshooting Workflow Process and Scripting Issues | Troubleshooting Security and Permissions Issues | Error Messages