Upload goes to local account folder
RAM version: 7.5.0.1
We have the asset location set to a NAS drive where the assets are uploaded or stored. However, we just discovered that if there are issues, such as permission issue with that location, RAM will still allow upload except that they are uploaded to the home directory (Documents and Settings in window platform) of the process account.
When the NAS location recovers or is fixed, RAM looks at that location again and those assets uploaded to the home directory are no longer available.
Is this a configuration issue or known issue? Is there is fix to this or has this been fixed in later release? Sorry if this is not a new topic. Thanks for your help in advance!
We have the asset location set to a NAS drive where the assets are uploaded or stored. However, we just discovered that if there are issues, such as permission issue with that location, RAM will still allow upload except that they are uploaded to the home directory (Documents and Settings in window platform) of the process account.
When the NAS location recovers or is fixed, RAM looks at that location again and those assets uploaded to the home directory are no longer available.
Is this a configuration issue or known issue? Is there is fix to this or has this been fixed in later release? Sorry if this is not a new topic. Thanks for your help in advance!
One answer
Hi,
This is a known "feature".
In the beginning we didn't want to fail so if no persist location was
defined or it couldn't be accessed then the default of user loc was
used. This was great during development but it wasn't until recently
that it was found to be a problem for production.
See the Defaulting persist location to local appserver causing issues for clusters.
--
Rich Kulp
Rational Asset Manager developer
This is a known "feature".
In the beginning we didn't want to fail so if no persist location was
defined or it couldn't be accessed then the default of user loc was
used. This was great during development but it wasn't until recently
that it was found to be a problem for production.
See the Defaulting persist location to local appserver causing issues for clusters.
--
Rich Kulp
Rational Asset Manager developer