PS 2003 - Faile to link Issues and Tasks

[Lucas Campos]

Hi,
I'm using PS 2003 over Win 2003 and WSS. I'm receiving a warning message
when I create an Issue (although the Issue is created) from Web Access
"Project Server failed to update links between the issue and the selected
tasks. Log on to Project Web Access and link the issue to tasks from Tasks,
Resource Assignments, or Project Drill-down page"

I wasn't trying to link this Issue, but just creating it.

On the other hand I can't link Issues to tasks (accessing through Tasks or
through Issues)

What could be wrong?

Thanks

LucasC

 

[David Gage - Project MVP]

Can you start going through the features to see what works?

Publish a test project with you as a project manager - does it build the
subweb automatically if you have it set to do so?
Delete the test subweb if it was automatically created - does that work?
(Re)Create the test subweb - can you do that successfully?
Upload a document to the test project - can you do it?
Create a risk in the test project - can you do it?
Create an issue in the test project- can you do it?

Also, are you using Windows authentication or Project Server authentication?

 

[Lucas Campos]

I could make all test until upload a document...and so on...

I could load a document, create an issue and create a Risk, but I received a
warning message as follows one for each operation:

"Project Server failed to update the links in Project Server database.
Please try again later or contact your administrator"

"Project Server failed to update links between the issue and the selected
tasks. Log on to Project Web Access and link the issue to tasks from Tasks,
Resource Assignments, or Project Drill-down page"

"Project Server failed to update links between the risk and the selected
tasks. Log on to Project Web Access and link the issue to tasks from Tasks,
Resource Assignments, or Project Drill-down page"

 

[David Gage - Project MVP]

Are you using Windows authenticated users for Project Server?

Are or can you use a user that is an administrator on the server as well as
a super user in Project Server (Add all groups to your user)?

If you weren't using the two above, try again with those settings. If you
were a super administrator user on the server and PServer2003, then let us
know.

David

 

[Lucas Campos]

I'm using Windows authenticated users (mixed authentication is allowed, but
I'm using Windows)
I belongs Administrators Project Server user Group.
I don't think that using Windows Administrators privileges could be a valid
scenario.

 

[David Gage - Project MVP]

I was trying to help you debug the problem and being a Windows Administrator
on the server
will allow us to determine if this is a permissions issue. If this is
possible, can you try it?

Also, please trying running the following script against the Project Server
and WSS database using Query Analyzer. Look down below and find the
WSS_DATABASE_NAME and change it to reflect the actual name of your WSS
database.

SET NOCOUNT ON
select p.wproj_id ,
p.proj_id,
p.proj_name COLLATE Latin1_General_CI_AI proj_name,
p.wproj_issue_list_name as PS_IssueID,
L1.tp_ID as WSS_ListID,
p.wproj_risk_list_name as PS_RiskID,
L2.tp_ID as WSS_RiskID
from msp_web_projects p
left outer join msp_web_sts_servers s
on p.wsts_server_id = s.wsts_server_id
left outer join [WSS_DATABASE_NAME].dbo.Webs w
on w.FullUrl = (s.wsts_managed_path + N'/' +
p.wproj_sts_subweb_name) COLLATE Latin1_General_CI_AI
left outer join [WSS_DATABASE_NAME].dbo.Lists L1
on w.ID = L1.tp_WebID and L1.tp_Title = N'Issues'
left outer join [WSS_DATABASE_NAME].dbo.Lists L2
on w.ID = L2.tp_WebID and L2.tp_Title = N'Risks'
COLLATE Latin1_General_CI_AI

 

[Lucas Campos]

The problems seems to be solved (I can create or modify Risk and Issues from
PS and WSS without receive warnings and I can link them). Lamentably I don't
know what solved it. I have to wait until the next failure :-s
The query return me a set of joining PS and WSS IDs. It seems to work fine.

Thank you very very much for your help David.

I was trying to help you debug the problem and being a Windows Administrator
on the server
will allow us to determine if this is a permissions issue. If this is
possible, can you try it?

Also, please trying running the following script against the Project Server
and WSS database using Query Analyzer. Look down below and find the
WSS_DATABASE_NAME and change it to reflect the actual name of your WSS
database.

