Madhan's Blog https://docs.microsoft.com/archive/blogs/madhan/feed.xml Tue, 16 Apr 2019 06:11:55 GMT en-US hourly 1 Hyperlinks will not run code in InfoPath https://docs.microsoft.com/archive/blogs/madhan/hyperlinks-will-not-run-code-in-infopath Wed, 23 Sep 2015 07:02:00 GMT https://blogs.technet.microsoft.com/madhan/2015/09/23/hyperlinks-will-not-run-code-in-infopath/ I have seen people coming up with requirements to run VB or C# code from InfoPath using hyperlinks. This could be achieved only using code editor and event handlers. When we insert the path of the code in the addresses, it goes through the default browser and downloads the code instead.

"The hyperlink control enables users to insert or edit a hyperlink on the form. Users editing and viewing the form can click the hyperlink which automatically opens the Web browser to the location that the link points to. This is useful when you are required to input a hyperlink as part of the form."

Workaround:

  • Insert a button in InfoPath form and go to developer tab -> click code editor.
  • Choose the programming language based on your requirements (I have used VB).
  • Make sure that the InfoPath form is in full trust. Otherwise you will get an error message as mentioned in the below article.

https://blogs.technet.com/b/madhan/archive/2015/09/16/common-errors-messages-in-infopath.aspx

  • Add the reference System.Diagnostics and use the namespace in the header "Imports System.Diagnostics".
  • The below code will run the VB script.

Public Sub CTRL1_5_Clicked(ByVal sender As Object, ByVal e As ClickedEventArgs)

Process.Start("C:\Windows\SysWOW64\wscript.exe", "C:\test.vbs")

Note : Modify the path of the VB file. CTRL_5 is the name of the clicked button event handler.

  • The above code will call the test.vbs which will get executed once the button is clicked.

** Please note that this code is not production ready. It has to be tested in the development/test environment.

Thanks to my colleague Ajay for his contribution.

]]> Common errors messages in InfoPath https://docs.microsoft.com/archive/blogs/madhan/common-errors-messages-in-infopath Wed, 16 Sep 2015 14:11:00 GMT https://blogs.technet.microsoft.com/madhan/2015/09/16/common-errors-messages-in-infopath/ While working with InfoPath we do see lot of error messages while publishing it to the Sharepoint forms library and opening the published Infopath form in browser. I have posted some common and rare error messages in this article.

Error message:

"Updating the content type failed"

   

Resolution:

https://blogs.msdn.com/b/microsoft_infopath_bloggers/archive/2015/05/18/quot-updating-the-content-type-failed-quot-while-publishing-the-infopath-form.aspx

Error message:

"The following external components are required to edit your form code. Please install them and try again."

Resolution:

InfoPath code editor is not supported in Visual Studio 2013 and other higher version.

Error message:

"InfoPath cannot modify the form library template because the file does not exist. copy the template to the form library or create a new form library."

 Resolution:

We need the forms library to publish the InfoPath form in other templates such as product catalog. The only solution is to publish the form as admin approved template.

https://technet.microsoft.com/en-in/library/cc262921(v=office.14).aspx

Error message:

While opening the browser based InfoPath form in IE 11, you might get the below error message.

"Object doesn't support property or method 'addEventListener' "

Resolution:

Sharepoint is doing a browser detection using the X-UA-Compatible meta tag set to IE 8 which forces the page to be loaded in IE 8 mode on IE 11 browser.  As addEventListener method (https://msdn.microsoft.com/en-us/library/ff975245(v=vs.85).aspx) is supported only in IE 9 and above (prior to IE 9, attachEvent was used instead – https://msdn.microsoft.com/library/ms536343(v=vs.85).aspx), the above error is thrown when the page is loaded in IE 8 mode as IE 8 does not support this addEventListener method.

The workaround is to add the Sharepoint site in IE compatibility view.

Error Message:

You will get the below error message while using event handlers and code behind InfoPath form.

System.Security.SecurityException
Request failed.
at fulltrust.FormCode.CTRL1_5_Clicked(Object sender, ClickedEventArgs e)
at Microsoft.Office.InfoPath.Internal.ButtonEventHost.OnButtonClick(DocActionEvent pEvent)
at Microsoft.Office.Interop.InfoPath.SemiTrust._ButtonEventSink_SinkHelper.OnClick(DocActionEvent pEvent)

Resolution:

1. Click Advanced Form Options -> Security and Full Trust -> Uncheck "Automatically determine security level" -> Choose Full trust.

2. Also Click Sign this form template and then select certificate.

Error Message:

"The SOAP message cannot be parsed."

This error message generally occurs while publishing the InfoPath form to the SharePoint server. When there are more data connections and lot of customization done on the form, then it takes lot of time for the SOAP message to be parsed. The list.asmx and Formsservice.asmx will take more time.


Resolution:

Increase the timeout in the web.config of the web application.

<httpRuntime maxRequestLength="51200" executionTimeout="600" />

For timeout values, refer : https://msdn.microsoft.com/en-in/library/e1f13641(v=vs.85).aspx

I will keep updating this article when ever i find some interesting and common errors. Happy Blogging!

]]> Shared with dialog doesn't load completely for Custom lists in Sharepoint https://docs.microsoft.com/archive/blogs/madhan/shared-with-dialog-doesnt-load-completely-for-custom-lists-in-sharepoint Wed, 16 Sep 2015 14:00:02 GMT https://blogs.technet.microsoft.com/madhan/2015/09/16/shared-with-dialog-doesnt-load-completely-for-custom-lists-in-sharepoint/ When we click "Shared with" dialog to share a custom list to users, it doesn't load completely. We could only see "EMAIL EVERYONE" and the other options such as "ADVANCED LINK" doesn't show up.

