Forum: Management Reporter Users ]]> http://boards.msxgroup.com/post?id=5850282 Thu, 17 May 2012 17:09:04 GMT http://boards.msxgroup.com/post?id=5850199 Error:

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

FRx is unable to process the output request for the following reason:

C:\Windows\system32\msxml.dll could not be found.

Solution:

To resolve this error, the MSXML files are missing or the incorrect version.  You will need to download and re-apply the following XML components.

1. XML 3.0 SP7

http://www.microsoft.com/downloads/details.aspx?FamilyID=28494391-052b-42ff-9674-f752bdca9582&DisplayLang=en

The file name is msxml3.msi

2. XML 4.0 SP 2

http://www.microsoft.com/downloads/details.aspx?FamilyID=3144B72B-B4F2-46DA-B4B6-C5D7485F2B42&displaylang=en

The file name is msxml.msi.

If the msxml.dll is not found, you can copy it from another workstation and then register it using the steps below.

1. Use Windows Explorer to find the file, right-click on it, click Open With, and then click Choose Program.

2. In the Open With dialog box, click Browse, then browse to the Windows\System32 folder.

3. In the System32 folder, highlight the Regsvr32.exe file and then click Open.

4. Click OK and you should receive a message that the file registered successfully.

Forum: Microsoft FRx Users ]]> http://boards.msxgroup.com/post?id=5850199 Thu, 17 May 2012 16:10:38 GMT http://boards.msxgroup.com/post?id=5849982 Hello,

Recently I had to reinstall the FRx Client on a Windows 7 64-bit system and the installation ran smoothly but when I access the program and click on any of the four main buttons "Row Formats", "Column Layouts", "Reporting Trees", or "Catalog of Reports" absolutely nothing happens.

The installation works perfectly fine on the server with Windows 2008 Enterprise Server R2 so I am not sure what else needs to be done on the client end.

Any ideas?

Thank you for your time.

Regards,

Christopher Koeber

Forum: Microsoft FRx Users ]]> http://boards.msxgroup.com/post?id=5849982 Thu, 17 May 2012 13:37:08 GMT http://boards.msxgroup.com/post?id=5845567 Management Reporter currently is not officially supported with SQL Server 2012 databases. It *should* run, but Microsoft will not release hotfixes or updates for Management Reporter 2012 for issues relating to SQL Server 2012 until RU#2 is shipped.

The current schedule for RU#2 is to ship in late summer or early fall of 2012.

Forum: Management Reporter Users ]]> http://boards.msxgroup.com/post?id=5845567 Mon, 14 May 2012 17:13:25 GMT http://boards.msxgroup.com/post?id=5830803 To share with other Management Reporter 2012 users out there, we received the following error for a report:  An unknown error has occured while processing the report.  The report would fail and there were no clues in the report status window.

Through trial and error, we discovered the issue was a blank line in the column headers.  There were actually two blank lines, but only one of the blank lines caused the report  to completely fail.  The one blank line which caused the report to fail was under another column header line that was boxed and spread.  We’ll have to do more testing and we passed this on to Microsoft support. 

There is also the column header code @Blank which may be used if there is an issue until resolved.

The Management Reporter 2012 build was: 2.1.1026.37.

Forum: Management Reporter Users ]]> http://boards.msxgroup.com/post?id=5830803 Fri, 04 May 2012 20:01:03 GMT http://boards.msxgroup.com/post?id=5830761 I've been testing the latest version of SQL Server (SQL Server 2012) with Forecaster.  I've been using Forecaster 7 SP3 with CU#5 (aka, the latest version that is readily available). 

To date, there have been no problems with it.  No unexpected errors, no connectivity issues, no functionality failures.

Note that it will still require that you follow the instructions for connecting to SQL Server 2008 databases (due to the Database Wizard and ExpressLink).  Details of that are here:

http://boards.msxgroup.com/post/Forecasters-Database-Wizard-Cannot-Connect-to-SQL-Server-2008-Database-Servers-4856519

Similarly, you will need to manually apply the 64-bit versions of these items if you are running Forecaster on a 64-bit machine.  Details for this are here:

http://boards.msxgroup.com/post/Installing-Microsoft-Forecaster-7.0-on-64bit-Operating-Systems-4920746

Finally, if you happen to be one of the few who was able to get Forecaster 7 SP4 before it was recalled, you still need to follow the instructions in THIS post:

http://boards.msxgroup.com/post/Forecaster-7-SP4-Has-an-Undocumented-Change-in-PreRequisites-5459996

Bottom line: Forecaster 7 appears to work absolutely fine with SQL Server 2012.  This is good news!  I will update this post if new information comes to light about it.

