My users are all on XP SP3 and we just recently updated GP 10.0 to SP5. We seems to be getting a large number of "Application Hang" issues on the user's computers.
I am researching all possibilities and wondered if there is some connection to the SP5 update? Ideas?
Event Type: Error
Event Source: Application Hang
Event Category: (101)
Event ID: 1002
Date: 1/6/2011
Time: 10:15:12 AM
User: N/A
Computer: xxxxxxx
Description:
Hanging application Dynamics.exe, version 10.0.331.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000.
*This post is locked for comments
Hello Sandip,
With the tax updates, we have seen some issues with the Reports.dic and even the Forms.dic file needing to be re-created to resolve issues with payroll and payroll reports, though this should normally only need to be done once after the upgrade is completed and not several times as you mentioned.
If you haven't already done so, login to Dynamics GP as SA, go into the Customization Maintenance window and export all modified forms and reports into a package file. Then, logout of Dynamics GP and re-name the existing reports and forms dictionary files.
Once this is done, log back into Dynamics GP as SA, go back into the Customization Maintenance window and import the package file with the modified forms and reports back into Dynamics GP, which will re-create the reports and forms dictionary files at the correct version and insert the forms/reports into those dictionary files.
Thank you
All,
Thanks much for reply, I have to create reports.dic file several times ,export and reimport report which has problem. But after installing Round 2 Tax Update system says report.dic file upgraded sucessfully even though reports shows error.
Thanks
Sandip
Hi Sandip,
Check your dex.ini file there might be printer driver name which is now removed (not used in network). It may cause issue. I had faced the same issue. later come to know that printer removed from network casued the issue.
Hope this will help.
Regards,
Santosh
Hello Sandip,
If you're printing a report and Dynamics GP is hanging, you may need to look at whether or not the report is a modified report or not which would relate to the report dictionary files. You can also use a dexsql.log running during GP hanging to see if there are any errors showing in the log.
If it isn't a modified report, if it is only happening on one machine or so, it could be the main dictionary file for whatever module the report is for, is damaged.
Thank you.
Derek,
I found issue in Reports also , while printing report GP get hung. Even though I did update reports.dic sucessfully. I am only one who facing this issue or others also ?
Thanks
Sandip
Hello David,
You are correct in that for Dynamics GP 10.0, this issue regarding the Analytical Accounting (3180) was fixed by the GP 10.0 US Round 2 update (KB 2477916). For GP 2010, it was fixed by SP1.
Unfortunately, for both GP 10.0 and GP 2010, the issue with the Dynamics Online Service (6499), which was scheduled to be fixed by the Round 2 update in both versions of GP, didn't make it and is now scheduled to be fixed in both GP 10.0 and GP 2010 by the Round 3 Tax Update due out the end of February or early March.
Thank you.
BTW,
I installed the Round 2 patch (MicrosoftDynamicsGP-KB2477916-v10-ENU.exe) In test and 6499 still increases.
I thought it was worth a mention.
*****************************************************
CmdDictID CmdParentDictID Count
0 0 633
0 -10 4
0 1 34
1 1 24
1 0 96
1 3107 3
1 -10 5
1 3830 4
258 0 104
258 258 34
309 0 58
342 0 2
414 414 70
414 0 64
681 0 3
949 0 3
1042 0 1
1198 0 2
1493 0 2
1911 0 19
1911 414 1
1911 1911 8
2277 0 12
2416 0 2
3104 0 2
3107 0 1
3107 3107 8
3278 0 7
3830 0 2
3830 3830 13
4522 0 1
4522 4522 1
4933 414 3
4933 0 14
4955 414 2
4955 0 7
5261 1 1
5261 0 10
6499 0 608
6499 6499 37 <---
Was KB 2435605 intended to contain the fix for 3180 duplicate records in SY07110? As much as I could tell, it seems to be the latest update for GP until yesterday when KB 2477916 was released. The reason I ask is the comment by Randal indicated there was an update available for the 3180 problem. Since we applied KB 2435605, the 3180 problem surfaced and the GP client is taking 5 to 10 minutes to load. Our temporary solution is to use Randal's advice of logging out all users, taking a backup of the database, and clearing the SY07110 table on a nightly basis. We are looking for the latest update to eliminate this process. Also, is our nightly process overkill to relieve the problem or is it good practice in case this process causes other problems? I really don't know the impact of doing this and would like to get some feedback. Thanks.
With users out of the system and SQL backups in hand, you can clear it. GP will auto populate the table as needed.
...Any other duplicate/growing records in the SY07110 is not a known issue.
Until now.....
- Can I clear it?
- Will they be recreated?
André Arnaud de Cal...
291,965
Super User 2025 Season 1
Martin Dráb
230,836
Most Valuable Professional
nmaenpaa
101,156