• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 366
  • Last Modified:

AD-LDS Instance 2008 Question

We have an ADAM instance that was migrated from 2003 to AD-LDS 2008. After doing so, the application broke after conecting to the AD-LDS 2008. We are using a wide IP alias that was never changed. The application works if we connect to 2003 but not to the 2008 instance. Any ideas? Thank you!
0
syseng007
Asked:
syseng007
  • 3
  • 2
  • 2
1 Solution
 
MaheshArchitectCommented:
Have you done in place gradation from 2003 server to 2008 server  as per below link ?
http://technet.microsoft.com/en-us/library/cc732566(WS.10).aspx
In that case you should not face any issues

Is AD-LDS 2008 is also Domain controller or just member server ?

if its member server, then request you to just disjoin server from domain and re-join again and check if application is working

Mahesh
0
 
syseng007Author Commented:
Hi Mahesh, the migration is not in place, and AD-LDS is a member server....
0
 
syseng007Author Commented:
We are getting this error when we are trying to connect:

Caused by: java.security.PrivilegedActionException: javax.naming.AuthenticationException: GSSAPI [Root exception is javax.security.sasl.SaslException: GSS initiate failed [Caused by GSSException: No valid credentials provided (Mechanism level: Server not found in Kerberos database (7))]]

        at java.security.AccessController.doPrivileged(Native Method)

        at javax.security.auth.Subject.doAs(Unknown Source)

        at mesh.entitlements.provider.adam.DirectoryConnection.doAsCurrentUserWithRetry(DirectoryConnection.java:104)

        at mesh.entitlements.provider.adam.DirectoryConnection.doAsCurrentUserWithRetry(DirectoryConnection.java:122)

        at mesh.entitlements.provider.adam.DirectoryConnection.doAsCurrentUser(DirectoryConnection.java:97)

        at mesh.entitlements.provider.adam.DirectoryConnection.getRootContext(DirectoryConnection.java:77)
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
MaheshArchitectCommented:
Have you tried disjoin \ re-join of 2008 ADLDS server please ?

If problem still persists you could give a try in place upgrade of 2003 machine as per above link

Mahesh
0
 
compdigit44Commented:
Judging by the error message it sounds like the proper service DNS entries are missing for the app to find the correct ADLDS instance also ADLDS security may be more stringent that 2003..

I would suggest you follow Mahesh advice and run through the upgrade graduation processess
0
 
syseng007Author Commented:
@Mahesh - there are 5 instances on the member server and there's only that's kicking off an error though...So I don't think disjoin and re-add to the domain would be the solution....
0
 
compdigit44Commented:
I would suggest to try to re-register your SPN for ADLDA to make sure the service account for this ADLDS instance is registered in AD


http://technet.microsoft.com/en-us/library/cc816802(v=ws.10).aspx
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 3
  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now