2,046
hi folks
version 6 GP c-tree - please no replies about upgrading and not being supported.
Getting the error
Great Plains runtime engine has stopped working
My memory of c-tree and dynamics v6 tell me that this usually indicated there was a problem with the reports dictionary.
Anyone remember 6 and c-tree that can confirm or deny my memory?
thanks!
*This post is locked for comments
Hi again,
If you want to do a screen sharing session, I could do that this week and take a look at your AFA reports. What you describe is very unique and the only way I could really troubleshoot it is to see it. Call me if you are interested 972-814-8550.
Kind regards,
Leslie
Just to add my two cents being an old timer, but how many workstations do you have? Do any of them work? How about the one that has the data? Did this just suddenly start on this one workstation? After you changed the launch file to point locally, did GP v6 work? How about after you copied over the forms and reports dictionary locally? Leslie has a good idea about renaming the old GP folder and copying over one that works. You may also want to recreate blank forms and reports dictionary and then import the reports into the newly created blank report dictionary using Report Writer. Also make sure you have no anti-virus software that is blocking DYNAMICS.EXE.
OK,
This is going to sound like I'm still back in the DOS days, but copy the application folder from a workstation that is working, and past it to the workstation that isn't. Rename the bad workstations folder, don't write over it.
It's pedestrian, but it often works when there is only one machine having a problem. Sometimes the code dictionaries get corrupted and cause odd things to happen.
Make sure the user has all of the security he needs. If you log in to his machine as domain and local admin, does it still mess up?
Kind regards,
Leslie
OK,
Do #3 first. Didn't mean to post it so soon. Hit the wrong button. I'll continue. To answer your question, your memory is good, it was usually a bad dictionary.
4. If after #3 it works fine, then you need to rebuild the Forms/Reports dictionary. Delete the old one first (copy it somewhere first and create a .package file of any modifications)
5. If it still doesn't work, think hard about any changes that have been made to that machine. Anything at all - not limited to relating to Dynamics.
6. Is the temp folder clean?
7. Forgot to ask the obvious - when does the error occur?
8. Is your Location Translation set properly? (don't think this would do it, buy hey, it's easy to check)
I would be surprised if building a new dictionary didn't solve the problem. Back then, a shared reports dictionary was more frequently corrupted.
Kind regards,
Leslie
Hi Leslie
Sigh - I remember versions 5 to 6 - happy times. We can't of course forget when we all got pervasive certified for b-trieve.
Yes it is the one workstation.
They got a new server over the weekend. Somehow the user got stuck and had to delete the two activity files off the server to get back in.
I suspect in the process they have corrupted the reports.dic file.
I am thinking a local reports dic and then import the reports from the shared network file should get them back in.
Hi,
Ah, Ctree, I remember her fondly (smiling longingly). First I have a barrage of questions.
1 Does this happen on all workstations?
2 Did it ever work on this workstation?
3 If you are sharing a Forms/Reports dictionary location, change the .set file to point to a local location.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,269
Super User 2024 Season 2
#2
Martin Dráb
230,198
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (