Activex Grids cannot be displayed

[Support]

I have implemented a solution EPM for a small company in a server located in
domain A. There is another domain (domain B) that store many users. For
project purposes, some of that users were created in domain A (to be project
server users, only windows users have to be logged). The platform was working
ok from the server. However, when I was making tests in another client host,
activex objects (grid) couldn't be viewed, a authentication windows is
displayed as if the user was not exist in the users group of project server.
All of this ocurrs in PCs contained in domain A. When I try to access to PWA
from a PC located in domain B or another domain, activex are displayed fine.
It sounds pretty strange... the issue only happens in PCs that belongs to
the same domain that project server.
I have installed Project Server SP2.
Any idea to solve this? I really appreciate your help.

Thanks a lot.

 

[Scott Wagner [MCP, MVP]]

Support,

Two ways that this can be resolved.
1) Active Directory with Domain Trees
2) Add users from other domain to local users of Server.

 

[Support]

Thanks Scott.
I tried second option you wrote, but the problem persists. The first option
is restricted in the client company (by now).
I have to say that there is a non-trusted relationship between the domains.
I put anonymous access for the isapi file (pjdbcomm.dll) and msadcs.dll in
the IIS and the grids for tasks, projects and resources worked. I thought I
have solved the bug, but... when I visited the issues, risks and docs
sections... it ocurred the same thing. Now, WSS is not working ok.
I have syncronized the admin accounts in PS admin tab - WSS admin - sync,
and I have syncronized every project in PS admin tab - WSS admin - Sites
admin - sync. The problem persists...
What can I do now?

Support,

Two ways that this can be resolved.
1) Active Directory with Domain Trees
2) Add users from other domain to local users of Server.

--
Have a great day!

Scott M. Wagner [MCP, MVP]

I have implemented a solution EPM for a small company in a server located
in
domain A. There is another domain (domain B) that store many users. For
project purposes, some of that users were created in domain A (to be
project
server users, only windows users have to be logged). The platform was
working
ok from the server. However, when I was making tests in another client
host,
activex objects (grid) couldn't be viewed, a authentication windows is
displayed as if the user was not exist in the users group of project
server.
All of this ocurrs in PCs contained in domain A. When I try to access to
PWA
from a PC located in domain B or another domain, activex are displayed
fine.
It sounds pretty strange... the issue only happens in PCs that belongs to
the same domain that project server.
I have installed Project Server SP2.
Any idea to solve this? I really appreciate your help.

Thanks a lot.

 

[Scott Wagner [MCP, MVP]]

It will not work with a non-trusted relationship between the domains. Sorry.

--
Have a great day!

Scott M. Wagner [MCP, MVP]

Thanks Scott.
I tried second option you wrote, but the problem persists. The first
option
is restricted in the client company (by now).
I have to say that there is a non-trusted relationship between the
domains.
I put anonymous access for the isapi file (pjdbcomm.dll) and msadcs.dll in
the IIS and the grids for tasks, projects and resources worked. I thought
I
have solved the bug, but... when I visited the issues, risks and docs
sections... it ocurred the same thing. Now, WSS is not working ok.
I have syncronized the admin accounts in PS admin tab - WSS admin - sync,
and I have syncronized every project in PS admin tab - WSS admin - Sites
admin - sync. The problem persists...
What can I do now?

Support,

Two ways that this can be resolved.
1) Active Directory with Domain Trees
2) Add users from other domain to local users of Server.

--
Have a great day!

Scott M. Wagner [MCP, MVP]

I have implemented a solution EPM for a small company in a server
located
in
domain A. There is another domain (domain B) that store many users. For
project purposes, some of that users were created in domain A (to be
project
server users, only windows users have to be logged). The platform was
working
ok from the server. However, when I was making tests in another client
host,
activex objects (grid) couldn't be viewed, a authentication windows is
displayed as if the user was not exist in the users group of project
server.
All of this ocurrs in PCs contained in domain A. When I try to access
to
PWA
from a PC located in domain B or another domain, activex are displayed
fine.
It sounds pretty strange... the issue only happens in PCs that belongs
to
the same domain that project server.
I have installed Project Server SP2.
Any idea to solve this? I really appreciate your help.

Thanks a lot.

 

[Support]

Hi Scott.
I have read some documentation and you're right, must be a specific
arquitecture to support non-trusted relationship domains.
However... I'm not sure that it is the cause of the problem, because now I
have tested other pc's and they don't work ok, when users visit the pages:
tasks, projects, pwa comes back to home page... for Resources Page is
displayed the following error:
"An error occurred while trying to access the resources stored on the
database. Either there are too many resources, or the Microsoft Project
Server may not have the correct DSN configuration. Contact the server
administrator. "
It supposed that SP2a solves this error
(http://support.microsoft.com/kb/906429/) ... but it occurs.
Issues, docs and problems don't load ('loading controls' stucks). This
happens in pc's logged locally, pc's in domain A and pc's in domain B. I was
testing in my laptop and it has many libraries installed, so... maybe that's
why pwa works fine there.
I'm really confused about it.

Thanks in advance.

It will not work with a non-trusted relationship between the domains. Sorry.

--
Have a great day!

Scott M. Wagner [MCP, MVP]

Thanks Scott.
I tried second option you wrote, but the problem persists. The first
option
is restricted in the client company (by now).
I have to say that there is a non-trusted relationship between the
domains.
I put anonymous access for the isapi file (pjdbcomm.dll) and msadcs.dll in
the IIS and the grids for tasks, projects and resources worked. I thought
I
have solved the bug, but... when I visited the issues, risks and docs
sections... it ocurred the same thing. Now, WSS is not working ok.
I have syncronized the admin accounts in PS admin tab - WSS admin - sync,
and I have syncronized every project in PS admin tab - WSS admin - Sites
admin - sync. The problem persists...
What can I do now?

Support,

Two ways that this can be resolved.
1) Active Directory with Domain Trees
2) Add users from other domain to local users of Server.

--
Have a great day!

Scott M. Wagner [MCP, MVP]

I have implemented a solution EPM for a small company in a server
located
in
domain A. There is another domain (domain B) that store many users. For
project purposes, some of that users were created in domain A (to be
project
server users, only windows users have to be logged). The platform was
working
ok from the server. However, when I was making tests in another client
host,
activex objects (grid) couldn't be viewed, a authentication windows is
displayed as if the user was not exist in the users group of project
server.
All of this ocurrs in PCs contained in domain A. When I try to access
to
PWA
from a PC located in domain B or another domain, activex are displayed
fine.
It sounds pretty strange... the issue only happens in PCs that belongs
to
the same domain that project server.
I have installed Project Server SP2.
Any idea to solve this? I really appreciate your help.

Thanks a lot.