In the Membership System installation directory there
is a directory called aspAdmin. This contains
the remote administration files.
Start page is DEFAULT.ASP
The StandardText sub-directory contains the original remote adminstration package and is text based. Start page is INDEX.HTM
The file Incl.asp is included in every other asp file and sets up the OCX object. If you drop the entire directory into your website, it will work appropriately. Try it!
You can set this directory up with Membership Systems protection - using the administrator settings, and you can also apply SSL to this directory which will ensure that the admin's username/password cannot be snooped.
You can also instead use NTCR (Integrated Windows Authentication in Windows 2000) or other protection schemes to protect this directory, however you cannot have both Membership Systems protection as well as another protection scheme at the same time, since they will conflict and the admin will never be able to get in. If you use an alternative protection scheme, it is a good idea to remove the link to the Administration Settings.
When creating a protected directory, you must know the absolute pathname of the directory (not the relative path).
Q. When I try and use ASP examples similar to yours I get 501 errors!
A. Make sure you have ASP installed - you will need at least IIS3 for this.
Q. When I added code similar to your example I get an error saying "object not found".
A. Make sure you use regsvr32 on the component first, and whenever you move it.
Q. I get, "The call to Server.CreateObject failed. The requested object instance cannot be created. "
Be sure files and directories that the object needs have full permissions, including spool directories if appropriate and the installation directory. Note that sometimes permissions do not change to what you have made them until a reboot!
Q. When I added code similar to your example I still get an error saying "object not found". This is what I get:
server object error 'ASP0177:800401f3 the call to Server.CreateObject failed. the requested object instance cannot be created
Perhaps you registered the component with regsvr32 in one subdirectory
and moved it to another. Reregister it.
Perhaps IIS or the login context of the application running the component does not have proper security permissions to access the component or the directory you installed it to.
Maybe your server is running low on memory.
Maybe you need to restart the IIS server or machine after registering the component.
Tip from the top: One user solved the problem which he had on his 2nd NT-Server, by setting read/write access for the user "IUSR_xx" in the directory containing the OCX component.
Q. When I am trying to update information in the database (UserModify) etc, the data seems updated as far as the OCX is concerned, but the other components (the filter, Windows GUI) don't see the change!
A. Check the Application Event Log. Is there a message with Source "Flicks", and Message contents:
The description for Event ID ( 0 ) in Source ( Flicks ) could not be found. It contains the following insertion string(s): Invalid Filename: Code 5, Access denied. The File cannot be accessedIf so, you need to modify the directory containing both the ocx component and the authx.adb database file so that the user "IUSR_MachineName" has full access.
When I use the sendmail method, I get an error message:
Mail was not sent, error message is:Bad recipient name: firstname.lastname@example.org
A. Try surrounding the recipient name with angle brackets: <email@example.com>
Q. When I use the sendmail method, I get 'cannot open socket'.
A. Most likely the recipient is bad, or the mailserver is wrong. Make sure you use "@" instead of a "." in the email address.
When I use the sendmail method, I get
Could not open socket 25
A. There is a problem connecting to your mailserver. Make sure it is not inside a firewall, the address is correct or check for some other problem.
A. The OCX could be being held open by another application. Rename the file, and reboot. That should do it.