InfoPath Dev

Hello Patrick, Clay, Jim et al,

I'm trying to install Database Accelerator 2.1 Developer on a SharePoint 2007 server, using an MSSQL 2005 Standard server install on another machine as the database server. Both machines are running Windows Server 2003.

Here is the error I am currently getting:

Event Type:    Error
Event Source:    Database Accelerator
Event Category:    None
Event ID:    2000
Date:        12/14/2007
Time:        2:13:55 PM
User:        N/A
Computer:    SHAREPOINT
Description:
Error initializing DBXL database.
The request failed with HTTP status 401: Unauthorized.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


Here are the installation settings I am using for the install:

Installation Address
    * Default Web Site
    * QdabraWebService

Logon

    * predefined (Network Service)

SQL Server
    * server name = <IP address of server>
    * authentication = SQL Server Authentication
       -- Username = dbxlAdmin
    * database = QdabraDBXL
    * (TestConnection Successful)

Domain Security
    * DBXLAdmin = Builtin\Administrators
    * Set Global user permissions = checked
    * Admin group = builtin\administrators

Forms Viewer
    * Account = Administrator    (Local admin on this server... Same account as logged into while installing)

Active Directory Service
    * LDAP://DC=<Local domain name>

Database Enumerator
    * server name = <IP address of server>
    * authentication = SQL Server Authentication
       -- Username = dbxlAdmin
    * database = (blank, for default)