SET NOCOUNT ON
select p.wproj_id ,
p.proj_id,
p.proj_name COLLATE Latin1_General_CI_AI proj_name,
p.wproj_issue_list_name as PS_IssueID,
L1.tp_ID as WSS_ListID,
p.wproj_risk_list_name as PS_RiskID,
L2.tp_ID as WSS_RiskID
from msp_web_projects p
left outer join msp_web_sts_servers s
on p.wsts_server_id = s.wsts_server_id
left outer join [WSS_DATABASE_NAME].dbo.Webs w
on w.FullUrl = (s.wsts_managed_path + N'/' +
p.wproj_sts_subweb_name) COLLATE Latin1_General_CI_AI
left outer join [WSS_DATABASE_NAME].dbo.Lists L1
on w.ID = L1.tp_WebID and L1.tp_Title = N'Issues'
left outer join [WSS_DATABASE_NAME].dbo.Lists L2
on w.ID = L2.tp_WebID and L2.tp_Title = N'Risks'
COLLATE Latin1_General_CI_AI


--
David Gage
Microsoft Project MVP
QuantumPM

I'm using Windows authenticated users (mixed authentication is allowed, but
I'm using Windows)
I belongs Administrators Project Server user Group.
I don't think that using Windows Administrators privileges could be a valid
scenario.


well
as

let

us build
the

 

[David Gage - Project MVP]

Glad to hear it is fixed although it would have been nice to know what the
fix was.

Also, I forgot to put in my post with the query that the two pairs of fields
should match as one set of fields comes from the Project Server database and
the other set come from the WSS database. If all four fields show different
guids then there is a problem as the WSS subwebs are not registered
correctly in the Project Server database.

--
David Gage
Microsoft Project MVP
QuantumPM

The problems seems to be solved (I can create or modify Risk and Issues from
PS and WSS without receive warnings and I can link them). Lamentably I don't
know what solved it. I have to wait until the next failure :-s
The query return me a set of joining PS and WSS IDs. It seems to work fine.

Thank you very very much for your help David.

I was trying to help you debug the problem and being a Windows Administrator
on the server
will allow us to determine if this is a permissions issue. If this is
possible, can you try it?

Also, please trying running the following script against the Project Server
and WSS database using Query Analyzer. Look down below and find the
WSS_DATABASE_NAME and change it to reflect the actual name of your WSS
database.

SET NOCOUNT ON
select p.wproj_id ,
p.proj_id,
p.proj_name COLLATE Latin1_General_CI_AI proj_name,
p.wproj_issue_list_name as PS_IssueID,
L1.tp_ID as WSS_ListID,
p.wproj_risk_list_name as PS_RiskID,
L2.tp_ID as WSS_RiskID
from msp_web_projects p
left outer join msp_web_sts_servers s
on p.wsts_server_id = s.wsts_server_id
left outer join [WSS_DATABASE_NAME].dbo.Webs w
on w.FullUrl = (s.wsts_managed_path + N'/' +
p.wproj_sts_subweb_name) COLLATE Latin1_General_CI_AI
left outer join [WSS_DATABASE_NAME].dbo.Lists L1
on w.ID = L1.tp_WebID and L1.tp_Title = N'Issues'
left outer join [WSS_DATABASE_NAME].dbo.Lists L2
on w.ID = L2.tp_WebID and L2.tp_Title = N'Risks'
COLLATE Latin1_General_CI_AI


--
David Gage
Microsoft Project MVP
QuantumPM

I'm using Windows authenticated users (mixed authentication is

allowed,
but

I'm using Windows)
I belongs Administrators Project Server user Group.
I don't think that using Windows Administrators privileges could be a valid
scenario.


"David Gage - Project MVP" <[email protected]> escribió en el mensaje
Are you using Windows authenticated users for Project Server?

Are or can you use a user that is an administrator on the server as well
as
a super user in Project Server (Add all groups to your user)?

If you weren't using the two above, try again with those settings.

If
you

were a super administrator user on the server and PServer2003, then

let

us
know.

David
--
David Gage
Microsoft Project MVP
QuantumPM

I could make all test until upload a document...and so on...

I could load a document, create an issue and create a Risk, but I
received
a
warning message as follows one for each operation:

"Project Server failed to update the links in Project Server database.
Please try again later or contact your administrator"

"Project Server failed to update links between the issue and the
selected
tasks. Log on to Project Web Access and link the issue to tasks from
Tasks,
Resource Assignments, or Project Drill-down page"

"Project Server failed to update links between the risk and the selected
tasks. Log on to Project Web Access and link the issue to tasks from
Tasks,
Resource Assignments, or Project Drill-down page"


"David Gage - Project MVP" <[email protected]> escribió en el mensaje
Can you start going through the features to see what works?

Publish a test project with you as a project manager - does it build
the
subweb automatically if you have it set to do so?
Delete the test subweb if it was automatically created - does that
work?
(Re)Create the test subweb - can you do that successfully?
Upload a document to the test project - can you do it?
Create a risk in the test project - can you do it?
Create an issue in the test project- can you do it?

Also, are you using Windows authentication or Project Server
authentication?

--
David Gage
Microsoft Project MVP
QuantumPM

Hi,
I'm using PS 2003 over Win 2003 and WSS. I'm receiving a warning
message
when I create an Issue (although the Issue is created) from Web
Access
"Project Server failed to update links between the issue and the
selected
tasks. Log on to Project Web Access and link the issue to

tasks
from

Tasks,
Resource Assignments, or Project Drill-down page"

I wasn't trying to link this Issue, but just creating it.

On the other hand I can't link Issues to tasks (accessing through
Tasks
or
through Issues)

What could be wrong?

Thanks

LucasC

 

[Lucas Campos]

OK. I'll check it. Thanks again David.

Glad to hear it is fixed although it would have been nice to know what the
fix was.

Also, I forgot to put in my post with the query that the two pairs of fields
should match as one set of fields comes from the Project Server database and
the other set come from the WSS database. If all four fields show different
guids then there is a problem as the WSS subwebs are not registered
correctly in the Project Server database.

--
David Gage
Microsoft Project MVP
QuantumPM

The problems seems to be solved (I can create or modify Risk and Issues from
PS and WSS without receive warnings and I can link them). Lamentably I don't
know what solved it. I have to wait until the next failure :-s
The query return me a set of joining PS and WSS IDs. It seems to work fine.

Thank you very very much for your help David.

I was trying to help you debug the problem and being a Windows Administrator
on the server
will allow us to determine if this is a permissions issue. If this is
possible, can you try it?

Also, please trying running the following script against the Project Server
and WSS database using Query Analyzer. Look down below and find the
WSS_DATABASE_NAME and change it to reflect the actual name of your WSS
database.

SET NOCOUNT ON
select p.wproj_id ,
p.proj_id,
p.proj_name COLLATE Latin1_General_CI_AI proj_name,
p.wproj_issue_list_name as PS_IssueID,
L1.tp_ID as WSS_ListID,
p.wproj_risk_list_name as PS_RiskID,
L2.tp_ID as WSS_RiskID
from msp_web_projects p
left outer join msp_web_sts_servers s
on p.wsts_server_id = s.wsts_server_id
left outer join [WSS_DATABASE_NAME].dbo.Webs w
on w.FullUrl = (s.wsts_managed_path + N'/' +
p.wproj_sts_subweb_name) COLLATE Latin1_General_CI_AI
left outer join [WSS_DATABASE_NAME].dbo.Lists L1
on w.ID = L1.tp_WebID and L1.tp_Title = N'Issues'
left outer join [WSS_DATABASE_NAME].dbo.Lists L2
on w.ID = L2.tp_WebID and L2.tp_Title = N'Risks'
COLLATE Latin1_General_CI_AI


--
David Gage
Microsoft Project MVP
QuantumPM

I'm using Windows authenticated users (mixed authentication is allowed,
but
I'm using Windows)
I belongs Administrators Project Server user Group.
I don't think that using Windows Administrators privileges could be a
valid
scenario.


"David Gage - Project MVP" <[email protected]> escribió en el mensaje
Are you using Windows authenticated users for Project Server?

Are or can you use a user that is an administrator on the server

as
well

as
a super user in Project Server (Add all groups to your user)?

If you weren't using the two above, try again with those settings. If
you
were a super administrator user on the server and PServer2003,

then
let

us
know.

David
--
David Gage
Microsoft Project MVP
QuantumPM

I could make all test until upload a document...and so on...

I could load a document, create an issue and create a Risk, but I
received
a
warning message as follows one for each operation:

"Project Server failed to update the links in Project Server database.
Please try again later or contact your administrator"

