Page 323 of 748« First...102030...321322323324325...330340350...Last »

Error message when you run the dbinstall command in Microsoft Forecaster: "parameter is missing"

When you run the dbinstall command, you receive the following error message: This problem occurs when you follow the instructions for installing a restored database that are included in the release notes for Microsoft Forecaster 6.7 Service Pack 5.
To resolve this problem, obtain the latest service pack for Microsoft Forecaster 6.7. For more information, visit one of the following Microsoft Web sites, depending on whether you are a partner or a customer.

Partners

Customers

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section. This problem was first corrected in Microsoft Forecaster 6.7 Service Pack 6.

Article ID: 912979 – Last Review: September 25, 2012 – Revision: 3.0


Applies to
  • Microsoft Business Solutions for AnalyticsForecaster 6.7
  • Microsoft Dynamics GP 9.0
  • Microsoft Business Solutions–Great Plains 8.0
  • Microsoft Business Solutions–Great Plains 7.5
  • Microsoft Business Solutions–Solomon 6.0
  • Microsoft Dynamics AX 3.0, when used with:
    • Microsoft Business Solutions for AnalyticsForecaster 6.7
kbmbsmigrate kbbug kbsolomonfrx kbgreatplainsfrx kbaxaptafrx KB912979

Read More:
Error message when you run the dbinstall command in Microsoft Forecaster: "parameter is missing"

Data is loaded into the wrong company if you perform an ExpressLink load in a company that was copied in Microsoft Forecaster 6.7

If you perform an ExpressLink load in a company that was copied, the data is loaded into the wrong company. For example, you copy the configuration from Company 1 to Company 2. Then, you perform an ExpressLink load to load the data into Company 2. In this example, the data is loaded into Company 1 again. However, the data should be loaded into Company 2.
To resolve this problem, obtain the latest service pack for Microsoft Business Solutions – Forecaster 6.7. For more information, visit one of the following Microsoft Web sites, depending on whether you are a partner or a customer.

Partners

Customers

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section. This problem was first corrected in Microsoft Forecaster 6.7 Service Pack 6.

Article ID: 912971 – Last Review: September 25, 2012 – Revision: 3.0


Applies to
  • Microsoft Business Solutions for AnalyticsForecaster 6.7
  • Microsoft Dynamics GP 9.0
  • Microsoft Business Solutions–Great Plains 8.0
  • Microsoft Business Solutions–Great Plains 7.5
  • Microsoft Business Solutions–Solomon 6.0
  • Microsoft Dynamics AX 3.0, when used with:
    • Microsoft Business Solutions for AnalyticsForecaster 6.7
kbmbsmigrate kbbug kbsolomonfrx kbgreatplainsfrx kbaxaptafrx KB912971

Originally posted here:
Data is loaded into the wrong company if you perform an ExpressLink load in a company that was copied in Microsoft Forecaster 6.7

You receive a "Run-time error ’438′: Object does not support this property or method" error message when you try to generate a report in Microsoft FRx

When you try to generate a report in Microsoft FRx 6.7, you receive the following error message:

Run-time error ’438′:
Object does not support this property or method

This issue occurs if the following conditions are true:

  • Microsoft FRx 6.7 Service Pack 4 (SP4) is installed.
  • The Prompt for output type at run time option is selected on the Output tab in the Catalog window.
To resolve this problem, obtain the latest service pack for Microsoft FRx. For more information, visit one of the following Microsoft Web sites, depending on whether you are a partner or a customer.

Partners

Customers

To work around this problem, click to clear the Prompt for output type at run time check box.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section. This problem was first corrected in Microsoft FRx 6.7 Service Pack 6.

Article ID: 907908 – Last Review: September 25, 2012 – Revision: 6.0


