Problems with Rlabkey package | Brian Connolly | 2012-07-17 14:06 |
Status: Closed | ||
Michael, Given that the status code is 401, this most likely an authentication problem or lack of permissions problem. It could be something else, but we should we rule out authentication or permissions first. The first thing to check, is your labkey.log file. You will want to see if there are any login error messages in the file. All failed login attempts get logged here. The second thing to check is Audit Log. All successful and failed logins get logged here. This log will tell you if the Rlabkey connection has successfully logged prior to attempting the selectRows. To access the AuditLog - goto the Admin Console - Click on the Audit Log link - In the drop down at the top of the page, select User Events The third thing to verify is that the user account actually has permissions to access the table in the selectRows statement, by logging into the LabKey Server as that user and using the schemaBrowser. |
||