|
"AspDNS never
works. I get Server object error
'ASP 0177:800401f3'." |
This error
means "Invalid class string" -- in
other words the call to
CreateObject failed because the
name object cannot be found by the
OLE sub-system. Causes include:
- You
really didn't run regsvr32 on
the server after all.
- You ran
regsvr32 but it reported an
error.
- Someone
modified security on part of the
registry that's preventing the
OLE subsystem from reading all
or part of the HKEY_CLASSES_ROOT
tree.
- The name
of the object you are trying to
create was mispelled or is
incorrect.
- Determine
if it's a permissions problem
Add the
anonymous user (used by IIS)
to the Administrators group.
The test page then worked,
proving it was a permissions
problem. Do not forget to
remove the anonymous IIS user
from the Admin group!
- Determine
if it is a file permissions
problem:
After
removing the Anonymous user
from the Admin group, add
failure auditing to the file (AspDNS.dll),
which will determine if the
file was ever accessed (by the
lack of the failure event). If
it isn't, this makes it clear
that the failure is prior to
file access but go ahead and
check file/directory
permissions to make sure the
anonymous IIS user can access
the file.
- Check
registry permissions
Using
Regedt32, do find on
AspDNS.dll. Check the
permissions for the key (and
sub keys), and make sure that
the anonymous user has read
rights. Do a find on the
class-id, which contains the
location value, and version,
and check those permissions as
well.
|
|
"AspDNS never
works. I get Server object error
80040154." |
This is the
most common error reported. The
error means that ASP could not
create the object. Causes include:
- You never
ran regsvr32 on the DLL. See
installation section of this
document.
- You
registered the DLL with regsvr32
in one subdirectory and moved it
to another.
- IIS does
not have proper security
permissions to access the DLL or
the directory you installed it
to. See the ASP FAQ (http://www.signmeup.com/faq/)
for information on changing
security.
- Your
server may be running low on
memory.
- Your
evaluation copy has expired. If
you purchased the product be
sure you followed directions to
install your product key.
Note: Some
users have reported that
restarting the server after
registering the DLL was required
to use the component. This should
not be necessary but reportedly
works in a few cases |
|
"AspDNS works
great but sometimes I get 'Server
object error 'ASP 0177:80040154'.
What's causing this?" |
If AspDNS works
fine, then it suddenly stops
working and ASP begins to report
this error, then you've probably
got a memory leak under IIS/ASP.
What has happened is that AspDNS
objects can no longer be created.
This could be caused by a) You
haven't installed the ASP patches
that fix known ASP memory leaks b)
You have a filter or extension
installed that's leaking memory c)
You have another component that's
leaking memory.
AspDNS 2.x
has been run under BoundsChecker
to verify that AspDNS does not
leak memory. |
|
"When running
regsvr32 I get an error: 'LoadLibrary
("AspDNS.dll") failed.
GetLastError returns 0x0000007e." |
- You are
trying to install the AspDNS
Intel binary on NT for Alpha.
Currently there is no Alpha
version of AspDNS. One is under
construction but there's no ETA
for the product yet.
- The DLL
isn't in the same directory you
are running regsvr32 from.
- The
account you are logged in under
doesn't have enough security
privileges to read the DLL.
- The copy
you have is corrupt.
|
|
How do I
upgrade to the latest version? |
Download the
latest "eval" version and follow
the upgrade directions provided
earlier in this document. |
|
Can I
redistribute this control with my
products? |
The license
agreement does not permit
redistribution of AspDNS. |
|
My component is
licensed. Should the Expires
property return a date? |
No. Licensed
versions return N/A for an
expiration date. The registration
process (per the instructions you
received) should be run on the
server. |
|
What are the
minimum security requirements for
AspDNS and IIS/ASP? |
Technically,
the only requirement AspDNS has is
that it must have access to the
temporary directory as noted in
one of the previous
troubleshooting tips. But IIS and
ASP have certain requirements that
must be met to run properly.
Thanks to Carl Howell for
providing this information.
|
ASP
script directory |
Creator
Owner: Full Control (All)(All)
System: ""
Admin: ""
IUSR: (None)(RX) |
|
\WinNT\ |
Creator
Owner: Full Control (All)(All)
System: ""
Admin: ""
IUSR: (WX)(X) |
|
\WinNT\System32\ |
System:
Full Control (All)(All)
Admin: ""
IUSR: (RX)(RX) |
|
Inetsrv |
System:
Full Control (All)(All)
Admin: ""
Everyone: (RX)(RX) |
|
|
Does the 2 CPU
license cover two servers or two
processors? |
In accordance
with the license agreement, the 2
CPU license would cover either 2
single CPU servers or 1 dual CPU
server. With this pricing model,
AspDNS is far more inexpensive
than any "competing" products. |