This issue happens only for the custom lists in Sharepoint and not for document library. Also, this happens after the installation of DEC 14 CU and later.

This issue is fixed in April 15 CU.

https://support.microsoft.com/en-us/kb/2965228.

Click here to download April 15 CU

Thanks Praveen for your help!

]]> The publish operation could not be completed. It cannot be determined if the form template was successfully published... while publishing InfoPath form to Sharepoint https://docs.microsoft.com/archive/blogs/madhan/the-publish-operation-could-not-be-completed-it-cannot-be-determined-if-the-form-template-was-successfully-published-while-publishing-infopath-form-to-sharepoint Wed, 16 Sep 2015 13:58:58 GMT https://blogs.technet.microsoft.com/madhan/2015/09/16/the-publish-operation-could-not-be-completed-it-cannot-be-determined-if-the-form-template-was-successfully-published-while-publishing-infopath-form-to-sharepoint/ When you are trying to publish Infopath form to Sharepoint forms library, you might get the below error messages.

"The publish operation could not be completed. It cannot be determined if the form template was successfully published. Try publishing the template again, or change the list settings to use the default SharePoint form."

"InfoPath cannot connect to the server. The server may be offline, your computer might not be connected to the network, or InfoPath Forms Services 2010 might not be enabled on the server. To fix this problem, start by checking your network connection, and then try again."

The above error message is a very generic error message. It might also occur due to execution time out and other reasons.To understand the issue better we captured the ULS logs and found the below error messages.

