SYMPTOMS
When Ilsbud.asp, Ilslist.asp, Ilsmps.asp or Shptop.asp is called from the Internet Locator Server (ILS) 2.0 sample templates on an ILS 3.0 server, one of the following error messages may be displayed in the Web browser:
The Internet Locator Server must be installed on the Web server in order to use this page. Please contact the Webmaster for this site.
The Microsoft Personalization System must be installed on the Web server in order to use this page. Please contact the Webmaster for this site.
HTTP 500.100 - Internal Server Error - ASP error
Error Type: Server object, ASP 0177 (0x800401F3)
Invalid ProgID. /ils/userlist.asp, line 3
Please note that these error messages affect all ASP pages that use the
ms.ils or
mps.PropertyDatabase objects.
WORKAROUND
The following workarounds are available to display ILS user information from an ASP page:
NOTE: Microsoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific requirements.
Method 1
Create a custom COM object to access data from the ILS server. A sample COM object is available from the link below:
The following file is available for download from the Microsoft Download Center:
Release Date: Sep-27-2000
For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591 How to Obtain Microsoft Support Files from Online Services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help to prevent any unauthorized changes to the file.
You can use this sample to send a NetMeeting client the information necessary to establish a call with a specified user who is registered on the ILS server.
Method 2
Use ADSI to access the ILS server. Copy the following sample to an IIS 5.0 ASP file named Ilsusers.asp:
<html>
<title>ILS User List</title>
<body>
<font face=arial size=2>
<table border=1 width=100%>
<tr bgcolor=#c0c0c0>
<td align=center width=15%><STRONG> User </STRONG></td>
<td align=center width=30%><STRONG> Location </STRONG></td>
<td align=center width=45%><STRONG> Email </STRONG></td>
<td align=center width=10%><STRONG> NetMeeting </STRONG></td>
</tr>
<%
Dim strServerName, strCn
Dim objADs, objADsContainer
' Connect to the Directory Service<BR/>
strILSport = "1002"
strILsServer = Request.ServerVariables("SERVER_NAME") & ":" & strILSport
Set objADsContainer = GetObject("LDAP://" & strILsServer & "/o=intranet/ou=dynamic")
' Enumerate Items in the members container
For Each objADs In objADsContainer
' the following properties are also available from the objADS object, but were not called:
' port, protocolMimeType, guid, mimeType, smodop, objectClass, ilsA39321630
' ilsA32964638, ilsA32833566, sFlags, ipAddress, c, rfc822Mailbox
On Error Resume Next
Response.Write "<tr>"
' Display the cn of the item
Response.Write "<td align=center>" & objADs.Get("givenName") & " " & _
objADs.Get("surName") & "</td>"
Response.Write "<td align=center>" & objADs.Get("location") & "</td>"
strCn = objADs.Get("cn")
Response.Write "<td align=center><a href=mailto:" & strCn & ">" & strCn & "</a></td>"
Response.Write "<td align=center><a href=callto://" & strILsServer & "/" & strCn & ">call</a></td>"
Response.Write "</tr>"
Next
Set objADsContainer = Nothing
%>
</table>
</font>
</body>
</html>
NOTE: Netscape has chosen not to support the
CALLTO protocol. As a result, a Netscape browser interprets any anchor with href=callto:// as a link to a local path, appending the hyperlink to the end of the BASE URL of the site that the browser is currently viewing. Additional information and workarounds for users with Netscape browsers are provided in the following Microsoft Knowledge Base Article:
273634Netscape Browsers Do Not Support the NetMeeting-installed CALLTO Protocol