locked
Applications adding rows to SharePoint lists and security policies RRS feed

  • Question

  • Platform MOSS 2007 32 bit, Win 2003, InfoPath

    Third party application: AgilePoint environment

    A developer has been creating and modifying InfoPath applications, installing them into a MOSS forms library, and getting them to run for the past year.

    In the past two months, he has begun using an AgilePoint part which takes data from a workflow and adds it to a SharePoint list.

    This has been working - until yesterday.

    Yesterday he attempted to install the application on a new SharePoint farm. One of the steps is to use an AgilePoint application to establish a "data connection" type of info between the workflow engine and his sharepoint list.

    Whereas this has always "just worked" before, now he is getting an error saying that the operation being requested by the application violates a security policy and that he has to take additional steps.

    When he contacted the vendor, he was told this was a SharePoint error and that he needed to address that problem from the SharePoint side.

    When he went back to his development environment, and attempted to re-establish the same connection, he now gets the same error there.

    We have not changed SharePoint itself. Of course, OS patches, etc. are applied by the OS group regularly.

    He has applied a service pack to the vendor software, but as I said, requests for assistance from the vendor redirect him to solving the problem on the SharePoint side.

    In web searching the words of the error, we have seen several postings talking about modifying the SP web.config file to change the security policy from WSS_Minimum to something else - either WSS_Medium or full, or to create our own security policy.

    We are unfamilar with security policies. However, on the test machine, when we changed the security from minimum to medium, it made no difference in this case.

    I have recommended the developer research creating his own security policy. I just wanted to check with other admins to see if they have encountered similar things with other third party tools - suddenly finding the act of creating a data connection being stopped as violating security policy, and what you found was necessary to do about it.

    Thank you for your help. 

    Thursday, September 5, 2013 12:13 PM

Answers

  • thank you for your reply.

    We actually started by trying to talk to the vendor - they informed us that this was a sharepoint problem.

    However, in the past few days, after pressing the vendor for more info, it was discovered that what we were experiencing was due to a bug in a service pack upgrade that we had applied a few weeks ago. They supplied a fix and the process yesterday was found to be working again.

    Thank you again for your help.

    • Marked as answer by lwvirden Thursday, September 12, 2013 11:55 AM
    Thursday, September 12, 2013 11:55 AM

All replies

  • It might also be an idea to post this question within the vendor forums http://forum.agilepoint.com/

    I'm not too clued up on AD Group Policies but it may be linked to any changes in them made by a Networks / Infrastructure / AD team.  Have you a change control log that you can peek into for any changes made on the day that your issues started to happen, or a team member you can approach?

    Monday, September 9, 2013 11:48 AM
    Answerer
  • thank you for your reply.

    We actually started by trying to talk to the vendor - they informed us that this was a sharepoint problem.

    However, in the past few days, after pressing the vendor for more info, it was discovered that what we were experiencing was due to a bug in a service pack upgrade that we had applied a few weeks ago. They supplied a fix and the process yesterday was found to be working again.

    Thank you again for your help.

    • Marked as answer by lwvirden Thursday, September 12, 2013 11:55 AM
    Thursday, September 12, 2013 11:55 AM
  • No problem.

    Are you in a position to tell us what the application was?  Might come in handy for others that might experience the same scenario?

    Thursday, September 12, 2013 12:15 PM
    Answerer
  • We were writing an InfoPath form and attaching it to an in-house written Agilepoint workflow template. Agilepoint is a third party add on workflow package. We had applied the version 5.0 service pack 4 a few weeks prior to our problems, and spent a lot of time trying to find where in our code, or our MOSS SP 2007 farm the problem was originating. Once we got the fix for SP4, things went smoothly.
    Friday, September 13, 2013 7:39 PM