Dynamics GP has stopped working

(0) Share

Report

Posted on by Chuck Evans

1,175

We have a situation where one Dynamics user and the sa user gets the error "Microsoft Dynamics GP has stopped working" after selecting any company in the login process. All other users can login without issue. We can log into the SQL server from SQL Management Studio as sa with an issue. I'm assuming that there is an issue in the Dynamics database for sa and the other user which is creating the problem. I would appreciate any suggestions as to what to look for.

Thanks

Chuck

*This post is locked for comments

I have the same question (0)

All responses (13)

Answers (1)

Richard Wheeler 75,848 Moderator on at

Like (0)

Report

Sounds like a corrupt Dynamics dictionary. I would try copying the entire GP folder from a work computer to this one. Are you saying if you go to the server and log in as 'sa' there is an issue? What is this issue? If you go to a working computer and log in as 'sa' does the issue appear? Likewise, if you log in as another user on the same computer as the 'sa' was using do you have an issue. In other words, does the problem follow the user or the computer?

Was this reply helpful? Yes No
Chuck Evans 1,175 on at

Like (0)

Report

Hi Richard,

I doubt it's corrupt Dynamics dictionary as we are getting the problem from two different terminal servers and problem consistantly occurs for only two users including sa. sa works fine from SQL Management Studio but not from Dynamics. We don't have a computer that will allow sa to log into Dynamics. In short the problem appears to be user related and not code set related.

Was this reply helpful? Yes No
Richard Wheeler 75,848 Moderator on at

Like (0)

Report

What roles are assigned to 'sa' in SQL? Does it have public and sysadmin roles? check the status of the 'sa' account in SQL. Does it still have permission to connect and login? How about mappings? Something in SQL is wrong with these two accounts. Users must be memebers of the DYNGRP group and be mapped to the company databases plus the DYNAMICS database.

Was this reply helpful? Yes No
Chuck Evans 1,175 on at

Like (0)

Report

sa is in the public and sysadmin server roles and is active. I can log in from SQL Management Studio as sa. The default installation of Dynamics doesnot map sa to the Dynamics or company databases. I don't recall ever seeing it mapped to Dynamics or companies accordingly it cannot be in the DYNGRP. The other user that is having the problem is mapped to Dynamics and companies and is in the DYNGRP

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

I would try running a dexsql log and see if anything interesting comes up:

support.microsoft.com/.../850996

Was this reply helpful? Yes No
Jonathan Fear on at

Like (0)

Report

Terry is right that a Dexsql.log might tell us what is going on. I would bet the issue is with reminders or something else on the homepage. Sometimes this will happen if there is a reminder based off a Smartlist that has been deleted. The Reminders table is the SY1404 table. There is a username column for each GP user.

You can also disable the homepage and try to narrow it down by adding each feature back one by one till GP crashes.

Was this reply helpful? Yes No
Richard Wheeler 75,848 Moderator on at

Like (0)

Report

Throwing SQL Profiler along with the DEXSQL.LOG should identify what is causing the problem. Limit SQL Profiler to just the user in question or try to do this after everyone has left for the day and you are the only one trying to log into GP.

Was this reply helpful? Yes No
Chuck Evans 1,175 on at

Like (0)

Report

We tried looking at the Dexlog but found nothing useful in it. But I'll try it again. We have deleted all records in the SY01404 table but still have the problem. I can't log in as sa. How can I disable the home page at the SQL level?

Thanks

Chuck

Was this reply helpful? Yes No
Jonathan Fear on at

Like (0)

Report

917998 How to disable home page features in Microsoft Dynamics GP

mbs.microsoft.com/.../KBDisplay.aspx

Was this reply helpful? Yes No
Verified answer

Chuck Evans 1,175 on at

Like (0)

Report

The problem was in the shortcuts. I deleted the shortcuts for sa in the SY01990 table and copied shortcuts from a working user. That solved the problem

Was this reply helpful? Yes No