Re: DBXL install on SP 2013 farm

Jim Cantwell — Wed, 23 Oct 2013 16:56:20 GMT

The DBXL v2.8 .NET 4 installer is required if using SharePoint 2013. We do not yet have a standalone ADWS installer for SharePoint 2013 at this time, but you can install and configure ADWS to use the SharePoint app pool. The asmx page will give a 500 error when launched, but you can manually fixup the web.config by removing the sectionGroup element (and its children) noted below:

...

</sectionGroup>

DBXL install on SP 2013 farm

justinr — Wed, 23 Oct 2013 16:02:38 GMT

I'm prepping a 2013 4-server farm to migrate our department's prod DBs and installed the DBXL 2.5 server package. I brought up the DBXL control panel site and added our license with the Admin Tool form. Everything appeared fine until I opened up a page in a webapp that's already been migrated to the new farm. I received a "The server is busy now. Try again later" message. Found a blog post elsewhere about this message that got me looking at the ASP.net performance counters on the WFE. I noticed that when I enabled the DBXL app pool and refreshed the Control panel page, the ASP.net Requests Current counter spiked to some ridiculous number, over 4 billion. The server had plenty of system resources available, but the request overload killed the webapps.

My hunch is that this has something to do with SharePoint 2013 running on the .net 4 framework. Running the DBXL app pool at 4.0 locks up everything, and @ 2.0 framework level just gives me 500 server errors on the control panel page (I assume from the v4/v2 mismatch).

Will we need to upgrade to v2.8 for DBXL/ADWS to work with a 2013 farm? We've got a few browser forms that utilize methods from the ADWS, so I need this working before I can complete the migration.

Qdabra Database Accelerator

Re: DBXL install on SP 2013 farm

DBXL install on SP 2013 farm