InfoPath Dev

I have DBXL 2.3. 

I have a SharePoint page in which I have a data table.  The data table is populated by a call to qdabrawebservice/querydb.asmx.  using the GetCloumnsXMLStrQuery. (Login is set to Don't attempt to authenticate.)

This works very well for me.  However when I release it to other users they are being prompted for their username and password three times before the screen opens and displays the data.  The same is true if they refresh the screen.

The users are in the correct permissions groups for the site/page, other pages without data connections on the same site are fine.  So I can only conclude that it is the data connection that is causing this.

Users may have either IE8 or IE6.  We have tried putting the SharePoint site into the Trusted list in IE. and this does not solve the issue.

Does anyone have any ideas about what the issue could be - or where I can start looking ? 

The permissions area of my Web.config for DBXL looks like - is there something missing ?

  <permissions>
   <groups useGlobalPermissions="true">
    <group name="Readers">
     <alias name="" />
    </group>
    <group name="Writers">
     <alias name="" />
    </group>
    <group name="Admins">
     <alias name="BUILTIN\Administrators" />
    </group>
    <group name="DbxlAdmins">
     <alias name="BUILTIN\Administrators" />
    </group>
   </groups>
   <providers>
    <!-- Add a connectionString attribute to the provider if it uses something besides the DBXL database -->
    <!-- connectionString="Integrated Security=SSPI;data source=(LOCAL)\SQLEXPRESS" -->
    <provider name="QdFlow" type="Qdabra.Dbxl.QdFlow.PermissionProvider, Qdabra.Dbxl.QdFlow" connectionString="Data Source=rudb001;Initial Catalog=QdabraSamples;Integrated Security=True">
     <doctypes>
      <doctype name="QdEmailFlow" />
     </doctypes>
    </provider>
    <!-- The below syntax is used to exclude one doctype from using the handler
     All other doctypes are included by default using an exclusion rule
    -->
    <!-- EXAMPLE -->
    <!-- <provider name="SpecialPermHandler" type="Customer.SpecialPermHandler">
     <doctypes exclusionRule="true">
      <doctype name="TestForm"/>
     </doctypes>
    </provider>-->
    <!-- The below syntax is used to include one doctype (and by default exclude all others) -->
    <!-- <provider name="SpecialPermHandler" type="Customer.SpecialPermHandler">
     <doctypes exclusionRule="false">
      <doctype name="TestForm"/>
     </doctypes>
    </provider>-->
   </providers>
  </permissions>

Thank you.

Catharine

Hi Catharine,

Trusted doesn't work for .NET and that applies to InfoPath forms with code. Your form has a lot of code so please remove from Trusted and add to Local Intranet and let us know if that fixes your issue.

I'm going offline now but Ernesto and the rest of the support team will be around to respond.

Hi,

The problem is nothing to do with InfoPath.

The problem occurs when opening a SharePoint screen which has a data connection to a DB via DBXL Query DB. - It is not opening any Infopath form.

The problem still exists.

Catharine

DBXL doesn't allow anonymous access, and from what I can find, the "Don't attempt to authenticate" option is designed to prompt for a password when anonymous access doesn't work.  Have you tried the Windows authentication option?

Hi

I have been doing some investigation and think I have got to the bottom of it....

It is not the data connection which is causing the problem.

Some time ago I got a file InfoPathOpen.js from you.  To be able to click on a hyperlink for an infopath file without getting prompted to open the file.  Put that on the server as suggested and put a <script type="text/javascript" src=".... reference in the form.

I obviously put it in the wrong place... I could access it but not all of the users.  I have now moved it and got rid of the 3 prompts. Phew !  Thank you for your help.

Catharine.