ActiveVfp and win2k3

Topics: Developer Forum, User Forum
Nov 1, 2009 at 9:35 PM

Hi:

I still can't get activeVfp to deploy properly on win2k3. I am now getting the following error: 

Can someone set out the steps in a 1,23.. format (please don't send me back to the help file) this is a production only install.

I've already installed dotnet2

Thanks

 

Server Error in '/Bpta' Application.
--------------------------------------------------------------------------------
Retrieving the COM class factory for component with CLSID {BEF60CED-FB7C-4835-A927-4EC90F5162CB} failed due to the following error: 80040154. 
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. 
Exception Details: System.Runtime.InteropServices.COMException: Retrieving the COM class factory for component with CLSID {BEF60CED-FB7C-4835-A927-4EC90F5162CB} failed due to the following error: 80040154.
Source Error: 
The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:
1. Add a "Debug=true" directive at the top of the file that generated the error. Example:
  <%@ Page Language="C#" Debug="true" %>
or:
2) Add the following section to the configuration file of your application:
<configuration>
   <system.web>
       <compilation debug="true"/>
   </system.web>
</configuration>
Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.
Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.  
Stack Trace: 
[COMException (0x80040154): Retrieving the COM class factory for component with CLSID {BEF60CED-FB7C-4835-A927-4EC90F5162CB} failed due to the following error: 80040154.]
   ASP.default_aspx.__Render__control1(HtmlTextWriter __w, Control parameterContainer) +31
   System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children) +2065835
   System.Web.UI.Control.RenderChildren(HtmlTextWriter writer) +24
   System.Web.UI.Page.Render(HtmlTextWriter writer) +26
   System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter) +25
   System.Web.UI.Control.RenderControl(HtmlTextWriter writer, ControlAdapter adapter) +121
   System.Web.UI.Control.RenderControl(HtmlTextWriter writer) +22
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1896
 
--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.42 

Server Error in '/Bpta' Application.

--------------------------------------------------------------------------------

 

Retrieving the COM class factory for component with CLSID {BEF60CED-FB7C-4835-A927-4EC90F5162CB} failed due to the following error: 80040154. 

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. 

 

Exception Details: System.Runtime.InteropServices.COMException: Retrieving the COM class factory for component with CLSID {BEF60CED-FB7C-4835-A927-4EC90F5162CB} failed due to the following error: 80040154.

 

Source Error: 

The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:

1. Add a "Debug=true" directive at the top of the file that generated the error. Example:

  <%@ Page Language="C#" Debug="true" %>

or:

2) Add the following section to the configuration file of your application:

<configuration>

   <system.web>

       <compilation debug="true"/>

   </system.web>

</configuration>

 

Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.

 

Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.  

 

Stack Trace: 

 

 

[COMException (0x80040154): Retrieving the COM class factory for component with CLSID {BEF60CED-FB7C-4835-A927-4EC90F5162CB} failed due to the following error: 80040154.]

   ASP.default_aspx.__Render__control1(HtmlTextWriter __w, Control parameterContainer) +31

   System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children) +2065835

   System.Web.UI.Control.RenderChildren(HtmlTextWriter writer) +24

   System.Web.UI.Page.Render(HtmlTextWriter writer) +26

   System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter) +25

   System.Web.UI.Control.RenderControl(HtmlTextWriter writer, ControlAdapter adapter) +121

   System.Web.UI.Control.RenderControl(HtmlTextWriter writer) +22

   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1896

 

 

 

 

--------------------------------------------------------------------------------

Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.42 

 

 

Coordinator
Nov 2, 2009 at 2:01 AM

ok, to start at the beginning, how did you deploy the application?  Did you use PostSetup at all (this is what's used in the avfp setup)?  If not, what were the steps you took?  What version of AVFP is this, btw?

AVFP setup and PostSetup will do the following:

1.) copy over the proper files including VFP runtimes if needed and all associated mtdll files, data files, etc.

2.) regsvr32 the mtdll  (did this happen successfully on the target machine??)

3.) make the virtual directory with proper settings

4.) set access rights and permissions especially for the data.

I did a quick lookup of your error message and it looks like the target machine may be missing some needed files possibly:

http://social.msdn.microsoft.com/forums/en-US/vbgeneral/thread/88a6ea68-f476-4231-822f-27fabe59f458