Hi,

we are experiencing problems with using type libraries on our asp-pages. We have created our own type libraries which we want to include with using metadata statement:


We use three-tier architecture with VB6 components (asp pages and ui-components on the web server and bl- and da-components on component servers) and we have several testing environments. The statement above works fine on my computer (as they always do) :-) and also on so called development testing servers. However, installing same asp-pages, components and type libraries on our system testing servers leads to error "TypeLib Not Found;METADATA tag contains a Type Library specification that does not match any Registry entry." If I use FILE attribute instead of UUID, it works everywhere. We would prefer using UUID instead of hard coded paths as different servers may have different drives in use etc. and we would want to minimize the work needed when installing new versions.

Does anyone have an idea about how to move on from this? The problem clearly lies on not being able to find type libraries with UUID, but what could be the reason for this? Not having enough permissions to read registry maybe?

Thanks in advance,

Riia

Quick question: Is the UUID the same on your testing server?


 - mega

Yes. The UUID is defined in the .ODL file from which I create the used type library.

Riia

Did you use Regedt32 and made sure that the Everyone group has Read permissions to your TypeLib?
Perhaps this article can help you, even though it is a bit off:
http://support.microsoft.com/default...b;en-us;274038

 - mega

The type library must be correctly registered as the METADATA statement works well with FILE attribute. Also, using the type library from a UI-component on the same server (installed in COM+) works well. The problem arises only when using from ASP with UUID attribute.

I'm a bit thumbs when it comes to technic and that sort of stuff, so would you allow this stupid question, from where can I check this permisson thing? We use W2K. Besides, this type library can be used with FILE attribute so it can't be about a permission to use the type library? For somehow it just doesn't find it when using the UUID so maybe it could be about not having enough permissions to read the registry? Where can I check this from?

I think we'll soon settle down with the solution defining all the possible type libraries in one file that is included in all of our asp-pages (or defining them in the global.asa). At least that way we need to modify the paths only in one place. Still, it would be great to learn what's really behind this problem.

Riia

Choose Run in the Start menu and write Regedt32. Next find your TypeLib either by Find (Ctrl+F) or by looking in the HKEY_[probably LOCAL_MACHINE] folder. Right click on your key and choose Permissions...

Anyway I think your last idea about defining the TypeLib in a global.asa is a better solution than what your started out with.

If it isn't a permission thing then I'm short of ideas.

 - mega

Everyone seemed to have read permissions to the type library so my last choice is to include them all in Global.asa-file with FILE attribute. Thanks anyway from all your help.

Riia