I am using Sitecore 7.1, created a new campaign in Marketing center, but after saving when i try to open it, it gives the error An error occurred while loading report data. Please try again or contact your administrator.
Same happens with Engagement plans, i get this error when i try to open it Error Loading Engagement Plan.
Try clearing the browser cache and restart browser, this usually helps.
Also. You need to approve the campaign through the workflow before publishing. And off course, make sure you have Sitecore DMS installed :-)
Related
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)
I just finished installing Tiki Wiki on my server (standard Hostgator account), and was able to log in as an admin. I am trying to create a new file gallery, but I keep receiving this error when I fill out the gallery settings and hit the "Save" button:
Youre are not logged in. Go to the Log In Page.
Problem is, that doesn't make sense. How could I even access the admin interface to create a new file gallery if I wasn't logged in as an admin!?
Any ideas what's going on, and how to fix it?
Thanks,
Lukas
Additional information would be helpful:
- What Tiki version?
- Are you storing Tiki session info in DB or File System?
- Did you turn on Tiki error reporting, and is anything shown?
- Are there any errors in your server log?
For best support, try the Tiki forums: http://tiki.org/forums
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
When posting an achievement with a user message it gives the following error:
{"error":{"message":"(#100) You haven't enabled User Messages for this action type (127701393971353) yet. Please update your Open Graph settings in the App Dashboard","type":"OAuthException","code":100}}
No clue where to enable that.
Managed to get access to the setting by modifying the url manually with the id.
https://developers.facebook.com/apps/your_app_id_here/opengraph/action_type/127701393971353/
In case this helps someone else, I had this issue. My situation was: I had a live app with an approved Open Graph action. I needed to release a new version of the app but I needed a new Open Graph action for this so the earlier version still worked until users upgraded to the new version. When I used the new Open Graph action, I got this error. My problem was that I had made a simple typo error in the bundle id of the new app version so it didn't match with the bundle id I had specified for the iOS settings in the Basic Settings page in the Facebook Developer app. The clue was that in the error given in the Xcode debug console, the app id didn't match up.