Ocean10000
msg:4183474 | 5:08 am on Aug 7, 2010 (gmt 0) |
The most common problem is a permission issue. And depending on version of IIS and how it is configured will effect which user account it uses to access network shares.
|
txbakers
msg:4183573 | 2:00 pm on Aug 7, 2010 (gmt 0) |
Thanks O. I can't see any issue with permissions. Both files are configured the same way, and both files MoveFile to the same directory.
But that give me another lead to investigate in the IIS.
|
Ocean10000
msg:4183625 | 3:24 pm on Aug 7, 2010 (gmt 0) |
Just to double check what user account IIS is using to connect to the fileshare run Process Monitor by sysinternals.com on the server hosting the UNC share and open the webpage that access the share.
Cannot access remote files with the FileSystemObject [support.microsoft.com]
Process Monitor [technet.microsoft.com] which replaces filemon
|
txbakers
msg:4183626 | 3:26 pm on Aug 7, 2010 (gmt 0) |
BINGO! It was a file-level permission on the file that has the MoveFile code.
It was set to IUSR in the IIS, but needed to be an administrator on the server.
|
|