06/12/2015 09:40:07.50 w3wp.exe (0x3528) 0x2D4C SharePoint Foundation General ai1wu Medium System.IO.FileNotFoundException: The system cannot find the file specified. (Exception from HRESULT: 0x80070002), StackTrace: at Microsoft.SharePoint.SPWeb.GetList(String strUrl) at Microsoft.Office.InfoPath.Server.Util.InstalledSolutions.VerifyListPresence(SPSite site, Boolean& foundFormTemplateLibrary, Boolean& foundConvertedLibrary) at Microsoft.Office.InfoPath.Server.Util.InstalledSolutions.<IsSupportFeaturePresent>b__15(SPSite revertedSite) at Microsoft.Office.InfoPath.Server.Util.InstalledSolutions.<>c__DisplayClass13.<IsSupportFeatureActiveNoCache>b__12(SPSite revertedSite) at Microsoft.Office.InfoPath.Server.Administration.NonAdminSolution.AccessSiteUnderSystemAccount(SPSite site, VisitSite siteHandler) at Microsoft.Office.InfoPath.Server.Util.InstalledSolutions.IsSupportFeatureActiveNoCache(SPSite site, Guid featureId, Action`1 actionIfFound) at Microsoft.Office.InfoPath.Server.Util.InstalledSolutions.IsSupportFeaturePresent(SPSite site, Guid featureId) at Microsoft.Office.InfoPath.Server.SolutionLifetime.DesignCheckerVerificationContext.OnAfterSolutionInformationParse(SolutionInformation information) at Microsoft.Office.InfoPath.Server.Converter.ConversionAppDomain.TryRunConversion(ConversionContext context, SolutionCabinet solutionCabinet, SolutionIdentity solutionId, Byte[] solutionData, WspSolutionInfo wspSolution) at Microsoft.Office.InfoPath.Server.Converter.ConversionAppDomain.RunConversion(ConversionContext context, SolutionCabinet solutionCabinet, SolutionIdentity solutionId) at Microsoft.Office.InfoPath.Server.Util.InstalledSolutions.<>c__DisplayClass7.<VerifyUnpackedSolution>b__6() at Microsoft.Office.Server.Diagnostics.FirstChanceHandler.ExceptionFilter(Boolean fRethrowException, TryBlock tryBlock, FilterBlock filter, CatchBlock catchBlock, FinallyBlock finallyBlock) at Microsoft.Office.InfoPath.Server.Util.InstalledSolutions.VerifyUnpackedSolution(SolutionCabinet solutionCabinet, String originalFileName, ConversionContext context, ConverterLog& outputConverterLog, Byte[]& outputConvertedData) at Microsoft.Office.InfoPath.Server.Util.InstalledSolutions.VerifySolution(String absoluteLocalPath, ConversionContext context, ConverterLog& converterLog, Byte[]& convertedData) at Microsoft.Office.InfoPath.Server.FormsServicesWebService.DesignCheckFormTemplate(Int32 lcid, String base64FormTemplate, String applicationId) at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor) at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments) at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) at System.Web.Services.Protocols.LogicalMethodInfo.Invoke(Object target, Object[] values) at System.Web.Services.Protocols.WebServiceHandler.Invoke() at System.Web.Services.Protocols.WebServiceHandler.CoreProcessRequest() at System.Web.Services.Protocols.SyncSessionlessHandler.ProcessRequest(HttpContext context) at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) at System.Web.HttpApplication.PipelineStepManager.ResumeSteps(Exception error) at System.Web.HttpApplication.BeginProcessRequestNotification(HttpContext context, AsyncCallback cb) at System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags) at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags) at System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompletion(IntPtr pHandler, RequestNotificationStatus& notificationStatus) at System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompletion(IntPtr pHandler, RequestNotificationStatus& notificationStatus) at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags) at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags) 16ad0f9d-0e35-d08a-3e99-936b9eee525f

06/12/2015 09:40:07.62 w3wp.exe (0x3528) 0x2D4C InfoPath Forms Services Runtime m1y5 Exception LoadDocumentAndPlayEventLog failed with unhandled exception Microsoft.Office.InfoPath.Server.Util.InfoPathLocalizedException: Activation could not be completed because the InfoPath Forms Services support feature is not present. at Microsoft.Office.InfoPath.Server.Util.InstalledSolutions.<IsSupportFeaturePresent>b__15(SPSite revertedSite) at Microsoft.Office.InfoPath.Server.Util.InstalledSolutions.<>c__DisplayClass13.<IsSupportFeatureActiveNoCache>b__12(SPSite revertedSite) at Microsoft.Office.InfoPath.Server.Administration.NonAdminSolution.AccessSiteUnderSystemAccount(SPSite site, VisitSite siteHandler) at Microsoft.Office.InfoPath.Server.Util.InstalledSolutions.IsSupportFeatureActiveNoCache(SPSite site, Guid featureId, Action`1 actionIfFound) at Microsoft.Office.InfoPath.Server.Util.InstalledSolutions.IsSupportFeaturePresent(SPSite site, Guid featureId) at Microsoft.Office.InfoPath.Server.SolutionLifetime.DesignCheckerVerificationContext.OnAfterSolutionInformationParse(SolutionInformation information) at Microsoft.Office.InfoPath.Server.Converter.ConversionAppDomain.TryRunConversion(ConversionContext context, SolutionCabinet solutionCabinet, SolutionIdentity solutionId, Byte[] solutionData, WspSolutionInfo wspSolution) at Microsoft.Office.InfoPath.Server.Converter.ConversionAppDomain.RunConversion(ConversionContext context, SolutionCabinet solutionCabinet, SolutionIdentity solutionId) at Microsoft.Office.InfoPath.Server.Util.InstalledSolutions.<>c__DisplayClass7.<VerifyUnpackedSolution>b__6() at Microsoft.Office.Server.Diagnostics.FirstChanceHandler.ExceptionFilter(Boolean fRethrowException, TryBlock tryBlock, FilterBlock filter, CatchBlock catchBlock, FinallyBlock finallyBlock) StackTrace: at Microsoft.Office.Server.Native.dll: (sig=678c0f87-966f-4d99-9c94-b49e788d2672|2|microsoft.office.server.native.pdb, offset=131CE) at Microsoft.Office.Server.Native.dll: (offset=21BE5) 16ad0f9d-0e35-d08a-3e99-936b9eee525f

  • From the above stack trace, we see that the feature is not activated.
  • We ran the below commands to get the status and the scope of the IPFSSiteFeatures. (Infopath Form Services Feature).

$a = get-spfeature "IPFSSiteFeatures"

$a.status

online

$a.scope

