>My application gives internal consistency error. Application runs automated from windows terminal services user preferences. If user runs it from click from desktop it runs without internal consistency error. If user runs it automated with foxpro standard version runtime it runs without internal consistency error. I tried run with compact exe with +x parameter it gets internal consistency error again. I tried run my application from foxprox, succeeded:
>
>-extended exe automated: fails (internal consistency error)
>-extended exe from desktup: runs
>-compact exe, automated standard runtime: runs
>-compact exe, automated extended runtime: fails (it seeks standart runtime - cannot located desired version error)
>-foxprox than run automated compact exe: runs
>
>I just found solution run foxprox, after that run my exe file. I can't use standard exe because of standard exe capacity problems. I have another application at this system it doesn't give internal consistency error. Other (which doesn't give error) is about 4MB and this is about 8MB. I wonder if is that about .EXE size. There isn't any difference with config.fp files.

Probably the most common cause of ICEs is index file corruption. Make sure they are OK before you try anything else.

There used to be an article on this site by Ed Rauh, outlining recommended various settings for memory for Fox2x. I can't find it any longer. You might want to make changes to CONFIG.NT on the TS machine, or start the app with a PIF that limits various types of memory.

If it is FP DOS, you might want to look at Thread#1448431

especially, http://www.markwilson.co.uk/blog/2005/01/troubleshooting-ms-dos-application.htm

I don't think any of that information is specific to Terminal Server