InfoPath Dev

I initially had "invalid application path" under IIS manager when I clicked 'test connection'.  Not sure why.... I decided to uninstall and on reinstall I get login prompt looping.

 I checked to see if DisableLoopbackCheck was set to 1 and it was but unable to get past login after login at end of installation.

     Error Log:

 Log Name:      Qdabra
Source:        Database Accelerator
Date:          9/20/2011 2:58:20 PM
Event ID:      0
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      ########
Description:
Error bootstrapping system doctypes
Credentials were needed but the user cancelled the credentials prompt. encountered a critical error and needs attention.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Database Accelerator" />
    <EventID Qualifiers="0">0</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2011-09-20T20:58:20.000000000Z" />
    <EventRecordID>163</EventRecordID>
    <Channel>Qdabra</Channel>
    <Computer>######</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Error bootstrapping system doctypes
Credentials were needed but the user cancelled the credentials prompt. encountered a critical error and needs attention.</Data>
  </EventData>
</Event>

Hi Shane,

Looks like an issue with your SQL permissions. When we installed last Friday I remember we had to be very careful to enter the correct credentials (for example, to your SQL server, which was on a different box). We're scheduled for 1 hour tomorrow at 1pm Pacific. Please send us email if you need more immediate assistance.

Regards,

 Hi,

 Was there are resolution to this problem?  I am attempt to reinstall DBXL to a new WFE and when it reaches the "bootstrapping system document types" it continually prompts for credentials and I cannot proceed regardless of what credentials I use.

 I have compared SQL permissions to the previous WFE/DB and they appear to be the same.

 Steve

Hi,

On searching our records, it seems the solution is to add the DisableLookbackCheck.

On load balanced servers you might encounter an issue installation DBXL; this is an issue encountered for any web service, not just DBXL. The issue is well described in the following link:

http://blog.crsw.com/2008/10/14/unauthorized-401-1-exception-calling-web-services-in-sharepoint/

Microsoft Support also discusses the issue here:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;896861

To install DBXL:

• Add the DisableLoopbackCheck registry entry discussed in this Microsoft KB article. Note: you will need to reboot your server before the DisableLoopbackCheck takes effect.

• Be sure to add your load balanced host name for your web farm to the Hosts file on each front end web server. Use the loop-back IP address (127.0.0.1). This will ensure that each web server looks at itself to access the web services preventing any trips back out to the load-balancer – and possibly calling the web service another web server in the farm. This will be much less efficient.

If this problem appeared to be inconsistent (sometimes erroring, sometime successful), this is most likely due having multiple web servers. The call to the web service will be successful if by chance the load balance redirected the call to the same (self) web server to access the web service. It will fail when trying to call across to a different web server.