SoftwareGreat Plains Consultant Newsflash: FRx move to new Server - Alba Spectrum
If your current Dynamics GP Great Plains server got to be replaced with new hardware, you should follow procedures to move Dynamics GP databases as well as FRx reporting system files.
NAPERVILLE, IL, April 06, 2009 /24-7PressRelease/ -- If your current Dynamics GP Great Plains server got to be replaced with new hardware, you should follow procedures to move Dynamics GP databases as well as FRx reporting system files. Being working for major Great Plains Dynamics GP VAR in US, we realized that our large customers are following this simple technique: place new server with newer Operating System (such as Windows 2003 instead of old Windows 2000), install SQL Server 2000 or 2005, move Great Plains DYNAMICS and all companies databases, move user logins, password and security access (you can also find these SQL scripts at Microsoft Dynamics Customer Source). Then shut down the old Dynamics GP Server, rename new server to its old server original name, and off you go! Well, this is about Dynamics GP Great Plains. FRx Financial reporting is more sensitive to UNC Path, Shared Folders and mapped drives. If you ran into these issues, this small publication is dedicated to you:
1. FRx Sysdata concept. Please login FRx reports designer, under Admin-_Organization-_SYSDATA - you should see where your current FRx metabase is located. Please, know that FRx is compatible with multiple ERP platforms: Great Plains, Axapta, Navision, Solomon and these are the reasons to lean on file location. Sysdata folder has FRx metabase and if you change settings for your companies: Company-_Information: Specification Set, Import and Export Path, Rates Database Path (in case if you deploy multicurrency in GP and FRx) - all the users will be updated
2. FRx System Specific Information. Here you have ODBC DSN, usually FRx deploys the same DSN as Dynamics GP Great Plains Workstation. For Each company please specify system database: DYNAMICS and company database
3. Admin View OFSI Settings. In our practice, OFSI tables were source of the problems with earlier FRx versions: 6.5 and down, These were the days in late 1990th where you would have to create OFSI tables manually in SQL Query Analyzer
4. G32 files error messages. The concept behind is pretty simple - FRx rebuilds GL indexes on logon. If you are getting error message, that you can not login FRX due to G32 file is locked, please open your sysdata directory, rename all G32 extension files and come back to FRx - this should fix the problem
5. If you are at the point where you are considering to give up on FRx issues, we understand and respect your position - consider to give us a call