Solved

Server.CreateObject Failed from ASP in IIS7

Posted on 2013-02-07
2
909 Views
Last Modified: 2013-11-21
We have a 32-bit application written in VB6 that runs as both a desktop client and web application.

Due to an upgrade to the back-end, we moved everything to a new environment Windows 2008 and IIS7. We recreated the 3-tier architecture of the old system (Web server running IIS7, App server where all the application COMs are installed and Database server).

Our problem is that we cannot get the COM objects to execute from the web interface. We can get the simple ASP stuff to work, like display the Login Screen, but once we pur a call out to the application, it fails. We even tried a simple ASP that makes a single call to the remote COM and we get the same error as below (with a different line number).

This is the error that we get:

Server object error 'ASP 0177 : 8007007e'

Server.CreateObject Failed

/submissions/ValidationOfLogin.asp, line 93

8007007e

We have researched all the occurrence of this problem in the internet and so far these are the steps that we have done:

1.      Enabled ASP in IIS 7
2.      Verified the registration the VBR/TLB files for the remote app server from the web server
3.      Allowed Anonymous and User access to all the file directories and COM objects.
4.      Tried different combinations of Default Authentication Level/Default Impersonation Level from the Compoenent Services
4.      We've enabled Failed Request Tracing but we get the same information as above

In an attempt to simplify things, we also took out the web server from the equation and installed IIS7 on the app server. But this did not improve the situation.

This is the Windows Logs>Application entry from the Event Viewer:
The application-specific permission settings do not grant Local access permission to the COM Server application C:\Windows\SysWOW64\inetsrv\w3wp.exe with APPID Unavailable to the user NT AUTHORITY\ANONYMOUS LOGON SID (S-1-5-7) from address LocalHost (Using LRPC). The application set this security permission programmatically; to modify this security permission contact the application vendor.

I downloaded PROCMON and ran it with filter set to the application name but I did not see any catastrophic errors.
0
Comment
Question by:Zopilote
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 53

Accepted Solution

by:
Scott Fell,  EE MVE earned 500 total points
ID: 38865258
I seem to remember I had problems with a com object like this and read somewhere it had to be registered inside the system32 folder for windows 2008 and it worked.  

http://geekswithblogs.net/TheJuice/archive/2011/08/23/classic-asp-in-windows-server-2008-r2.aspx
0
 
LVL 5

Author Comment

by:Zopilote
ID: 38865770
Thanks for the quick response.

I followed the applicable steps outlined in that posting but I still got the same error.

1.      Located the applicationhost.config file in C:\Windows\System32\inetsrv\config
2.      ASP Feature was already enabled.
2.      preCondition='bitness64' was not present in the "ASPClassic" entry for <handlers accessPolicy="Read, Script"> section.
3.      Changed \System32\inetsrv\asp.dll to \SysWOW64\inetsrv\asp.dll
4.      Recycled IIS

At this point, I got a 404.2 error when I tried the site. I had to change the reference to \System32\inetsrv\asp.dll\ to SysWOW64\inetsrv\asp.dll in the <isapiCgiRestriction> section of the applicationhost.config file. Then I got the same error as the original problem.

There was also another reference to \System32\inetsrv\asp.dll in the <handlers accessPolicy="Read, Script"> section immediately below the "ASPClassic" entry for "SecurityCertificate" but changing that did not do anything so I changed it back.
0

Featured Post

Does Powershell have you tied up in knots?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

If you are a web developer, you would be aware of the <iframe> tag in HTML. The <iframe> stands for inline frame and is used to embed another document within the current HTML document. The embedded document could be even another website.
A safe way to clean winsxs folder from your windows server 2008 R2 editions
This tutorial will give a an overview on how to deploy remote agents in Backup Exec 2012 to new servers. Click on the Backup Exec button in the upper left corner. From here, are global settings for the application such as connecting to a remote Back…
This tutorial will give a short introduction and overview of Backup Exec 2012 and how to navigate and perform basic functions. Click on the Backup Exec button in the upper left corner. From here, are global settings for the application such as conne…

734 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question