Page 322 of 749« First...102030...320321322323324...330340350...Last »

Error message when you click Print Preview in Microsoft FRx 6.7 Report Manager: “Print operation failed”

Consider the following scenario. You generate a report in Microsoft FRx 6.7 Report Manager. Then, you click Print Preview to view the report. In this scenario, you receive the following error message:

Print operation failed

Will try to display the print document in its current state.

System.Runtime.InteropServices.COMException

Class not registered.

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 Microsoft FRx 6.7 Service Pack 9.

Article ID: 934825 – Last Review: September 26, 2012 – Revision: 3.0


Applies to
  • Microsoft Business Solutions for Analytics–FRx 6.7 Desktop
  • Microsoft Dynamics GP 9.0
  • Microsoft Business Solutions–Great Plains 8.0
  • 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
kbtshoot kbsolomonfrx kbsmallbusinessfinancialsfrx kbnavisionfrx kbgreatplainsfrx kbexpertiseinter kbaxaptafrx kbmbsmigrate kbbug KB934825

More:
Error message when you click Print Preview in Microsoft FRx 6.7 Report Manager: “Print operation failed”

Error messages when you try to log on to Microsoft FRx or when you try to change companies in Microsoft FRx: "Failed to Create GL Index File"

When you try to log on to Microsoft FRx, or when you try to change companies in Microsoft FRx, you receive the following error messages.

Error message 1

Error message 2

FRx Failed to Create GL Index File

This problem occurs for one of the following reasons.

Cause 1

The path of the .f32 file is incorrect. See Resolution 1 in the “Resolution” section.

Cause 2

The company code in Microsoft FRx contains one or more spaces. See Resolution 2 in the “Resolution” section.

Note Causes 3 through 6 are specifically for the financial application that is mentioned.

Cause 3

In Microsoft Dynamics GP, there are no open fiscal periods or no overlapping fiscal periods. Or, the fiscal period is not populated completely in Microsoft Dynamics SL. See Resolution 3 in the “Resolution” section.

Cause 4

In Microsoft Dynamics GP, there is a budget that has a budget ID of Actual. See Resolution 4 in the “Resolution” section.

Cause 5

There is a segment ID mismatch in Microsoft SQL Server.
The SGMTNUMB field in the GL40200 table is set to 0 in Microsoft Dynamics GP. See Resolution 5 in the “Resolution” section.

Cause 6

In Microsoft Dynamics AX, the default company does not have its own chart of accounts or its own dimensions. The company uses the Virtual Company information. See Resolution 6 in the “Resolution” section.

Resolution 1

To check the path of the .f32 file, follow these steps:

  1. Click Start, point to All Programs, click FRx 6.7, and then click Report Designer.
  2. Determine which specification set you are using for this company. To do this, follow these steps:
    1. Click Company, and then click Information.
    2. Select the company, and then note the name of the specification set on the FRx System Information tab.
    3. Click Close.
  3. Click Company, and then click Specification Sets.
  4. Click the specification set that you noted in step 2b.
  5. Verify that the location of the specification set is valid. Then, in Windows Explorer, locate the folder that contains the .f32 file to confirm that you have access to the directory.

Resolution 2

To resolve this problem, follow these steps:

  1. Click Start, point to All Programs, click FRx 6.7, and then click Report Designer.
  2. Click Company, and then click Information.
  3. Check the Company Code field for spaces.
  4. Delete any spaces, and then click Save.
  5. Repeat steps 1 through 4 earlier in this section for each company.

Resolution 3

To resolve this problem, follow the appropriate steps for the General Ledger financial system.

Note Resolution 3 applies only to Microsoft Dynamics GP and to Microsoft Dynamics SL.

Microsoft Dynamics GP

  1. In Microsoft Dynamics GP or in Microsoft Business Solutions – Great Plains, click Tools, point to Setup, point to Company, and then click Fiscal Periods. The Fiscal Periods Setup dialog box opens.
  2. Make sure that one fiscal period has at least one open period. Make sure that the dates for the fiscal periods do not overlap.
  3. Click OK.

Microsoft Dynamics SL

  1. In Microsoft Dynamics SL or in Microsoft Business Solutions – Solomon, click Module, click General Ledger, and then click GL Setup in the Setup section. The GL Setup dialog box opens.
  2. Click the Fiscal Info tab, and then make sure that the information in the Fiscal Period Ending Dates section is completely filled in.
  3. Click Save.