Applies to
  • Microsoft Business Solutions for Analytics–FRx 6.7 Desktop
  • Microsoft Dynamics GP 10.0
  • Microsoft Dynamics GP 9.0
  • Microsoft Business Solutions–Great Plains 8.0
  • Microsoft Business Solutions–Great Plains 7.5
  • Microsoft Dynamics SL 6.5
  • Microsoft Business Solutions–Solomon 6.0
  • Microsoft Dynamics AX 4.0
  • Microsoft Dynamics AX 3.0
  • Microsoft Dynamics NAV 4.0
  • Microsoft Business Solutions–Navision 3.70
  • FRx Financial Reporter 6.5
kbsolomonfrx kbsmallbusinessfinancialsfrx kbnavisionfrx kbgreatplainsfrx kbaxaptafrx kbmbsmigrate kbbug KB907908

View post:
You receive a "Run-time error ’438′: Object does not support this property or method" error message when you try to generate a report in Microsoft FRx

The data in the Message box of the Import User Wizard is not moved to a corresponding Message column in Microsoft Forecaster

When you import data by using the Import User Wizard in Microsoft Business Solutions – Forecaster, some data is not moved. Specifically, the data in the Message box of the wizard is not moved to a corresponding Message column in the User worksheet. The other data that you want to import does appear in the User worksheet.
This problem occurs because the Message box in the Import User Wizard is not valid.
To resolve this problem, obtain the latest service pack for Microsoft Forecaster 6.7. For more information, visit one of the following Microsoft Web sites, depending on whether you are a partner or a customer.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section. This problem was first corrected in Microsoft Forecaster 6.7 Service Pack 5.

Steps to reproduce the problem

  1. Create a tab-delimited user import file.
  2. Log on to Microsoft Forecaster as an administrative user.
  3. Click Administration, click Import, and then click Import Users.
  4. Click Browse, and then select the import file that you created.
  5. Click to select the Tab Delimited check box, and then click Next.

The page in the wizard contains the Message box. No corresponding column is present in the User worksheet.

Article ID: 907940 – Last Review: September 25, 2012 – Revision: 3.0


Applies to
  • Microsoft Business Solutions for AnalyticsForecaster 6.7
  • Microsoft Business Solutions–Great Plains 8.0
  • Microsoft Business Solutions–Great Plains 7.5
  • Microsoft Business Solutions–Solomon 6.0
  • Microsoft Dynamics AX 3.0, when used with:
    • Microsoft Business Solutions for AnalyticsForecaster 6.7
kbsolomonfrx kbaxaptafrx kbgreatplainsfrx kbmbsmigrate kbbug KB907940

Read the original post:
The data in the Message box of the Import User Wizard is not moved to a corresponding Message column in Microsoft Forecaster

Account numbers that are outside the specified range are incorrectly included in the calculation when you use the range calculation function in Microsoft Forecaster 6.7

When you use the range calculation function in Microsoft Business Solutions – Forecaster 6.7, you notice that account numbers that are outside the specified range are incorrectly included in the calculation
To resolve this problem, obtain the latest service pack for Microsoft Forecaster 6.7. For more information, visit one of the following Microsoft Web sites, depending on whether you are a partner or a customer:

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.
This bug was corrected in Service Pack 6 for Microsoft Forecaster 6.7.

Article ID: 912981 – Last Review: September 25, 2012 – Revision: 3.0


Applies to
  • Microsoft Business Solutions for AnalyticsForecaster 6.7
  • Microsoft Dynamics GP 9.0
  • Microsoft Business Solutions–Great Plains 8.0
  • Microsoft Business Solutions–Great Plains 7.5
  • Microsoft Business Solutions–Solomon 6.0
  • Microsoft Dynamics AX 3.0, when used with:
    • Microsoft Business Solutions for AnalyticsForecaster 6.7
kbmbsmigrate kbbug kbsolomonfrx kbgreatplainsfrx kbaxaptafrx KB912981

Continue reading here:
Account numbers that are outside the specified range are incorrectly included in the calculation when you use the range calculation function in Microsoft Forecaster 6.7

Revenue data that is imported from an XML file does not populate the 13th period or the comments field in Microsoft Forecaster

