T
tanzimshaik
While logged into the windows domain, the installation of Project
Server 2007 on SQL 2005 Express as a standalone deployment was
completed, hence it took the same user account (Windows Account =
[domain]\tanzims, Full Name = Tanzim Aftab Haji) as EPM Administrator
by default. After configuring the Project Server 2007 for testing
purposes the above mentioned user was removed from the Administrators
group and signed out. After signing back in with the above mentioned
user name there were no permissions (Admin permissions) to modify the
users and there was no other user created with Admin permissions.
By default SQL 2005 Express doesn't come with SQL Server Management
Studio Express. Hence we did the following steps:
1. Downloaded SQL Server Management Studio Express.
2. After downloading it we went to the database called
"PWA_Published_xxx" for our database name was
(PWA_Published_B7AE9D7A_7C17_44F8_AC53_D06D6B065545).
3. Identified the WRES_GUID, RES_SECURITY_GUID from the Table
MSP_RESOURCES against the user name mentioned in the problem. The
query to retrieve the data is "SELECT * FROM MSP_RESOURCES WHERE
RES_NAME = 'Tanzim Aftab Haji'"
4. Identified the WSEC_GRP_GUID from the Table MSP_WEB_SECURITY_GROUPS
against the group name "Administrators". The query to retrieve the
data is "SELECT * FROM MSP_WEB_SECURITY_GROUPS WHERE WSEC_GRP_NAME =
'Administrators'"
5. Identified on which row the UPDATE query needs to run on. The query
is "SELECT * FROM MSP_WEB_SECURITY_GROUP_MEMBERS".
6. Since there were two groups associated to each user, the UPDATE
query should run on a unique row or else it would try to replace all
the rows found with the criteria. The columns identified for
uniqueness were WSEC_GRP_GUID, WRES_GUID and CREATED_DATE. The final
UPDATE query looked like the following "UPDATE
MSP_WEB_SECURITY_GROUP_MEMBERS SET WSEC_GRP_GUID =
'B0928A2E-3DDA-4ACF-9D0B-E626DBF0E57E' WHERE WRED_GUID =
'550CB35C-8B8B-4EB1-B9FD-277CD473DA64' AND CREATED_DATE = '2007-05-01
13:23:06:063'"
Al-Hamdulillaah (All praises and thanx to God), the problem was
solved.
I thought to share this with you'll.
Server 2007 on SQL 2005 Express as a standalone deployment was
completed, hence it took the same user account (Windows Account =
[domain]\tanzims, Full Name = Tanzim Aftab Haji) as EPM Administrator
by default. After configuring the Project Server 2007 for testing
purposes the above mentioned user was removed from the Administrators
group and signed out. After signing back in with the above mentioned
user name there were no permissions (Admin permissions) to modify the
users and there was no other user created with Admin permissions.
By default SQL 2005 Express doesn't come with SQL Server Management
Studio Express. Hence we did the following steps:
1. Downloaded SQL Server Management Studio Express.
2. After downloading it we went to the database called
"PWA_Published_xxx" for our database name was
(PWA_Published_B7AE9D7A_7C17_44F8_AC53_D06D6B065545).
3. Identified the WRES_GUID, RES_SECURITY_GUID from the Table
MSP_RESOURCES against the user name mentioned in the problem. The
query to retrieve the data is "SELECT * FROM MSP_RESOURCES WHERE
RES_NAME = 'Tanzim Aftab Haji'"
4. Identified the WSEC_GRP_GUID from the Table MSP_WEB_SECURITY_GROUPS
against the group name "Administrators". The query to retrieve the
data is "SELECT * FROM MSP_WEB_SECURITY_GROUPS WHERE WSEC_GRP_NAME =
'Administrators'"
5. Identified on which row the UPDATE query needs to run on. The query
is "SELECT * FROM MSP_WEB_SECURITY_GROUP_MEMBERS".
6. Since there were two groups associated to each user, the UPDATE
query should run on a unique row or else it would try to replace all
the rows found with the criteria. The columns identified for
uniqueness were WSEC_GRP_GUID, WRES_GUID and CREATED_DATE. The final
UPDATE query looked like the following "UPDATE
MSP_WEB_SECURITY_GROUP_MEMBERS SET WSEC_GRP_GUID =
'B0928A2E-3DDA-4ACF-9D0B-E626DBF0E57E' WHERE WRED_GUID =
'550CB35C-8B8B-4EB1-B9FD-277CD473DA64' AND CREATED_DATE = '2007-05-01
13:23:06:063'"
Al-Hamdulillaah (All praises and thanx to God), the problem was
solved.
I thought to share this with you'll.