Microsoft Dynamics Brand

I've been reading a lot about the new branding that Microsoft did to its MBS products and I thought why not give my own opinions about it.

Back to old times I would say.

Yesterday, it was Great Plains Dynamics Ctree or Btrieve and Great Plains eEnterprise.

Today, we have Microsoft Business Solutions–Axapta, Microsoft Business Solutions–Great Plains, Microsoft Business Solutions–Navision and Microsoft Business Solutions–Solomon and Microsoft CRM.

Tomorrow, it's going to be Microsoft Dynamics CRM, Microsoft Dynamics GP, Microsoft Dynamics AX, Microsoft Dynamics NAV, Microsoft Dynamics SL.

Do you see any resemblance?

Error: Failed to Export the Report

When you try to print a document in Great Plains and you're using Forms Printer, you get the following error: Failed to Export the Report.

Solution:

Crystal Reports 8.5: Copy all Crystal Dlls from C:\WINDOWS\Crystal folder to the C:\WINDOWS\system32

Crystal Reports 9.0: Copy the Files in C:\program files\Common Files\Crystal Decisions\2.0\Bin TO C:\WINDOWS\system32

Crystal Reports 10: The path is C:\program files\Common Files\Crystal Decisions\2.5\Bin

The recommended way is to copy the files but don't overwrite any existing files in Windows\system32, but just add the Crystal files.

Adding more audience to this blog

To cater to a broader audience, I've decided to add Crystal Reports. I've been helping a lot of users in MBS Great Plains community site and Tek-tips in how to create, look for sql tables or even linking tables.

FRx 6.5 error in Windows Server 2003

We're upgrading all our servers to Windows Server 2003 and the last servers for upgrade were the SQL Server and FRx. When we try to start FRx 6.5, we get Error 339 on CSTEXT32.OCX.

I found an article in CustomerSource on this error:

CAUSE

FRx 6.5 has been installed on a Windows 2003 Server. Service Pack build 6.5.152 (Service Pack 4) has been applied, instead of the Windows 2003 Hot Fix. The Windows 2003 Hot Fix is required in order to successfully start FRx 6.5 on a Windows 2003 server.

RESOLUTION

Download and apply the Windows 2003 Hot Fix on the Windows 2003 server. The Windows 2003 Hot Fix is located on PartnerSource, CustomerSource, and the Great Plains FTP site:

PartnerSource -
https://mbs.microsoft.com/partnersource/products/
greatplains/downloads/hotfixes/frx65w2003hotfix.htm

CustomerSource -
https://mbs.microsoft.com/customersource/support/
downloads/hotfixes/frx65w2003hotfix.htm

Database and application versions do not match error in Enterprise Reporting database

When you try to log on to a Microsoft Business Solutions - Enterprise Reporting database, you receive the following error message:

Database and application versions do not match. Please contact your sales representative concerning an upgrade.

This problem occurs if the name of the Microsoft SQL Server database on the server includes a space. Before you follow the instructions in this article, make sure that you have a complete backup copy of the database that you can restore if a problem occurs.
To resolve this problem, rename the database by using a name that does not contain a space.
To rename the database, follow these steps:
1. Start SQL Server Enterprise Manager.
2. Locate the database whose name contains a space. Make sure that you know where the .mdb file for this database is located on the server.
3. Right-click the database, click All Tasks, and then click Detach Database.
4. Right-click Databases, click All Tasks, and then click Attach Database.
5. In the Attach Database dialog box, locate the .mdb file for this database.
6. In the Attach as field, rename the database. Use a name that does not contain any spaces.
7. Update your Open Database Connectivity (ODBC) connection with this new database name.

Great Plains 7.5 Service Pack 7 Now Available

The latest service pack for Great Plains 7.5 (Microsoft SQL Server), part of the Dictionary and Utilities service packs, is available for download here:
https://mbs.microsoft.com/customersource/support/
downloads/servicepacks/customerfaqs_gp_75_sp7.htm

Great Plains ver7.5 Bug Report 1

Scenario:

1) Customer is on Hold
2) Sales line item is drop-ship

When you create a SOP/POP link in ver7.5, the system don't show you any message that the customer is on hold. When you try to generate the Purchase Order, the Purchase Order Generation Register report would show you an error- " The customer is missing".

This bug was fixed in ver8.0, now the Purchase Order Preview window would show you a message that the customer is on hold.