1. John Vaughn
  2. PowerBuilder
  3. Thursday, 30 May 2019 16:43 PM UTC

FileMove and FileCopy Fail on a Windows 2016 Server when the file path is not local. Works fine when source and destination are on the C or D drive but fails (Opening Source) when it is a network location. My development machine is Windows 10 and it works fine there, only fails when deployed to Windows 2016. Have tried with full path and mapped drive.

Thanks,

John Vaughn

Brad Mettee Accepted Answer Pending Moderation
  1. Friday, 31 May 2019 12:52 PM UTC
  2. PowerBuilder
  3. # 1

Have you tried it out on other versions of WindowsServer?
What access rights does the app have while running?
Is it being run as a service? If so, as what user?
What version of Powerbuilder? Do all of the DLLS on the server match your local machine? Are there multiple versions of the DLLS on the server and search path possibly causing issues?

 

Comment
  1. Chris Pollach @Appeon
  2. Friday, 31 May 2019 16:36 PM UTC
Hi John;

Are you using UNC (Universal Naming Convention - ie: \\Server\Name\ ... ) path declarations instead of "Mapped" drives?

Regards ... Chris
  1. Helpful
There are no comments made yet.
John Vaughn Accepted Answer Pending Moderation
  1. Monday, 3 June 2019 20:39 PM UTC
  2. PowerBuilder
  3. # 2

All,

Brads Questions:

Application has been running on Windows 2008 R2 for several years without issue, we are upgrading all of our servers to Windows 2016 (VM).

Set to run as Admin

Application is executed from the Windows Task Manager on a regular interval. Closes after running

Server is a new build and we only installed one version(2017 R3 1858)

Chris:

Move or Copy Fail using mapped drive or full path. We have a dedicated File system that is not part of a single server.

New Information:

We found that if we create a new PB 2017 application it works correctly but when we migrate our application from PB 12.5.1 it does not. We also tried exporting the Source Code in PB 12.5.1 and then creating a new application in PB 2017 and then importing the PB 12.5 objects it also fails. BTH this is a very small application 1-Window, 1-DataWindow, 1-UserObject, and a few Functions. PBL's are zipped and attached.PBL's have been migrated to Appeon 2017 R3. I can send original PB 12.5 if needed.

One more thing:

I tried using both methods to do Move and Copy files native to Appeon FileMove() and also using Kernel32 call in Local External Function (MoveFileA()) both return -1 unable to open source.

Attachments (1)
Comment
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.