Hi,

I have tested "inplace upgrade" of SharePoint Services v 3.0 ( WSS 3.0 + DBXL v2.3) to SharePoint Foundation (Foundation + DBXL v2.3).  The Foundation works without any problem, but we are not able to keep DBXL, it does not work after upgrade of SharePoint.  I am wondering if there is any wokraround to keep DBXL in the process of "inplace upgrade of SharePoint" by modifing web.config file or some other files of DBXL or not.  Thanks

Hello Mr. Oka,

 Thank you for getting in touch with us.  I've notified our support team of your question and somebody should be looking into it soon.

Regards,
Jimmy Rishe

Could you tell us specifically what behavior you are encountering when you try to use DBXL after the upgrade?

The first item to check is that the QdabraWebService virtual directory still shows up under the website.  Then check that the DBXL application pool is set correctly (it should be DbxlAppPool{siteid}).

Thank you for the reply, and sorry for my late reply.

To duplicate issue I have tried to test upgrade process, but now I have problem with SharePoint mapping on DBXL v2.3 and WSS 3.0.

The below is a copy of Error in event view;

--------------------------------------------------------------------------------------------------- 

An error occurred while setting up a SharePoint collection mapping with the adminstrative tool.
This could be a user error. In case it is a system problem, error details have been logged.

SharePoint URL:
http://sv3459/TestForm1

Exception:
System.Net.WebException: The remote server returned an error: (405) Method Not Allowed.
   at System.Net.WebClient.UploadDataInternal(Uri address, String method, Byte[] data, WebRequest& request)
   at System.Net.WebClient.UploadData(Uri address, String method, Byte[] data)
   at Qdabra.Dbxl.Domain.SharePointMethod.EnsureFormLibraryAndPublishXsn(String qdabraWebServiceUrl, SharePointListMap mapping, ICredentials ssoCredentials, DocumentTypeProperties docTypeProperties, ISharePointXsnTemplateProvider templateProvider)
   at Qdabra.Dbxl.Domain.SharePointObjectModel.EnsureFormLibrary(String qdabraWebServiceUrl, SharePointListMap mapping, DocumentType docType, ISharePointXsnTemplateProvider templateProvider)
   at Qdabra.Dbxl.WebService.Implementation.ServiceImplementation.UpdateSharePointListMappings(DocumentTypeInfo docTypeInfo, DocumentType docType, Session session)

Stack Trace:
   at System.Net.WebClient.UploadDataInternal(Uri address, String method, Byte[] data, WebRequest& request)
   at System.Net.WebClient.UploadData(Uri address, String method, Byte[] data)
   at Qdabra.Dbxl.Domain.SharePointMethod.EnsureFormLibraryAndPublishXsn(String qdabraWebServiceUrl, SharePointListMap mapping, ICredentials ssoCredentials, DocumentTypeProperties docTypeProperties, ISharePointXsnTemplateProvider templateProvider)
   at Qdabra.Dbxl.Domain.SharePointObjectModel.EnsureFormLibrary(String qdabraWebServiceUrl, SharePointListMap mapping, DocumentType docType, ISharePointXsnTemplateProvider templateProvider)
   at Qdabra.Dbxl.WebService.Implementation.ServiceImplementation.UpdateSharePointListMappings(DocumentTypeInfo docTypeInfo, DocumentType docType, Session session) 

-------------------------------------------------------------------------------------

Somehow, SharePoint is creating the above form library.  But when I create a form from the library, I get error message.

From DAT (DBXL) I can create a document.

Please advise me. 

I skipped SharePoint mapping, then I went to upgrade process.

 I hope there may be some workaround.

Thanks

-------  Error Page of http://server/QdabraWebService/default.htm -----------

Line 112:      <remove verb="GET,HEAD,POST" path="*" />
Line 113:      <add verb="GET,HEAD,POST" path="*" type="Microsoft.SharePoint.ApplicationRuntime.SPHttpHandler, Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" />
Line 114:      <add verb="OPTIONS,PROPFIND,PUT,LOCK,UNLOCK,MOVE,COPY,GETLIB,PROPPATCH,MKCOL,DELETE,(GETSOURCE),(HEADSOURCE),(POSTSOURCE)" path="*" type="Microsoft.SharePoint.ApplicationRuntime.SPHttpHandler, Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" />
Line 115:      <add verb="*" path="*_AppService.axd" validate="false" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
Line 116:      <remove verb="*" path="*.asmx" />

----------------------------------  End -----------------------------------------------------------------------------------------------------------------------------

Please email us your SharePoint and DBXL web.config files.

Thanks,

Jim

The cause of the 405 "Method not allowed" with SharePoint mapping is likely that having WebDAV role installed on the server.  Removing the WebDAV role from the server should fix the SharePoint HTTP 405 errors.  There are known issues with SharePoint servers having the WebDAV role installed.

Thank for the live meeting, Jim.

The workaround to get back DBXL was very simple!  For other users, I posted what you did for us.

Open web config file of SharePoint, and comment out from line 111 and 116 between <httphandlers> like below;

<httpHandlers>
      <!--
      <remove verb="GET,HEAD,POST" path="*" />
      <add verb="GET,HEAD,POST" path="*" type="Microsoft.SharePoint.ApplicationRuntime.SPHttpHandler, Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" />
      <add verb="OPTIONS,PROPFIND,PUT,LOCK,UNLOCK,MOVE,COPY,GETLIB,PROPPATCH,MKCOL,DELETE,(GETSOURCE),(HEADSOURCE),(POSTSOURCE)" path="*" type="Microsoft.SharePoint.ApplicationRuntime.SPHttpHandler, Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" />
      <add verb="*" path="*_AppService.axd" validate="false" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
      <remove verb="*" path="*.asmx" />
      <add verb="*" path="*.asmx" validate="false" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
      -->
    </httpHandlers>

That's it, right?

Also, I have tested SharePoint mapping after I got back DBXL without WebDAV feature in IIS.  Then, I succeeded SharePoint mapping this time as you saw. 

Thank you so much.