site

  • The IPFSSiteFeatures is activated already. When we ran the below command, we got the error messsage "Feature 'a0e5a010-1329-49d4-9e09-f280cdbed37d' is not activated at this scope"

Stsadm.exe -o deactivefeature -filename IPFSWebFeatures\feature.xml -url ""

  • We activated the IPFSWebFeatures using the below command and we are able to publish the InfoPath form successfully.

Stsadm.exe -o activatefeature -filename IPFSWebFeatures\feature.xml -url ""

]]> Unable to publish an InfoPath form to Sharepoint when there is no root site collection https://docs.microsoft.com/archive/blogs/madhan/unable-to-publish-an-infopath-form-to-sharepoint-when-there-is-no-root-site-collection Wed, 16 Sep 2015 13:58:34 GMT https://blogs.technet.microsoft.com/madhan/2015/09/16/unable-to-publish-an-infopath-form-to-sharepoint-when-there-is-no-root-site-collection/ I recently came across an interesting issue while publishing an InfoPath form. When we are trying to publish an Infopath form to the Sharepoint site collection, we got the below trimmed pop error message (trimmed completely).

  • When I tried to publish it to other site collections in different web applications, I was able to publish successfully. The only difference between the working and the non-working scenario is that the web application in the non-working scenario didn't have the root site collection "/".

In the fiddler trace,  we are seeing 401 when the request is going to webs.asmx and the request is going through the root site.

POST https://<site collection name>/_vti_bin/webs.asmx HTTP/1.1
Content-Type: text/xml; charset=utf-8
SOAPAction: https://schemas.microsoft.com/sharepoint/soap/WebUrlFromPageUrl
X-Office-Version: 14.0.5128

Cause:

  • When we publish the InfoPath template the template gets copied to the forms folder in the Sharepoint library and this goes as a WebDAV request.

SOAPAction: https://schemas.microsoft.com/sharepoint/soap/GetListContentTypes

<?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="https://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="https://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="https://www.w3.org/2001/XMLSchema"><soap:Body><GetListContentTypesResponse xmlns="https://schemas.microsoft.com/sharepoint/soap/"><GetListContentTypesResult><ContentTypes ContentTypeOrder="0x01010100DC185DBC959A0C48AEC172B44A668F10"><ContentType Name="Form" ID="0x01010100DC185DBC959A0C48AEC172B44A668F10" Description="Fill out this form." Scope="https://sp2013-13r/sites/123/asdf" Version="28"><XmlDocuments><XmlDocument NamespaceURI="https://schemas.microsoft.com/sharepoint/v3/contenttype/forms"><FormTemplates xmlns="https://schemas.microsoft.com/sharepoint/v3/contenttype/forms"><Display>DocumentLibraryForm</Display><Edit>DocumentLibraryForm</Edit><New>DocumentLibraryForm</New></FormTemplates></XmlDocument></XmlDocuments></ContentType><ContentType Name="Folder" ID="0x012000CFF8159696099D4184D50EB2D7CC69C9" Description="Create a new folder." Scope="https://<site collection name>" Version="0"><XmlDocuments><XmlDocument NamespaceURI="https://schemas.microsoft.com/sharepoint/v3/contenttype/forms"><FormTemplates xmlns="https://schemas.microsoft.com/sharepoint/v3/contenttype/forms"><Display>ListForm</Display><Edit>ListForm</Edit><New>ListForm</New></FormTemplates></XmlDocument></XmlDocuments></ContentType></ContentTypes></GetListContentTypesResult></GetListContentTypesResponse></soap:Body></soap:Envelope>

  • This is the below response when we have root site collection.

OPTIONS https://<site collectoin name>/ HTTP/1.1
User-Agent: Microsoft Office Protocol Discovery
Host: <host name>

HTTP/1.1 200 OK
Cache-Control: private,max-age=0
Allow: GET, POST, OPTIONS, HEAD, MKCOL, PUT, PROPFIND, PROPPATCH, DELETE, MOVE, COPY, GETLIB, LOCK, UNLOCK
Content-Length: 0
Expires: Thu, 20 Aug 2015 22:26:24 GMT
Accept-Ranges: none
Server: Microsoft-IIS/8.5
X-SharePointHealthScore: 3
MS-Author-Via: MS-FP/4.0,DAV
X-MSDAVEXT: 1

  • But when we remove the root site collection, we are getting a 401.
  • When you are using WebDAV request, you need root site collection.

Resolution:

We need a root site collection in the web application when we publish the InfoPath form.

Fore more information about root site collection and WebDAV request, refer the below KB article.

https://support.microsoft.com/en-us/kb/2625462

Thanks Rajeev for helping me to figure out the Root Cause!

]]>