Symptoms

When loading the task tree or progress view, an error message including the phrase “Catastrophic Failure” is displayed instead.

Solution

Reinstall the TASKey TEAM COM+ objects using Component Services management console.

TEAM should then behave normally and this error will not be visible.

Scope

This involves COM+, so the solution would be different were the problem to occur on Window NT.

Details

From Administrative Tools, select component services, expand the tree until the TASKey TEAM application is shown as below.

Select the TASKey TEAM application by clicking on it, then right click on it, and select delete, say yes to the confirmation.

Then click on COM+ Applications, right click and select New COM+ application.

Create an empty application

Name the Server Application Exactly as below:

This will be the identity of the TASKey TEAM business objects, they need access to the database.

The identity needs to be a valid SQL server user, and have read/write access to the TASKeyTEAM database. 

If the database is installed on the same machine as the TEAM application, then the local administrator may be a good choice. 

If the database is on another machine, then the domain administrator may be a good option. 

The interactive user is probably not a good choice, as this means the identity can change depending on who is logged on, (or not logged on) to the machine. 

Then select Install new component(s).

Then select these files, (the default location is C:\Inetpub\wwwroot\TASKeyTeam\taskey\team).

Finish.

The TASKey TEAM application should now have some components in it.

Click on roles, right click, add a new role called “Admin”.

Expand roles, expand Admin, click on users, right click and add a new user.

This is the windows user/s or groups which can access the TASKey TEAM business objects.  The WebTeam ISAPI dll needs to be able to access the business objects, as do some other TEAM modules and services. 

You need to specify the user that you specifed in the install as the IIS user.  If you specify a different user, the TEAM ISAPI dlls will not be able to use the business objects.

The default user used by the automatic installation (preTEAM  3.1.1) here is IUSR_<machinename>.

Eg if the machine where named “SUPERTED”, then this user would be named as below.

*TEAM 3.1.1 does not recommend the use of IUSR_<machinename> for installations using IIS6. 
This is because IIS6 does not have sub-authentication (IIS maintaining the IUSR_<machinename> users password) enabled by default for security reasons.

As a best practice for tight security on Win2003, create a user who is a member of guests, and choose that user for the TEAM IIS user.  (The user must still have sufficient permissions, and those that a guest has from a Win 2003 install, together with the IIS and ACL access granted to this user by the TEAM install is enough).

The TASKey TEAM application should now look something like below.

The installation/upgrade of TEAM should now be fixed, try logging in, and viewing the task tree, and progress.

If problems persist or other support is required, contact support@taskey.com.