We built Asp Application using MSXML 4.0 DOM. Everything works perfect on developers' machines and user machines where MSXML 4.0 Parser was installed. Unfortunately, it did not work if Parser 4.0 was not installed. We got Error message like "ActiveX cannot create object on MSXML 2.0 DOM ... " or something like that. Is there where way to fix this problem without installation of Parser 4.0?

I regret to say that but I need help ASAP

Thanks a lot for any help/advise/suggestions.

This message was edited by raymcd at 2003-6-26 13:42:45

---

: We built Asp Application using MSXML 4.0 DOM. Everything works perfect on developers' machines and user machines where MSXML 4.0 Parser was installed. Unfortunately, it did not work if Parser 4.0 was not installed. We got Error message like "ActiveX cannot create object on MSXML 2.0 DOM ... " or something like that. Is there where way to fix this problem without installation of Parser 4.0?
:
: I regret to say that but I need help ASAP
:
: Thanks a lot for any help/advise/suggestions.
:

No. You need the dll registered on the machine that is creating the object. I am not sure exactly what dll you need. This is strange for asp. Unless you are using client side activeX, only the server needs the object. The client should just be getting the resulting HTML.

Are you using Server.CreateObject()? (I assume not since its a client issue)
Are you passing the xml to the client and letting the browser parse it?
Are you using an <object> tag to create an activeX object on the client?

Maybe if you posted more info I could be more useful. :)

-ray

: This message was edited by raymcd at 2003-6-26 13:42:45

---

: : We built Asp Application using MSXML 4.0 DOM. Everything works perfect on developers' machines and user machines where MSXML 4.0 Parser was installed. Unfortunately, it did not work if Parser 4.0 was not installed. We got Error message like "ActiveX cannot create object on MSXML 2.0 DOM ... " or something like that. Is there where way to fix this problem without installation of Parser 4.0?
: :
: : I regret to say that but I need help ASAP
: :
: : Thanks a lot for any help/advise/suggestions.
: :
:
: No. You need the dll registered on the machine that is creating the object.
We using the DOM and it's registered on IIS server I am not sure exactly what dll you need. It's MSXML 4.0 This is strange for asp. Unless you are using client side activeX, only the server needs the object. This portion of code were wriiten by another person and I have to check it but I thing this is our problem. The client should just be getting the resulting HTML.
:
: Are you using Server.CreateObject()? (I assume not since its a client issue)
: Are you passing the xml to the client and letting the browser parse it?
: Are you using an <object> tag to create an activeX object on the client?
:
: Maybe if you posted more info I could be more useful. :)
:
: -ray
:
Thanks for your reply
:

: : This message was edited by raymcd at 2003-6-26 13:42:45

---

: : : We built Asp Application using MSXML 4.0 DOM. Everything works perfect on developers' machines and user machines where MSXML 4.0 Parser was installed. Unfortunately, it did not work if Parser 4.0 was not installed. We got Error message like "ActiveX cannot create object on MSXML 2.0 DOM ... " or something like that. Is there where way to fix this problem without installation of Parser 4.0?
: : :
: : : I regret to say that but I need help ASAP
: : :
: : : Thanks a lot for any help/advise/suggestions.
: : :
: :
: : No. You need the dll registered on the machine that is creating the object.
: We using the DOM and it's registered on IIS server I am not sure exactly what dll you need. It's MSXML 4.0 This is strange for asp. Unless you are using client side activeX, only the server needs the object. This portion of code were wriiten by another person and I have to check it but I thing this is our problem. The client should just be getting the resulting HTML.
: :
: : Are you using Server.CreateObject()? (I assume not since its a client issue)
: : Are you passing the xml to the client and letting the browser parse it?
: : Are you using an <object> tag to create an activeX object on the client?
: :
: : Maybe if you posted more info I could be more useful. :)
: :
: : -ray
: :
: Thanks for your reply
: :
:
:
I took a look at the code and found out that everything was done on server site. So it's not that kind of problem.

: : This message was edited by raymcd at 2003-6-26 13:42:45

---

: : : We built Asp Application using MSXML 4.0 DOM. Everything works perfect on developers' machines and user machines where MSXML 4.0 Parser was installed. Unfortunately, it did not work if Parser 4.0 was not installed. We got Error message like "ActiveX cannot create object on MSXML 2.0 DOM ... " or something like that. Is there where way to fix this problem without installation of Parser 4.0?
: : :
: : : I regret to say that but I need help ASAP
: : :
: : : Thanks a lot for any help/advise/suggestions.
: : :
: :
: : No. You need the dll registered on the machine that is creating the object.
: We using the DOM and it's registered on IIS server I am not sure exactly what dll you need. It's MSXML 4.0 This is strange for asp. Unless you are using client side activeX, only the server needs the object. This portion of code were wriiten by another person and I have to check it but I thing this is our problem. The client should just be getting the resulting HTML.
: :
: : Are you using Server.CreateObject()? (I assume not since its a client issue)
: : Are you passing the xml to the client and letting the browser parse it?
: : Are you using an <object> tag to create an activeX object on the client?
: :
: : Maybe if you posted more info I could be more useful. :)
: :
: : -ray
: :
: Thanks for your reply
: :
:
Registering on the IIS server does you absolutely no good in solving this particular problem. It's obviously a client issue because some clients work and some don't. So the fact that you need the dll registered on every single client that uses it is unchanged.

You can't use client side activeX without proper planning. The users need to be able to download the control or they need it installed prior to using the app. Also, I assume this to be a non-issue but you can't use this app in Netscape. Only MS IE can use ActiveX controls. I would normally assume that you already planned for that, but someone didn't plan for the control to be installed at all so whoever planned the deployment phase obviously didn't look at the architecture too closely.

I'm not all knowing, but I really can't think of too many reasons why you can't parse the xml on the server and send it down as HTML. Not to suggest that one size fits all, but a real slick solution when working with xml is to transform it to html using a model/view/controller design pattern and xslt.

Hope that's helpful.

-ray

This message was edited by kel1981b at 2003-6-30 8:47:23

---

Registering on the IIS server does you absolutely no good in solving this particular problem. It's obviously a client issue because some clients work and some don't. So the fact that you need the dll registered on every single client that uses it is unchanged.
:
: You can't use client side activeX without proper planning. The users need to be able to download the control or they need it installed prior to using the app. Also, I assume this to be a non-issue but you can't use this app in Netscape. Only MS IE can use ActiveX controls. I would normally assume that you already planned for that, but someone didn't plan for the control to be installed at all so whoever planned the deployment phase obviously didn't look at the architecture too closely.
:
: I'm not all knowing, but I really can't think of too many reasons why you can't parse the xml on the server and send it down as HTML. Not to suggest that one size fits all, but a real slick solution when working with xml is to transform it to html using a model/view/controller design pattern and xslt.
:
: Hope that's helpful.
:
: -ray
:
:
Thanks for your reply but this is not what I am looking for.