The trust relationship between the primary domain and the trusted domain failed in Windows 2003 and Windows 2008 servers while launching .NET web application.
The trust relationship between the primary domain and the trusted domain failed in Windows 2003 and Windows 2008 servers while launching web application.
The trust relationship between the primary domain and the trusted domain failed.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.SystemException: The trust relationship between the primary domain and the trusted domain failed.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[SystemException: The trust relationship between the primary domain and the trusted domain failed.
]
System.Security.Principal.
System.Security.Principal.
System.Security.Principal.
System.Web.Configuration.A
System.Web.Configuration.A
System.Web.Configuration.A
System.Web.Security.UrlAut
System.Web.SyncEventExecut
System.Web.HttpApplication
__________________________
Version Information: Microsoft .NET Framework Version:2.0.50727.1891; ASP.NET Version:2.0.50727.1887
The trust relationship between the primary domain and the trusted domain failed.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.SystemException: The trust relationship between the primary domain and the trusted domain failed.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[SystemException: The trust relationship between the primary domain and the trusted domain failed.
]
System.Security.Principal.
System.Security.Principal.
System.Security.Principal.
System.Web.Configuration.A
System.Web.Configuration.A
System.Web.Configuration.A
System.Web.Security.UrlAut
System.Web.SyncEventExecut
System.Web.HttpApplication
__________________________
Version Information: Microsoft .NET Framework Version:2.0.50727.1891; ASP.NET Version:2.0.50727.1887
Seth Simmons
remove that computer from the domain and add again
ASKER
Web Application is deployed in all the environments like Dev, Test and Prod. There are several servers associated. Following tasks has already been performed but still not able to identify the cause.
• No patches/installation has been performed in associated servers.
• Validated the trust between the source domain and target domain. It is validating successfully.
• Modified the primary and alternate dns to recommended I.P address in Internet protocol properties from Network connections.
• Performed DNS flush and restarted IIS.
• Cleared the cache and history.
• No patches/installation has been performed in associated servers.
• Validated the trust between the source domain and target domain. It is validating successfully.
• Modified the primary and alternate dns to recommended I.P address in Internet protocol properties from Network connections.
• Performed DNS flush and restarted IIS.
• Cleared the cache and history.
check if you can validate domain trust between two from "active directory domain and trusts"
It seems that name resolution is failing between two domains..
How you established name resolution between both domains, can you refresh name resolution between two domains and try to validate trust again?
It seems that name resolution is failing between two domains..
How you established name resolution between both domains, can you refresh name resolution between two domains and try to validate trust again?
ASKER
Naming resolution has been performed and got confirmation from Active Directory team it is working as expected.
Are they able to validate trust from both sides?
ASKER
Yes it has been confirmed.
I believe you are accessing resource for migrated users (AD migration)
If that's the case, you need to allow / enable sidhistory and disable sid filtering in resource domain where web app exists
If that's the case, you need to allow / enable sidhistory and disable sid filtering in resource domain where web app exists
ASKER
As per the confirmation from AD team, no updates has been performed. It stopped working in all the environments.
are you able to logon with your account in computers of trusted domain?
ASKER
Yes I'm able to login to the trusted domain.
ASKER
Service account belongs to target domain. App pool and services are configured using the service account. Application was working fine all this time and suddenly stopped working in all the environments.
did anybody changed service account password and its not changed on app server?
please check your service account, that is the only possibility I can think of...
please check your service account, that is the only possibility I can think of...
ASKER
We were able to configure again using the same service account without any issue.
Same service account is true but you must have reset its password
ASKER
Nope it has not happened. We got the confirmation.
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.