I am trying to create a LinqPad connection to a SharePoint Server's List Services. I have selected WCF Data Services 5.1 (OData 3) as the data context and http://sharepoint.host.com/_vti_bin/Lists.asmx as the URL
I get the following error: XmlException: For security reasons DTD is prohibited in this XML document. To enable DTD processing set the DtdProcessing property on XmlReaderSettings to Parse and pass the settings into XmlReader.Create method.
It doesn't matter if I use credentials or not.
What is the cause of this error? What is the soure of this error? I don't see how I can change the property in XmlReaderSettings.
Is this a security configuration on the server? Is there a solution or workaround to this problem?
Please try to connect to /_vti_bin/ListData.svc
Related
I'm trying to read data from Share Point online. I'm using KingwaySoft SharePoint Drivers on SSIS.
I'm getting below error even though with provided credentials
what could be the reason?
do I have to change the URL pattern?
Resolved
I have added /_vti_bin/listdata.svc/ at the end of the site URL.
like :
https://company0.sharepoint.com/sites/sfinfo/IT_team/_vti_bin/listdata.svc/
Thanks
The ideal service URL that you would need to provide should include the base site and subsite, if necessary, and no other details.
Give it a try and if the error persists, please reach out to our support team with the screenshot of the SharePoint connection manager configuration.
I am trying to publish a SOAP service registered in the Governance Registry through a proxy in WSO2 ESB. I get an error saving the proxy due to an incorrect schema location of the resources referenced in the WSDL.
In particular I get:
Caused by: javax.wsdl.WSDLException: WSDLException (at /wsdl:definitions/wsdl:types/xsd:schema): faultCode=PARSER_ERROR: Problem parsing '../../../../schemas/org/tempuri/1.0.0/TestSoap1.xsd'.: java.io.FileNotFoundException: /../schemas/org/tempuri/1.0.0/TestSoap1.xsd (No such file or directory)
When I search the WSDL in the Governance Registry the imported schemas have a location pointing to a relative path using "../../../{xsd name}", obviously the cause of the error. The solution seems to be to remap all the schemas locations to the registry internal keys (aka gov:/trunk/... and so on).
This behaviour does not make sense for me. The integration between ESB and GREG should be useful to use previously GREG imported WSDL when creating proxies. Am I missing something?
When you select a registry resource with dependencies, you need to specify them within the proxy service you are building. In the following example I show you the configuration that you need to perform in a proxy based on a WSDL that has an XSD as a dependency, and both are registered in the GREG.
<publishWSDL key="gov:/trunk/wsdls/org/example/www/util/auditoria/1.0.0/Auditoria.wsdl">
<resource key="gov:/trunk/schemas/org/example/www/util/auditoria/1.0.0/Auditoria.xsd"
location="../../../../../../../schemas/org/example/www/util/auditoria/1.0.0/Auditoria.xsd"/>
</publishWSDL>
I have deployed an Xpage in Bluemix and binded a no-sql xpage database to the app. Anonymous has manager access to both the database. Anyone can create a document but once created cannot open the he document. It gives the following error:
Error 500
HTTP Web Server: Command Not Handled Exception
Can anybody help?
From your comment I can read that you are just having an XPage to create a document. When you open it you reference it only by the UNID and not calling the .xsp page with the UNID like
doc.xsp?docid=892D819ECE966BF486257E9B0037DB01&action=openDocument
Either you calculate the opening link this way OR you create a corresponding form and set it's properties to open the XPage when accessed through the browser.
But as I said: without any code sample this is just a guess.
Try to add a definition to your XPages application in your XSP properties file:
xsp.domino.form.xpage.<NAME OF THE FORM>=<NAME OF YOUR XPAGE>
f.e.
Form="foo", XPage="bar"
xsp.domino.form.xpage.foo=bar.xsp
Alternativly, create your own VirtualPageTransformer: http://hasselba.ch/blog/?p=1028
I am having an issue using an OData SharePoint List Source with a dynamically changing connection string (inside the OData Connection Manager). The OData Source inside of my Data Flow Task fails to validate with the error message, “Cannot acquire a managed connection from the run-time connection manager” when executing the DFT from a parent package.
I have done some extensive Googling, and combed the forums relentlessly; however, I have not found anything that seems to offer a solution to this problem. Any help figuring out a solution would be greatly appreciated!
Here is the general flow of the main SSIS package:
Truncate staging table
Get all Site Collection URLs and their GUIDs from SQL Table
Execute Package Task for each site collection (foreach ADO loop container)
Extract data from UserInformationList (OData source)
Add a column for the GUID of this site collection
Load the data into staging table
etc. . .
Main Package:
Child Package Control FLow:
E-L UserInformationList DFT:
Package Output With Error Message:
When testing the entire solution, everything (tasks, parameters, variables, etc.) behaves properly until 3.1(see above), when the OData Source fails during validation. The only aspects of the source and connection manager that change are the URL and ConnectionString for the connection manager; the specific SharePoint list that I access on each site never changes. When the solution enters the child package, the URL and ConnectionString for the Connection Manager are properly set, prior to entering the DFT.
When testing the child package via the Execute Package Task, using hard-coded parameter values, the child package fails to validate.
When testing just the child package, there are no errors and the list information is stored in the database, as expected. However, with individual testing, the OData Connection Manager uses the default value of the package parameters.
Things I have tried so far:
Set DelayValidation to True
Changing the debugging runtime from 64 to 32 bit (and back again)
Use collection to specify the list (in the OData Source Editor)
Use resource path to specify the list (in the OData Source Editor)
Running the child package as a Farm Admin
Running the solution as Farm Admin
Other information:
SharePoint 2013
Data Tools for Visual Studios 2012
Microsoft’s OData Source for SQL Server 2012
i think you don't have access to the source sharepoint or you are not passing the right credentials thats why you are getting this error. Please use valid connection and test your connections.
I had the same issue while I was reading the URL for OData source from database. In my case, I was passing old value for URL which has changed in the SharePoint side that is, the DB had URL value http://sharepointsite/News but the actual site was modified by user to http://sharepointsite/NewsUpdated
So, check the passing URL value in your case in case you still having this issue
I had the same issue, and it looks like at the moment of starting for loop container, you need to provide a valid value for the URL variable, it will be overwritten this or the other way, but if I would go with "0" or null I would get the same error as you
For the first time I have stumbled upon a problem where the solution has not already been provided (completely) on SO, but I hope someone out there can help.
My problem is similar to PUT and DELETE in RESTful WCF Service cause 401 Unauthorized error .
That is, I have a WCF Data Service where I get a 401 whenever I try to do updates or deletes (read and post works without any problems). The difference to the abovementioned post is that I am not hosting my service in IIS but on Windows Azure, so I am not able to apply that solution.
I have the same problem (401: invalid credentials when attempting updates or deletes) on both a .NET client and a restlet client using the OData extension. However, on the .NET client I am able to resolve the issue by setting UsePostTunneling = true.
In my service I have set config.SetEntitySetAccessRule("*", EntitySetRights.All).
Does anyone know how I can resolve the issue for my restlet client?
First thing I would check is to see if you have PUT and DELETE verbs enabled in your handlers. Are you running this from a web role in full IIS or are you using Hosted Web Core (HWC), or something else? Usually, more than a 401, I see a 405 error because WebDAV is on the machine and PUT and DELETE verbs conflict there. You end up having to disable WebDAV for the app.
I would also check your authentication method in your web.config. I have seen the 'none' type cause issues, so change that to Forms.