Issues connecting to a VFP application with MS 2012 R2 Remote Desktop Services

We have recently deployed a 2012R2 Terminal services box, with 4 users on it.  We have a FoxPro app called Broker Plus installed on our primary server.  There are a dozen stand alone PC clients accessing the app with no issues.  When a client tries to access Broker Plus through the terminal server, they are getting a number of errors, each of which kills the session.  The RDS client is setup exactly the same as the local desktop client.  Same user.   Same permissions.  Same drive mappings.  But while it works fine on the desktop, it crashes from the TS.
I have recreated profiles, restarted the server, verified AV is not scanning the folder, disabled SMB1 and SMB2, disabled Fair Share... I dont know where else to turn.  The software mfr has no clue at this point.  Most of the errors are file read errors  (error 1104, error reading file location.cdx)

Any help or ideas would be greatly appreciated.
CrimsonwingzAsked:
Who is Participating?
 
pcelbaConnect With a Mentor Commented:
But your desktops do not use 2012R2 operating system most probably, they have different network drivers, and the virtualization has its own specifics...  Maybe the drivers update could help. You could try Microsoft support and ask them how to setup 2012R2 RDS for network shared files access. You just cannot tell them we are using Visual FoxPro but "We are using Win32 API application"... (Win32 API is still supported whereas FoxPro isn't) which uses following Win32 API entry point calls... These calls are visible in e.g. Process Monitor incl. parameters and result codes. So you could even see what was the problem reported by OS to VFP right before 1104 error and ask Microsoft why this function call failed?

... as I said nightmare ...
0
 
pcelbaCommented:
RDS does not have problems with SMB2,3 when data are accessed locally on the same machine. So the data folder containing all DBF files must be on the local drive on your Terminal server. Also check the temporary files location in the application.

Error 1104 points to the data possibly accessed via network which is not good solution for RDS. To tune such environment up is a nightmare... Better solution would be to use SQL Server to store the data in this case.

The app vendor must tell what Broker Plus setup is necessary to successfully run it under the RDS environment. Some applications do not support RDS.
0
 
CrimsonwingzAuthor Commented:
So my only option will be to move the database from its current location to the terminal server.
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
pcelbaCommented:
Yes, it should help. And remember the shared files access via network is less and less supported today and Microsoft ignores legitimate demands of developers.  Servers make more money...
0
 
CrimsonwingzAuthor Commented:
One last question, please.   What is the difference between running this client app on the server and on a normal desktop?  Drive mappings, access, etc, are all identical.  The only difference is the hardware, essentially.   I would think that if data access was an issue on the RDS, it would also show the same type of errors on the PCs.  They are all in the same network, same IP range, etc, accessing through the same drive mapping.  I am going to suggest that the vendor move the app, but I am sure there will some cost associated to that and would hate to be no farther along after its done.
0
 
CrimsonwingzAuthor Commented:
Thanks so much for the help and guidance!  I will take this up with MS and with the software vendor at this point...
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.