Different Errors for One Reason!!!

Sometimes you finds your self in a very deep technical investigations looking for the cause of a very stupid error message or behavior that does not represents the actual cause of the message, such as situations below:

1. “All Call Stack in use. Cannot Start Script” When opening GL Transaction Entry From.

callstackserror

2. Smart-list has no objects and tree view that holds the smart-lists is empty.

https://community.dynamics.com/forums/p/25304/43005.aspx

3. Smart-lists returns no data, smart-lists are exist but no data are shown in the lists.

http://www.eggheadcafe.com/forumarchives/greatplains/Feb2006/post25875635.asp

4. On checkbook reconciliation, no data is presented on transactions preview to be reconciled.

Go to Reconcile Bank Statement>> Select your checkbook>> Click on Transactions>> No data!!

5. Smart-list exports unknown letters when exporting non-English characters to Excel.

6. Integration Manager integrates question marks “???” instead of the original non-English text upon importing any kind of transactions.

All the above point became well known behaviors to the collation conflict for non-Unicode characters, the simple solution for all the above errors is to Set the language to English under “Advanced” tab in Regional and Language options.

Hope that helps.

Regards,

Mohammad R. Daoud
MVP, MCP, MCBMSP, MCTS, MCBMSS
Software Development Manager
+962 – 79 – 999 65 85
Great Package For Business Solutions
daoudm@greatpbs.com
http://www.greatpbs.com

Advertisements

About Mohammad R. Daoud
Mohammad R. Daoud has been working as a Microsoft Dynamics GP consultant since 2004. His career path started with version 7.5; he studied every single tip of the application technicalities and did allot of successful implementations that includes functional consultations, analysis, and custom development projects. He holds a graduate degree in Computer Science and currently he is pursuing MBA degree in Accounting. In January 2007 he was nominated to the Microsoft Most Valuable Professional (MVP) certificate and was certified in April 2008 due to his online contributions in the Dynamics Community (Dynamics GP Newsgroups, Forums, User Groups and his blog: http://mohdaoud.blogspot.com). Worth to mention that he was also listed as one of the Microsoft Dynamics Top 100 Most Influential People in 2009 by DynamicsWorld. And more... • Demonstrated Passion for MS Products through participating in beta testing for some product versions, an effective member of Microsoft Connect. • Talented in securing strong high quality relationships with premier customers, partners and sales teams passionately and profitably. • Dedicated to meeting the expectations and requirements of internal and/or external customers • Problem Solver – Uses systematic approach to uncover true problem(s) and practical solution and can marshal resources to solve problem! • Proven record of effective account management, including Account Planning, Opportunity Management, and Business Management Excellence and working as part of a larger virtual team • Successful in delivering high quality technical engagements in the enterprise Dynamics GP implementations area according to customer requirements. • Dedicated, Committed, Self Motivated, Creative and highly focused with excellent communication, Negotiation, presentation, Active Listening and Objection Handling skills. • Experienced in Profitable researches and studies including white papers and technical presentations.

One Response to Different Errors for One Reason!!!

  1. sam01 says:

    Thank you for your posting. I like to add one more scenario to this issue. This issue also happens if you move GP data to a new SQL Server instance, and the new SQL Server instance was installed with a different “Server Collation”.

    In my case, the original SQL server instance had “Server Collation” = SQL_Latin1_General_CP1_CI_AS, but the new SQL Server instance had Server Collation = Latin1_General_CI_AS. GP was giving blank SmartList and other errors mentioned above. Setting all the Region and Language options to English did not resolve the issue in this case.

    Eventually the issue was resolved by reinstalling the SQL Server using the same “Server Collation” as the original SQL Server instance.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: