InfoPath Dev

Hello.

 Trying to install on a Win2K3 Enterprise server, running SQL 2005 and MOSS 2007.

However i get all the way through the configuration then recieve an error that it coudn't configure database, http 404 database couldn't be found.

 Can someone please help,

Hi OKWArchitects and welcome to the forum!

I am sorry to hear that you are experiencing an installation error. During the installation, there is a button to Test Connection which you can use to make sure the database name is correct. Please try to install again and test this. What are you specifying for your SQL 2005 database name? Is it installed locally or on another server?

Thanks!

Patrick,

 Thanks for the response.  The Test SQL option worked both pre your response and again when I tried this morning. Still no change.

 During the copying of files in the beginning, i also recieve this message "The specified path '/LM/W3SVC/1/Root/Forms' is unavailable. The IIS Might not be running or the path exists and is redirected to antoehr machine.

 I know it's running because my sharepoint is working.

Then the exact message after going through the settings, is "The installation failed, and the rollback has been performed. --> Error initalizing DBXL database. --> The request failed with HTTP status 404: Not Found.

 I'm assuming that the last message is related to the first.

Hi again,

Try unchecking Forms Viewer so that it doesn't install and see if this helps. Forms Viewer wants to use Forms and that may have already been created without access. At any rate, our Forms Viewer product does not need to install in order for you to try the SQL Web Service suite.

Same error message during the beginning portion of the install, then I removed Forms Viewer during the configuration, and recieved the same collection of errors

It sounds like it's unrelated to Forms Viewer. I haven't encountered the first error you mention, but the second error sounds like an error when DBXL is trying to modify permissions, probably related to the SQL instance.

Here is the sequence of events when DBXL installs, which might help us to narrow down the problem: database connection tested, web.config is created, Qdabra event log is created, registering with ASP, checking for Sharepoint, installing for Sharepoint (if present), QdabrawebService, Database creation, Trial License installation, Admin Tool published. During the initialization of the installation, the installer tests the creation of the databases QdabraSamples and QdabraDBXL.

Are there are errors or warnings in eventvwr? I've commonly seen warnings logged when DBXL tries to add a user to the SQL instance.

I'm getting the same error as the OP with using the same configuration.  At the beginning of the setup I get this error:

Please check the Application and Qdabra eventlogs for any additional information.  And if you are running MOSS 2007 with a different account than DBXL, you will need to add that account to the WSS_WPG group.

From the server's application log:

Event ID: 11314

Product: Qdabra Web Services Solution Pack v2.2 -- Error 1314. The specified path '/LM/W3SVC/769376297/ROOT/QdabraWebService' is unavailable. The Internet Information Server might not be running or the path exists and is redirected to another machine. Please check the status of this virtual directory in the Internet Services Manager.

Event ID: 11001

The description for Event ID ( 11001 ) in Source ( MsiInstaller ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Product: Qdabra Web Services Solution Pack v2.2 -- Error 1001. User cancelled installation, (NULL), (NULL), (NULL).

The server's Qdabra log shows the install information events and that's all.  I cancelled the install after receiving the error shown in the screenshot above.

Also, I'm running WSS 3.0 and not MOSS 2007 if that makes a difference.  I didn't see anything documented stating that it would.

It's too bad, this looked like a great product...

I would take a long, hard look at the IIS settings - is there anything irregular there? One of the biggest known problems is that ASP.NET is not properly configured but you've got MOSS so this is taken care of.

The other thing is the website: which one are you installing DBXL in? We recomment to always install into the same site as your main SP site (typically on port 80). Is this what you are doing?

Finally, there is the matter of identity: we install to run under NETWORK SERVICE by default but people often configure their servers to run under a different user - check the SharePoint's appDomain to see who is running it (properties, then Identity tab).

Let me know if this helps... (other things to look out for: do you have HTTPS? DBXL works with HTTPS but there might be some configuration hiccups. Do you have more than one IP/hostname? This is known to have caused problems in the past)

The error message indicates it is being installed to the default website (ID is 1).  The WSS installation should be disabling the default website and creating a new site for WSS.  Make sure that you select the WSS site when installing DBXL.

I'm trying to install it to the same website as the sharepoint site on port 80.

The identity for the application pool is set to a domain user account which I'm using during the install.

I do have multiple NICs and multiple IP addresses on the server, no https and a single windows hostname (multiple dns hostnames though)

Make sure the domain account you are using for the webservice is added to the WSS_WPG group.