If you save any changes to the Fiscal Periods dialog box in Microsoft Dynamics GP or in Microsoft Dynamics SL, you must also follow these steps:

  1. In Microsoft FRx, have all users exit Microsoft FRx. To exit Microsoft FRx, click File, and then click Exit.
  2. Locate the shared SysData folder, right-click the shared SysData folder, and then rename all the .g32 files to .old.
  3. To log on to Microsoft FRx, click Start, click Programs, click FRx, and then click Report Designer.
  4. Click Company, click Select Default, click a live company, and then click OK to set the company as the default company.

Resolution 4

In Microsoft Dynamics GP, verify that there is no budget that has a budget ID of Actual, and then re-create the .g32 files. To do this, follow these steps:

  1. Click Start, point to All Programs, click Microsoft Dynamics, click the folder for the version that you are using, and then click GP.
  2. Click Cards, point to Financial, and then click Budgets.
  3. If there is a budget that has a budget ID of Actual, re-create the budget by using a different name. When the new budget is created, delete the budget ID of Actual.

    For more information, click the following article number to view the article in the Microsoft Knowledge Base:

    850688

    (http://support.microsoft.com/kb/850688/
    )

    How to use Excel based budgeting

  4. Re-create the .g32 files. To do this, follow these steps:
    1. Right-click Start, and then click Explore.
    2. In Windows Explorer, locate the SysData folder. To verify the location of the SysData folder in Microsoft FRx, click Admin, click Organization, and then click SysData.
    3. Make sure that all instances of Microsoft FRx are closed, and then delete all the .g32 files or rename all the .g32 files.
    4. Click Start, point to All Programs, point to FRx 6.7, and then click Report Designer.
    5. If a logon window appears, click Cancel.
    6. Click Company, click Select Default, select a live company, and then log on to the company.
    7. To re-create all the .g32 files, repeat step 4f earlier in this section for each live company.

Resolution 5

To resolve this problem, follow these steps:

  1. Exit Microsoft FRx.
  2. In Microsoft SQL Server, select the company database.
  3. Run the following statement in SQL Query Analyzer.
  4. Run the following statement in SQL Query Analyzer.
  5. Verify that the segment IDs listed in the SGMTNUMB column in the SY00300 table match the values in the SGMTNUMB column in the GL40200 table.
  6. If a line in the SGMTNUMB column in the GL40200 table does not match the segment IDs in the SGMTNUMB column in the SY00300 table, remove the line from the GL40200 table.
  7. Back up the GL40200 table. To do this, follow these steps:
    1. Run the following statement in SQL Query Analyzer.
      select * into GL40200temp from GL40200

    2. Verify that the table is backed up. To do this, run the following statement in SQL Query Analyzer.
      select * from GL40200temp

      If you receive results from the statement, the table is successfully backed up.

  8. After you back up the table, run the following statement to remove the incorrect segment ID.
    Delete GL40200 Where SGMTNUMB= ‘value’

    Note In this statement, replace the value placeholder with the incorrect value from the SGMTNUMB column. You must include the single quotation marks.

  9. Start Microsoft FRx. To do this, click Start, point to All Programs, point to FRx 6.7, and then click Report Designer.
  10. Delete the GL40200temp backup table. To do this, run the following statement in SQL Query Analyzer.

Resolution 6

Note This resolution applies to Microsoft Dynamics AX only.

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

Article ID: 935599 – Last Review: September 26, 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 Dynamics SL 7.0
  • Microsoft Dynamics SL 6.5
  • Microsoft Business Solutions–Solomon 6.0
  • Microsoft Dynamics AX 4.0
  • Microsoft Dynamics AX 3.0
  • Microsoft Dynamics NAV 5.0
  • Microsoft Dynamics NAV 4.0
  • Microsoft Business Solutions–Navision 3.70
kberrmsg kbprb kbtshoot kbsolomonfrx kbsmallbusinessfinancialsfrx kbnavisionfrx kbmbsmigrate kbgreatplainsfrx kbexpertiseinter kbaxaptafrx KB935599

Other Support Sites

Community

Get Help Now

Read More:
Error messages when you try to log on to Microsoft FRx or when you try to change companies in Microsoft FRx: "Failed to Create GL Index File"

Error message when you try to generate a report as an Excel worksheet after you install Microsoft FRx 6.7 Service Pack 9: "Error 91 Object Variable or with Block Variable"

In Microsoft FRx 6.7, you receive the following error message when you try to generate a report as a Microsoft Office Excel worksheet:

Error 91 Object Variable or with Block Variable

This problem occurs if the following conditions are true:

  • You installed Microsoft FRx 6.7 Service Pack 9.
  • You are using a thin-client installation of Microsoft FRx.
  • The path in the File name box on the Output Options tab in the Catalog dialog box contains a space.

If you change the path in the File name box to a location that does not contain spaces, you receive the following error message when you try to generate the report:

To resolve this problem, follow these steps:
  1. Download the Client Setup Utility for Microsoft FRx 6.7 Service Pack 9 from one of the following Microsoft Web sites, depending on whether you are a partner or a customer.

    Partners

    Customers

  2. Extract the files to the existing Client Setup directory on the server. Make sure that you back up the FRxClient.cfg file in the directory before you extract the files.

    Note If you do not have a Client Setup directory on the server, you must create the Client Setup directory in the root directory for Microsoft FRx on the server. Next, extract the files to that directory. Then, change the path in the FRxClient.cfg file to the correct path.

  3. From each thin-client workstation, locate the Client Setup directory, and then run the Setup.exe file.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.

Article ID: 935785 – Last Review: September 26, 2012 – Revision: 3.0


Applies to
  • Microsoft Business Solutions for Analytics–FRx 6.7 Desktop
  • Microsoft Dynamics GP 9.0
  • Microsoft Business Solutions–Great Plains 8.0
  • 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
kbtshoot kbsolomonfrx kbsmallbusinessfinancialsfrx kbnavisionfrx kbgreatplainsfrx kbexpertiseinter kbexpertiseadvanced kberrmsg kbaxaptafrx kbmbsmigrate kbbug KB935785

Read the original:
Error message when you try to generate a report as an Excel worksheet after you install Microsoft FRx 6.7 Service Pack 9: "Error 91 Object Variable or with Block Variable"

Error message when you print a report in Microsoft FRx DrillDown Viewer: "Run-time error -2147417848 (80010108)"

oneMscomBlade,oneMsomNav,oneMscomFooter,

See the original post:
Error message when you print a report in Microsoft FRx DrillDown Viewer: "Run-time error -2147417848 (80010108)"

Microsoft Forecaster 6.7 Service Pack 9 is available

You can install Microsoft Forecaster 6.7 Service Pack 9 on any computer that is running Microsoft Forecaster 6.7. This article describes how to install Microsoft Forecaster 6.7 Service Pack 9 in a single-tier environment and in a two-tier environment. This article also includes a list of the problems that are corrected in Microsoft Forecaster 6.7 Service Pack 9.

Microsoft Forecaster 6.7 Service Pack 9 (SP9) is available.

How to obtain Microsoft Forecaster 6.7 Service Pack 9

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

Prerequisites

To install this service pack, you must have Microsoft Forecaster 6.7 installed.

Installation information

To install this service pack, use the appropriate method.

Method 1: Single-tier environments

  1. Log on to the server by using a local administrator account.
  2. Locate and then double-click the FRxForecaster67SP9.exe file.
  3. On the Welcome page, click Next.
  4. Read the license agreement, click I accept the terms of the license agreement, and then click Next.
  5. Type the name and the port number of your Simple Mail Transfer Protocol (SMTP) mail server, and then click Next.

    Note To use the e-mail features in Microsoft Forecaster, you must type a valid SMTP server name or IP address. If you do not have this information, click Next to skip this step. Later, contact your support representative to obtain this information, and then update the information.

  6. Accept the location in which the backup files will be located, or select another location, and then click Next.
  7. If you created a copy of the Microsoft Forecaster database, and if you are ready to upgrade the existing database, click Next.

    Note If you have not created a copy of the database, click Cancel. Then, create a copy of the database before you install the service pack. After you create a copy of the database, install the service pack.

  8. Verify that the correct information is listed, and then click Next to install the service pack.
  9. Click to select the Display Install Log File check box if you want to view the log file, and then click Finish.

    Note The log file is in the same folder in which the Microsoft Forecaster files are installed.

Method 2: Two-tier environments

To install the service pack on the Web server, follow these steps:

  1. Log on to the server by using a local administrator account.
  2. Locate and then double-click the FRxForecaster67SP9.exe file.
  3. On the Welcome page, click Next.
  4. Read the license agreement, click I accept the terms of the license agreement, and then click Next.
  5. Accept the location in which the backup files will be located, or select another location, and then click Next.
  6. Type the name and the port number of your SMTP mail server, and then click Next.

    Note To use the e-mail features in Microsoft Forecaster, you must type a valid SMTP server name or IP address. If you do not have this information, click Next to skip this step. Later, contact your support representative to obtain this information, and then update the information.

  7. Verify that the correct information is listed, and then click Next to install the service pack.
  8. Click to select the Display Install Log File check box if you want to view the log file, and then click Finish.

    Note The log file is in the same folder in which the Microsoft Forecaster files are installed.

To install the service pack on the database server, follow these steps:

  1. Log on to the server by using a local administrator account.
  2. Locate and then double-click the FRxForecaster67SP9.exe file.
  3. On the Welcome page, click Next.
  4. Read the license agreement, click I accept the terms of the license agreement, and then click Next.
  5. Accept the location in which the backup files will be located, or select another location, and then click Next.
  6. If you created a copy of the Microsoft Forecaster database, and if you are ready to upgrade the existing database, click Next.

    Note If you have not created a copy of the database, click Cancel. Then, create a copy of the database before you install the service pack. After you create a copy of the database, install the service pack.

  7. Verify that the correct information is listed, and then click Next to install the service pack.
  8. Click Finish.

Installation support

If you have questions about how to install the service pack, contact Technical Support for Microsoft Dynamics and for related products. You can log on to the Technical Support Web site for Microsoft Dynamics and for related products to create a new support request. To do this, visit the following Microsoft Web site: In the subcategory list, click FRx Forecaster.

You can also contact Technical Support for Microsoft Dynamics and for related products by telephone by calling (888) 477-7877.

File information

The English version of this service pack has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Collapse this tableExpand this table

File name File version File size Date Time Platform
Forecaster67sp9.exe 7.1.100.1248 27,814,832 23-Oct-2006 18:16 x86

Problems that are corrected in Microsoft Forecaster 6.7 SP9

This service pack corrects the problems in Microsoft Forecaster 6.7 that are documented in the following Microsoft Knowledge Base articles:

925565

(http://support.microsoft.com/kb/925565/
)

Error message when you drill into a type A view in Microsoft Forecaster: “Page Can Not Be Displayed”

925569

(http://support.microsoft.com/kb/925569/
)

An element calculation is not calculated on a Type T Total column or on a Type Y Total column in Microsoft Forecaster

925599

(http://support.microsoft.com/kb/925599/
)

You cannot drill down into certain types of view if a type M column is not present in the column set in Microsoft Forecaster

925600

(http://support.microsoft.com/kb/925600/
)

Large fonts are displayed when you drill down to details in a view in Microsoft Forecaster

928521

(http://support.microsoft.com/kb/928521/
)

Only some of the data is copied when you copy data from Microsoft Excel to an input set in Microsoft Forecaster

928524

(http://support.microsoft.com/kb/928524/
)

Historical data is deleted when you run the ExpressLink Wizard in Microsoft Forecaster

928525

(http://support.microsoft.com/kb/928525/
)

A data load is unsuccessful in ExpressLink in Microsoft Forecaster

928526

(http://support.microsoft.com/kb/928526/
)

An element calculation is ignored when you use an element calculation in a column that is a “T Total” type column in Microsoft Forecaster

928527

(http://support.microsoft.com/kb/928527/
)

Error message when you post a version load in Microsoft Forecaster: “Error: ‘value’ is null or not an object”

928912

(http://support.microsoft.com/kb/928912/
)

The drop-down list on the Benefits worksheet incorrectly displays the user name in Microsoft Forecaster

928913

(http://support.microsoft.com/kb/928913/
)

The Design Wizard does not set the correct prompt values when you use the Design Wizard to create a Type P view in Microsoft Forecaster

928914

(http://support.microsoft.com/kb/928914/
)

Error message when you enter today’s date in the “Clear History Before Date” field in the “Clear Tables” screen in Microsoft Forecaster: “The page cannot be displayed”

928915

(http://support.microsoft.com/kb/928915/
)

Microsoft Forecaster 6.7 lets you create a task without requiring you to enter a name for the task

928916

(http://support.microsoft.com/kb/928916/
)

When you delete a company in Microsoft Forecaster 6.7, the company data is not removed from the SQL Server database tables

928917

(http://support.microsoft.com/kb/928917/
)

Error message when you try to insert an account in an input set in Microsoft Forecaster 6.7: “Internet Explorer Script ErrorLine: 32764 Char: 4″

928918

(http://support.microsoft.com/kb/928918/
)

When you use the Zap feature to remove users and assignments, the user is not removed from the Routings view in Microsoft Forecaster 6.7

Article ID: 929204 – Last Review: September 26, 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 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, when used with:
    • Microsoft Business Solutions for AnalyticsForecaster 6.7
kbexpertiseinter kbexpertiseadvanced kbsolomonfrx kbnavisionfrx kbgreatplainsfrx kbaxaptafrx atdownload kbinfo kbmbsmigrate KB929204

More here:
Microsoft Forecaster 6.7 Service Pack 9 is available

No dimension information is included when you create an FRxVirtualMap.xml file in Microsoft FRx 6.7

When you create an FRxVirtualMap.xml file after you import the FRx.xpo file, no dimension map information is included. The FRx.xpo file is provided with Microsoft FRx 6.7 Service Pack 8. Additionally, when you use the Microsoft FRx Dimension Wizard, only the account information appears. None of the dimensions appear in the wizard.
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.
If you downloaded Microsoft FRx 6.7 Service Pack 8 for Microsoft Dynamics AX 4.0 before December 27th, 2006, you must download the updated version of the service pack. The updated version contains a new FRx.xpo file.

Note After you import the updated FRx.xpo file, the job in Microsoft Dynamics AX will be FRxMetaData, instead of DumpVirtualCompanyMap.

Article ID: 930304 – Last Review: September 26, 2012 – Revision: 3.0


Applies to
  • Microsoft Business Solutions for Analytics–FRx 6.7 Desktop
  • Microsoft Dynamics AX 4.0
  • Microsoft Dynamics AX 3.0, when used with:
    • Microsoft Business Solutions for Analytics–FRx 6.7 Desktop
kbbug kbaxaptafrx kbexpertiseinter atdownload kbmbsmigrate KB930304

Follow this link:
No dimension information is included when you create an FRxVirtualMap.xml file in Microsoft FRx 6.7

Error message when you view a report in Microsoft FRx Report Manager: "The page cannot be displayed"

oneMscomBlade,oneMsomNav,oneMscomFooter,

Continue reading here:
Error message when you view a report in Microsoft FRx Report Manager: "The page cannot be displayed"

Error message when you try to access Microsoft Dynamics GP: "Unhandled script exception: Object has no reference: EXCEPTION_CLASS_SCRIPT_BAD_PARAM, SCRIPT_CMD_DEFER_TABLE"

You are using Report Writer in Microsoft Dynamics GP. When you try to access Microsoft Dynamics GP from Report Writer or Modifier, you receive the following error message:

Unhandled script exception: Object has no reference:
EXCEPTION_CLASS_SCRIPT_BAD_PARAM, SCRIPT_CMD_DEFER_TABLE

This
problem occurs if you have the Analytical Accounting module installed in Microsoft Dynamics GP.

A record is missing in the AA Company Setup (AAG00104) table in the Dynamics database for the company you are trying to access.
To resolve this problem, obtain the latest service pack for Microsoft Dynamics GP 10. 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, follow the appropriate method below depending on whether you are using Analytical Accounting.

Method 1: Not using Analytical Accounting

If you are not using Analytical Accounting, you can remove this module from the Dynamics .set file as follows:

To delete the lines for Analytical Accounting in the Dynamics.set file, follow these steps:

  1. Right-click
    the Dynamics.set file, and then click Edit.

    Note By
    default, this file is located
    in the following location:

    C:Program FilesMicrosoft
    DynamicsGP

  2. Decrease the first number in the file by 1.
  3. Delete the following lines.
    3180
    Analytical Accounting
    :C:Program Files/Microsoft Dynamics/GP/AA.DIC
    :C:Program Files/Microsoft Dynamics/GP/AA3180F.DIC
    :C:Program Files/Microsoft Dynamics/GP/AA3180R.DIC
    

  4. On
    the File menu, click Exit.
  5. When you are prompted to save the changes, click Yes.

