InfoPath Dev

 Hi Guys,

 I am trying to add a listdata.svc to my infopath form, when i go to add it i get the following:

Could not open "url to listdata.svc"

 Infopath cannot open the XML document: "url to listdata.svc"

Not enough storage is availible to process this command.

I think this error is misleading, there are only 280 records, but i have tried with other lists with fewer items and still the same issue. The XML works in the browser just fine.

Please Help!

Hi Gristy,

I think it's only supported in InfoPath 2010. You must be using InfoPath 2003 or 2007, no?

Are you saving it as InfoPath 2010 Filler? If so, add a new data connection and choose receive and see if REST Web Service shows up as an option. If you are choosing that and you still have a problem, it's probably a bug.

 yes i am doing everything correctly just getting this error which is frustrating.

Please search the Microsoft Support site for a Knowledge Base article. This sounds like a bug.

 does not seem to work with SSL, enabled HTTP and it was working.

Not a complete solution but at least i tested what i had to.

Very interesting. We can debug this further if you are interested. Let us know.

I have the same problem; however, I must use SSL for some employees.  Basically I can work with rest within my domain fine; however, when I attempt to access a SP2010 Rest Service over https it fails telling me it cannot connect.

Any interest in helping me figure out why I cannot connect to rest over the internet?

I found my problem - see:

http://msftplayground.com/Lists/Posts/Post.aspx?List=5878e505%2Df9a8%2D4295%2D9d5b%2D056fe05f8e56&ID=89&Web=b057dbe4%2Df419%2D42c3%2D9205%2D7443e3274182

Can't find a solution yet other than to delete the yes/no calculated field.

 I am also having the same problem.  I can access the REST web service using an https connection directly but when I try and access it through InfoPath 2010 I receive an error that there is not enough storage to process this command.  Please advise as I was in the middle of putting a release in production when this issue came up.

Thanks.