It is throwing the following exception after submitting the data using Web form created after it is upgraded from Web Form for Marketers 2.1.0 to 2.3.0. Followed the step by step upgrade instructions.
Exception in the Log file:
6772 22:24:13 WARN Web Forms for Marketers: an exception: has occured while trying to execute an action.
Error/Warning on the UI:
Sitecore: We experienced a technical difficulty while processing your request. Your data may not have been correctly saved
However, it is saving the data to database, and when I view the report for the same form using Web Form Reports, nothing is shown.
Action Method : Save to Database
The reading/creating counters warning is covered by adding the 'Performance log users' role to the account used by the application pool as previously answered here. It seems unlikely that this is causing the WFFM error, but it's worthing getting rid of the warning, restart IIS, and try again.
This is related to smtp setup on Send Email Message action which is used on webforms for marketers.
Refer:
http://blog.arkesystems.com/post/2010/05/18/SiteCoreWeb-Forms-for-Marketers-Send-Email.aspx
Related
I created a form in info path which will connect to SQL DB and all connectivity are fine. I preview the form and all SQL data retrieved fine without any issue.
I published the form but when end-users try to load the form, it was shown an error like (An error occurred querying a data source. An error occurred while using the form. For more information, contact the site administrator).
Means I can only retrieve the data while I am at info path and previewing the form but not after the publish.
Is there any things which need to be allowed at SharePoint level to connect to connect to SQL DB which I used in the info path.
Please help and advice .. what could be the issue ??
I would think about permissions on the database.
Have you tried to access the form from the browser with the same user you used in InfoPath designer?
Not my normal line of questions, sometimes we've got to be flexible!
I've designed an InfoPath form that I'd like to upload to a Sharepoint site.
On my form I've got a data source that is consuming the following SOAP service
https://SharepointServer/Site/_vti_bin/UserProfileService.asmx?WSDL
I call the Operations "GetUserProfileByName" and get various information about the account looking at the form. In preview this works very well. I've got the header saying "Hello Pete" and I'm able to filter lists based on the user's data. However. When it comes to uploading the form to the server, I'm greeted with the following exception:
Warning
An error occurred querying a data source.
Click OK to resume filling out the form. You may want to check your form data for errors.
HIDE ERROR DETAILS
An error occurred while trying to connect to a Web service.
An entry has been added to the Windows event log of the server.
Log ID:5566
Correlation ID:19df2c9d-a036-2000-3929-0bce8940cf2a
Any ideas what I'm doing wrong? Is there limitations due to the way that my account details are being used on SharePoint? If so what's the work around? I'm not a full admin on the server, so I've only got access to a Sandbox site.
Any help greatly appreciated,
Pete
The issue is loopback protection. In o365, it cannot be disabled. Stupid though, there are a lot of useful web services available for information. See this link: Error message when you connect an infopath form to a sharepoint online web service
When i am publishing site in Sitecore it is giving error.
Job started: Publish to 'web'|#Exception: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.FormatException: Unrecognized Guid format.
Please guide me how can i resolve this error.
Did you an upgrade recently? If so, maybe this will help:
http://reasoncodeexample.com/2015/03/26/sitecore-linkdatabase-unrecognized-guid-format/
Try to rebuild the Link Database, gives that an error.
With Sql server Profiler (from SQL server Management Studio) you can find the item with the issue. Create a filter to capture the Web database. Start the publish, and press pause when the error occur. Now you see the latest publish action and can you see the guid in the query.
This is described here: Upgrade Sitecore experience with modules
In this case the issue was in the Webforms For Marketers (WFFM) module, the Tracking Field.
Also look for broken links. (Press right mouse button on the left white space in the content editor to choice with icons you want to see)
Does anyone know if there is any way to get server errors back from the listdata.svc in SharePoint 2010 WITHOUT setting CallStack to true in the web.config for the site?
The client we are deploying to will not allow CallStack to be set to true for security purposes. However, we have ItemEventReceivers that catch processing errors that we need
to return so we can inform end users that they have made a mistake, but I can't find an
alternative method to the CallStack setting to get errors back from the server.
You say: "processing errors that we need to return so we can inform end users that they have made a mistake", if it's throwing an error due to user error then it's not a user mistake is an application design problem.
For instance you should validate your data before trying to commit to a list and not rely on the exception to warn the user for mandatory fields, etc.
Having said this, you can use a custom tracer and send the exception to the ULS logs where you can analyse it.
Another option is to hook up some sort of email notification when error happen and dump the exception details on the email. I just recently hooked up Elmah to Sharepoint and it works great
In the Elmah error log page it shows server variables. However, while it is nice to have this extra info I'd like to turn this off as it displays authorization tokens which are sensitive. Is there way to configure Elmah to turn this feature off so they aren't displayed?
I think the only way to do this will be to create a custom Log viewer. From the Elmah Project Home Page:
Use ErrorLogDataSourceAdapter together with ObjectDataSource from ASP.NET to create your own custom views of the error log, almost purely in server-side markup and without a line of code!
Also, have you considered just restricting access to viewing the Elmah logs? See Securing Error Log Pages for more details.