Microsoft Business Solutions-Axapta 3.0 is now part of Microsoft Dynamics AX 3.0. All references to Microsoft Business Solutions-Axapta and Microsoft Axapta pertain to Microsoft Dynamics AX.

Revenue data that is imported from an XML file does not populate the 13th period or the comments field in Microsoft Business Solutions – Forecaster.
To resolve this problem, obtain the latest service pack for Microsoft Forecaster 6.7. For more information, visit one of the following Microsoft Web sites, depending on whether you are a partner or a customer:

Partners

Customers

This problem was first corrected in Microsoft Forecaster 6.7 Service Pack 4.

Steps to reproduce the problem

  1. Click Administration, and then click Defaults.
  2. In the Number of Input Periods box, click to select 13.
  3. Create a version with 13 periods. To do this, follow these steps:
    1. Click Administration, and then start the Version wizard.
    2. In the ID box, type 5B, type Benefits in the Label box, and then click Next.
    3. Click to select 2005 for the year, and then click Next.
    4. Accept the defaults for periods 1 through 12. For period 13, type Jan1, and then click Next.
    5. Click Finish to complete the wizard.
  4. Create a column set. To do this, follow these steps:
    1. Click Setup, and then start the Column Set wizard.
    2. In the Column Set Name box, type B5_13MNTH, and then click Next.
    3. Click to select Monthly Periods, and then click Next.
    4. In the Version box, click to select 5B.
    5. Add all the months from the left column to the right column.
    6. Click to select the box next to Click to add total column, and then click Next.
    7. Accept the default in step 3b of the wizard, and then click Next.
    8. Click Finish to complete the wizard.
  5. Create a line set. To do this, follow these steps:
    1. Click Setup, and then start the Line Set wizard.
    2. In the Line Set Name box, type Workcomp.
    3. Click to select the Account option, and then click Next.
    4. Click to select account 21001, and then click Next.
    5. Click Finish to complete the wizard.
  6. Create an input set. To do this, follow these steps:
    1. Click Administration, and then start the Input Set wizard.
    2. In the Input Set ID box, type 5B13MNTH, and then click Next.
    3. In the Line Set box, click to select Workcomp, click to select B5_13MNTH in the Column Set box, and then click Next.
    4. In the Version box, click to select 5B, and then click Next.
    5. Click Finish to complete the wizard.
  7. Create a second line set. To do this, follow these steps:
    1. Click Setup, and then start the Line Set wizard.
    2. In the Line Set Name box, type Workcomp.
    3. Click to select the Account option, and then click Next.
    4. Click to select accounts 21001, 26900, and 26901, and then click Next.
    5. Click Finish to complete the wizard.
  8. Click Setup, and then click Planning.
  9. Open the Products worksheet, and then follow these steps:
    1. Click the Insert button, and then insert one row.
    2. In the ID box, type TestProduct.
    3. In the Label box, type Test Product.
    4. In the LineSet box, type Workcomp.
    5. Click Save to save the worksheet.
  10. Create an XML file for importing. The import file should have data for periods 1 through 13 for center 11010.
  11. Click Administration, click Import, and then click Import Planning and Modeling.
  12. Click Browse, and then click to select the revenue import file.
  13. Select the XML option, and then click Next.
  14. Map the fields to the correct fields in the XML file, and then click Next.
  15. Click to select version ID 5B, and then click Finish.

In the input set, the 13th period does not contain any data. The import process imports only periods 1 through 12.

Article ID: 902700 – Last Review: September 25, 2012 – Revision: 3.0


Applies to
  • Microsoft Business Solutions for AnalyticsForecaster 6.7
  • Microsoft Dynamics GP 9.0
  • Microsoft Business Solutions–Great Plains 8.0
  • Microsoft Business Solutions–Great Plains 7.5
  • Microsoft Dynamics SL 6.5
  • Microsoft Business Solutions–Solomon 6.0
  • Microsoft Dynamics AX 3.0, when used with:
    • Microsoft Business Solutions for AnalyticsForecaster 6.7
kbsolomonfrx kbgreatplainsfrx kbaxaptafrx kbmbsmigrate kbbug KB902700

Other Support Sites

Community

Get Help Now

Taken from:
Revenue data that is imported from an XML file does not populate the 13th period or the comments field in Microsoft Forecaster

An account is not included in calculations that use a range when the account number appears on the last line of an input set in Microsoft Forecaster

Microsoft Business Solutions-Axapta 3.0 is now part of Microsoft Dynamics AX 3.0. All references to Microsoft Business Solutions-Axapta and Microsoft Axapta pertain to Microsoft Dynamics AX.

When an account number appears on the last line of an input set, that account is not included in calculations that use a range in Microsoft Business Solutions – Forecaster.
To resolve this problem, obtain the latest service pack for Microsoft Forecaster 6.7. For more information, visit one of the following Microsoft Web sites, depending on whether you are a partner or a customer.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section. This problem was first corrected in Microsoft Forecaster 6.7 Service Pack 4.

Steps to reproduce the problem

Create an account

  1. Click Administration, and then open the Account worksheet.
  2. Click the Insert button to insert a new line.
  3. In the Label box, type Total. In the Description box, type Total.
  4. In the Type column, enter A. In the Level column, select Posting.
  5. Save the Account worksheet.

Create a version

  1. Click Administration, and then start the Version wizard.
  2. In the Version ID box, enter a version identifier. In the Label box, enter a label, and then click Next.
  3. Select a year, and then click Next.
  4. In step 3 of the wizard, accept the default values, and then click Next.
  5. Click Finish.

Create a line set

  1. Click Setup, and then start the Line Set wizard.
  2. In the Line Set Name, type a name. Select Account, and then click Next.
  3. In the Account List list, select the Total account that you created, and then select accounts 13050, 13051, and 13060.

    Note You can select any three accounts. However, these steps use accounts 13050, 13051, and 13060.

  4. Click Next, and then click Finish.

Create a calculation set

  1. Click Setup, and then open the Calc Set worksheet.
  2. Create a calculation set that uses the following line calculation:

    Total=’13050..’13060

Create a column set

  1. Click Setup, and then start the Column Set wizard.
  2. In the Column Set Name box, type a name. Click to select the Input check box, and then click Next.
  3. Select Monthly Periods, and then click Next.
  4. In step 3 of the wizard, select the version ID that you created in the “Create a version” section. Select all the periods, insert the periods in the right column, and then click Next.
  5. Accept the default values in step 3b of the wizard, and then click Next.
  6. Click Finish.

Create an input set

  1. Click Administration, and then open the Input Set worksheet.
  2. Click the Insert button to create a new input set.
  3. In the Input Set ID box, enter an input set identifier. In the Label box, type a label.
  4. Enter the column set, the line set, the calculation set, and the version identifier that you created.
  5. Save the input set.

Final steps

  1. Click Input, and then select the input set that you created.
  2. In account 13050, enter 1000. In account 13051, enter 2000. In account 13060, enter 5000.
  3. Click the Calculator button.
  4. Verify the amount in the Total line.

Article ID: 902670 – Last Review: September 25, 2012 – Revision: 4.0


Applies to
  • Microsoft Business Solutions for AnalyticsForecaster 6.7
  • Microsoft Dynamics GP 9.0
  • Microsoft Business Solutions–Great Plains 8.0
  • Microsoft Business Solutions–Great Plains 7.5
  • Microsoft Dynamics SL 6.5
  • Microsoft Business Solutions–Solomon 6.0
  • Microsoft Dynamics AX 3.0, when used with:
    • Microsoft Business Solutions for AnalyticsForecaster 6.7
kbsolomonfrx kbgreatplainsfrx kbaxaptafrx kbmbsmigrate kbbug KB902670

Other Support Sites

Community

Get Help Now

Read More:
An account is not included in calculations that use a range when the account number appears on the last line of an input set in Microsoft Forecaster

