This article was previously published under Q316952
This article has been archived. It is offered "as is" and will no longer be updated.
With the Web Storage System's security model, you can manage item security descriptors by using Microsoft ActiveX Data Objects(ADO) with the Exchange 2000 OLEDB provider (Exoledb). In Exchange 2000 Server Service Pack 1 (SP1) and later, this functionality may not work and a security descriptor that you retrieve from Exchange 2000 Server may be empty.
To resolve this problem, obtain the latest service pack for Microsoft Exchange 2000 Server. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
301378 XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack
The English version of this fix should have the following file attributes or later:
Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server. This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 3.
The following Microsoft Visual Basic sample retrieves the security descriptor for a given item in the "MyFolder" public folder:
Dim con As ADODB.Connection Dim rec As ADODB.Recordset Dim strSQLQuery As String Dim strSD As String dim strDAVDisplayName as String
If con.State = adStateOpen Then rec.Close con.Close End If
con.Provider = "ExOLEDB.Datasource" con.ConnectionString = strFolderURL con.Open strSQLQuery = "select ""DAV:displayname"",""http://schemas.microsoft.com/exchange/security/descriptor"" from """ + strFolderURL + """" rec.Open strSQLQuery, con If rec.RecordCount > 0 Then rec.MoveFirst strDAVDisplayName = rec.Fields("DAV:displayname") strSD = rec.Fields("http://schemas.microsoft.com/exchange/security/descriptor") End If ...
For the RTM version of Exchange 2000 Server, "strSD" contains the Extensible Markup Language (XML)-formatted security descriptor for the first item in the "MyFolder" public folder that matches the preceding query. In Exchange 2000 Server SP1 and later, this functionality does not work; you receive a run-time error "94" with an "Invalid use of Null" message instead of the expected XML-formatted security descriptor.