The information in this FAQ applies to the following:

• ProHelp® EPM, Releases 6.2.0, 6.1.0, 6.0.0


• ProHelp® EPM, Releases 5.2.2, 5.2.1, 5.2.0, 5.1.0, 5.0.0

The SQL Server database must be configured to run reports as a user account that has permissions to read the database and print to the printer. If the default security is used during the installation of ProHelp® EPM and SQL Server, you may not receive any errors relating to the missing permissions. In addition, the user who schedules the report must be part of the sysadmin role or another user (with appropriate permissions) can change an existing job owner to a user who is a part of this role.

All reports should be scheduled on the ProHelp® EPM host, otherwise some/all features may not work correctly. If a ProHelp® EPM client computer schedules a report, you may be able to correct the job in SQL Server Enterprise Manager.

To correct the security for SQL Server Agent service either:

• Open the Control Panel.
• Double-click on Services.
• Select the SQLServerAgent service.
• Press the Startup button
• In the lower half of the service startup dialog, under Log On As, select This Account as shown below:

• Provide an account and password which has read access to the ProHelp® EPM database.
• If reports are to be printed, the above account must also have print permissions on the printer(s) that the report(s) are using.

OR

• In SQL Server Enterprise manager open the computer with your ProHelp® EPM database .
• Open Management.
• Right-click on the SQL Server Agent and select Properties.
• Under Service startup account select This account:.

• Provide an account and password which has read access to the ProHelp® EPM database.
• If reports are to be printed, the above account must also have print permissions on the printer(s) that the report(s) are using.

After configuring the SQLServerAgent service, the service must be stopped and restarted for the changes to take effect. If reports are being generated, a log of their creation will appear in the ProHelp\tmp directory in the file errors.log.