Troubleshooting steps to date (I tried to address questions you have had for others in the forums):

  o Earlier on in the install process, I was getting the same error ( The installation failed, and the rollback has been performedàError initializing DBXL databaseàClient found response content type of “text/html”;charset=utf-8”, but expected “text/xml”), as in this post:
     -- http://www.infopathdev.com/forums/p/6827/24977.aspx
     -- As per Patrick's posting -- http://www.infopathdev.com/files/folders/dbxlsupport/entry20602.aspx:
        o I made the change in C:\Inetpub\wwwroot\QdabraWebService\web.config, after the first part of the install (Web service install).
     -- At this point, started to get the authorization error on install (above).

  o By default, the Sharepoint installer deactivates the Default Website, and takes over port 80 without a virtual host header.
     -- Configured the Default Website with the virtual host header 'dbxl', then configured (temporarily), the hostfile on the Sharepoint and DB servers with an entry for this virtual host header.     

  o At the partway point (after the WebService was installed, before rollback did the uninstall), checked that I could get to the Web Service page (http://dbxl/QdabraWebService/default.htm)
     -- Sharepoint changes the default Guest account to IUSR_SHAREPOINT... Gave this user Modify access to all of C:\Inetpub\wwwroot for now.
     -- Also gave Network Service modify access to C:\Inetpub\wwwroot, and double-checked that the local Admin had 'Full' privs.
     -- In IIS console, turned off Domain authentication for the Default Website
     -- At this point, could connect to http://dbxl/QdabraWebService/default.htm, and click on links, without getting a login prompt.

  o Double-checked privs for the dbxlAdmin account on the DB server:
     -- Gave account dbcreator and sysadmin privs
     -- For now, also mirrored sa privs on the master, model, msdb and tempdb...
     -- Logged into the Database from another machine using SQL Management Studio, created a DB, then added a table.
     -- Confirmed that there are no named instances of MSSQL, I'm using the default instance.

  o Changed the Default Web Server .NET version to 2.0.507272.
  o Confirmed that the DbxlAppPool1 Web Service App pool was running, Checked for errors in the IIS Log (none).
  o Changed WebDAV setting for Devault Website to 'Allowed'
  o From this posting: http://www.infopathdev.com/forums/t/5678.aspx
     -- Stopped all Sharepoint services, Sharepoint websites, Repatched web.config after service install, re-ran install... Same Error.

  o The only error I am seeing during the install is the one I posted above, from the Qdabra Event Log, and a matching entry under the Application log for MSIInstaller.
  o The Web Service IS being installed, the Database is NOT being created.
  o There doesn't appear to be anything useful in the IIS log at C:\WINDOWS\system32\LogFiles

-----------


  This obviously looks to to be a permissions error, but I cannot seem to figure out where the error is originating. Any ideas?

Thank you,

--Jason

Hey Jason.

It can get a bit tricky when the SQL server is remote.  I am assuming the account you are logged in and doing the installation with is a local admin on the SharePoint server. Does it also have permission to create a database on the remote server? Is it a domain admin?

Here is the documentation from the installation instructions.

1.   SQL Authentication is preferred but                                           
2.   Windows Authentication will work if you give the server machine account where the Web Service is installed sysadmin access to SQL instance 

So either you need to give your DBXL / SharePoint machine account access to the database or use an SA account instead.

 Hi Clay,

  Thanks for replying so quickly...

   I am using SQL authentication (I must not have been as clear as I thought)... And I setup the dbxlAdmin account that I am using with the same permissions as the sa account (at least for the install, I'll reduce that as I can later).

 
  Likewise, actually using the sa account yields  the same '401: unauthorized' error.

Thanks again for the help,

--Jason
 

Right I knew you were using SQL but thought I would make sure you had that info.

Are you using the IP address or the name for the SQL Server? I do not think that should matter but typically I always use name.

Jim has the most knoweldge on the interaction.  I think he is in a meeting at the moment but I will let him know to check this out and get back to you.

The error you received "HTTP status 401: Unauthorized." indicates a problem calling the webservice, not with database access.

When you get the error, leave the error message displayed, and try to navigate to http://servername/QdabraWebService/default.htm and let me know if you can access this page.

At this point, before the rollback, copy the /QdabraWebService/web.config and email to me Jim.Cantwell@nospam-Qdabra.com (remove nospam-).

 Hi Jim,

  Thanks again to both of you for looking at this for me...

   As I mentioned, I can get to the http://servername/QdabraWebService/default.htm page, and I made sure that the sublinks off of that page weren't causing any authentication errors (there had been issues with the Sharepoint anonymous user, as I mentioned in my original post).

  I'll send you the file in a few minutes, just need to do the first part of the install, and update the <httpModules> section.

Thanks!

--Jason 

The httpModules section does not need to be updated. That change only applies to DBXL v2.0.

The httpModules section should look like the following:

  <httpModules>
   <clear />
   <add name="OutputCache" type="System.Web.Caching.OutputCacheModule"/>
   <add name="WindowsAuthentication" type="System.Web.Security.WindowsAuthenticationModule"/>
   <!-- Uncomment the following remove if using the QdabraWebDAVRoot handler in the root web.config -->
   <!-- <remove name="QdabraWebDAVRootHandler"/> -->
   <!--
   Add the following line to the root web.config httpModules section for your site if you require Windows Vista support
   <add name="QdabraWebDAVRootHandler" type="Qdabra.Dbxl.WebDAV.WebDAVRootModule, Qdabra.Dbxl.WebDAV, Version=2.0.0.0, Culture=neutral, PublicKeyToken=016fd7c1933d6163" />
   -->
   <add type="Qdabra.Dbxl.DocumentRetrieval.WebDAVModule,Qdabra.Dbxl.WebService" name="WebDAVModule" />
  </httpModules>

The information you provided indicates the machine name is SHAREPOINT.  The web.config url shows http://dbxl

  <!-- The DocumentHandlerPath is the public URL (minus docid/filename) -->
  <add key="DocumentHandlerPath" value="http://dbxl/QdabraWebService/Documents" />
  <!-- The TemplateHandlerPath is the public url (minus typename/filename) -->
  <add key="TemplateHandlerPath" value="http://dbxl/QdabraWebService/Forms" />

Do you have some hostheaders configured that might be causing this?  If the machine name is SHAREPOINT and no hostheaders are defined, thhe DocumentHandlerPath and TemplateHandlerPath should begin with http://sharepoint/QdabraWebService/

Hi Jim,

  Ah... Good to know about the httpModules and 2.1. Without the changes I had been making, my web.config looks just as you say. Unfortunately, I'm still getting the 401 error.

  As to the machine name...

  By default, the Sharepoint installer seems to disable the Default Website, and take over the Default, non-host-header IP (and thus hostname) for the server. In order to install the Qdabra web service into the Default Website (as opposed to the sharepoint website, which I did not want to use), I needed to use a host header configuration. I used 'dbxl', and added a record to the hostfiles of both the Sharepoint/DBXL server and the database server. (I'll change this to a DNS A record on the AD server later, once all this is up and running).

  I mentioned this in my initial post, but it was mixed in with everything else, and probably wasn't clear.

  The web service does show up on http://dbxl/QdabraWebService/default.htm, but has this config broken something else, do you think?

Thanks again,

--Jason 

 Hello all... just bumping this again... Still having issues.

--J 

WHat happens if you try the following url: http://dbxl/QdabraWebService/DbxlAdmin.asmx ?

Check that the DBXL webservice is configured to use a DbxlAppPool and configured for .NET 2.0.  This should normally be the case when Setup runs.