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:

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 am using template design 1510.

I changed the background color of the top nav.

I was able to change the font color in the utilitynav_style to blue, but when I change the color of LoginStatusMenu it does not change.

Here is the code for the login:

<asp:LoginStatus ID="LoginStatus1" runat="server" LoginText="Log On" LogoutText="Log Off" AccessKey="l" OnLoggedOut="LoginStatus1_OnLoggedOut" CssClass="LoginStatusMenu" />

I created a meeting in iMIS and enabled it for online registration. I walked through the Event Setup and was able to view the event for online registration. I get to the end and received the following error message. I'm not sure what to do with this.

I'm working through set up for WCM. I'm in System Setup > Set up Web components > Exchange Settings.

iMIS Reference materials for public View Setup state the following:

This window defines the Microsoft Exchange account in your organization from which event meeting requests are sent to users who register for events through the Public view of iMIS.

Release/Version 15.1.2

In WCM I'm working through setup  for Web components.

System set > Organization Configuration > URL of Registration page

Documentation state:

URL of registration page

Specifies the URL of the page for new account registration.

Release/Version 15.1.2

iMIS 15 along with WCM was installed on a  dedicated Web server. Currently, the Web site that was created using WCM has a url of http://[orgnaization_name]-web01/imis15/[site_name]. There is a domain name that should be used for this site. How do we replace the [orgnaization_name]-web01/imis15 with the domain name?

Thanks,

Brad

We're having issues with importing content from dev to production when the content in dev contains links to other content in the the testenvironment (example: ;"><a href="/imistest/DevSite/EventContent/EventPages/file.aspx" needs to be "/imis15/ProdSite/....>  Does the html code exist in the database so that i could do a mass update to change those references to the correct directory path? I am unable to edit the imported file through WCM?

Version 15.1.2.4730

I have finished walking through set up for this site, and when I try to create an account there is no list of states appearing in the state drop down list. Where does this list come from?

Brad

When we export a document (IQA query, business object, content, content type, etc.) today, if that document has custom permissions it will not import into a database that didn't already have that content with custom permissions.  This comes up in the following scenarios:

• Create a new query in Dev, set permissions, test, copy to production.
• Create a generic iPart with permissions, import to new clients.
• Modify the ACL for a query to include a new Role in Dev, then import to Test.
• Import new Nav items we've set up in Dev.

Beside all that, we often have to apply the same permissions over and over to multiple items.  Having our own predefined security sets would make this a lot simpler.  (It would also keep the Access* tables from growing excessively, since each "custom set" is assigned its own key.)