InfoPath Dev

After about 7 hours of trouble shooting, I have come to the conclusion that my form will no longer publish when it gets over 1700kb.  If I delete a few things, buttons, rules etc and get it under that amount, then it will be compatible with Web browsers. Once I get back over 1700, the error happens again.  The error that I receive is

"The form template has been published to the server but it can only be opend in the InfoPath Filler because it contains features that are not compatible with Web browsers.  To fix this problem, close this dialog and review the errors in the Degisn Checker task pane."

 I've tried unchecking "Verify on Server" and also add executionTimeout="3000" to the web.config, but that didn't seem to help.

 Any ideas?

 Thanks

 Any code in this form? If you check the SharePoint logs during the time you are trying to publish, do find any helpful info? Are you getting any errors in the Design Checker, or does it just show a message about not being able to verify the form on the server (which can happen if the form is huge - the Design Checker will time out)? You can sometimes work around that with Fiddler - it will show you the returned info on errors - you just have to sort through the XML...

I have to add (just because I'm famous for my un-asked for advice) - that is a really big form. It may be worth considering whether it is encompassing too many processes and should be turned into several less ginormous forms....

Hi Hilary,

 Thanks for your quick reply.  There is no code in the form and I don't believe I'm allowed install Fiddler on this computer.  The only Design Checker errors are "Can't verify form on server" and "Data connections contain parameterized queries"  I've had these warnings before with no publishing issues .  At this point I don't believe I can turn this into several froms, due to time. 

 Is there a limit on the amount of rules, buttons or fields that a form can have?  People as asking if a rule weighs as much as a field or button in terms of total max of capacity.  I haven't come across anything online which talks about a rule limit.  This form is SERIOUSLY packed with picture buttons (11 per page, down from 18 per page), which makes it very large and it takes about 15 mins to do a quick publish.

Thanks

 I don't think you are hitting a rule limit - I think you are hitting a size limit. Can your SharePoint admin access the log files when you try to publish? "Can't verify form on server" is a timeout issue in this case, I'd bet (which is why I suggested Fiddler to inspect the returned info)

Hi Hilary, thanks again for your help. We didn't end up see anything strange in the log files. When I removed a good handful of those picture buttons everything seem to go back to normal with publishing. But then after a couple views new views, I was right back to that same error message. So I deleted more picture buttons , and then it started publishing again. I've ran this cat and mouse game about 10 times. At first I thought it was a size issue at 1700kb, but with all those picture buttons removed I'm down to 910kb and this back and forth game keeps happening. Now my issue is that I've just about run out of things to delete and I have a few more views to build. The publishing error has also happened just by adding a few new rules, but then after a few picture button deletes or an unused view delete, it publishes. Could I have maxed out the total combination of rules+fields+views? Is there some deep dark setting that I can change?

HI Hilary, I just came across these logs.  I the biggest thing I spotted was  "Microsoft.SharePoint.SPException: The specified file is larger than the maximum supported file size".  Can you spot anything else in this log that may help?

Thanks again 

 

Conversion and Deployment      f7d4 Verbose  NonAdminSolution.StoreConverted - Storing converted file. Site is http://d1dtwtapbwsspt1:2121/test/BWAT, original file is GUI_BWAT_Analysis/Forms/template.xsn, content is not empty, keepOnlyLatestVersion is False 
Runtime                        e56k Verbose  PERF:Getting tag from file directly for: GUI_BWAT_Analysis/Forms/template.xsn 
Runtime                        e56k Verbose  PERF:Getting tag from file directly for: GUI_BWAT_Analysis/Forms/template.xsn 
Conversion and Deployment      74nh Medium   Activation of non-admin solution: adding converted to "IWConvertedForms\c14-YsM6WVDrLlHxyjPjfSwhPNjIMnBBOWR55k8EPYnsLQ-B58MOyoNVF8CqTgRojiQY0yjV11lkwl3RL5Ny1YqOaE.cvt" for "/test/BWAT/GUI_BWAT_Analysis/Forms/template.xsn" 
General                        72nz Medium   Videntityinfo::isFreshToken reported failure. 
Runtime                        82mv Exception Activate NonAdminSolution failed with unhandled exception Microsoft.Office.InfoPath.Server.Util.InfoPathException: This form template cannot be activated. There is already a form template named template.xsn activated on http://ssfdsfwtasgsspt1:2121/test/BWAT/IWConvertedForms. Either choose a different site collection for activation or rename the form template and upload again. ---> Microsoft.SharePoint.SPException: The specified file is larger than the maximum supported file size.     at Microsoft.SharePoint.SPFile.CloneStreamToSPFileStream(SPWeb web, Stream stream, Int64 bytesToCopy)     at Microsoft.SharePoint.SPFile.CloneUnknownStreamToSPFileStream(SPWeb web, Stream inputStream)     at Microsoft.SharePoint.SPFileCollection.AddStreamOrBytesInternal(String urlOfFile, Stream file, PutFileOp... 
Runtime                        82mv Exception ...t fileOpt, String createdBy, String modifiedBy, Int32 createdByID, Int32 modifiedByID, DateTime timeCreated, DateTime timeLastModified, Object varProperties, String checkInComment, Stream formatMetadata, String lockIdMatch, String etagToMatch, SPLockType lockType, String lockId, TimeSpan lockTimeout, Boolean validateRequiredFields, SPVirusCheckStatus& virusCheckStatus, String& virusCheckMessage, String& etagNew, Boolean& ignoredRequiredProps)     at Microsoft.SharePoint.SPFileCollection.Add(String urlOfFile, Byte[] file, Boolean overwrite, String checkInComment, Boolean checkRequiredFields)     at Microsoft.SharePoint.SPFileCollection.Add(String urlOfFile, Byte[] file, Boolean overwrite)     at Microsoft.Office.InfoPath.Server.Administration.NonAdminSolution.<>c__DisplayClassb.<StoreConver... 
Runtime                        82mv Exception ...ted>b__9(SPSite revertedSite)     --- End of inner exception stack trace ---     at Microsoft.Office.InfoPath.Server.Administration.NonAdminSolution.<>c__DisplayClassb.<StoreConverted>b__9(SPSite revertedSite)     at Microsoft.Office.InfoPath.Server.Administration.NonAdminSolution.AccessSiteUnderSystemAccount(SPSite site, VisitSite siteHandler)     at Microsoft.Office.InfoPath.Server.Administration.NonAdminSolution.StoreConverted(SPSite site, SPFile originalFile, Byte[] uncompressedContent, Boolean keepOnlyLatestVersion)     at Microsoft.Office.InfoPath.Server.Administration.NonAdminSolution.<>c__DisplayClass3.<Activate>b__0()     at Microsoft.Office.Server.Diagnostics.FirstChanceHandler.ExceptionFilter(Boolean fRethrowException, TryBlock tryBlock, FilterBlock filter, CatchBlock catchBlock... 
Runtime                        82mv Exception ..., FinallyBlock finallyBlock) 
Unified Logging Service        c91s Monitorable Watson bucket parameters: SharePoint Server 2010, ULSException14, 41b7c39f "infopath forms services", 0e00129b "14.0.4763.0", fd34ba92 "microsoft.office.infopath.server", 0e0017dd "14.0.6109.0", 4e41890c "tue aug 09 15:22:52 2011", 000037e0 "000037e0", 00000182 "00000182", cfbbc66e "infopathexception", 38326d76 "82mv" 

