-
I don't see anything referring to the Harvest tasks in the event log you provided. Actually, I doubt the CS event log would say anything about the Harvest Tasks anyhow. The Harvest task service is installed as a Windows Service, either totally independent from CS or merged with the Enterprise Search tasks. Did you complete the Task Setup part of the Harvest installer? Check your Windows Services (Control Panel > Administrative Tools > Services) and see if the Telligent Tasks Service is
-
This one was reported a few weeks ago. There was a bug in the code, and the fix required recompiling The fix will be available VERY soon with the upcoming 2.1 release. – Andrew
-
Hello Igor, Harvest 2.0 does use impersonation to differentiate between the different sites and their corresponding schemas. If impersonation is allowed in your database environment, ensure that the master connection user has db_owner rights, so that the impersonation will be successful. This connection string is specified in connectionStrings.config as "HRSDB". If impersonation is not allowed in your database, you will unfortunately lose the mult-site functionality. You can, however, successfully
-
From looking at your connection strings, I notice the connection string names have been renamed to "Infosec", "InfosecSharedMembership", and "InfosecReporting". This is fine, as long as you ensure the connection strings under each task are updated to use these names instead of the defaults. Under each task you will see a <ConnectionStringNames> section that looks like this: <ConnectionStringNames> <add Source="CommunityServer" Destination="CommunityServerReporting"
-
Executing additional queries in FormatTitle is normally not a problem. The error message you are seeing is often indicative of an exception of some sort behind the scenes. Have a look at the ExceptionReport (/Report.aspx/1/ExceptionReport) and check your most recent Exceptions to see if any of them give you a hint into what is causing this. – Andrew
-
You need to ensure the string is properly Url encoded when creating the link. There is a Library.Helper.UrlEncode(string) method you can use, but this may not cover all possible characters. Using the UrlKey class and setting its Param1 and Param2 properties SHOULD cover all possible characters. There is some arbitrary character replacement done to compensate for odd characters like \ and . The UrlKey is used like this: UrlKey url0 = new UrlKey(); url0.Site = ReportingContext.Current.UrlKey.Site;
-
Yeah, I dislike how the UserData task pulls all users each time it runs. With tasks like this, it's not entirely possible to make it Incremental, since there is not a field in cs_Users that updates each time the row is updated. For this reason, if you have a large number of users, I recommend actually putting this one on a separate thread and increasing the interval between executions for this task, even upwards of several days between executions. That is off topic, though. Since your user base
-
Those are not "SubGroups", they are Visible reports. This ordering is set in the rs_Reports table in a similar fashion (set the Ordinal column). – Andrew
-
This is accomplished by overriding the FormatTitle() method in the report class. You can either replace the string returned with a hard-coded title, or look up a friendly display name by executing an additional query. Here is an example from one of our reports where the Parameter is a Forum's SectionId. Instead of displaying the integer SectionId, we use that value to lookup the Forum Title, then display that as the title. public override string FormatTitle() { if (ReportingContext.Current =
-
If your membership tables are on the same database, the connection string for CommunityServerSharedMembership should be the same as the connection string for CommunityServer. For MergeQueryTasks (those that execute more than one query and merge them into the final result), multiple source connections are specified. The order does matter for these, because the queries are executed in order, and each pulls from the corresponding in-order connection string. The installer will automatically configure