... navigate to the SQL Reporting Services folder ... ... SQL Server\ MSSQL \Reporting Services ... ... account has modify permission . ... , add these permissions . ... account has modify permission . ... , add these permissions . ... account has modify permission . If not, add these permissions . ... SBM Event Logging for Mashup Event notifications in Mariner. The following log can be found on the SBM server itself and may help diagnose issues with Mashup Event notifications fired from within a Mariner notification. C:\Program Files\Serena\ Business Mashups \Common\jboss405\bin\AlfEventManager.log
This will occur when anonymous access has been removed from the Reports and ReportServer virtual directories that Mariner is setup to use. It looks like installing any of the MSSQL Service Packs removes anonymous access which is required for reports to function from within Mariner.
The PPM or Agile Admin tool may show you have X number of licenses available but when you try to add a user to a license it may say you don't have any left. The following sql statements can be run against the database to help troubleshoot where the discrepancy may be.
Click the "Enable Serena Business Mashups Security Authentication" check box In the Username/Password fields use the same SBM user that you use in the "Auth" sections of your SBM Web Services. The username specified on this screen is only used to login to the SSO server but the actions performed by the web services will still be performed by the username specified in the Orchestration Workflow steps.
The SQL login or password have changed. To test this, log into SQL Enterprise Manager with the same login that is given in the web.config file. This will give a better error.
Find out from the user having the problem what their login name is for Mariner/PPM Run the following sql command substituting the 'xxxx' value with the users login name. DELETE PES_UserSetting
Often times, running a report from within Report Server will give a better or more complete error message. Mariner provides a pre-configured data source that requires a security token from a logged in user in lieu of a password. It also determines which Mariner data connection to use from this security token.
The PPM Admin tool makes two connections to the PPM database when you attempt to save your changes. One as the NT user running the PPM App Pool and another as the NT account of the Logged in user . For that reason make sure the user you're logged into Windows as is either the same NT account that runs the PPM App pool or that the account you're logged in with is also a member of the database as a db_owner role.
