Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 898
  • Last Modified:

XP Pro & IIS 5.1 ASP Server object error ASP 0177

The following error message is generated when attempting to preview an ASP web page with Frontpage 2002 under Windows XP Professional.

  Server object error 'ASP 0177 : 8007007e'
  Server.CreateObject Failed
  /henrycty/treasurer/search.asp, line 111
  8007007e

The ASP command triggering the error is the "Scripting.FileSystemObject" in a command such as this:

  set fs = Server.CreateObject("Scripting.FileSystemObject")
  set fm = fs.GetFile(Server.MapPath("../fpdb/treas.mdb"))

The error only happens on my XP computer, the code works fine on the host server this code is published to.

I've been to a lot of places attempting to fix this and the one thing I'm "rather" sure it is NOT is Norton AntiVirus script blocking -- This computer came pre-installed with NAV 2002, but I've uninstalled it, ran RNAV, manually removed all possible references to script blocking (see http://service1.symantec.com/SUPPORT/nav.nsf/docid/2001083014161306 for full details) and now I'm running NAV corporate edition version 7.6 which does NOT have script blocking (yes, i've also tried removing NAVCE 7.6, but still get the error.)  I've also completed a registry search for "scriptblocking" and have disabled (renamed) what I could to their default settings.

I'm the only user on this XP computer and therefore also have Administrator rights to the system.  Through all of my searches I've came across this ASP code:

<%
  Response.Write("LOGON_USER: " & _
  Request.ServerVariables("LOGON_USER"))
%>

Which displays: LOGON_USER: PC822\Bruce Lang

According to this MS knowledge base article Q175804 (http://support.microsoft.com/default.aspx?scid=kb;EN-US;q175804)

So, the directory and file permissions should be using me and not the anonymous "IUSR_PC822" correct?

I've also attempted to change the IIS authentication method under "Control Panel | Administrative Tools | Internet Information Services" navigate to "Default Web Site" and/or down to the actual web site name - Do a right-click on the item you've navigated to and select Properties / Directory Security / Edit - And selected "Anonymous access" and entered my name (i.e. "Bruce Lang") and my password (also tried having "Allow IIS to control password" selected with my name)

Now what?  I'm afraid to remove and reinstall IIS for these possible problems: 1) Getting rid of my web sites  2) Loosing preferences  3) XP "thinking" all IIS "Windows update"'s are applied if it's reinstalled 4) Who knows...

Thank you very much - Happy hunting
0
bdlang
Asked:
bdlang
  • 3
  • 2
1 Solution
 
dew_associatesCommented:
This message often results from an unregistered DLL. It could also be one of several related issues:

1. DLL or one of its dependent files missing or damaged
2. DLL(s) not registered
3. Inadequate NTFS file permissions on DLL or its dependent files
4. Inadequate Registry permissions to read DLL's registry entries

You can run the third-party tools RegMon and FileMon while the error is being reproduced, which may help to troubleshoot this error condition. http://www.sysinternals.com/

Look for possible rules conflicts as well.
0
 
bdlangAuthor Commented:
I've used these two utilities in an earlier attempt to fix the problem.  Then as now an open attempt to the Symantec Script Blocking file SCRBLOCK.DLL was displayed.  As previously noted - NAV and its files were completely deleted from this computer along with the SCRBLOCK.DLL.  So, this could not be the problem since the file no longer existed - right?  WRONG!

It turns out that the registry references containing the SCRBLOCK.DLL file was disabling scripting because the references should have been pointing to another file.

The scripting worked after changing the "(Default)" value of the following registry entries from "C:\Program Files\Common Files\Symantec Shared\Script Blocking\ScrBlock.dll"  TO  "C:\WINNT\System32\scrrun.dll"

HKEY_CLASSES_ROOT\
  CLSID\
    {0D43FE01-F093-11CF-8940-00A0C9054228}\
      InprocServer32

HKEY_LOCAL_MACHINE\
  SOFTWARE\
    Classes\
      CLSID\
        {0D43FE01-F093-11CF-8940-00A0C9054228}\
          InprocServer32

HKEY_LOCAL_MACHINE\
  SOFTWARE\
    Classes\
      CLSID\
        {72C24DD5-D70A-438B-8A42-98424B88AFB8}\
          InProcServer32

HKEY_LOCAL_MACHINE\
  SOFTWARE\
    Classes\
      CLSID\
        {F935DC22-1CF0-11D0-ADB9-00C04FD58A0B}\
          InProcServer32

And the "(Default)" value of these registry entries to "C:\WINNT\System32\wshom.ocx"

HKEY_CLASSES_ROOT\
  CLSID\
    {72C24DD5-D70A-438B-8A42-98424B88AFB8}\
      InProcServer32

HKEY_CLASSES_ROOT\
  CLSID\
    {F935DC22-1CF0-11D0-ADB9-00C04FD58A0B}\
      InProcServer32

This was an "uneducated" guess on ALL of these registry values, because of what values were showing within or around the registry key.  That means some of these values could be wrong, but this "seems" to have fixed my problem.
0
 
dew_associatesCommented:
That would make sense, as changing the default back to scrrun.dll re-enables both policies and permissions on XP as opposed to a brick wall blocking as with Symantecs ScrBlock.dll. You would think that they would better document their changes, or at least build in more flexibility. I don't see anything errant in the changes you made, but only testing will tell for sure. The only hole I can see would be if Symantecs installer deleted a necessary key to build reliance around their DLL.
0
 
bdlangAuthor Commented:
Even though the answer dew_associates gave was not, and could not have been, specific enough to directly answer my question - it did give me the fortitude to look a little deeper into the problem.  I really hope this solution helps someone else.

Thanks dew_associates!
0
 
dew_associatesCommented:
Unfortunately BD, there's no possible way to directly equate the error received to the specific problem. However, as noted above, the correct action was to look at the DLL's involved, which was the eventual resolution. That error code has many, many possibilities, and I chose the areas mentioned for no other reason than they best fit the situation.
0

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

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