Xml Parser Issue

Welcome to LawsonTalk. We hope you enjoy your visit.

You're currently viewing our forum as a guest. This means you are limited to certain areas of the board and there are some features you can't use. If you join our community, you'll be able to access member-only sections, and use many member-only features such as customizing your profile, sending personal messages, and voting in polls. Registration is simple, fast, and completely free. After registration, please check your e-mail within 24 hours for an message from us, read it, and reply to it.

Join our community!

If you're already a member please log in to your account to access all of our features:

Xml Parser Issue; Anyone have a workaround?
Topic Started: Jan 19 2006, 01:26 PM (345 Views)
michellm	Jan 19 2006, 01:26 PM Post #1
Newbie Posts: 1 Group: Members Member #351 Joined: January 19, 2006	Hi everyone - we are in the process of rolling out ESS to our organization. However, we have encountered a roadblock: the XML parser problem with IE. Without dispatching a desktop support person to each employee's computer each time the XML parser patch needs to be applied (we have 3600 ees), we wondered if anyone had any bright ideas for how to handle this? :banghead: Any and all suggestions are much appreciated!!



bags	Jan 19 2006, 02:08 PM Post #2
Advanced Member Posts: 42 Group: Members Member #85 Joined: January 12, 2006	We have a login script that checks for the presence of the XML parser and installs it and the hotfix if the parser does not exist. This way there is no manual effort to install the parser and it is automatically installed when new PC's are issued, etc.



mthedford	Jan 19 2006, 02:51 PM Post #3
Super Member Posts: 102 Group: Members Member #257 Joined: January 13, 2006	If you have that many PC's, how do you rollout any new patch or sofware package to them? Do you have any type of remote management for them? If so, then you should be able to push it out automatically. For a manual method, and if the users have security access to install patches to their PC's, then you could put the msxml4 and patch fixes in a public folder that they can access with instructions on how to install/re-install when they get the error. For the reply above, I would like to see your bat file. Is it able to check to see if IE is broken? Even after the patch file is installed, a new IE patch can disable the fix, and the patch file will need to be applied again. How is that handled at your site?



bags	Jan 20 2006, 06:18 AM Post #4
Advanced Member Posts: 42 Group: Members Member #85 Joined: January 12, 2006	I'll send you an email with the script when I have a chance. We have a live cutover of a server migration this weekend so I am pretty tied up at the moment. To be completely honest I have never looked at the script until yesterday. I have been here for a year now and it was in place prior to my arrival. There are a couple of issues that occassionally arise with the XML parser, but for the most part things are clean. I'll mention these items in the email and will post any important details here as well.


« Previous Topic · Other · Next Topic »