Note After
you delete the lines, Analytical Accounting will
not run when you start Microsoft
Dynamics
GP.

Method 2: Using Analytical Accounting

If you are using Analytical Accounting, you can insert a record into the AA Company Setup table to resolve this issue. To do this, follow these steps:

  1. Run the following script in SQL Server Management Studio to indentify the Company ID value (CMPANYID) for the company you are working in. You will need this value in a later step.

    Select * from Dynamics..SY01500

  2. Now, run the following script to view the records in the AA Company Setup table:

    Select * from Dynamics..AAG00104

    Note In the results from the “AAG00104″ script, there should be a record in this table for each record or Company ID that you found in step 1 that has AA installed. This error will occur if there is no corresponding record in the AAG00104 table for the company that you logged in to from Report Writer or Modifier.

  3. If you do not find a corresponding record for the company that you are using, then you can insert it by using the appropriate script, as described here:

    Insert into DYNAMICS..AAG00104 Values (CMPANYID, X, Y, 0, 0)

    Note Insert the appropriate values for the placeholders in this script:

    • CMPANYID – Insert the company ID that you found in step 1.

    • X
      – Insert 4 if you have AA successfully installed and activated. If you have AA installed but not yet activated, instead insert 1 for the X placeholder.

    • Y
      – Insert 9 if you are using Microsoft Dynamics GP 9.0 or insert 10 if you are using Microsoft Dynamics GP 10.0.

    Example: If you are using Microsoft Dynamics GP 10.0 and have AA successfully installed and activated in a company that has a company ID (CMPANYID) of 5, you would use the following example script to insert the missing record:

    Insert into DYNAMICS..AAG00104 Values (5, 4, 10, 0, 0)

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 Dynamics GP 10.0 Service Pack 4.

Article ID: 928171 – Last Review: September 26, 2012 – Revision: 5.0


Applies to
  • Microsoft Dynamics GP 10.0
  • Microsoft Dynamics GP 9.0
  • Report Writer
kbtshoot kbexpertiseinter kbmbsinstallation kbmbsmigrate kbbug KB928171
Retired KB Content Disclaimer

This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered “as is” and will no longer be updated.

See more here:
Error message when you try to access Microsoft Dynamics GP: "Unhandled script exception: Object has no reference: EXCEPTION_CLASS_SCRIPT_BAD_PARAM, SCRIPT_CMD_DEFER_TABLE"

Error message when you enter today’s date in the "Clear History Before Date" field in the "Clear Tables" screen in Microsoft Forecaster: "The page cannot be displayed"

You enter today’s date in the Clear History Before Date field in the Clear Tables screen. Then, you click Submit. In this situation, you receive the following error message:

The page cannot be displayed.

This problem occurs in Microsoft 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

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 9.

Article ID: 928914 – Last Review: September 26, 2012 – Revision: 5.0


Applies to
  • Microsoft Business Solutions for AnalyticsForecaster 6.7
  • Microsoft Dynamics GP 9.0
  • Microsoft Business Solutions–Great Plains 8.0
  • Microsoft Dynamics SL 6.5
  • Microsoft Dynamics AX 4.0
  • Microsoft Dynamics AX 3.0
  • Microsoft Dynamics NAV 4.0
  • Microsoft Business Solutions–Navision 3.70, when used with:
    • Microsoft Business Solutions for AnalyticsForecaster 6.7
kbexpertiseinter kbexpertisebeginner kbsolomonfrx kbnavisionfrx kbgreatplainsfrx kberrmsg atdownload kbmbsmigrate kbbug kbaxaptafrx KB928914

See more here:
Error message when you enter today’s date in the "Clear History Before Date" field in the "Clear Tables" screen in Microsoft Forecaster: "The page cannot be displayed"

Error message when you try to insert an account in an input set in Microsoft Forecaster 6.7: "Internet Explorer Script ErrorLine: 32764 Char: 4"

oneMscomBlade,oneMsomNav,oneMscomFooter,

Read the original post:
Error message when you try to insert an account in an input set in Microsoft Forecaster 6.7: "Internet Explorer Script ErrorLine: 32764 Char: 4"

Page 322 of 749« First...102030...320321322323324...330340350...Last »

Recent Comments

    Archives

    Categories