SOLUTION to MBI 7 if use of "&" results in XML Parsing Error or xmlParseEntityRef:

There is a known issue with some web browsers that if:

  1. you log into MBI 7
  2. and the scheduled items have a client name or a workorder item status or a Schedule marker name that has the “&” ampersand symbol:
    that you will get either of the following similar errors:

(below is example of error if running FireFox)

ML Parsing Error: not well-formed
Location: http://mbi.ayanova.com/(S(gcetp5pjlovn2khhwv5c21n2))/schedule.aspx
Line Number 24, Column 346: <span class=“secthead”>All day<br/></span><span class=“sectsubhead”>2:15 PM - 4:30 PM</span><br/><a href=“ro.aspx?id=64a44c56-111e-4013-8d18-eb43002829b0&o=23”>80</a> <a href=“ro.aspx?id=93ffea54-6699-4b23-b360-69a87ca4ce6d&o=3”>Bill & Sons</a> <br/><a href=“status.aspx?id=975e4bb1-d29e-4191-ba3b-e54cd444514e”>Status & Name</a><br/><br/>
---------------------------------------------------------------------------------------------------------------

(below is example of error if running Google Chrome)

[i]This page contains the following errors:

error on line 24 at column 265: xmlParseEntityRef: no name

Below is a rendering of the page up to the first error.

| Memos | Recent… |
12/6/2012
All day
2:15 PM - 4:30 PM
80 Bill & Sons [/i]

Have also received report occuring with the web browser on a Blackberry 7.1 OS

This issue does not occur with Internet Explorer 9

SOLUTION:
Use IE9
Or at this time client name or a workorder item status or a Schedule marker name to not use the “&” ampersand symbol, instead use “and”

Update January 21 2013 Apply latest AyaNova MBI 7.2.0.0 Hotfix 3 as we are unable to recreate with with 7.2.0.0 Hotfix 3