Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

LDAP and multiple Domains



  • Hello,

    Background:

    Proget was up and running and we had it setup with LDAP and integrated configuration.
    We were having some difficulties however to get all users access through the "Domain Users" Security group.

    I was in the process of troubleshooting this when I made matters worst.

    Current issue: I had discovered there was a setting of Active Directory with Multiple Domains. So I went in my setting of proget where it monitors the LDAP folder and I changed it to AD with multiple Domain. At that point I was still able to load the Proget page. However after this, I enabled integrated authentication again and since then I can no longer load the page and any login that I try results in the same error

    "Creating an instance of the COM component with CLSID {080D0D78-F421-11D0-A36E-00C04FB950DC} from the IClassFactory failed due to the following error: 800401e4 Invalid syntax (Exception from HRESULT: 0x800401E4 (MK_E_SYNTAX))."

    Please help? Is there a way for me to quickly revert back to previous settings or change the web interface settings through a config file?

    Thank you!

    Product: ProGet
    Version: 4.4.0



  • You can reset this via the ProGet.Service.exe, just run the program and one of the optiosn will be to reset the directory.

    Note you can also do this by going to the database, the [Configuration] table and setting [UserDirectoryId] to 1



  • Ok, Thank you

    This as worked but we are unable to login from there. How can we manage credientials from the DB or how can we easily get around this?

    Right now we aren't able to edit the settings because of this.

    Also, could it be possible for you to provide us your Proget Code for "active directory query" ? If so, could you send that code to my email?

    Thank you for your quick support. :)



  • UPDATE:

    we are now getting this error through playing with the SQL tables:

    Illegal operation attempted on a registry key that has been marked for deletion.

    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.Runtime.InteropServices.COMException: Illegal operation attempted on a registry key that has been marked for deletion.

    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:

    [COMException (0x800703fa): Illegal operation attempted on a registry key that has been marked for deletion.
    ]
    System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail) +576673
    System.DirectoryServices.DirectoryEntry.Bind() +45
    System.DirectoryServices.DirectoryEntry.get_AdsObject() +40
    System.DirectoryServices.PropertyValueCollection.PopulateList() +27
    System.DirectoryServices.PropertyValueCollection..ctor(DirectoryEntry entry, String propertyName) +122
    System.DirectoryServices.PropertyCollection.get_Item(String propertyName) +162
    System.DirectoryServices.DirectorySearcher.get_SearchRoot() +149
    System.DirectoryServices.DirectorySearcher.FindAll(Boolean findMoreThanOne) +45
    System.DirectoryServices.DirectorySearcher.FindOne() +47
    Inedo.ProGet.WebApplication.Security.UserDirectory.LdapDirectory.TryGetUser(String userName) +233
    Inedo.ProGet.WebApplication.ProGetHttpModule.AuthenticateRequest(HttpApplication app) +457
    System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +142
    System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +92



  • That is just a "regular" COM+ that happens every now and then when doing anything with LDAP, so you an usually restart IIS, restart the server to fix it.

    Will send the code ASAP!



Inedo Website HomeSupport HomeCode of ConductForums GuideDocumentation