- Microsoft webmatrix run asp classic 64 Bit#
- Microsoft webmatrix run asp classic 32 bit#
- Microsoft webmatrix run asp classic full#
Originally when I installed the server I set up most of my Application Pools to 32 bit mainly for backwards compatibility.
Microsoft webmatrix run asp classic 64 Bit#
My server is Server 2008 64 bit and by default Application Pools run 64 bit. Just to be sure I assigned an Admin user to the Application Pool but still no go.Ī couple of weeks back I had set up a few of my Application pools to 64 bit mode. I double checked permissions for the Application Pool and the permissions of the folder where the DLL lives and both are properly set to allow access by the Application Pool impersonated user. This leaves startup failures or permissions as the problem. Since this both works it tells me the server is registered and working properly. vbs file from the command prompt: Set banner = Server.CreateObject( "wwBanner.aspBanner")
Microsoft webmatrix run asp classic full#
If you don't have a full dev environment on the server you can also use VBScript do the same thing and run the. In my case I tried the server in Visual FoxPro on the server with: loBanners = CREATEOBJECT( "wwBanner.aspBanner")Īnd it worked just fine. One thing I always do to check for COM errors fire up the server in a COM client outside of IIS and ensure that it works there first - it's almost always easier to debug a server outside of the Web environment.
The COM server fails to load during initialization ie. Access permissions aren't set on the COM server (Web account has to be able to read the DLL ie. The server isn't registered (run regserver32 to register a DLL server or /regserver on an EXE server). There are a number of traditional reasons why this error can crop up of course. This error can be caused by a COM server that doesn't load. The class is in fact registered though and the COM server loads fine from a command prompt or other COM client. Results in: Retrieving the COM class factory for component with CLSID failed due to the following error: 80040154 Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)). In ASP.NET invoking the same COM object with code like this: To find out what the problem is this code is more useful at least for debugging: Ĥ29 - ActiveX component can't create object Originally this code had no specific error checking as above so the ASP pages just failed with 500 error pages from the Web server. The ASP classic code that uses it looks like this: The code basically looks up banners from a database table and displays them at random. In my case the code that's been giving me problems has been a FoxPro COM object I'd been using to serve banner ads to some of my pages. (actually without error handling the error just shows up as 500 error page) In classic ASP applications the error will show up as:ĪctiveX component can't create object (Error 429) If you're running on IIS 7 and a 64 bit operating system you might run into the following error using ASP classic or ASP.NET with COM interop.
0 kommentar(er)
