July 25, 2003 at 6:22 am
I am trying to access the public folders in exchange and cannot do so. I have tried several scenarios and none seem to work. Script as follows:
if exists(select 1 from master..sysservers where srvname = 'E2KPublicFolders') exec sp_dropserver 'E2KPublicFolders', 'droplogins'
go
EXEC sp_addlinkedserver 'E2KPublicFolders',
'Exchange OLE DB provider',
'exoledb.DataSource.1',
'file:\\.\backofficestorage\MyDomain.Local\public folders'
go
In EM when I double click the tables under the linked server I get error 7304 could not create new session on OLE DB provider.
If I add the following code
exec sp_addlinkedsrvlogin
'E2KPublicFolders',
false,
NULL,
'MyDomain\Administrator',
'password'
I get the following error
error 7399 ....... authentication failed
E2K and SQL 2000 are on the same server
Instance was created using SQL authentication
Instance started using administrator account
client permissions on the contacts folder in public folders are anonymous = reviewer
please advise thanks
July 28, 2003 at 8:00 am
This was removed by the editor as SPAM
August 4, 2003 at 2:25 am
I have established a few things
1. THE MSDN example is incorrect
'file:\\.\backofficestorage\localhost\public folders' does not work nor the local domain name but the exchange domain ie the email address domain does.
2. If the instance logon is the administrator then the public folders are visible and I can query them but I cannot query individual mailboxes
3 I have tried the scenarios in Microsoft Knowledge Base Article - 262054 XADM: How to Get Service Account Access to All Mailboxes in Exchange 2000 but none help
I do not want to connect as administrator.
If I connect using any other account I receive
Server: Msg 7399, Level 16, State 1, Line 2
OLE DB provider 'exoledb.DataSource.1' reported an error. Access denied.
OLE DB error trace [OLE/DB Provider 'exoledb.DataSource.1' IUnknown::QueryInterface returned 0x80070005: Access denied
though I can see the public folders in EM but cannot access them
I have searched the web - everyone has the same problem but no solutions. I realise this is an exchange permission issue but the microsoft solution does not help
Please advise - ANYBODY
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply