Trouble Accessing Active Directory

[Ripped]

I recently set up a Project Server 2007 installation and everything seems to be working fairly well. The only problem I've ran into so far is the following error when I click Server Settings / Groups and then any of the group names. When I do, I get the following message.

There was a problem accessing the Active Directory global catalog. Check that the following are true. 1. The Shared Services Provider (SSP) server can access an Active Directory domain controller hosting a copy of the global catalog. 2. The Windows account used for the SSP service credentials can read from the global catalog.

Any help would be appreciated.

Thanks,
Ripped

[ssanderlin]

Originally Posted by Ripped

I recently set up a Project Server 2007 installation and everything seems to be working fairly well. The only problem I've ran into so far is the following error when I click Server Settings / Groups and then any of the group names. When I do, I get the following message.

There was a problem accessing the Active Directory global catalog. Check that the following are true. 1. The Shared Services Provider (SSP) server can access an Active Directory domain controller hosting a copy of the global catalog. 2. The Windows account used for the SSP service credentials can read from the global catalog.

Any help would be appreciated.

Thanks,
Ripped

Ripped,

What service packs/hotfixes are you running? Have you checked the two possible causes suggested by the error?

[Ripped]

Originally Posted by ssanderlin

Ripped,

What service packs/hotfixes are you running? Have you checked the two possible causes suggested by the error?

Stephen,

I'm running the following Service Packs

Windows Server 2003 SP2
Microsoft Office 2007 Suite SP1
Microsoft .Net Framework 2.0 SP1
Microsoft .Net Framework 3.0 SP1
SQL Server 2005 SP2
Microsoft Visual Studio SP1

Im also running all hot fixes and security patches from the Microsoft Windows Update site.

Regarding the 2 possible causes mentioned, I'm not sure how to check those problems.

How do I verify the Shared Services Provider server can access an Active Directory domain controller hosting a copy of the global catalog?

Thanks,
Ripped

[ssanderlin]

Originally Posted by Ripped

Stephen,

I'm running the following Service Packs

Windows Server 2003 SP2
Microsoft Office 2007 Suite SP1
Microsoft .Net Framework 2.0 SP1
Microsoft .Net Framework 3.0 SP1
SQL Server 2005 SP2
Microsoft Visual Studio SP1

Im also running all hot fixes and security patches from the Microsoft Windows Update site.

Regarding the 2 possible causes mentioned, I'm not sure how to check those problems.

How do I verify the Shared Services Provider server can access an Active Directory domain controller hosting a copy of the global catalog?

Thanks,
Ripped

My question about the Service Pack was related to Project Server. Try using ADSIEdit or the AD U&G when logged in to the server as the SSP Account. This will point you to whether the user has access.

Also try the following (from this article for 2003, though the AD troubleshooting should still be valid):
When you synchronize Active Directory to a group cross forest, do the following things:
• Use the full Fully Qualified Domain Name (FQDN) to specify the group. For example, use the following FQDN to specify the group:
groupname@childdomain.rootdomain.com
• Make sure that the target domain in the remote forest contains a copy of the global catalog for that forest.
• If your domain contains Microsoft Windows NT 4.0 backup domain controllers (BDCs) and Microsoft Windows Server 2003 domain controllers, you may be running the Windows Server 2003 Active Directory forest in Interim Mode. Running the Windows Server 2003 Active Directory forest in Interim Mode can prevent Project Server from accessing the global catalog.
• When you use either the full FQDN or the domain\username format to specify a group, make sure that the target domain contains a copy of the global catalog for your forest.
• Make sure that port 3268 is open between the computer that is running Project Server 2003 and the domain controller that is hosting a copy of the global catalog. Port 3268 is used for global catalog communication. If your global catalog communication is encrypted by using Secure Sockets Layer (SSL), make sure that port 3269 is open.
• Make sure that the network and security topology is enabled for communication between Project Server and a domain controller that is hosting a global catalog. For example, if the computer that is hosting Project Server is a member of a workgroup, global catalog communication fails.