Forum: Microsoft Forecaster Users ]]> http://boards.msxgroup.com/post?id=5830761 Fri, 04 May 2012 19:33:04 GMT http://boards.msxgroup.com/post?id=5830159

Forum: Microsoft FRx Users ]]> http://boards.msxgroup.com/post?id=5830159 Fri, 04 May 2012 12:37:51 GMT http://boards.msxgroup.com/post?id=5828935 https://mbs.microsoft.com/Cms/Templates/document/General.aspx?NRMODE=Published&NRNODEGUID=%7bF8CF0C93-1AFF-483E-9598-A8415F2CB79D%7d&NRORIGINALURL=%2fcustomersource%2fdownloads%2fservicepacks%2fmroverview%2ehtm&NRCACHEHINT=Guest

With this new release, the Management Reporter Migration Wizard can copy report definitions including Row Formats, Column Layouts, Reporting Tree Definitions and Catalog ID's from FRx into Management Reporter 2012. There is no longer a requirement to install Management Reporter SP2, run the Migration Wizard and then upgrade to MR2012.

Forum: Management Reporter Users ]]> http://boards.msxgroup.com/post?id=5828935 Thu, 03 May 2012 16:04:01 GMT http://boards.msxgroup.com/post?id=5828684 The Management Reporter Process Service is responsible for generating reports, scheduling of reports, and performing the integrations related to data mart.

The Management Reporter Application Service is what the client connects to. It surfaces the client, and is responsible for serving up everything that is a design time experience, or connecting Viewers to the Report Library.

Forum: Management Reporter Users ]]> http://boards.msxgroup.com/post?id=5828684 Thu, 03 May 2012 13:31:14 GMT http://boards.msxgroup.com/post?id=5824302 The documentation specifies that the first field in setting up the AX company information window is the AX Instance. Actually, this should be the AX server name instead.

Forum: Management Reporter Users ]]> http://boards.msxgroup.com/post?id=5824302 Mon, 30 Apr 2012 21:37:39 GMT http://boards.msxgroup.com/post?id=5818362 Management Reporter 2012 supports the following Microsoft Dynamics ERP solutions:

• Microsoft Dynamics AX 2012
• Microsoft Dynamics AX 2009
• Microsoft Dynamics GP 2010
• Microsoft Dynamics NAV 2009 (only for customers replacing Microsoft FRx)
• Microsoft Dynamics SL 2011

Forum: Management Reporter Users ]]> http://boards.msxgroup.com/post?id=5818362 Fri, 27 Apr 2012 04:52:24 GMT http://boards.msxgroup.com/post?id=5818351
We are also including information regarding Management Reporter.

For those on Non-Dynamics ERPs, please contact Support@MSXGroup.com for additional information relating to your GL system.

FRx	General Availability Date	Mainstream Support End Date	Extended Support End Date	Service Pack Support End Date
Dynamics GP 10	08/04/07	10/09/12	10/10/17	01/12/10
Dynamics NAV 5.0	04/01/07	04/10/12	04/11/17	04/13/10
Dynamics NAV 2009	02/12/09	04/08/14	04/09/19	10/11/11
Dynamics AX 4.0	09/10/06	10/11/11	10/11/16	01/08/08
Dynamics AX 2009	08/14/08	10/08/13	10/09/18	01/11/18
Dynamics SL 7.0	08/31/07	10/09/12	10/10/17	01/12/10
Dynamics SL 6.5	01/14/06	04/12/11	No Support	01/07/11
Non-Dynamics	05/30/04	07/14/09	07/08/14
Management Reporter	General Availability Date	Mainstream Support End Date	Extended Support End Date	Service Pack Support End Date
Dynamics GP 2010	06/15/10	10/13/15	10/13/20	10/09/12
Dynamics AX 2009	08/14/08	10/08/13	10/09/18	01/11/18
Dynamics AX 2012
Dynamics SL 2011	06/15/11	07/12/16	07/31/21
NAV 2009 (for those on FRx)

Management Reporter 2012 supports the following Microsoft Dynamics ERP solutions:

• Microsoft Dynamics AX 2012
• Microsoft Dynamics AX 2009
• Microsoft Dynamics GP 2010
• Microsoft Dynamics NAV 2009 (only for customers replacing Microsoft FRx)
• Microsoft Dynamics SL 2011

Forum: Microsoft FRx Users ]]> http://boards.msxgroup.com/post?id=5818351 Fri, 27 Apr 2012 04:40:35 GMT http://boards.msxgroup.com/post?id=5814606 A user may have an issue when launching Management Reporter (MR) with the connection pointing to the development server rather than the production server. 

The most likely fix is to update the registry with additional notes below.  Be very careful and have experienced IT (or MSFT Support or Partner) asssist.