We have successfully published XSNs for Forms Services that were larger than 5Mb so maybe there is some server setting.  

However, 99% of all XSNs should be <1Mb. Check your XSN for duplicate images in the InfoPath Designer by going to File->Publish->Export Source and creating a folder. Set the windows folder to show large icons and look for duplicate images. If there are any and these are large, it could be a good place to start for reducing the size since these images can be consolidated into one. It's a little tricky but easy to do.

The other chief culprit for large XSN size is large secondary XML data sources. Since you're publishing a browser form, you should consider moving these outside of your form to a document library and referring to them from the form.

Just two ideas for now. Hope they help.

Good luck!

Hi Patrick, thanks for the tips! So here are the file sizes that I'm working with....XSN 900kb, total export source 11.3mb, manifest.xsf 3200kb. Most of the large views/xls (about 60 of them) are about 125kb. They all used the same image that is 12kb. I only have a few very small XML data sources, everything else is data connections to sp lists. Am I doing something really wrong here. Also, how can I get all the pictures to use the same file? Many thanks for your time!

 The first line of that is perplexing, isn't it? Suggesting that it simply can't overwrite - at any rate - I don't know if changing the maximum allowed file size will help at all, but here's a link on that. Perhaps you could try admin approving the form? See if that gets you around this issue?

 Whoops - didn't see Patrick's reply. You'd need to manually modify the view file to change the image file used by the view.

Deleting all the picture buttons let me publish, but the error came back when I added two more views. The Export Source File is showing a total of 225 files. I keep running into this mystery max limit. Can you think of anything else? I think I've tried just about everything. Thanks again

Actually, I was able to publish it as an admin approved form. Does that give any clues?

 Well - if it had code, I'd guess the sandbox worker process had been timing out when publishing to the library....

We were finally able to publish without an Admin approved xsn. The xsn was only 898kb (with over 70 views and 4200 rules), but the 64 encoding is converting the size to more than 50mb after decompression (this was discovered by a co-worker). He suggested to increase the Maximum upload size from 50mb to 100mb in the Web Application General Settings. This solved the problem...I was very surprised...and happy.

 i have same problem, my form is less than 1 MB ,, and after extracting it the size is 6 MB

how did you fix it please