This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal


Apr 18, 2017, 8:20 PM
8 Posts

Anyone seeing a problem with $Dir() after upgrading to 901FP8?

  • Category: Application Development
  • Platform: Windows
  • Release: 9.0.1
  • Role: Developer
  • Tags:
  • Replies: 4

Hi Everyone

  I built an agent back in 2004 (yep, 13 years ago!) which gets a list of files from a directory (on a network drive which our server has access to) using $Dir() to get a list of file names.  I then returns a html page with url links to these files.  That allows my users to click link and download the files.  It was working fine all these years but when we recently upgraded to FP8, the $Dir() now returns 'Path not found'.  It's working on a FP7 server we have.   Anyone else have a problem with this?  

thanks

clem

Apr 19, 2017, 11:23 AM
4 Posts
$Dir() ?

Are you sure that you use $Dir() and not Dir$()?

I tested Dir$ (FILE_PATH, ATTR_NORMAL) where FILE_PATH is "c:\temp\*.* and "S:\somedirectory\*.*" (Servershare) on FP4 and FP8 with Database on Server and Local.

All results are ok.

 

 

 

Apr 19, 2017, 10:51 PM
323 Posts
Was the server installed with upgrades?

What upgrades?

Generally a Dir$() won't scan folders it doesn't have access to.

Was ND9 or its service installed under a particular account?

How about the underlying OS. Was the underlying OS upgraded or modified so that the directories are configured with different accesses?

If Domino is still running as SYSTEM, it should have access to directories granting access to SYSTEM.

Apr 20, 2017, 2:52 PM
8 Posts
Found the problem..

Thanks for the replies.  

I had always run Domino as a foreground program.  After upgrading to FP8, I decided to run it as a service.  I made sure it was running under the right user account which had access to the network drives.  It didn't dawn on me till a week of trying to troubleshoot this the run it, again, as a foreground process.  That fixed it.  Turned out that the service process didn't have access to the network drives!  Dumb admin error!

 

thanks again.

clem

Apr 20, 2017, 4:46 PM
323 Posts
glad it helped.

Yeah, network drives are a bear. If you can, sometimes you can get the network stuff connected through your own account; and then set the service to run on something other than SYSTEM.

This also works, but it's also a little dicey. I'm not a huge fan of the way network drives work on Windows, though, so maybe you can tolerate it where it just spins me up.


This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal