DBXL installation failing with Error Bootstrapping system doctypes - InfoPath Dev
in

InfoPath Dev

DBXL installation failing with Error Bootstrapping system doctypes

Last post 06-28-2011 01:29 PM by Jim Cantwell. 3 replies.
Page 1 of 1 (4 items)
Sort Posts: Previous Next
  • 06-28-2011 12:09 PM

    DBXL installation failing with Error Bootstrapping system doctypes

    This is the event log entry Log Name: Qdabra Source: Database Accelerator Date: 6/28/2011 3:06:02 PM Event ID: 0 Task Category: None Level: Error Keywords: Classic User: N/A Computer: dcvw-spprod01.choa.org Description: Error bootstrapping system doctypes Call to BoostrapSystemDocumentTypes failed. encountered a critical error and needs attention. Event Xml: 0 2 0 0x80000000000000 127 Qdabra dcvw-spprod01.choa.org Error bootstrapping system doctypes Call to BoostrapSystemDocumentTypes failed. encountered a critical error and needs attention. I have installed this on our Test Farm and it installed fine. The only difference between the 2 farms is the number of servers. I also made sure I was installing as the administrator.
  • 06-28-2011 12:17 PM In reply to

    Re: DBXL installation failing with Error Bootstrapping system doctypes

    Hi dspayne,

    How many webservers are there in the environment where the install is returning this error?

    Does the admin account you are installing with on the other farm have permissions to create DB's in the target SQL DB?

    Ted

  • 06-28-2011 12:21 PM In reply to

    Re: DBXL installation failing with Error Bootstrapping system doctypes

    Hi Ted, Thanks for getting back to me so quick. I just found the answer. I was using a url to our WFE's that are load balanced.
  • 06-28-2011 01:29 PM In reply to

    Re: DBXL installation failing with Error Bootstrapping system doctypes

    When installing on load balanced servers, the url of the site needs to resolve to the local server IP address and not the load balancer address.  That allows the requests being sent from the installer to be directed to the local machine and not the LB address.  If it gets routed to the LB address, it causes a machine hop and authentication fails.

    The easiest way for this is to edit the Windows hosts file, but you will need to read this KB on configuring the BackConnectionHostNames http://support.microsoft.com/kb/896861. 

Page 1 of 1 (4 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.