Fatal Error: Language database file c:\prog~1\FRXSOF~1\FRX6~1.7\REPORT~2\FRxXML4.dat not found.

Unable to generate FRx reports the above error keeps displaying.

To resolve:
SOLUTION 1: Try the KB article by Microsoft 932318. 


If the KB article doesn't work the below is guaranteed to work.


SOLUTION 2:  Run the FRxReg.exe located in the FRx 6.7 directory and then attempt to run the report again. You should have no issues.

How to create a macro to automatically log in and Post a batch

STEP 1: Create macro to sign into GP and post batch.

Click on GP launch file.
When the sign in window appears click 'Alt + F8' to begin the recording of the macro.
Name your macro and the location to be saved to.
Continue the process as if you were going to post the batch.
Therefore, enter userid and password, click ok, select company, etc.
Go to Menu and click Transactions>> Sales>> Series POst (for example). click on batch to post and continue with the steps that the auto proceedure should complete. once finished click 'Alt + F8" to stop recording the macro.


STEP 2: Create Notepad file.

Create a note pad document, in the contents of the document enter the location of the Dynamics exe file, the set file and the location of the macro.
For example: "C:\Program Files\Microsoft Dynamics\GP\DYNAMICS.EXE" "C:\Program Files\Microsoft Dynamics\GP\DYNAMICS.SET" "C:\Program Files\Microsoft Dynamics\GP\DATA\AUTOPOST.MAC"


STEP 3: Change notepad file to batch file.

Right click on the notepad file and change the extention from '.txt' to '.bat'


STEP 4: Run macro.
To run macro just double click on the batch file.

*If you need to edit the batch file - right click on the file and click 'edit'

For more information on Integration manager autoposts see the following link by Mariano Gomez.
http://dynamicsgpblogster.blogspot.com/2009/01/how-to-schedule-dynamics-gp-to.html

Entering Licence Keys for Dynamics NAV

To upload your license file

1. Open the Classic client.
   Click Start, and then click Microsoft Dynamics NAV 2009 Classic with Microsoft SQL Server
2. On the Tools menu, click License Information.
3. In the License Information window, click Upload.
4. In the Upload License File window, browse to the folder where your Microsoft Dynamics NAV license file is located.
5. Select the license file, and then click Open to upload it to the SQL Server database.

 

Copying the License File to Classic Database Serverupload your

This procedure assumes that you are using a database on the Database Server instead of running in single-user mode.

To copy your license file to the Classic Database Server

1. Locate and copy your license file.
2. On the computer where you have installed the Classic Database Server, navigate to the directory where the Classic Database Server executable, Server.exe, is located.
   The default location is Program Files\Microsoft Dynamics NAV\60\Database Server.
3. Paste the license file in the server directory.
4. Rename the file fin.flf if you have not already done so.
5. Restart the Microsoft Dynamics NAV Database Server service.

http://msdn.microsoft.com/en-us/library/dd338774.aspx

Installing SQL on Windows Server

Please note that contrary to popular belief you CAN install SQL 2005 32 bit on Windows Server 2008R2 64 bit.

The system will not prompt you with any errors and the system will work fine.

Lessons Learnt.

Stock Status Report and Bins

BINS CANNOT BE ADDED TO THE STOCK STATUS REPORT IN REPORT WRITER FOR DYNAMCIS GP.

There is an option in the report options for bin but you cannot even select it because the system will tell you that you cannot use multi bins as a range.

After trying and trying it is now quite clear that bins cannot be added through report writer for this report. However it can be done through Crystal Reports or SRS.

Regards,

R.

The stored procedure verify/versioninformation() of form duSQLInstall Pass Through SQL returned the following results: DBMS: 468, Microsoft Dynamics GP: 0.

After installing SQL and restoring GP database backups you sign into GP and get the following error:
The stored procedure verify/versioninformation() of form duSQLInstall Pass Through SQL returned the following results: DBMS: 468, Microsoft Dynamics GP: 0.

This is because of the collations.

To resolve this you need to uninstall SQL and go to control panel and change the location to United States. Restart the machine and ensur that the location remains the same.

Reinstall SQL and ensure you change the collation to: SQL_Latin1_General_CP1_CI_AS

Then run GP Utilites to recreate new company. (this is so the database folder will be present in SQL so you can restore to them) after company has been created restore the SQL backups.

Run script in SQL "sp_helpdb" expand the "status" column and ensure that all databases have the correct collation: SQL_Latin1_General_CP1_CI_AS, SQLSortOrder=52

"The date cannot be part of a different fiscal year".

This error will display if there is another year with the same periods in it. To resolve this go through the years already setup in the Fiscal Periods window and take note of the "culprit" year.

Go to SQL and run the following statements on the database:

delete sy40100
where year1=20**
delete SY40101
where YEAR1=20**
delete sy40102
where year1=20**
delete SY40103
where YEAR1=20**

please repalce 20** with the "culprit" year. The year  I am referring to is the field titled "Year" as seen in the Fiscal Period Setup window screen shot below.

PLEASE DO NOT DELETE IF YOU HAVE TRANSACTIONS POSTED FOR THE PERIODS LISTED UNDER THAT YEAR.