Exception EDOMParseError in module xmlrt190.bpl at 0002F20D. An invalid character was found in text content

All installed years of Lacerte will no longer start. Instead, I get "Exception EDOMParseError in module xmlrt190.bpl at 0002F20D. An invalid character was found in text content."

Server went down and a new server has been installed, backup restored. This error appears on both workstations when trying to start Lacerte. Have tried a force update on a workstation, did not help.

Any thoughts would be appreciated?


4 people found this helpful

All years are particularly troubling. I think a call to support is probably best. You can try the FORCE install on at least 2018 https://accountants-community.intuit.com/articles/1859152-running-the-lacerte-web-setup-with-the-force-switch

I assume you have rebooted the server and all work stations. 

Simpler posts https://accountants-community.intuit.com/questions/1850298-does-anyone-know-how-to-fix-this-error-exception-efopenerror-in-module-rtl190-bpl-at-0010f176-cannot-open-file-d-lacerte-18tax-option18-wlog002-w8-access-is-denied

I do see xmlrt190.bpl listed as a file for each year, so hopefully the FORCE install will overwrite and make things good. 

Was this answer helpful? Yes No

No answers have been posted

More Actions

People come to Accountants Community for help and answers—we want to let them know that we're here to listen and share our knowledge. We do that with the style and format of our responses. Here are five guidelines:

  1. Keep it conversational. When answering questions, write like you speak. Imagine you're explaining something to a trusted friend, using simple, everyday language. Avoid jargon and technical terms when possible. When no other word will do, explain technical terms in plain English.
  2. Be clear and state the answer right up front. Ask yourself what specific information the person really needs and then provide it. Stick to the topic and avoid unnecessary details. Break information down into a numbered or bulleted list and highlight the most important details in bold.
  3. Be concise. Aim for no more than two short sentences in a paragraph, and try to keep paragraphs to two lines. A wall of text can look intimidating and many won't read it, so break it up. It's okay to link to other resources for more details, but avoid giving answers that contain little more than a link.
  4. Be a good listener. When people post very general questions, take a second to try to understand what they're really looking for. Then, provide a response that guides them to the best possible outcome.
  5. Be encouraging and positive. Look for ways to eliminate uncertainty by anticipating people's concerns. Make it apparent that we really like helping them achieve positive outcomes.

Select a file to attach: