I have a scheduled agent which performs FTP functions. Using the NotesFTP script library developed a lllooonngg time ago.
The winInet api (and all the associated data structures) appears to be the same (looking at current MS documentation)… and when I run the agent from my client, everything works just fine.
When running on server as a scheduled agent, the calls to enumerate a directory’s contents (via FtpFindFirstFile and InternetFindNextFile) returns filenames missing the 1st 4 characters of the filename. Other functions to connect, get, put, change directory, etc appear to work just fine.
I am stumped to determine what/where the issue is. On the one hand, I read that winInet “WinINet does not support server implementations. In addition, it should not be used from a service. For server implementations or services use Microsoft Windows HTTP Services (WinHTTP).” Though, WinHTTP does not contain any FTP functionality (and is documented as such… even tho MS says to use that for ‘server implementations’.
So, I’m stumped to determine…
- is this a Windows/2012 server issue (i havent attempted the agent on Server/2008).
- is this a 64 bit O/S issue… and/or 64 bit Domino issue… In my case, I am running 64 bit domino
- is this a winInet issue … either as invoked by domino… or the O/S (though, I can run the agent in a Notes client running on Windows/2012 server)
Anybody got any ideas on where the problem is and getting past it. I might consider file-shares, but there’s a bunch of challenges on that front as well.
Thanks
Scott Wagert