InfoPath Dev

Hi All,

I have run again into a problem, which I have resolved in the past, but can not find a reference this time. SP 2010 Enterprise, IP 2010.

I have had successfully injected a SPD Workflow Task Form with qRules 4.3 and used to successfully submit a number of sub-tasks, actions to a separate SP List.

The form was working without problems until this weekend, when unexpectedly, it started giving errors, but mostly hiding the People picker control used in the form. from qRules only SubmitToSharePointList and ClearErrors command are used.

I tried re-publising the form, but the attached message started showing. Tried re-injecting (licensed version), but the issue remains. This is my current problem.

Sandbox services enabled and I even restarted the server. As it is a Workflow Task Form, as you may know it does not allow adding custom code, thus no Programming tab in Infopath.

Besides the qRules injected code, there is no other custom code, just rules. Even tried removing the qRules data connection, re-injecting. Injection is completing with skipping over some steps but successfull anyway. There is a secondary data connection pulling data (those created actions form a separate list), but it has not been a problem in the past.

Originally the form was injected with the trial version, but as stated, was re-injected later with the licensed version and was working without problems. The form was working in the browser (IE).

Any feedback would be appreciated.

Can you check the SharePoint Log files for the time where you are publishing and getting the error?

Hi Hilary,

I did not see anything related to the publishing. No events logged when Least Level set to  warning.

 This was in the log files generally found here:

c:\Program Files\Common Files\Microsoft Shared\web server extensions\14\LOGS
OR
c:\Program Files\Common Files\Microsoft Shared\web server extensions\12\LOGS

Update: After adjusting the logging settings to lower levels and filtering the logs for infopath services and category to "Conversion and deployment" I was able to isolate all related publising events:

Listing the sequence of events logged for a single publishing attempt below. I have been able to isolate many regular/successful publishing events of Workflow Task forms without qRules, as well as several erroneous ones with qRules.

 Well - when you publish this form with code (or qRules), it appears to have to be sandboxed - and for some reason the sandboxing is failing. Since workflow forms don't support code, I'm kind of surprised that SharePoint was letting you publish this to begin with....

Not only it was letting me:

 1)  It was also working without further issues in the browser (100%). Even the "claim task" buttons on group assignments.

  2) Outlook Task Forms did not execute the SubmitToSharepointList code, but

  3) If I open the Form Library document from SP in Infopath client, see the Task button, open from there - it was working perfectly again, even the "Claim Task".

 - it was working with the trial version (posted on this forum, too) and it was working for about a month after being re-injected with the Licensed version.

 It was also one of the reasons we got qRules.

 I am still trying to find if there have been any server setup changes, but found nothing so far. Also restarted sandbox services a couple of times.

 I would make a wild guess here, that it might be related to the trial-license originally injected was about to expire mid March. As stated, The same work-form was re-injected with licensed version.

Both versions, injector screen, stated: "Version: 4.3.4738.26423". I would expect those to be different, but was assured all is good.

Update:

   case 1) Attempts to open in the browser fail with "

 Any insight would be appreciated.

 Just found, that "SharePoint 2010 User Code Host" Windows service on the Sharepoint server is Not Running, even though on CA page "Microsoft SharePoint Foundation Sandboxed Code Service" states it is started.

Re-starting the windows service stops within seconds from start.

Re-starting from CA, does NOT start the Windows service above.

Stopping the SP service on CA and attempting to start it the corresponding windows service, changes nothing, the Windows service again stops within seconds if not right away.

Can I see the form? You can attach a copy under the Options tab.

When the license expires in a trial version, the error node will simply provide a message about the trial having expired. The March trial expires on the 15th.

Can you temporarily put the command & result node on your form along with the error node and try a simple command like GenerateGuid?

EDIT: Just saw your latest post about the sandbox service.

Attached:

 - A new sample Task form with just injected qRules 4.3, attached to a SPD workflow with a customized by IP Task form.

 - First picture when run on the client(preview) and hitting the qRules button, shows that a Guid was generated.

 - Second picture, when opening the form by clicking "Open Task" from the Form Library Form, from SP (open in Infopath the form, not preview mode), the library has the SPD workflow attached with the Task form.

   Clicking the same qRules button again provides a sample Guid# by using GenerateGuid from qRules - working.

- Attempt to open in the browser, error as before. Publishing is the primary issue I believe (see previous post)

I'm not trying to be difficult - I'm just trying to understand and help you narrow things down. So, your new workflow form with qRules in it works correctly for a simple command but still can't be opened in the browser? I think that's what you are saying. But your original workflow form errors in filler and also can't be browser enabled - and it sounds like your sandbox service is shutting down spontaneously as well?

All help appreciated. I am trying to publish my findings as soon as I find anything interesting.

All my original workflows tests, unchanged for weeks started showing the same error.

Issue has been resolved!!!!

All Working again: Customized with Infopath+qRules SPD Workflow Taskform - works in browser.

1) Primary cause is believed to be broken performance monitor counters. Right after rebuilding those and restarting server the  "SharePoint 2010 User Code Host"

 Windows service successfully restarted and running stable. The following link proved helpful, in our case at least.

http://answers.microsoft.com/en-us/windows/forum/windows_7-performance/perfmon-problems-unable-to-add-counters/e90f231d-0014-457d-8b1f-5f342971597a?auth=1

Now all previously published Workflow Task forms, utilizing qRules started working again, some without needing any re-publishing.

Re-publishing the Task Forms to the same Worlflow Tasks lists (Multiple custom content types, one for each Approval Step in the Workflow) was successful from Infopath and running GREAT.

2) Additional: Another helpful article, which I found and checked matching all settings, excerpt and link below:

 Wonderful - thanks for posting back w/ all this additional info!