This issue typically occurs if the user was accidentally restricted to certain lines or if the SQL setup is incorrect. Below are the steps to follow:
1. Clear any assigned lines lists.
A. Start Forecaster and log in as an admin.
B. Go to Setup -> Security.
C. Right-click on the user(s) in question and choose Properties.
D. At the bottom-right corner of the User Properties window, there is a Lines List select window. If you scroll through that, I am guessing that one or more lines have been highlighted.
Note: What this select list does is it restricts users to the accounts that are used with the lines you select. It is fairly easy to accidentally select something here when normally the list should be clear.
E. To clear a selection, you will have to click two times in the upper-left corner of the Lines List. The first time you do this it will highlight all lines. The second time will clear them. You most likely want to clear them unless you do want to restrict the user to certain lines.
2. If the above doesn't work, the other potential cause is an incorrect SQL security setup. The steps below walk you through each component that must be in place.
A - Review the Forecaster schema:
Click on the Databases folder to expand the list of databases restored on this server.
Click on the Forecaster 7.0 database name to expand the folder.
Click on the Security folder to expand security components for this database.
Click on the Schemas folder to expand the schema list.
Double-click the Forecaster schema to review its setup.
On the General page, click on Search next to Schema Owner.
Click the Object Types button and select Database Roles only.
In the Search Roles and Users window, type Forecaster in the Object Types window and click Check Names. The Forecaster role should be confirmed. Click OK.
Click OK to close the schema window.
B - Review the Forecaster role:
Click on the Roles folder under the Forecaster 7.0 database name to expand it.
Click on the Database Roles folder to expand the list
Double-click the Forecaster role to review its setup.
Check that the Owner is dbo.
Under Owned Schemas, make sure that the Forecaster schema is the only one checked.
Review the Role Members group to ensure that the Forecaster users are included here.
Review the Forecaster table ownership:
Click on the Tables folder under the Forecaster 7.0 database name to expand the list of defined tables.
Confirm that the tables are owned by the dbo user. The tables with very long names are temporary tables that are owned by the individual users logged into the application. These tables do not have to be owned by dbo.
If the tables are not owned by dbo, contact Microsoft Forecaster Support for additional information.
C - Review the DBO schema:
Click on the Forecaster 7.0 database name to expand the folder.
Click on the Security folder to expand security components for this database.
Click on the Schemas folder to expand the schema list.
Double-click the dbo schema to review its setup.
Click on the Permissions page.
The Users or Roles section will contain the Forecaster role. If it does not exist, click the Add button.
In the Select Objects and Roles window, click Object Types.
Click on the Database Roles checkbox and click OK.
Type in Forecaster and click on Check Names to confirm. Click OK to close this window.
In the section entitled Explicit permissions for Forecaster, the GRANT permission must be selected for the following actions: Alter, Delete, Execute, Insert, Select, Update.
D - Review the Forecaster users setup in SQL Server 2005:
Click on the Security folder for SQL Server 2005 (not under the Forecaster 7.0 database name).
Click on the Logins folder to expand the user list.
Double-click on the Forecaster 7.0 userid to review the setup.
Click the User Mapping page.
Select the checkbox next to the Forecaster 7.0 database.
Assign public and Forecaster as roles.
Share
Report
4,096
All responses (
Answers (
