Paul S. Withers 26.Aug.10 12:57 PM a Web browser LEILEI - 8.0Windows
Recently we moved LEI to its own dedicated server, but since then have had a problem with a replication activity where Readers and Authors fields are involved. The error message is "Error: You are not authorized to perform that operation, Connector 'SEAS - Update JBA Number', Method -Fetch- (582)". The connector in question is the Notes connection, so that's definitely where the problem is, not the ODBC side.
I've seen a number of posts for this problem, tried the various options, but still have no joy. The keyfilename parameter in the notes.ini is the server ID, which is in the LocalDomainServers group. I've also just now signed the LEI Administrator database with that ID, so that everything should be running with that authority, but it still fails.
LocalDomainServers has access to run unrestricted operations on the target server (different from the server where LEI resides). LocalDomainServers has Manager access to the database in question and has a role which is in the Readers fields of all documents in the view which the connector uses.
I've also tried adding the relevant ID explicitly into both the Readers and Authors fields of the relevant documents, as a belt-and-braces approach, but the job still fails.
The job is set to log key values on error, but I'm not getting a reference to a particular Notes Document it's failing on. I've also tried switching on diagnostic logging, but couldn't find anything more of use.
Can anyone see any holes in my logic for eliminating potential issues, or can suggest any other possible cause? The full activity report is below:
25/08/2010 07:30:16 Activity started
25/08/2010 07:30:22 Trace Statement: <SELECT SEAS75, LREF75 FROM
OSLM13LIV.WGL075 ORDER BY SEAS75>, Connector 'SEAS -
Update JBA No', Method -Select-
25/08/2010 07:30:23 Error: You are not authorized to perform that
operation, Connector 'SEAS - Update JBA Number', Method
-Fetch- (582)
25/08/2010 07:30:23 Activity Ended With An Error
Return to top
Activity error: You are not authori... (Paul S. Withers... 26.Aug.10)
. . 
Print this page
