Qdabra Active Directory Web Service

Re: Qdabra Active Directory Web Service is unavailable.

Jim Cantwell — Tue, 17 Apr 2012 19:50:53 GMT

If the AD webservice is installed on a SharePoint site, some SharePoint updates or admin operations may have affected the app pool assignment. Make sure the app pool assigned is DbxlAppPool{SITEID} {SITEID} will be the ID of the site. It should show as Classic managed pipeline mode if on IIS7.

If you remote desktop to the server, enter the url to the AdUserInfo.asmx page (e.g. http://server/QdabraAD/AdUserInfo.asmx) and then click on the GetMyInfo link and then click Invoke. You should get more error detail.

I would also check the Qdabra eventlog for additional details.

Re: Qdabra Active Directory Web Service is unavailable.

drewified — Tue, 17 Apr 2012 17:38:17 GMT

When I look in the event log, I get "The following query failed: GetMyInfo...... Exception Message: The remote server returned an error: (500) Internal Server Error. The remote server returned an error: (500) Internal Server Error.)

Qdabra Active Directory Web Service is unavailable.

drewified — Tue, 17 Apr 2012 17:17:39 GMT

Hi Guys,

This morning something odd happened - the AD Web Service stopped working - when I got to the AdUserInfo.asmx page I get the following error message:

Server Error in '/QdabraAD' Application.

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
    </system.web>
</configuration>

Naturally, forms that are using this service are unable to open correctly because queries cannot execute. Please let me know what I can do to fix! Thank you.