-
Sorry for the slow reply. If the logs do not show an error saving to SharePoint, let's setup a meeting to look at your server configuration.
-
Resolution Summary:
SharePoint was unable to make a secure connection for the webservice data connection (using HTTPS). It requires configuring SharePoint via Central Admin using the "Manage Trust" under Security.
Add the root certificate authority of the certificate you are using for your site.
-
Have you tried converting your data connection to a UDC? You will need to first create a data connection library if you don't have one.
-
You should see an error in the Qdabra eventlog similar to below if the file is already checked out:Caught exception saving document to SharePoint collection http://server/formlibrary. (DocType = 'TestDocType', DocId = 200) encountered a critical error and needs attention:Microsoft.SharePoint.SPFileCheckOutException: The file ...
-
I would first check the SharePoint web.config to verify that impersonation is on:
<identity impersonate="true" />
You may also check the app pool accounts configured in SharePoint Central administration. If accounts were updated directly in IIS Manager, SharePoint may have reset the accounts and caused some ...
-
Is the assembly one that you control? It sounds as if the assembly is executing some code during initialization which requires administrative access. It could be a log file is being created, or some other resource is being accessed requiring elevated permissions. If this is the case, once the assembly is initialized, other users ...
-
You may want to compare your settings with the Office Blog on this subject: http://blogs.office.com/b/microsoft-excel/archive/2008/03/24/setting-up-excel-services-to-refresh-workbooks-when-opened.aspx
You may also be seeing an issue with authentication and crossing the machine boundary. If the data source is on a different server, the ...
-
Add a location section like below in your root web.config (the folder where the QdabraWebService folder is), just before the enclosing </configuration>. This should prevent the attempted compilation of the Silverlight dll when accessing DBXL.
<location path="QdabraWebService">
...
-
What is your OS ?
Also, make sure IIS is configured to support ASP.NET and Windows Authentication.
Do you have pre-existing content on your IIS site which is accessible?
-
There are likely some settings in the parent web.config which are being inherited and will need to be explicity excluded for the QdabraWebService directory. Can you send the web.config from the SharePoint site to support at qdabra.com? We can take a look to determine what specific entries are causing this.