locked
C5 error replicates accross all users. RRS feed

  • Question

  • We have a Visual FoxPro 9 SP2 w/hot patches application running in a virtual machine, VmWare EXS, with Windows 2008 32 bit terminal server OS using remote app to deploy the application to the end users.  Every once in a while the application will crash with a c5 error.  The problem is once one person crashes everyone starts to crash or people that start the application will crash until everyone logs off the applicaion and the VFP DLLs are not in use. Then they can go back in and everything is fine until the next time.  It's like the server is sharing the VFP DLL across everyone and once it becomes corrupt it stay corrupt until everyone logs off and it clears the memory.  Is this the case and is there a way to prevent the shared memory pool?

     

    Monday, July 25, 2011 6:19 PM

Answers

  • Hello, try set resource off or similar in config.fpw. We sometimes have had problems with corrupted foxuser in virtual env. hth tom
    Monday, February 27, 2012 8:27 AM
  • If you have an "installation" of your software on a server, real or virtual, and users have a lnk pointing to the exe, then still client pcs run the exe and dlls, but indeed files are shared. To get rid of such mutliple user problems use that central folder as a template to copy to a client, eg via robocopy. a cmd can include a robocopy and start command. If robocopy is not available on clients you could also use xcopy, if only to copy robocopy in the first place. xcopy with the option to only copy newer files is fine, but robocopy copying in mirror mode is more to the point of your needs and includes retrying, for example.

    If you really want an app to run server side, you'd need to switch to remote desktop or terminal server anyway, then the installation realy is on the server and run on the server and that does not run into problems.

    Bye, Olaf.

    Saturday, February 25, 2012 7:31 PM

All replies

  • Hello CNRice,

    Thanks for your post.

    Could you please provide more specific information? Which VFP dlls do you use? Which code line leads to this C5 error?

    Have a nice day.

    Best regards


    Liliane Teng [MSFT]
    MSDN Community Support | Feedback to us
    Get or Request Code Sample from Microsoft
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Friday, July 29, 2011 5:18 AM
  • We are using the latest VFP9.dll version 9.0.0.7423.  The line of code that breaks it is always different.  We are checking their hardware but even if it is hardware it still seems weird that once it's crashed everyone crashes.  One point it was just reading a directory that would crash it once it was in the 'error state' another time was converting an XML string to a table.  Once in the 'error state' it's easy to crash it.  We are trying to trace down why it's crashing in the first place.  What I'm more concerned about is in Dermal Server it seems once one c5 crash happens to one users it replicated out to all users like the vfp9.dll have been corrupted in the terminal server memory.  I would assume each user gets their own memory space on the server.
    Monday, August 8, 2011 2:47 PM
  • Get rid if VMWare. It's a hoax that it saves money. I've seen nothing but problems with sites running it. The cost savings in hardware and software are more than offset in maintenance and support.
    Craig Berntson
    MCSD, Visual C# MVP
    INETA Community Speaker
    www.craigberntson.com
    Monday, August 8, 2011 2:52 PM
  • I would be glad to know whether or not this problem is solved.

    VMWare surely saves money and time when you are testing apps in many different OS envirionments. The production use could be questionable but VMWare was surely upgraded since last year...

    @CNRice: The error behavior points to possible problems in your VMWare installation or hardware. If you are still here could you post some news?

    Saturday, February 25, 2012 4:31 PM
  • If you have an "installation" of your software on a server, real or virtual, and users have a lnk pointing to the exe, then still client pcs run the exe and dlls, but indeed files are shared. To get rid of such mutliple user problems use that central folder as a template to copy to a client, eg via robocopy. a cmd can include a robocopy and start command. If robocopy is not available on clients you could also use xcopy, if only to copy robocopy in the first place. xcopy with the option to only copy newer files is fine, but robocopy copying in mirror mode is more to the point of your needs and includes retrying, for example.

    If you really want an app to run server side, you'd need to switch to remote desktop or terminal server anyway, then the installation realy is on the server and run on the server and that does not run into problems.

    Bye, Olaf.

    Saturday, February 25, 2012 7:31 PM
  • Hello, try set resource off or similar in config.fpw. We sometimes have had problems with corrupted foxuser in virtual env. hth tom
    Monday, February 27, 2012 8:27 AM