InfoPath Dev

I'm trying to install the DBXL 2.0 trial on a new box for testing. It's Win 2003 R2, WSS 3.0, .Net 1.1, 2.0 and 3.0 all installed. We have external SQL boxes that we'd like to house the databases.

I get an error when I try to install the Web Service. It indicates that the initialization of the database has failed and to run DBXKLAdmin.asmx in order to complete. However, when I run that I get an error message saying that it's been excluded by Sharepoint.

Any help?

- Phil

Are you saying that the urlhttp://servername/QdabraWebService/DbxlAdmin.asmx gives you a Sharepoint message?

This link should give you a page titled 'AdminService'.

There is an InitializeDatabase method on the AdminService page which needs to run.

In the IIS manager, check the ASP.NET page for QdabraWebService. It should be using version 2.0.50727.

That's correct. The ASP.NET version is correct. The QdabraWebService installed under the DefaultWebSite, which is currently stopped (WSS 3 is using Port 80).

EDIT: When I stopped Sharepoint and started the Default site and tried to run the page, I received a "Service Not Available" error.

You will need to reinstall to the WSS v3 site, or another site which is enabled.

OK - That fixed the original problem.

Now when running the DAT tool setup, InfoPath indicates it cannot open the form because it requires Domain privileges and it is running under restricted. Does InfoPath have to be on the Server itself? I am running it from a client.

InfoPath is not required on the server.
Adding the server to your Local Intranet zone in IE should fix the problem. Once added to your Local Intranet zone, close IE and InfoPath and then try the DAT form again.

Working through this - the install doco is not the greatest ...

Where exactly on the Sharepoint server should the Manifest.xsf be published? Any particular form name?

Hi FearlessFreep,

Thank you for the feedback. We are definitely not satisfied with our documentation in the beta eval that you got. Improving documentation is the main remaining priority before we release V2. You should see documentation improve significantly in the final release (hopefully in the next month).

In the meantime, if you have specific feedback on what is bad or confusing, please let us know.

Where should the manifest.XSF be published?
What should the name of the form be?

When you open up the DBXL Admin Tool, do you see the DAT configuration? Send e-mail and we can walk you through it via Live Meeting or Webex.

----------------------------------------------------------
To publish a separate form to the database (i.e. not DAT)
1. save or publish the solution to your local hard drive (you'll see an XSN package appear in the location).
2. open the DBXL Admin Tool (DAT), and create a new configuration.
3. name the configuration and attach the XSN saved in step 1
4. click save to save the configuration

Now, you should be able to enterhttp://<server>/<QdabraWebService>/forms/<config name>/template.xsn into your browser to open the form from DBXL.