- Unable to update the password. The values provided as the current password is incorrect.
- COM error 80040154 or Retrieving the COM class factory for component with CLSID {...}
- File not found (80070002)
- Element not found (80070490)
- This operation can not be performed on the current domain.
- The specified domain either does not exist or could not be contacted
- The system cannot open the device or file specified 98007006
- Unable to cast COM object of type 'System.__ComObject' to interface type 'Microsoft.Interop.Security.AzRoles.IAzApplication'
- The authorization store component is not installed
- FileLoadException: The process cannot access the file because it is being used by another process
This is an issue with the user making a call out to AzMan. You should set Everyone as a Reader or turn impersonation on (if cross-domain). You should see full details in the event log where AzMan is located.
The error is that .NET can't find the AzMan COM objects. If you copy azroles.dll into %WINDIR%\System32\and then run regsvr32 azroles.dll you should be ok. You can also GAC the Microsoft.Interop.Azroles.dll which is found in %WINDIR%\Microsoft.NET\AuthMan .
The solution for me was to Add the Authenticated Users to the Reader mode in AzMan. You can also try and add everyone (not the best idea) to the reader mode.
You usually get this when the msldap or msxml string is wrong. Check your connection string and make sure it can talk to the right domain or XML file. Also, I have seen this if you attempt to talk to an operationName or operationID that is not there or spelled incorrectly.
Seems to be tied to mismatched SIDs or going cross domain. Usually, this is just a trust issue. You can also try and impersonate to solve this problem. This error is tied to an AD backed store and you should not really see this in an XML store system.
A solution for this can be found Here. Personally, I never had this error happen to me.
Another security/trust issue. Make sure you have correct roles to read AzMan and the trusts or impersonation is set in place correctly.
Solution can be found Here.
Make sure you GAC the AzRoles Interop Assembly.
Something with how the DOM opens up XML. I never really had this issue as I oly worked with AD store.
No comments:
Post a Comment