Here’s how the Management Reporter (MR) connection string process works:

1.       MR reads from KEY_CURRENT_USER\SOFTWARE\Microsoft\Dynamics\ManagementReporter\<version>\Client\ServerConnection.  If that value is not empty, that’s what MR uses.

 2.       If #1 was empty, we read from HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Dynamics\ManagementReporter\<version>\Client\ServerConnection.  If that value is not empty, that’s what MR uses.

3.       If #2 was empty, MR will ask the user for the connection string.

The typical scenarios are:

1.       The client has an HKCU value for the proper server, while other users don’t have an HKCU value and are getting the HKLM value, which points to the other server.     OR

 2.       The client doesn’t have an HKCU value and is getting the HKLM value (which points to the proper place), while the other users have an HKCU value that points to the wrong place.

#1 above is probably more likely.

There are a couple of things to check:

 1.       Check the HKCU value in his profile.  If they have one, delete it.  They should then pick up the same value as the other users (assuming #1 above is the case).

2.       If that’s the case, have them change the HKLM value in the registry (requires admin) – users should pick that up automatically.

3.       If users have HKCU entries instead, the best bet may be to use a login script to set their HKCU entry to the proper location (or clear it out so they pick up the HKLM value).

If there are multiple terminal servers in play, they may be using roaming profiles, which may complicate things a bit more.  However, the bet is it’s #1 that is described above, which should be an easy fix.

Forum: Management Reporter Users ]]> http://boards.msxgroup.com/post?id=5814606 Wed, 25 Apr 2012 21:29:14 GMT http://boards.msxgroup.com/post?id=5813930 I was recently asked to assist a Forecaster user with the following scenario:

This is actually a very easy item to accomplish in Forecaster. But it takes a little understanding of what is going on.

On the input screen, when you enter a value in a calculated period's column, Forecaster will spread that value back to the periods which make it up, using the current spread method assigned to the row.  If there is no spread method, it attempts to perform an EVEN spread.  As in all other spread method scenarios, the spread calculations will put any remainder value into the last open period that makes up the total (i.e. December for a total year column).

The math involved also takes the number of decimal places you are showing into account.  So, if there are 0 decimal places in the columns or on the row, the calculation will assume you want no decimal places in the result.  For a number like ".46", this results in all periods being 0, except december which will have the full .46 added into it. 

The solution is actually very easy. 

1. In the line set, add at least two (2) decimal places to the RATE row.

2. Change the calculation set such that the formula becomes:

L     OVHD=DRVR*(TOTAL.RATE)

Note: In the above, "TOTAL" should be replaced by the Code for Calculations for the Total column you are using.

3. Close and reopen the Input Screen after saving the changes to the Lines and Calculations. If the new decimal setting doesn't show for the RATE row, refresh the rows to the default line set.

4. Now enter .46 into the total column for the RATE row.

At this point, the .46 will spread back (evenly) to the periods, with any remainder going into the last open period.  However, the TOTAL will be correct.  The updated formula that runs will now pull the value from the cell where you entered the .46 (TOTAL.RATE).  It will use this value across the entire OVHD row and your calculations will now be correct.

Forum: Microsoft Forecaster Users ]]> http://boards.msxgroup.com/post?id=5813930 Wed, 25 Apr 2012 13:16:12 GMT http://boards.msxgroup.com/post?id=5806684 I receive numerous questions about various screen and system "lock" situations that come up.  Some examples:

When opening a Rollup screen you receive the message:

When logging into the system users (and administrators) receive:

When opening the Security screen or Routings screen, you receive:

These messages come up when other users are doing things within Forecaster, such as modifying periods, rollups or security.  Sometimes, though, these messages come up when there is no one actively working in the system.  This situation may be due to server disk space issues (specifically with period maintenance activities), a Forecaster crash, system timeout or product bugs.

If you are absolutely certain that no one is using the Security, Routings, Periods or Rollups screens, the fix for this is to use the Recovery tool.  Log into Forecaster as an administrator.  Go to Tools | Recovery.  When prompted, click "Yes" to run the recovery.  After the cleanup is complete, you will be asked if you'd like to run the Validate Database tool.  Typically you just say "No" to that prompt as there is likely no reason to run it for these scenarios.

I cannot stress enough that you need to be certain that no one else is using these screens.  If you release the locks while they are using them, the results could be unpredictable. 

As always, the MSX Group is here to assist you with all of your Forecaster needs, so if you are not sure about the error message you are receiving contact your MSX support representative or consultant for help.

Forum: Microsoft Forecaster Users ]]> http://boards.msxgroup.com/post?id=5806684 Fri, 20 Apr 2012 14:45:46 GMT