Question Status

Unanswered
Ian Grieve asked a question on 5 Jul 2013 12:34 AM

I have a client where people who leave MDGP 2013 untouched for a while receive an error message stating "A remove range operation on table 'syContentPageXMLCache' cannot find the table" when they resume using GP.

The More Info is "[Microsoft][SQL Server Native Client 10.0][SQL Server]Invalid object name '##1675106'".

It looks to me like it might be a timeout but I wondered if anyone could shed more light on the issue? Hopefully including a resolution.

This is Microsoft Dynamics GP 2013 running on SQL Server 2012.

Thanks.

Ian


Author of azurecurve|Ramblings of a Dynamics GP Consultant
Senior Consultant at Perfect Image Ltd

Perfect Image/ Dynamics GP
Tel: +44 (0) 843 289 2656
1 Kings Manor, Newcastle upon Tyne, NE1 6PA, United Kingdom

Reply
Renjan Mathew Varughese responded on 5 Jul 2013 1:32 AM

You can try by setting as 'Never' for sleep mode.

I have seen errors like FP:Couldn't Close table when users do not use their machine for sometime. This error occurs due to the interruption in network connection as system goes to sleep mode. I have seen results by changing the sleep option to Never for this error. I would suggest you can also try this.

Hope this helps.

RENJAN MATHEW VARUGHESE

DYNAMICS GP CONSULTANT, MCP, PMP

Reply
Ian Grieve responded on 5 Jul 2013 7:10 AM

Hi Renjan,

Where is this setting?

Ian


Author of azurecurve|Ramblings of a Dynamics GP Consultant
Senior Consultant at Perfect Image Ltd

Perfect Image/ Dynamics GP
Tel: +44 (0) 843 289 2656
1 Kings Manor, Newcastle upon Tyne, NE1 6PA, United Kingdom

Reply
Richard L. Whaley responded on 5 Jul 2013 9:44 AM

Do you have any third party products installed on GP?  There is one that logs people out after a specific amount of time.  You may need an upgrade to this.

Richard L. Whaley Author, Publisher, Consultant

http://www.AccoladePublications.com

Enhancing your Dynamics Knowledge!

Reply
Ian Grieve responded on 5 Jul 2013 10:31 AM

No, there are no third party addons.


Author of azurecurve|Ramblings of a Dynamics GP Consultant
Senior Consultant at Perfect Image Ltd

Perfect Image/ Dynamics GP
Tel: +44 (0) 843 289 2656
1 Kings Manor, Newcastle upon Tyne, NE1 6PA, United Kingdom

Reply
Renjan Mathew Varughese responded on 5 Jul 2013 4:08 PM

The setting is in Control Panel >> PowerOptions.

Click on 'Change plan settings' for the plan which is selected.

Select 'Never' for 'Put the computer to sleep'

RENJAN MATHEW VARUGHESE

DYNAMICS GP CONSULTANT, MCP, PMP

Reply
Rosemary responded on 6 Jul 2013 7:58 PM

Control Panel>Power options...

I have seen this in GP 10, when the default settings  were changed the interruptions stopped.

Reply
Judy Hirst responded on 14 Nov 2013 11:29 AM

Hi Ian,

Thanks for posting this.  We have a client that also is getting this error, and, thanks to you, we now have a fast resolution.  Thanks to Rejan, too, for the solution!

Thanks,

Judy

 Judy Hirst CMA

Senior Financial Systems Consultant| Etelligent Solutions

(403) 204-6930 | jhirst@esicanada.com

 

Reply
Lisa.sorensen responded on 5 Feb 2014 12:07 PM

Is there any other settings to check regarding this issue? I have a client with the same issue occurring on the Terminal Server - I checked the Power Options on both the SQL Server and the Terminal Server and the 'Put The Computer To Sleep' is set to NEVER for both machines.  

Anything else that can cause the Network Connection to timeout or cause connection issues?

Reply
Bill Campbell responded on 24 Apr 2014 3:09 PM

I was wondering if you had every determined a solution to your problem noted above.

I have a client in the same configuration -Terminal Server, GP2013, SQL 2012 - who left their GP session running while working on a spreadsheet for about 10 min this morning and when she re-clicked on the GP Screen to get more information, she got this error.

She had to 'quite' from the system and got the FP: Cant Close Table error message - then restarted her GP session and was for a couple of hours - then she got the same cycle of error messages again.

Hope there is a better solution available than to not have the server sleep - which by definition I don't think the Remote Application on Terminal server can do.


Bill Campbell
Director, Operations
M.I.S. Management Information Solutions Ltd.
Skype: billc.edmonton
Cell: +1 780 994 2455
Off : +1 780 481 5564     

Reply
Lisa.sorensen responded on 25 Apr 2014 8:08 AM

With my client, the issue was the Terminal server was running in a virtual environment and the network connection was paused every time a snapshot of the virtual environment was performed. This seems to have been the cause of the issue for them.

Reply