"Project Server failed to update links between the issue and the
selected
tasks. Log on to Project Web Access and link the issue to tasks from
Tasks,
Resource Assignments, or Project Drill-down page"

"Project Server failed to update links between the risk and the
selected
tasks. Log on to Project Web Access and link the issue to tasks from
Tasks,
Resource Assignments, or Project Drill-down page"


"David Gage - Project MVP" <[email protected]> escribió en el
mensaje
Can you start going through the features to see what works?

Publish a test project with you as a project manager - does it build
the
subweb automatically if you have it set to do so?
Delete the test subweb if it was automatically created - does that
work?
(Re)Create the test subweb - can you do that successfully?
Upload a document to the test project - can you do it?
Create a risk in the test project - can you do it?
Create an issue in the test project- can you do it?

Also, are you using Windows authentication or Project Server
authentication?

--
David Gage
Microsoft Project MVP
QuantumPM

Hi,
I'm using PS 2003 over Win 2003 and WSS. I'm receiving a warning
message
when I create an Issue (although the Issue is created) from Web
Access
"Project Server failed to update links between the issue and the
selected
tasks. Log on to Project Web Access and link the issue to tasks
from
Tasks,
Resource Assignments, or Project Drill-down page"

I wasn't trying to link this Issue, but just creating it.

On the other hand I can't link Issues to tasks (accessing through
Tasks
or
through Issues)

What could be wrong?

Thanks

LucasC

 

[Lucas Campos]

Those values are matching.
The problem started again I added myself to Administrators Group and Stop
happening. I remove myself from this group and it continue working OK. I
don't know if it is related to the problem.
I keep the Internet Explorer instance where I get the problem opened. And I
opened another one. So, I get two Internet Explorers, one fail and the other
doesn't, al the same time!!!!!!!!!!!!!

Thanks again

LucasC

OK. I'll check it. Thanks again David.

Glad to hear it is fixed although it would have been nice to know what the
fix was.

Also, I forgot to put in my post with the query that the two pairs of fields
should match as one set of fields comes from the Project Server database and
the other set come from the WSS database. If all four fields show different
guids then there is a problem as the WSS subwebs are not registered
correctly in the Project Server database.

--
David Gage
Microsoft Project MVP
QuantumPM

The problems seems to be solved (I can create or modify Risk and

Issues
from

PS and WSS without receive warnings and I can link them). Lamentably I don't
know what solved it. I have to wait until the next failure :-s
The query return me a set of joining PS and WSS IDs. It seems to work fine.

Thank you very very much for your help David.

"David Gage - Project MVP" <[email protected]> escribió en el mensaje
I was trying to help you debug the problem and being a Windows
Administrator
on the server
will allow us to determine if this is a permissions issue. If this is
possible, can you try it?

Also, please trying running the following script against the Project
Server
and WSS database using Query Analyzer. Look down below and find the
WSS_DATABASE_NAME and change it to reflect the actual name of your WSS
database.

SET NOCOUNT ON
select p.wproj_id ,
p.proj_id,
p.proj_name COLLATE Latin1_General_CI_AI proj_name,
p.wproj_issue_list_name as PS_IssueID,
L1.tp_ID as WSS_ListID,
p.wproj_risk_list_name as PS_RiskID,
L2.tp_ID as WSS_RiskID
from msp_web_projects p
left outer join msp_web_sts_servers s
on p.wsts_server_id = s.wsts_server_id
left outer join [WSS_DATABASE_NAME].dbo.Webs w
on w.FullUrl = (s.wsts_managed_path + N'/' +
p.wproj_sts_subweb_name) COLLATE Latin1_General_CI_AI
left outer join [WSS_DATABASE_NAME].dbo.Lists L1
on w.ID = L1.tp_WebID and L1.tp_Title = N'Issues'
left outer join [WSS_DATABASE_NAME].dbo.Lists L2
on w.ID = L2.tp_WebID and L2.tp_Title = N'Risks'
COLLATE Latin1_General_CI_AI


--
David Gage
Microsoft Project MVP
QuantumPM

I'm using Windows authenticated users (mixed authentication is allowed,
but
I'm using Windows)
I belongs Administrators Project Server user Group.
I don't think that using Windows Administrators privileges could

be

a settings.
If

but

I tasks
from tasks
from does
that from
Web and
the