Invalid ProgId ASP 0177 (0x800401F3)

saravananedu · June 8th, 2004, 02:03 AM

Dears...
   I've used a dll (which is created in vb) in my asp application.
   the dllname is customerRegis and the class name is customer
   i registered that dll on the machine where the application is running using regsvr32 <pathname>
so i've used the statement in asp as
   set objcust=server.createobject("customerRegis.custome r")
   and Its Working!... but after... i do changes in my class module and make dll by overwritting the existing dll..and then unregister and register that dll.
now I got an error as ASP 0177 (0x800401F3) Invalid ProgId

pls..guide me..

Yours,
Saran

om_prakash · June 8th, 2004, 02:12 AM

While creating the component again, have u made any chenges to compatibility?

Om Prakash

Imar · June 8th, 2004, 02:42 AM

Hi there,

It's quite possible that IIS is still using the old GUID to refer to the DLL. If you're recompiling without binary compatibility, your project gets a new GUID every time you recompile.
It looks like you need to restart IIS before you un and reregister the DLL.

To avoid all this hassle, host your DLL inside a COM+ package. That's quite easy to do, and will make a lot of things (including recompiling) a lot easier. Look here for more info:

http://authors.aspalliance.com/nothi...ngmn_96&aid=96

Cheers,

Imar
---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.

saravananedu · June 8th, 2004, 06:21 AM

hi...
thanks for ur reply.
actually i didn't set any compatablity option. ie. it's in no compatablity always.

Quote:

quote:Originally posted by om_prakash
While creating the component again, have u made any chenges to compatibility?

Om Prakash

Yours,
Saran

saravananedu · June 8th, 2004, 07:24 AM

hi imar,
thanks for ur reply.
is there any other way apart from MTS/COM+ choice?
because i found little difficulty on COM+ package.
it's a simple object. so i don't want to go into com+.

Yours,
Saran

Imar · June 8th, 2004, 07:31 AM

I think restarting IIS should release the lock on the DLL as well.

However, personally, I think that setting up a COM+ package once is much less work than restarting IIS once. Since you probably need to restart IIS many times, I suggest you take another look at COM+. Following the FAQ I pointed you to should take less than 10 minutes. After that, things are as easy as replacing the DLL and restarting the COM+ package.

Don't forget to set binary compatibility on your project.....

Imar
---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.