The product documentation does not indicate that HR jobs are present in the JobQ queue after you upgrade to Microsoft Forecaster 6.7 Second Edition

After you upgrade to Microsoft Forecaster 6.7 Second Edition, the HR jobs are present in the JobQ queue. The HR jobs are running even after you receive a message that states that the installation is complete. However, the product documentation does not indicate that the HR jobs are present in the JobQ queue after you receive the message.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section. This problem was first corrected in Microsoft Forecaster 6.7 Service Pack 4.
The service pack that is mentioned in the “Status” section updates the product documentation. The updated product documentation tells the user not to restart Microsoft Forecaster after the user receives a message that states that the installation is complete. Restarting Microsoft Forecaster may cause the HR jobs to fail.

Article ID: 902703 – Last Review: September 25, 2012 – Revision: 3.0


Applies to
  • Microsoft Business Solutions for AnalyticsForecaster 6.7
  • Microsoft Dynamics GP 9.0
  • Microsoft Business Solutions–Great Plains 8.0
  • Microsoft Business Solutions–Great Plains 7.5
  • Microsoft Dynamics SL 6.5
  • Microsoft Business Solutions–Solomon 6.0
  • Microsoft Dynamics AX 3.0, when used with:
    • Microsoft Business Solutions for AnalyticsForecaster 6.7
kbsolomonfrx kbgreatplainsfrx kbaxaptafrx kbmbsmigrate kbbug KB902703

See more here:
The product documentation does not indicate that HR jobs are present in the JobQ queue after you upgrade to Microsoft Forecaster 6.7 Second Edition

Error message when you export Microsoft FRx reports to Excel or to formatted Excel: "Error 5"

Consider the following scenario:
  • You export Microsoft Business Solutions – FRx reports to Excel or to formatted Excel.
  • The Subtotal on segment option is selected.
  • You select the Rounding Adjustments option in the Row Format window.
  • The rounding adjustment row references a row that links to the general ledger.

In this scenario, you receive the following error message:

Error 5: Invalid procedure call or argument

To resolve this problem, obtain the latest service pack for Microsoft FRx 6.7. For more information, visit one of the following Microsoft Web sites, depending on whether you are a partner or a customer:
Partners
Customers
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section. This problem was first corrected in FRx Reporter 6.7 Service Pack 4.

Steps to reproduce the problem

  1. Click Start, click All Programs, click FRx 6.7, and then click Report Designer.
  2. Click Company, click Select Default, click to select the FW company, and then click OK.
  3. Click File, click Open, click to select the BS report, and then click OK.
  4. In the Detail Level box, click to select Financial & Account.
  5. Click the Report Options tab, click the Acct/Tran Detail tab, and then click to select Subtotal on segment.
  6. Click the Output tab, click the Output Options tab, and then click to select either Formatted Excel or Excel.
  7. Click Save, and then click Generate Report.

You expect that the report will be generated and subtotaled based on the segment that is designated on the Acct/Tran Detail tab on the Report Options tab.

Instead, you receive the error message that is mentioned in the “Symptoms” section.

Article ID: 902626 – Last Review: September 25, 2012 – Revision: 4.0


Applies to
  • Microsoft Business Solutions for Analytics–FRx 6.7 Desktop
  • Microsoft Dynamics GP 10.0
  • Microsoft Business Solutions–Great Plains 8.0
  • Microsoft Business Solutions–Great Plains 7.5
  • Microsoft Business Solutions–Solomon 6.0
  • Microsoft Dynamics AX 3.0, when used with:
    • Microsoft Business Solutions for Analytics–FRx 6.7 Desktop
kbmbsmigrate kbbug kbsolomonfrx kbsmallbusinessfinancialsfrx kbgreatplainsfrx kbaxaptafrx KB902626

View article:
Error message when you export Microsoft FRx reports to Excel or to formatted Excel: "Error 5"

You receive "No Permissions for Company Code" and "Object Variable or With block variable not set" error messages when you try to generate a report in Microsoft FRx Report Launcher

