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.

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.

I've been spending more time than I wanted, trying to figure out how to use AsiMembership provider and how it's meant to work alongside RoleProvider and Asi.iBO.dll in general. Frankly, I'm a fair amount unhappy that this kind of stuff is not documented - it seems crazy that I'm having to dig around to find out how things are supposed to integrate together.

It seems that in certain areas the custom Membership provider (AsiMembershipProvider) is not going to work well with iBO.Net.

I notice there are two Asi assemblies that seem, on the surface at least, to serve the same function - to provide an API to expose contact information to a .Net application:

1. Asi.iBO
2. Asi.Business.Contact

Looking under the covers at the implementation, Asi.Business.Contact seem to be based on Business Objects, whereas Asi.iBO, erm is not.

So my questions:

We have a client that is currently on iMIS 15.1.1.3632. I have this first client's database on a dev server and upgraded their database to iMIS 15.1.2.5184 and was still able to recreate the error. Just today I received the same error on another client's iMIS Public site - they are on iMIS 15.1.2.5184.

Both versions are getting similar error messages. When a user goes into iMIS Public to register for an event - or to register another roster member for an event - they receive the following error message (this does not always happen, but it happens enough to where the first client that is currently live can't use event registration and our 2nd client won't go live without a fix for it):

We are curerntly setting up a test WCM site. However, when we login and click System Setup and several other links on the WCM tab we get "An unexpected iMIS error has occurred. Please try your operation again; if you still receive an error, contact the system administrator. "

Is there somewhere these errors are being logged? This is a stand alone WCM site on a different server than the app server.

I need to delete over 400 users, and when I call the deleteimisuser web method from the membership service from a powershell script I get authentication errors:

The createimisuser web method works without problems.

Can anyone help me with this please?

thanks,

Odoro Erivwo

Has anyone had any experience using the 10.6 release client on a Windows 7 OS? We skipped Vista altogether but will likely upgrade to Windows 7 soon and need to know if upgrading to Windows 7 must be preceeded by an upgrade to iMIS 15.

iMIS version 15.1.2

In the installation documentation there is discussion about one model where the public views is at an external server and the application server and database server are inside the firewall. It is also described that you need to open up ports 1433, 443, and 80. We are having issues on one of our clients. In this scenario do you have to have an SSL certificate on the internal application server? Since the manual indicates that 443 has to be open it would make sense that you need to do that. In addition you would really want all traffic between the public views and the application server going over 443.