InfoPath Dev

hi guys

windows 2008 r2/ sharepoint 2010 with DBXL

windows 2008 r2/ sql server 2008 r2

i created a form library first and tried to map it in DAT

why do i get the following error ? pls help

DAT is opened thru default address

DBXL app pool account is a member of the WSS_WPG group

 

 

One option we could try is to allow DBXL to create the Form Library. This means:

1. Let's assume your form library already exists at http://<servername>/<formlibname>/Forms/AllItems.aspx

2. Delete the form library

3. Return to the SharePoint mapping in DAT and enter the URL, for example: http://<servername>/<formlibname>/

This should allow DBXL to create the form library, making sure you have checked Publish Library and XSN.

Let us know if this still produces an error. Thank you!

got the same error message.

but the form library was created. i went to advance setting and checked "Open in browser"

went back to and clicked add document. lo and behold an old "form 44" opened up in infopath designer .

now what do i do ... thanks for helping

You mention in your original post that DBXL and SharePoint are on the same machine. Was DBXL installed to the SharePoint - 80 site?

 yes it was.

Would you be able to attach the XSN to this forum post? I'd like to try a ShP mapping using your XSN, on one of our machines. Thanks.

will do as soon as i get to work tomorrow. thanx

 

Thank you for the XSN. On one of our machines, where ShP mapping works for other forms, I get the same error you do. In addition I see that the XSN generates some eventvwr errors. At the moment, I do not know why this XSN is causing this error but we are investigating.

Can you try creating a doctype with ShP mapping using the attached XSN? (which I confirmed works on our end) Please let us know of your result. Thank you.

We have noticed that the manifest has some relative paths. We tried to address this in a December build of DBXL v2.4, but it may be that your copy is previous to that.

The workaround (which I have tested on one of our machines) is to open the XSN in design mode, select File > Save As, and save the xsn to your local drive. Then attach that to DAT.

Here is the manifest issue >

Original:

    <xsf:submit caption="Submit" disableMenuItem="no" onAfterSubmit="close" showStatusDialog="no">
        <xsf:errorMessage>The form cannot be submitted because of an error.</xsf:errorMessage>
        <xsf:webServiceAdapter wsdlUrl="../../QdabraWebService/DbxlDocumentServiceEx.asmx?WSDL" queryAllowed="no" submitAllowed="yes" name="Main submit">
            <xsf:operation name="SubmitDocument" soapAction="http://qdabra.com/webservices/SubmitDocument" serviceUrl="../../QdabraWebService/DbxlDocumentServiceEx.asmx">
                <xsf:input source="Submit.xml">
                    <xsf:partFragment match="/dfs:myFields/dfs:dataFields/tns:SubmitDocument/tns:xml" replaceWith="/" sendAsString="yes"></xsf:partFragment>
                </xsf:input>
            </xsf:operation>
        </xsf:webServiceAdapter>
    </xsf:submit>


After File > Save As to local drive:

    <xsf:submit caption="Submit" disableMenuItem="no" onAfterSubmit="close" showStatusDialog="no">
        <xsf:errorMessage>The form cannot be submitted because of an error.</xsf:errorMessage>
        <xsf:webServiceAdapter wsdlUrl="http://kotcshare/QdabraWebService/DbxlDocumentServiceEx.asmx?WSDL" queryAllowed="no" submitAllowed="yes" name="Main submit">
            <xsf:operation name="SubmitDocument" soapAction="http://qdabra.com/webservices/SubmitDocument" serviceUrl="http://kotcshare/QdabraWebService/DbxlDocumentServiceEx.asmx">
                <xsf:input source="Submit.xml">
                    <xsf:partFragment match="/dfs:myFields/dfs:dataFields/tns:SubmitDocument/tns:xml" replaceWith="/" sendAsString="yes"></xsf:partFragment>
                </xsf:input>
            </xsf:operation>
        </xsf:webServiceAdapter>
    </xsf:submit>

Can you let us know your build of DBXL v2.4? A screenshot of the DAT footer should show this data. This will tell us if we should upgrade you.

Also let us know if the workaround works.

Thank you.

hi

 

Tested the above mentioned method. that is go "design mode" and "save as".  That works else errors out.

So i guess an upgrade is in order.

 

You will be receiving our purchase order soon. pls dont let me down guys. i will be in deep trouble if i dont get this working for the company :) . thanx.

 

I'm sorry; what do you mean by "That works else errors out"? Are you getting the same error, or a new error, or did the workaround solve the issue?

If you'd like the most recent version of DBXL v2.4, it can be downloaded from Qdabra.com. Then uninstall DBXL from your server, and install the latest, making sure to check the checkbox for "Use existing databases".

the first down load of DBXL was on 26th dec, 2010.

i downloaded again today and reinstalled. i have noticed that both the downloaded files have the same name. so i guess i was using the latest DBXL which is producing this problem.

it works the way you said above. go to  "design mode" and "save as".  and also not all the time. sometimes i have to close infopath designer. right click on the XSN file and click design mode and do the "save as" . its is a little bit frustrating.

 

Hi Harishu,

Rest assured that you will get a working solution. We have many people using the latest release and there are no blocking bugs that we know of. Of course, we will fix any blocking issues that come up, but my first guess is that this may be a config issue.

What time zone are you in? Can we set up a Live Meeting to debug this with you? Please email Support (at) Qdabra (dot) com and we can arrange something for tomorrow.

Best regards,

Hi again,

OK, I looked into this and we did drop a hotfix for the relative path issue on 12/10 but we haven't uploaded this to our trial download site yet. I'm guessing that may be because we still haven't had time to test it. Anyway, I've asked Mel Balsamo to send you the latest DBXL v2.4 drop from 2010-12-10 (you can verify the date of yours via the lower left-hand corner of DAT). Please uninstall and reinstall and let us know if this changes the behavior at all.

More soon,