Microsoft Business Solutions-Axapta 3.0 is now part of Microsoft Dynamics AX 3.0. All references to Microsoft Business Solutions-Axapta and Microsoft Axapta pertain to Microsoft Dynamics AX.

When you try to generate a consolidated report in Microsoft Business Solutions – FRx 6.7 Report Launcher, and you enable Microsoft FRx security, you receive the following error messages, where XXX is the name of the company for which you are trying to generate the report:

Error #0: No Permission for Company Code: XXX. Report will close.

Error #91: Object Variable or With block variable not set.

To resolve this problem, obtain the latest service pack for Microsoft FRx 6.7. For more information, visit one of the following Microsoft Web sites, depending on whether you are a partner or a customer:
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the “Applies to” section.
This bug was corrected in Microsoft FRx Reporter 6.7 Service Pack 4.

Steps to reproduce the problem

  1. Click Start, click All Programs, click FRx 6.7, and then click Report Designer.
  2. Click Company, click Information, and then click New.
  3. Create two new companies in FRx. Create a company by naming it TWO. Point the company to the TWO company in Microsoft Dynamics GP or in Microsoft Business Solutions – Great Plains. Create a second company by naming it TWOA. Also point this company to the TWO company in Microsoft Dynamics GP or in Microsoft Business Solutions – Great Plains.
  4. Close the Company Information window.
  5. Click Admin, click Organization, and then click FRx Security. Click to select the Use FRx Security check box, and then click OK to save the changes and to close the window.
  6. Click Company, click Select Default, select TWO, and then click OK. When you are prompted, log on as an administrator in Microsoft FRx, and then log on as an sa user of the TWO database.
  7. Click File, click New, and then click Tree. Create a consolidated report by using a tree that contains both the TWO and the TWOA companies.
  8. Click File, click Save, and then enter a name for the new tree.
  9. Click File, click New, and then click Catalog.
  10. Assign an existing row and an existing column to the catalog. Select the tree that you created in step 8, and then assign the tree to the catalog.
  11. Click the Output tab, click the Output Options tab, and then select DrillDown Viewer on the Output Type list.
  12. In the Catalog ID box, enter a name.
  13. Click Save, and then click Generate Report. The report will generate correctly to the DrillDown Viewer, and you will see all the information for both companies.
  14. Click Start, click All Programs, click FRx 6.7, and then click Report Launcher.
  15. Log on to Report Launcher as an administrator.
  16. Select TWO.
  17. Select and generate all units of the report that you created in step 13.
  18. When you are prompted for a user ID and password, click either the Use Separate Login Information option or the Use Same Login Information option, enter the sa database user and the password for both the TWO and the TWOA companies, and then click OK.

Expected result:

The report generates to the DrillDown Viewer as it did in step 13.

Actual Result:

The report does not generate. Instead, you receive the following error messages:

Error #0: No Permission for Company Code: TWOA. Report will close.

Error #91: Object Variable or With block variable not set.

Article ID: 902637 – Last Review: September 25, 2012 – Revision: 4.0


Applies to
  • Microsoft Business Solutions for Analytics–FRx 6.7 Desktop
  • Microsoft Dynamics GP 10.0
  • Microsoft Dynamics GP 9.0
  • Microsoft Business Solutions–Great Plains 8.0
  • Microsoft Business Solutions–Great Plains 7.5
  • Microsoft Dynamics SL 6.5
  • Microsoft Business Solutions–Solomon 6.0
  • Microsoft Dynamics AX 3.0
kbsmallbusinessfinancialsfrx kbsolomonfrx kbgreatplainsfrx kbaxaptafrx kbmbsmigrate kbbug KB902637

Other Support Sites

Community

Get Help Now

Original post:
You receive "No Permissions for Company Code" and "Object Variable or With block variable not set" error messages when you try to generate a report in Microsoft FRx Report Launcher

Page 323 of 748« First...102030...321322323324325...330340350...Last »

Recent Comments

    Archives

    Categories