Forums

Jeff,

I used Dynamics GP Web Services very extensively I never faced this problem. Can you check event veiwer for any system errors?

May be server is having some issue?

Thanks

Sandip

Have you checked the Event Viewer? What troubleshooting have you done?

Yes, I have looked all over and did not see any errors that give me any good information.  The strange thing about this is that can go long periods of time without having to restart.  It does not seem like it is a standard timeout issue.  

There should be information in the Event Viewer Jeff. I would recommend opening a support case so an engineer can gather some log files.

I have witnessed this again.  The error is:  System.Runtime.InteropServices.COMException : The handle is invalid. (Exception from HRESULT: 0x80070006 (E_HANDLE))

With Stack Trace:

at Microsoft.Dynamics.Security.ValidationHelper.ValidateContext(SecurityContext context)

  at Microsoft.Dynamics.Security.AzManMemberAccess.GetRoles(SecurityContext context, String member)

  at Microsoft.Dynamics.Common.SecurityServiceManager.GetRoles(Context context)

  at Microsoft.Dynamics.Common.Context.Validate(ValidationResult validationResult, Context context)

  at Microsoft.Dynamics.Common.BusinessService.GetByKey(Key key, Context context, Type[] types)

I've been experiencing the same problem for over a year. I even opened a case with Microsoft but they couldn't resolve it... They mentioned the issue originated from the cache module of the eConnect API..

Stack Trace:

System.Runtime.InteropServices.COMException : The handle is invalid. (Exception from HRESULT: 0x80070006 (E_HANDLE))

at Microsoft.Dynamics.Security.ValidationHelper.ValidateContext(SecurityContext context)

at Microsoft.Dynamics.Security.AzManMemberAccess.GetRoles(SecurityContext context, String member)

at Microsoft.Dynamics.Common.SecurityServiceManager.GetRoles(Context context)

at Microsoft.Dynamics.Common.Context.Validate(ValidationResult validationResult, Context context)

From what I was told, when you start the Dynamics service, it opens a connection to your SQL server.  This connection remains open.  If something goes bad with the connection and you try to call the web service, you can get this error.  We moved environments and have not seen this issue come back up.  I was thinking a way to get around this issue is to write an application that restarts that service nightly to try and keep the connection from getting closed.

I just upgraded to GP 2010 and am getting the exact same error.  Restarting the GP Service Host fixed the problem for now.  I'll check the SQL Server to determine if that service was restarted for some reason.

This is a known issue with GP 2010 Web Services. We have seen the same for many customers. We end up scheduling a daily reset of Web Services until MS resolve this.