• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1705
  • Last Modified:

Server object error 'ASP 0196 : 80040154' Cannot launch out of process component

I'm on the final (I hope) stages of porting an ASP application to a new Win Server 2003 box (x64).

I am, however, getting the following error:

Server object error 'ASP 0196 : 80040154'

Cannot launch out of process component

/jbasales/dorun/NOISFStep.asp, line 32

Only InProc server components should be used. If you want to use LocalServer components, you must set the AspAllowOutOfProcComponents metabase setting. Please consult the help file for important considerations.

Line 32 is as follows: Set regExcel = Server.CreateObject("Sales_Backend.clsSalesRun")

Note the above 'class' is in a DLL which I have compiled and registered on the new server. It functions with XL and Word stuff.

After a bit of searching I ran the following:

C:\Inetpub\AdminScripts>adsutil set w3svc/AspAllowOutOfProcComponents True

And I got this response:

C:\Inetpub\AdminScripts>adsutil set w3svc/AspAllowOutOfProcComponents True
ASPAllowOutOfProcComponents          : (BOOLEAN) True

Then I ran: net stop iisadmin /y

and :net start w3svc
 (note I got above fix from Expert Exchange, so I did some searching before posting a new question)

Feeling pretty good with myself I ran the application again...but got the same error. Any help is appreciated!
  • 3
  • 2
2 Solutions
Try this comment from

You changed to a 64bit OS and is trying to use a legacy 32bit OCX that
you used on Windows Server 2000. This means you must run the ASP page
with an 32bit application pool on IIS7 to be able to launch the legacy
32bit OCX.

By default, 64bit OS has 64bit application pool, and thus you see
0x80040154. The correct thing is to create a 32bit Application Pool in
IIS7 and assign it to this ASP/VB application.

This problem will not exist if you ran IIS7 on Windows Server 2008
32bit since there will be no mismatched bitness.

Since you changed OS and 64bit, you should expect additional
configuration to maintain compatibility, and even possible

You might have the same problem if you are running win2003 on a 64 bit system.
aaron63Author Commented:
Okay...obviously this is a much more difficult problem than I first thought so I'm increasing the points to the max.

I have a Win 2003 Server Running IIS 6. I don't know why I ever chose 64 bit...well yes I do. Pure ignorance as to the compatibility issues I'd face.

Searching based on your comments I came up with the following solution (or so I thought):

To enable IIS 6 to run 32-bit worker processes follow these steps:

   1. Open a command prompt and navigate to the %systemdrive%\Inetpub\AdminScripts directory
   2. Type the following command:
      cscript.exe adsutil.vbs set W3SVC/AppPools/Enable32BitAppOnWin64 true

If I set this to 'true', however, I get the following error on all webpages on my site:

%1 is not a valid Win32 application.

If I change the above setting back to 'false' everything comes back up fine (but I'm back where I started).

Now one thing I should also mention is that after I recompiled my dll I registered it with the following:

regsvr32 salesbackend.dll

Perhaps I can unregister it and register it again with something else? Would the computer have compiled it as 64 bit since I'm running 64 bit operating system?

Thanks for any help guys. Sorry for my ignorance.
aaron63Author Commented:
Any more input on this question? Should I just reformat the system and start with Windows Server 2003 32 bit? Is that the best solution? If so anyone have a good link to directions on doing this (I don't suppose there is an equivalent of the Win 98 startup disk? ;)
aaron63Author Commented:
No real solution seems to exist for IE6. So I'm reformatting to 32 bit.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now