Martin,
The source directory, destination directory and user Temp directory are typically all the directories that are needed. However, depending on your configuration, there may be exceptions to this. You may have a log or pipeline file setting with a specified path other than the user's. Your workspace may have a datasource that also reads in a template or schema file from another path. Also, the Environment variables and paths you have defined will affect where your cache data is written. For example, if you have a user TMP directory defined, FME will first try to write there. If not, FME will try to write to the system TMP directory. Go to control panels - system - properties - advanced and check the environment variables there. The best way to determine where FME is trying to write is to examine the log file. In my case I have a user defined environment variable of: TMP = %USERPROFILE%\Local Settings\Temp When I load a dataset into workbench, I get the log: ... Opening the Geodatabase reader. ... Opened mapping File C:\DOCUME~1\dhintz\LOCALS~1\Temp\fme12.tmp.fmw for output ... Which shows that the temp cache is being written to the user temp directory. Steps to try: 1) note where cache is being written from the log. 2) see if any new cache files are successfully being written. If not, then there may be a space limitation or write permission or write access problem. 3) If write location is inappropriate, try changing the user TMP path 4) Try changing the permissions on the TMP directory 5) Try purging the TMP directory Overall, if these pointers do not help, the best thing is to send us your workspace and log file to [EMAIL PROTECTED] so that we can take a look at it and try to duplicate the problem. Be sure to include which build are you using as well as a list off your environment variables and values. Regards, Dean P.s. There is likely no problem with the feature merger transformer. Most likely what is happening is that the when the featuremerger is used, more data is read in and stored at the same time to support the join, and so more memory and thus cache is needed. -----Original Message----- From: jaeger2010 [mailto:[EMAIL PROTECTED] Sent: November 19, 2004 4:30 AM To: [email protected] Subject: [fme] FME-Transformation on Windows Server 2003 Hello, When running a simple translation with FME 2004 ICE (merging two FFS files with a feature merger and writing it to a new FFS file) the translation stopped without any error message while reading the data. Converting the same data without the feature merger didn't cause any errors. This transformation took place on a machine with Windows Server 2003. The problem only occured when not being logged in as admin. All other users definitely had write access to their TEMP directory. Are there any other directories for which read/write access is necessary? Regards, Martin Get the maximum benefit from your FME, FME Objects, or SpatialDirect via our Professional Services team. Visit www.safe.com/services for details. Yahoo! Groups Links Get the maximum benefit from your FME, FME Objects, or SpatialDirect via our Professional Services team. Visit www.safe.com/services for details. Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/fme/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
