Hi, Ramesh -

Installing and reading an ini file from C:\Windows is generally considered a bad idea. You should seriously consider changing your application logic. You should also familiarize yourself with the Windows "virtual store" folder and "roaming" files. Your app is trying to do things that Windows doesn't permit unless the user has admin rights. In my opinion, you're fighting a losing battle attempting to restore your application to the way it used to work.

Here is a link to a very recent Q&A topic that involves the Virtual Store:

https://community.appeon.com/index.php/qna/q-a/find-directory-of-a-file

There is also plenty of information publicly available on this topic via a web search.

Here is a link to some info on roaming folders:

https://community.appeon.com/index.php/qna/q-a/find-directory-of-a-file

Again, there are many articles available on the web on this topic.

HTH

Regards, John

Team. 

   Somebody please help me. I created support ticket for this issue and provided a sample code and still  waiting for the response. In the meantime I did more research on this and narrowed down what's happening. 

   Issue :   

           I have a application compiled in 2019 R3 ( Installed it recently ) .

           This is my code :    Trim(ProfileString("C:\windows\choice.ini", "Choice", "drive", "")

          When I run this application in my laptop( windows 10 ) first its looking for the .ini file in my user profile folder. ie
C:\Users\rgovinda\AppData\Local\VirtualStore\Windows , if the file is not available then its going to c:\windows.

   But when I run this in the server ( windows 2016 ) then its not going to my user profile folder instead its directly going to  c:\windows.

************************************************************************

Note :   

    We have RDS ( Remote desktop services )  installed on our windows 2016 server to redirect printer/driver/ports for RDP connection.  That said  , Printer is also not working in windows 2016 server with PB 2019 R3.

          I am thinking  PB 2019 with RDS has some issues . My both issues... accessing the user profile folder and Printer not working will be resolved if we figure out the issue with newer version of PB and RDS.

Your help is greatly appreciated.

Thanks

Ramesh G

Thanks Mike for your response.

 Production  ( windows 2008 )

    Code : OLD Code  -  accessing user profile folder is working. ( It has remote desktop services RDS installed )

Development ( windows 2016 )

   Code : OLD Code ( copied from Prod)  -  Accessing user profile folder is working. ( after installing remote desktop services RDS )

   Code :  New code , Compiled in Appeon 2019 R2 -  Accessing user profile folder is NOT working.

Ant thoughts ?

Thanks

Ramesh G

"running fine in production (  windows 2008 and SQL 2008 )"

"new server ( windows 2016 )" 

it is probably changes in windows server.  microsoft has been securing windows (especially server) to prevent applications writing to files in windows directory, programfiles directory, etc.

Appeon PB standard Edition
Version 2019 Build 2353

Chris.

  Thanks for your response. I am sure this code is from older version of the PB. Only we have the source code. I upgraded to 2019 R2.  Did you see my updated message ? its working in my laptop not in the server.  ( windows 2016 ). 

Appreciate your help.

Thanks

Ramesh G

Hi Ramesh;

   What PB version & build are you currently using?

   FWIW: There should be no changes to the ProFileString() method unless you are moving from a PB version <10 to a PB version >10. That is when PB went from being ANSI based to being Unicode based.

   Also note that PB2019 R2 does not support the W2008 Rx O/S any more.

http://docs.appeon.com/pb2019r2/installation_guide_for_pb/ch01s01.html

Regards ... Chris