Make sure you have installed the appropriate software prerequisites on the server before installing the Access Workflow Designer server components. For details, see Server Prerequisites in the Installation Prerequisites topic.
Setting up the Access Workflow Designer server components involves the following considerations:
Note If you encounter errors during Setup, see the Setup Issues in the Troubleshooting topic in the Access Workflow Designer Developer's Guide.
For additional installation and setup information, see the modServerReadme file on the Microsoft Office Developer CD-ROM before installing any components.
To install server components
Note You return to the Component Options page when installation for the selected component is complete.
After installation is complete, the server contains the administrative tools and the server infrastructure for team solutions.
Note You may receive the following message: "Unable to verify that FrontPage 2000 Server Extensions are setup and working properly. Please set up FrontPage 2000 Server Extensions manually." If you do, run Fpsrvadm.exe to reregister the FrontPage Server Extensions. For more information, search for "fpsrvadm.exe" in the Troubleshooting topic in the Access Workflow Designer Developer's Guide.
Note When installing the Windows NT Option Pack, SMTP Services may not be installed by default. If you receive the message "Unable to start SMTP Services," you must reinstall the Option Pack. For details, see "Unable to start SMTP Services error message" in the Troubleshooting topic in the Access Workflow Designer Developer's Guide.
After the server components are installed, you can install the Access Workflow Designer development tools on the server as well. For more information, see Setting Up the Development Computer.
The Access Workflow Designer Server Components Setup program installs the following components"
| Component | Description |
| Team Solutions Manager | A tool that makes it possible for the solution administrator to manage all the team solutions, templates, and users for the server. |
| New Team Solutions wizard | A wizard used to create a solution based on a template. For example, this wizard can be used to create a new team solution based on the Issue Tracking template installed with the server setup. |
| SilentClient.exe | End-User Client Setup program that installs components required for team solutions to be used offline. |
| http://<servername>/modweb | A Web site created on the server with a default page linking to the End-User Client Setup program. |
| modSystem.mdf | The modSystem SQL Server database that stores information about the solutions, templates, and users on the server. |
| Stored procedures, SQL views, and extended stored procedures | Components used by the team solution to provide core services. |
| Issue Tracking solution template | The template provided by Access Workflow Designer that can be used to create an instance of an issue tracking solution. |
| modAdminGuide.chm | The Access Workflow Designer Administrator's Guide online documentation. |
| modAppOwners | A Windows NT Group with appropriate SQL Server login permissions to register and create team solutions. |
After the server is set up, the server administrator should do the following:
Note Developers must be added to the modAppOwners Windows NT group created during server setup. This provides a SQL login and the appropriate permissions to create new team solutions on the server.
Note For more information, see Creating Accounts, Logins, Roles, and Users in the Access Workflow Designer Administrator's Guide.