34
Views
1
Comments
[Active Directory] Unspecific Error with Active Directory Forge
active-directory
Web icon
Forge component by Renato Pauleta
Application Type
Reactive

Hello everyone
Have you tried with Active Directory Forge?
https://www.outsystems.com/forge/component-overview/11126/active-directory-library
When I used this Forge with a sample demo, I received [Unspecific Error] at Service Center.
Does anyone know what might be the causes for this error and how to fix it

Here is the error in details
-----------------------------------
eSpaceVer: Id=9498, PubId=0, CompiledWith=11.18.1.37828
RequestUrl: https://.../DataActionGetUserList (Method: POST)
AppDomain: //.../1/ROOT/AD_Demo-875-133287212239896285
FilePath: D:\OutSystems\Platform Server\running\AD_Demo.804009476\
ClientIp: XX.XX.XX.XXX  X-Forwarded-For: XX.XX.XX.XX
Locale: en-US
DateFormat: yyyy-MM-dd
PID: 7896 ('w3wp', Started='5/8/2023 3:32:52 AM', Priv=2799Mb, Virt=2110319Mb)
TID: 368
Thread Name:
.NET: 4.0.30319.42000
Stack
Unspecified error
   at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail)
   at System.DirectoryServices.DirectoryEntry.Bind()
   at System.DirectoryServices.DirectoryEntry.get_AdsObject()
   at System.DirectoryServices.DirectorySearcher.FindAll(Boolean findMoreThanOne)
   at OutSystems.NssActiveDirectory_Ext.CssActiveDirectory_Ext.MssAD_SearchUser(String ssSearch, Int32 ssSearchBy, Boolean ssActiveOnly, DateTime ssLastUpdatedOn, RLADExtendedGetRecordList ssExtendedAttributes, RLADUserRecordList& ssADUsers)
   at OutSystems.NssActiveDirectory_Ext.CssActiveDirectory_Ext.MssAD_ListUsers(Boolean ssActiveOnly, DateTime ssLastUpdatedOn, RLADExtendedGetRecordList ssExtendedAttributes, RLADUserRecordList& ssADUsers)
   at ssActiveDirectory_IS.RssExtensionActiveDirectory_Ext.MssAD_ListUsers(HeContext heContext, Boolean inParamActiveOnly, DateTime inParamLastUpdatedOn, RecordList inParamExtendedAttributes, RecordList& outParamADUsers)

Thank you




From the context of the error it looks like you're never getting connected to the AD server.

My first check would be firewall rules, SSL settings, verify the specific port of your instance and that your service account is valid by pulling from an alternative source.

It does sound to most likely be a firewall issue, however, from the lack of binding ever connecting.

Hope you got this working in the past 3 months, but if not, let us know so that we can continue to assist!


Best,
RAD Manage

Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.