RESOLUTION
To resolve this issue, create an SQL script that contains the following lines of code.
DECLARE @tempTable Table(relID int)
INSERT INTO @tempTable (relID)
SELECT
DISTINCT p.WSEC_REL_ID
FROM
dbo.MSP_WEB_SECURITY_SP_CAT_PERMISSIONS p INNER JOIN
dbo.MSP_WEB_SECURITY_SP_CAT_RELATIONS r ON
p.WSEC_REL_ID = r.WSEC_REL_ID INNER JOIN
dbo.MSP_WEB_VW_SEC_ALLSP a ON
r.WSEC_SP_GUID = a.WSEC_SP_GUID
WHERE
a.WSEC_SP_NAME IN ('Black Belt', 'Master Black Belt', 'Executive Sponsor', 'Finance', 'Champion', 'Site VP of Six Sigma', 'Corp VP of Six Sigma', 'Executives', 'Administrators')
INSERT INTO MSP_WEB_SECURITY_SP_CAT_PERMISSIONS (WSEC_REL_ID,WSEC_FEA_ACT_ID,WSEC_ALLOW,WSEC_DENY,WSEC_ACCESS)
select relID,10001,1,0,1 from @tempTable
Run the SQL script to add
the permissions settings for the
Financials tab back to the Office Solution Accelerator for Six Sigma roles.
This SQL script works as follows. The script declares a temporary table and then inserts data that is based on the query that uses the SELECT DISTINCT statement. The query returns a list of relationship IDs that correspond to categories that are available to the Office Solution Accelerator for Six Sigma roles. The INSERT INTO statement uses the relationship IDs from the temporary table to insert a row for each relationship ID into the
MSP_WEB_SECURITY_SP_CAT_PERMISSIONS table. The value of the relationship ID is inserted into the
WSEC_REL_ID column. The INSERT INTO statement also inserts the following values into the following columns.
The value of 10001 in the
WSEC_FEA_ACT_ID column corresponds to the
Financials tab.
Notes- Make sure that you back up data on the server before you run the SQL script.
- If you receive a primary key error message when you run the script, remove the roles that are referenced in the error message from the SELECT DISTINCT statement.
- An alternative method that you can use when you run this script is to run the SELECT
DISTINCT statement by using one role at a time. After you run the SELECT DISTINCT statement for one role, manually insert the rows into the MSP_WEB_SECURITY_SP_CAT_PERMISSIONS table for each relationship ID. Repeat this procedure for each role.
- In scenarios where you have to frequently use the SQL script, you may want to incorporate the SQL script into an Active Server Pages (ASP) page. Then, add a link to the ASP page to the Admin menu in Project Web Access 2003.