Server object, ASP 0177 (0x800401F3)

[julian.tklim]

Hi,

I have built a DLL using VB 6.0 and trying to run create the object in
ASP.

Eg:

<%
set a = Server.Createobject("Office.clsOffice")
%>

When the ASP is executed, I received the error message:

Error Type:
Server object, ASP 0177 (0x800401F3)
Invalid class string

I have regsvr32 the dll, added the DLL in Component services, grant
full access to the dll for the ISUR_XXX , IWAM_XXX users and even
administrator. But no matter what, it still doesn't work.

I am using WinXP Pro client and IIS 5.1.

The ASP and DLL works fine in my Win2K server. Is there some settings
in XP that I have missed out?

Any help is appreciated. Thanks.

Julian Lim

 

[Anthony Jones]

Hi,

I have built a DLL using VB 6.0 and trying to run create the object in
ASP.

Eg:

<%
set a = Server.Createobject("Office.clsOffice")
%>

When the ASP is executed, I received the error message:

Error Type:
Server object, ASP 0177 (0x800401F3)
Invalid class string

I have regsvr32 the dll, added the DLL in Component services, grant
full access to the dll for the ISUR_XXX , IWAM_XXX users and even
administrator. But no matter what, it still doesn't work.

I am using WinXP Pro client and IIS 5.1.

The ASP and DLL works fine in my Win2K server. Is there some settings
in XP that I have missed out?

Any help is appreciated. Thanks.

Check that the component has registered properly.

In using RegEdit search for the key Office.clsOffice in HKEY_CLASSES_ROOT.

Under this key look at the value of the CLSID key which will be a GUID.

Now search HKEY_CLASSES_ROOT\CLSID for a key name of that GUID.

Under the GUID key find the value of the InprocServer key. This should be
the path to your DLL.

 

[julian.tklim]

Hi Anthony,

Thanks for your reply. I checked the registry, it is pointing to the
right path where the DLL resides.

I tried to instantiate the object using my EXCEL VBA referencing to the
same DLL. It works fine. Eg: Set a = CreateObject("Office.clsOffice").

But it just totally doesn't work in IIS. Wierd ..
Regards,
Julian

 

[Anthony Jones]

Hi Anthony,

Thanks for your reply. I checked the registry, it is pointing to the
right path where the DLL resides.

I tried to instantiate the object using my EXCEL VBA referencing to the
same DLL. It works fine. Eg: Set a = CreateObject("Office.clsOffice").

But it just totally doesn't work in IIS. Wierd ..
Regards,
Julian

On thing that is confusing me is you mentioning you've been fiddling with
Component services trying to get this to work. Have you installed this DLL
in a COM+ application? If so why is it in a COM+ app?

 

[julian.tklim]

Hi,

Mmm. Sounds like I may be doing the wrong thing.

Yes, I have installed the DLL in COM+ application. It is part of our
client requirement to deploy the DLL in COM+ application. Is it not
suppose to be a COM+ application?

I am sorry for the confusion. I know that instantiate the DLL from
Excel is totally different from using it from the COM+ way. I am just
trying to ensure the DLL is working fine.

Julian