![]()
Common Tech Support Questions and Answers
Download TShoot, our new Troubleshooting Utility (NT Only)
The component never works. I'm getting "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 the component's installation instructions.
- 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 security chart below for Microsoft recommendations.
- 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 some cases.
The component usually works fine but sometimes I get "Server object error ASP 0177:80040154." If the component 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 some objects can no longer be instantiated. This could be caused by
- You haven't installed the ASP patches that fix known ASP memory leaks.
- You haven't installed updated scripting DLLs (some older versions of VBScript leak memory).
- You haven't installed NT service packs.
- You have a filter or extension installed that's leaking memory.
- You have another component that's leaking memory.
Server object error 'ASP 0178 : 80070005' Server.CreateObject Access Error
Check permissions on the DLL file Microsoft VBScript runtime error '800a01ad'
ActiveX component can't create objectThis is typically due to a lack of security but may also be caused by a resource leakage. We suggest you check the following items in the order listed:
- Check the security on the DLL. Make sure the DLL has Read and eXecute privileges for the SYSTEM user, the anonymous IIS user and any users that authenticate under IIS. You can use file manager and right click on the DLL to bring up the menu. Select properties from the menu, then select the Security tab. Click the permissions button to view the current permissions and adjust if necessary.
- Using regedt32 make sure the registry keys for the class have read privileges for the same users.
- Having checked permissions reboot your server.
You can turn security failure auditing on using User Manager (NT only) to look for the failure point. Execute the page where the problem is occuring and then check the Security Event Log.
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 misspelled or is incorrect.
- If you are running multiple Web servers make sure that the Web server you are hitting is the one you think you are hitting and that it really does have the software installed and registered with COM (using regsvr32).
- Determine if it's a permissions problem
Add the anonymous user (used by IIS) to the Administrators group. Test the page that is failing. If it worked, then 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 component file, 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 the dll name. 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 key, which contains the location value, and version, and check those permissions as well.Error was 452 Insufficient system storage One customer reports: "I've found : my hard disk was full...." When running regsvr32 I get an error: 'LoadLibrary ("dllname.dll") failed. GetLastError returns 0x0000007e. (or some other errors from regsvr32)
- You are trying to install the component Intel binary on NT for Alpha. There are currently no Alpha binaries for ServerObjects Inc. products.
- The DLL is not in the same directory you are running regsvr32 from.
- The account you are logged in under does not have enough security privileges to read the DLL.
- The copy you have is corrupt. Some customers have found that remote control programs were sending files to the remote server using an ASCII mode rather than a binary mode. Be sure the files are transferred using a binary mode transfer!
Using one of the WinSock based components (AspMail, AspPOP3, AspHTTP etc), I am getting, "11004 Valid Name, no data record requested type." The equivalent Winsock code is WSANO_DATA. This commonly occurs with
gethostbyname.Typical causes we've found include:
- You don't have a DNS entry for the server you are operating from or
- You have not set a host and domain for the server.
How do I update to the latest version of the product? Download the latest eval copy from our products page. Follow the upgrade instructions found in the component's instructions. Make sure your license key is installed on your server. ASP is returning "Invalid Application Name" This is a Microsoft ASP problem. The component I'm using is trying to access a network/shared drive. It's not working. What's wrong? The anonymous IIS user does not have rights to access network drives. The is a security feature and has nothing to do with functionality of the component. To change that: 1) Make sure you have a full backup before making any changes to your registry, available. Incorrect settings can make the server machine unusable. ServerObjects Inc. will not be liable for damages arising use or misuse of this information. Be very careful when making changes to the registry. Run Regedt32.exe. Modify the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters registry setting for the value NullSessionShares to include the share name of the disk you wish to access. This allows unauthenticated users to access the specified drive. This may not work on Novell drives.
I'm getting an error from one of the components using Winsock: "Can't send after socket shutdown" or
"Socket is not connected"
What's wrong?
The error indicates that the server you are connecting to has closed the socket connection for some reason. Since there are so many possible reasons, we can't list them all, but the most common are:
- The server doesn't like the domain/IP you are connecting from. Contact the server administrator to resolve this server security/configuration issue.
- The server may be limiting the number of concurrent connections. This might occur when too many users/threads are created to talk with a server. NTMail Developer Edition, for example, seems to throw out more than 5 concurrent SMTP connections and AspMail will return this result. Contact the server administrator to resolve this server configuration issue.
- In other cases the server might be in a maintenance mode and refusing to accept connections. Contact the server administrator to resolve this server configuration issue.
The number of possibilities for this error is almost limitless. You'll have to contact the server administrator and find out why the server is rejecting the connection request.
What will cause Winsock Error 10054 : "Connection reset by peer"? and
Winsock Error 10053 : "Software caused connection abort"
Known causes are:
- Loss of connection to the remote socket
A connection can reset due to a timeout or a reboot of the remote system.- A duplicate IP address on your network
- A misconfigured firewall or proxy server
A firewall or proxy server may block the connection.- Lost of packets or an aborted transfer
If the remote server stops responding, or if too many packets are dropped, or if the remote system aborts a transfer, it can cause a 10054 error.What does "Host not found" mean? The error indicates that the hostname you are using wasn't found in the DNS. Possible solutions include
- With products that use have a RemoteHost or Host property you can change this to an I/P address.
- You can fix the DNS setup or DNS server so that the DNS entry for your hostname is found.
What would cause an "Operation timed out error"? or
"[product] has been working great but suddenly I'm getting an 'Operation timed out' error."
Reasons for operation timed out include:
- The remote server is down, overloaded or simply not responding
- Firewall blocking the port you are trying use
- Packet filtering
- IP route is down
- Your Winsock configured DNS server is down
- Too many lost packets
Security Requirements for IIS and ASP
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)
Copyright © 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003 by ServerObjects Inc. All Rights Reserved.