Dexterity Runtime has encountered a problem and needs to close 1

[WatchNerd]

We are running GP8. This morning when we arrived and tried to start Dynamics we received the error noted above. We tried installing SP5 and this didn't solve the problem.

Any ideas?

-Mike

 

[winthropdc]

When exactly does Great Plains crash? Is it just after login and company selection? If so, please see the other posting about Named Printers.

Otherwise, I would suggest making a backup of your Dynamics.set and removing products one by one until Great Plains works again.

This should hope narrow down the product that is causing the problem.

To remove a product you would need to decrement the product count on the first line, then remove the product ID and Product Name lines and the 3 path lines from each workstation set (if there is more than one).

David Musgrave [MSFT]
Senior Development Consultant
Escalation Engineer - Great Plains
Microsoft Dynamics Support - Asia Pacific

Micorosoft Dynamics (formerly Microsoft Business Solutions)

http://www.microsoft.com/Dynamics

Any views contained within are my personal views and
not necessarily Microsoft Business Solutions policy.
This posting is provided "AS IS" with no warranties,
and confers no rights.

 

[winthropdc]

Named Printers can cause a crash when logging in
================================================

Named Printers can cause an unexplained crash just after clicking OK to the company login dialog.

If Named Printers has been configured for a workstation, as you log into a company it will attempt to change the Great Plains application default printer to the Printer ID configured as the System Default printer. If there is a Company Default printer set up for the current Company and User combination, it will change to this printer.

If either of those two printers no longer exist or the printer drivers for them has been changed or are not valid in any way, it can cause Great Plains to crash just as you login.

If you believe that this situation may be causing problems in your system, please edit the DEX.INI can change ST_SetDefault=TRUE to ST_SetDefault=FALSE. This will stop Named Printers from setting the default printer on login. You can then go to Tools >> Setup >> System >> Named Printers and edit the settings for the System Default Printer (and optionally the Company Default Printer) to point to printers that do exist. Once you have fixed the settings, change the setting back to ST_SetDefault=TRUE.

Note you can temporarily disable Named Printers entirely, by placing a semicolon ( in front of the ST_MachineID= setting in the DEX.INI.


David Musgrave [MSFT]
Senior Development Consultant
MBS Services - Asia Pacific

Microsoft Business Solutions

http://www.microsoft.com/BusinessSolutions

Any views contained within are my personal views and
not necessarily Microsoft Business Solutions policy.
This posting is provided "AS IS" with no warranties,
and confers no rights.

 

[IvoryJoe]

A corrupt forms.dic or reports.dic has caused this problem for us. You might try restoring from a backup before the problem occurred.

 

[WatchNerd]

The problem turned out to be a corrupt report.dic. Thanks for all your help and suggestions!