InfoPath Error - On .Net 3.5 SP1 update

By -
Are you getting errors like the following that makes you frustrated even after validating/checking the webservices URL Path:

1. Some rules were not applied

2. "An error occurred accessing a data source.
An entry has been added to the Windows event log of the server.
Log ID:5566"

If this happens only on certain servers  then, the issue might be with the crazy .Net framework 3.5 SP1

If you're getting the above infopath error after installing .net framework 3.5 SP1, then perform the following. I broke my head for nearly 8 hours:


1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
3. Right-click Lsa, point to New, and then click DWORD Value.
4. Type DisableLoopbackCheck, and then press ENTER.
5. Right-click DisableLoopbackCheck, and then click Modify.
6. In the Value data box, type 1, and then click OK.
7. Exit Registry Editor.
8. Restart the computer.

This should solve the issue.

Believ me, this costed me a lot of time for the second time. Damn it.

Comments

Unknown said…
When you promoted your form from dev->qa->prod, did you run into a scenario where it worked in one environment but not the other? Both our DEV and QA enviornment have .net 3.5 SP1 installed. The form works in DEV, but not in QA.

Any ideas?
3:31 PM
Nag said…
Hi,

We had same issue for one of Prod sites.

Please can you let me know shall we enable same registry loopback setting for PROD front end servers..

Thanks,
Nag...
10:15 AM
Anonymous said…
This worked for our issue. Our farm has multiple web front ends, so we enabled this registry setting and added host file entries to each WFE server so they only look to themselves for things like web service calls.
1:12 PM
Post a Comment

Popular posts from this blog

Linksys Wireless Connection Failure

By -
I configured the Linksys wireless router [WRT54G] couple of years before and it just worked great. I myself configured the password and everything worked great at my home. Anyone comes in home takes my password and it just worked great most of the time. all these were with windows server 2003 and Dell machaines. When I bought a new Hp DV9000 (XP) I had an issue connecting to the home wireless. I started browsing and found this solution: Issue : Couldn't connect to the selected connection. 1. Installed an update http://www.microsoft.com/downloads/thankyou.aspx?familyId=17d997d2-5034-4bbb-b74d-ad8430a1f7c8&displayLang=en Issue after the update : Acquiring Network address status and stayed there. Did the following after that: 1. Browsed http://192.168.1.1/ 2. used the user-id / password of the connection (default userid is empty & pwd is admin) 3. Navigated to wireless (Basic wireless settings), click Reset security and name your userid for SSID 4. Clicked save settings 5. cli
Read more

The security validation for this page is invalid. Click Back in your Web

By -
If you are getting the following error, while renaming the page title using publishingpage object " The security validation for this page is invalid. Click Back in your Webbrowser, refresh the page, and try your operation again ." Code Snippet: PublishingWeb publishingweb = PublishingWeb.GetPublishingWeb(newUri(" http://YourPortal/Plans/ ")); PublishingPage pp =publishingweb.GetPublishingPages()["Pages/TestArticle.aspx"]; pp.Title = e.Node.Text; pp.Update(); You should check for this : Navigate thru the followwing and turn the security validation Off Central Administration--->application management---->web application settings-->"turn security validation off"
Read more

Power Apps toPower Automate Error - The input body for trigger 'manual' of type 'Request' did not match its schema definition , the input String does not validate against the date

By Vinod Thachin -
While working with power Apps to Power automate, passing the Date time values as Text(DateTimeValue) throws error as below. The input body for trigger 'manual' of type 'Request' did not match its schema definition. Error details: 'String '' does not validate against format 'date'.'. After checking the Microsoft documentation and few blogs i found out the date values should be passed as a formatted date time. TO pass the date time  we need to use following functions. Text(<<DateTimePicker>>.SelectedDate,"[$-en-US]yyyy-mm-dd") Even after passing the value i am still seeing the same issue and finally found out the default value ids sending as empty and formulae failing for empty values. So we need to make sure the Date Value should not go blank to the formulae and the value should be formatted using the formulae as above. Hope this helps.
Read more