When the client opens GP2013 and attempts to access the Account Transaction details this is the screen that is presented.
There are no error messages generated and interesting to point out - the Link to Journal Entry XXXX WORKS
Where or what is causing the XML to display like this. Is it possible that there is a table or file folder that is locked?
Thanks in advance for assistance.
*This post is locked for comments
Hi Bill,
Thanks so much for the update. I read the other link (thanks Kirk!) I also found the quality issue #TFS 68877, and it is triaged as 'won't fix' because they couldn't consistently repro it in-house, so there is no specific fix for it. I saw in the notes that installing Windows Updates resolved it for a few, and Derek installed the January GP hot fix and then his started to work fine, and he mentioned installing Visual Studio too, so the reported 'fixes' appears to be all over the board..... Thanks for sharing yours!
Cheryl W
Microsoft Support
Kurt / Cheryl
An interesting thing has happened - when I went back to the client machine and user that was having the issue there were other 'computer' issues he was fighting with - one was related to an update that was sitting on the Bootstrapper that was demanding a reboot.
He had been ignoring this since he started getting the message shortly after we completed the GP2010 to GP2013 update.
So, long story, once he did a reboot of the computer, the XML error is gone.
Case Closed - Lesson - get weird message, look for simply answer and reboot is simple as it gets.
Hi Bill,
I believe this is a known bug. Here is a link to another post about it and the workarounds. community.dynamics.com/.../344756.aspx
Regards,
Kirk
Hi Bill,
We have not been able to recreate this in-house, so could not log it as a quality report. It seems to be caused by something with the Dynamics.exe.config file in the GP code folder. If you rename* this file and launch into GP again, it seems to work right then. *However, you can't do this if you use a DLL like for workflow, Lync integration, Payment Services, SSRS, etc. (and whatever else you have installed that has a dll.) Renaming it would break these.
Thanks,
Cheryl W
Microsoft Support
#1
André Arnaud de Cal...
292,516
Super User 2025 Season 1
#2
Martin Dráb
231,430
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (
