You’re offline. This is a read only version of the page.
So all of our end-users cannot access GP via the Web Client. Upon inspection I was able to log in fine, but when trying to create a new session or reconnecting to an old session I was getting a message that said,
'An error occurred while initializing communication with the server.'
I tried rebooting our Web Apps server and the same thing still occurs. After wiping Internet Explorer of cache, history, etc. I still get the same thing.
If I hit the Restart button on the bottom of the dialog box, I get a few application errors:
'AsyncCallbackException'
'Common_MethodFailed'
'CrossDomainError'
After clicking Restart I have a few mili-seconds to select the button on the bottom of the page that says, "Trusted Application - The machine configuration does not allow Microsoft Dynamics GP to run as a trusted application in the browser. The result is that some application functionality may be disabled or behave differently. You can update the machine configuration to allow the application to run as trusted using the action below."
Below is a hyperlinked text that will prompt me to 'Install Trusted Configuration' but I never get the opportunity because of the Application Errors dialog box over the window.
I've also had an end-user send me a screenshot that just gave them a general message: "Error. An error occurred while processing your request."
I'm not sure where to go from here.
*This post is locked for comments
Hi Troy,
You're welcome.. about your employee that has an issue with approving TS cards, you may want to have a look at this blog post (it's a little old, but should still apply in the HR module) :
[View:https://blogs.msdn.microsoft.com/developingfordynamicsgp/2010/10/22/missing-hr-menu-items-in-dynamics/:750:50]
it could well be related to a missing permission to "see" some employees in the HR module setup..
Tools>>Setup System>>Human Resources Preferences. On the bottom of this form is an employee Filters and you can filter on division and Department.
Thanks for the input on resetting the IIS. Everyone can log-in now, but I'll keep it in mind for the future. And I'll probably have the certificate put in the trusted root container, thanks.
Yes.. since it's a web service, sometimes you just do a reset on the IIS side and all comes back to normal :-).. since nobody can login anyway, it won't harm to try it.
The SSL warning is a common one and yes you want likely to install the certificate on every workstation, or have it put in the trusted root container by your domain admin. I'm not dealing with that usually, so you need to dig a little further on that side.
And one of our end-users is always receiving error messages when trying to do her job. One error we solved when she was trying to approve timecards in GP, was solved with a SQL query, but she got a few more a few days ago...
"'HR_Emp_Filters' failed accessing SQL data" and "Unhandled Script Exception: Illegal address for field 'User ID' in script 'EmployeeFilter'. Script terminated."'
Obviously the last few error messages might have been because of an invalid entry with the input field, but GP is starting to get annoying with all of these small issues on a daily basis.
The GP client would allow me to log in, but was not able to reconnect to a session or make a new one. I called our technology services number and while I was on the phone with them, it seemed to fix itself.
The only changes I can think of were made in December with the Year-End update. We've been making backups since then, but nothing else.
As far as certificates are concerned, we get a certificate error when accessing GP through our custom URL (kandu-webapp.kanduindustries.com/.../LogOn). It will say that the connection isn't secure. I was told by the company to export the certificates to each workstation that was having the problem, but I'm not sure how to do that. I looked into it through MMC, but not completely sure. We can access the website fine if we hit the "Proceed to..." option.
Thanks Bill,
Good point.. I always setup my SQL servers in mixed mode.. but if you don't do it yourself, someone else may not have checked the GP requirements during the setup.
Beat, I experienced something similar with an client when we moved to a new SQL installation. We did not do the installation of SQL but were told that everything was exactly the same. However when attempting to log on to the system we go a similar error message about the 'trusted site'
We worked out that then the DBA did the new SQL installation they did not do a Mixed Mode security installation and therefore SA was not a valid login for the system, as were a number of the other logins created.
We changed the SQL Server installation to use Mixed Mode Authentication and then were able to enable SA login as well as our other service users. Our 'trusted site' login error message was resolved and we were able to connect and access GP as expected.
Just my findings on a similar error message - hope this helps.
Dear ITDEPT,
Was the GP client working once in the past or is this a new setup ?
If it had been working in the past, were there any changes made on the Web client server side, like patch updates installed or .Net update, etc.. ?
If it had never worked and this is a fresh new setup, have you checked all your SSL certificates and run all the setup as recommended in the installation guide ?
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,219
Super User 2024 Season 2
#2
Martin Dráb
230,056
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (