InfoPath Dev

I have a form with about 200 fields that I need to make read-only after it is submitted. I know this is feasible (I followed this guide, but I am getting an error when copying over my fields to the read-only view. Publishing works up until a certain point, and then it seems after a certain number of fields I become unable to publish, with the message "The form template has been published to the server but it can only be opened in InfoPath filler. The sandboxed solution could not be activated. The custom code in the form cannot be run. The functionality may be deactivated on the server...There may be additional details in the Design Checker task pane". What does this mean and could it be a result of some maximum allowed number of fields in a form?

 It is more likely that the SPUCWorkerProcess thread is timing out - do you have access to the SharePoint Log files? Look for a message that says:

 Timeout while waiting for request to complete within the sandboxed appdomain

around about the time you are trying to publish. 

Yes, I found it around the time I tried to publish: "03/07/2013 17:48:51.80 SPUCHostService.exe (0x07E4) 0x191C SharePoint Foundation Sandboxed Code Service fe8i Medium - - Timeout while waiting for sandboxed code execution request to complete within the worker process. - userCodeWrapperType.FullName = "Microsoft.Office.InfoPath.Server.Host.FormServerUserCodeWrapper", userAssemblyGroup = ".UserCodeAssemblyGroupId = ", GroupId = "20517A2A7A0F49FFBC8F6A9769677959-FHR2dwtPHUMplDjkp6xtUHx3BKuC2zdH/VgxmcnzwK4="" what does this mean? And how to prevent it?

 You can admin approve instead of Sandboxing, or you can try to make the form template smaller, or you can extend the timeout for the process using PowerShell. http://stackoverflow.com/questions/5722320/sharepoint-2010-sandbox-solution-timeout may also help you.

Yes, that looks to be the problem. I'm not able to reduce the size of my form because of the business requirements, but it does seem to publish sometimes and not others (doing little to no changes on the form), leading me to believe that it is a service timeout. I am not sure of the risks of changing the timeout length, but I will have to get an admin to try it out. Thanks for the good information Hilary.