<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://www.infopathdev.com:443/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Qdabra Active Directory Web Service</title><link>https://www.infopathdev.com:443/forums/57.aspx</link><description>Qdabra Active Directory Web Service enables showing all Microsoft Active Directory user details in InfoPath forms. It is available in Database Accelerator, WSSP and as a standalone tool.</description><dc:language>en</dc:language><generator>CommunityServer 2007 SP3 (Build: 31118.962)</generator><item><title>Re: Installing AD Webservice on MOSS 2007</title><link>https://www.infopathdev.com:443/forums/thread/29479.aspx</link><pubDate>Wed, 18 Jun 2008 18:23:36 GMT</pubDate><guid isPermaLink="false">033a2e2d-04e2-4a9d-be01-a4634161eefd:29479</guid><dc:creator>chscott</dc:creator><slash:comments>0</slash:comments><comments>https://www.infopathdev.com:443/forums/thread/29479.aspx</comments><wfw:commentRss>https://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=57&amp;PostID=29479</wfw:commentRss><description>&lt;p&gt;Seems I may have fixed this issue by&amp;nbsp;adding the following (per another post) on this forum.&lt;/p&gt;
&lt;p&gt;&amp;quot;&amp;lt;httpModules&amp;gt;&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;lt;clear /&amp;gt;&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;lt;add name=&amp;quot;WindowsAuthentication&amp;quot; type=&amp;quot;System.Web.Security.WindowsAuthenticationModule&amp;quot; /&amp;gt;&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;lt;/httpModules&amp;gt;&lt;br /&gt;&amp;quot;&lt;/p&gt;</description></item><item><title>Installing AD Webservice on MOSS 2007</title><link>https://www.infopathdev.com:443/forums/thread/29430.aspx</link><pubDate>Tue, 17 Jun 2008 12:49:41 GMT</pubDate><guid isPermaLink="false">033a2e2d-04e2-4a9d-be01-a4634161eefd:29430</guid><dc:creator>chscott</dc:creator><slash:comments>0</slash:comments><comments>https://www.infopathdev.com:443/forums/thread/29430.aspx</comments><wfw:commentRss>https://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=57&amp;PostID=29430</wfw:commentRss><description>&lt;p&gt;Our company purchased the AD Webservice a couple of years ago for our SharePoint 2003 server. We are currently migrating the contents of the old box to a new MOSS 2007 system.&amp;nbsp;I am currently getting&amp;nbsp;a Runtime Error when testing on the new server. I have checked the Web.Config on the other server and the LDAP settings are correct.&lt;/p&gt;
&lt;p&gt;I have the setup instructions, but they specify the older version of SharePoint. Will the old version of the AD Webservice work with MOSS 2007? If so, do you&amp;nbsp;have detailed instructions on how to setup it up?&lt;/p&gt;
&lt;p&gt;Thanks!&lt;/p&gt;
&lt;p&gt;Scott&lt;/p&gt;&lt;span&gt;&lt;/span&gt;&lt;span&gt;
&lt;h1&gt;Server Error in &amp;#39;/ADService&amp;#39; Application. 
&lt;hr /&gt;
&lt;/h1&gt;
&lt;h2&gt;&lt;i&gt;Runtime Error&lt;/i&gt; &lt;/h2&gt;
&lt;p&gt;&lt;/span&gt;&lt;font face="Arial, Helvetica, Geneva, SunSans-Regular, sans-serif "&gt;&lt;b&gt;Description: &lt;/b&gt;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. &lt;br /&gt;&lt;br /&gt;&lt;b&gt;Details:&lt;/b&gt; To enable the details of this specific error message to be viewable on remote machines, please create a &amp;lt;customErrors&amp;gt; tag within a &amp;quot;web.config&amp;quot; configuration file located in the root directory of the current web application. This &amp;lt;customErrors&amp;gt; tag should then have its &amp;quot;mode&amp;quot; attribute set to &amp;quot;Off&amp;quot;.&lt;br /&gt;&lt;br /&gt;
&lt;table class="" bgcolor="#ffffcc"&gt;

&lt;tr&gt;
&lt;td class=""&gt;&lt;code&gt;&lt;pre&gt;&amp;lt;!-- Web.Config Configuration File --&amp;gt;

&amp;lt;configuration&amp;gt;
    &amp;lt;system.web&amp;gt;
        &amp;lt;customErrors mode=&amp;quot;Off&amp;quot;/&amp;gt;
    &amp;lt;/system.web&amp;gt;
&amp;lt;/configuration&amp;gt;&lt;/pre&gt;&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;&lt;br /&gt;&lt;b&gt;&lt;font face="Verdana"&gt;Notes:&lt;/font&gt;&lt;/b&gt; The current error page you are seeing can be replaced by a custom error page by modifying the &amp;quot;defaultRedirect&amp;quot; attribute of the application&amp;#39;s &amp;lt;customErrors&amp;gt; configuration tag to point to a custom error page URL.&lt;br /&gt;&lt;br /&gt;
&lt;table class="" bgcolor="#ffffcc"&gt;

&lt;tr&gt;
&lt;td class=""&gt;&lt;code&gt;&lt;pre&gt;&amp;lt;!-- Web.Config Configuration File --&amp;gt;

&amp;lt;configuration&amp;gt;
    &amp;lt;system.web&amp;gt;
        &amp;lt;customErrors mode=&amp;quot;RemoteOnly&amp;quot; defaultRedirect=&amp;quot;mycustompage.htm&amp;quot;/&amp;gt;
    &amp;lt;/system.web&amp;gt;
&amp;lt;/configuration&amp;gt;&lt;/pre&gt;&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;&lt;/font&gt;&lt;/p&gt;</description></item></channel></rss>