I am working at a customer, CBM Australia.  We are trying to create a campaign structure.  When we get to adding source code details, whenever we try to add an Insert or Source List (simple query) to the campaign, we get the following 2 errors:

Error - Value must be unique with a System

Error - The 'Name' property should not be Null

These errors have been occurring intermittently since go live.  We logged an SMR but as tech support could not recreate the issue they could not progress it.  We have tried to run a trace (output attached) but can't really make any sense of it.  We now cannot create any new source codes and cannot generate campaign output.  At points in the past, by changing details in the campaign profile we could get the details to save but this no longer works.  I am guessing it is related to the PAckage tables but can't get any further than this.

For those individuals already using WCM and iMIS, what backup (and system maintenance) practices have you put into place?

We feel pretty confident about our SQL backup strategy, but the only items we're finding in the official docs are for SQL at http://docs.imis.com/15.1/index.asp?topic=/15.1/34128.htm and nothing regarding iMIS itself and the WCM sites.

This is a response to the question about including HTML in Event descriptions here: http://www.imiscommunity.com/complete_newbie_need_help   I'm posting it here so I can attach a screenshot.

Something else that might help...

The Event Directions field, from Define an Event in Desktop, is rendered as an asp:Label in public view and template sites, so it can include HTML formatting for bold and hyperlinks.  The attached screenshot shows the desktop setup, with html in the Directions field, and its effect in public view.  I didn't check to see how confirmation notices would handle HTML, so you'd probably want to check "Suppress printing of directions on Confirmation Letters".

One of the more common critical iMIS errors involves a failed attempt to build the sitemap. In the currently released version of iMIS, the errors discussed below will result in the application server being unable to load. In an upcoming update, iMIS will at least continue to work until the application pool is recycled, giving you a little bit of time to resolve the problem.

In existing versions, the problem will manifest itself either as errors publishing a website or navigation item(s), or as an ASP.NET worker pool crash with no error message. In the upcoming version, iMIS will log an error similar to the following in the Windows Application Event log rather than crashing:

I am in the process of upgrading a client to 15.1.2 and need to know where to find the COM IBOs for this version. Anyone know where I can get these?

Thanks

Joe

How long will eCM be supported for? considering WCM is out and there are no more enhancements being made to eCM?

Considering eSeries is still supported, so I would presume eCM would be supported for a while.

However, if it isn't then it would be wise to let the client know not to invest in any eCM customisations as they will have to be re-developed in the near future.

Also, it would be a good way to get clients to move to WCM.

As part of my efforts at trying to get the AsiMembershipProvider working, I have hit against problems because I've got old versions of certain referenced Asi assemblies.

This came as a surprise as I am using assemblies copied from the ASI\IMIS15\net\bin directory on an 15.1.1.3441 installation.

Just having a quick look through the assembly versions and I observe I have a mix of 15.1.1.2998 and 15.1.1.3441 versions. My suspicion is that because we upgraded from 15.1.1.2998, for whatever reason some of the assemblies where not upgraded.

I'm looking for some direction/information on building a custom iPart that uses communities information.  Specifically I need something that will display a headline for each blog post based on the ID of a blog.  This sounds like something that one of the standard iParts should cover - but there doesn't seem to be one that's appropriate (unless someone can point me in that direction).

Hey guys,

I'm having an issue with creating an account on our Production database through the out-of-the-box iMIS create account page. The iMIS database was upgraded from version 10.6 a few months ago (we're now on 15.1.2). (It might also be worth noting that the same error happens when we use iBO to create a customer record)

This functionality works fine on my test databases that were originally created from the Demo DB - the error only happens on our production database.