Service Management - NAS drive connectivity concerns
Article ID: 186797
Updated On:
Products
Issue/Introduction
Attempting to configure SC 17.X to connect to a NAS (Network Access Server or Network Attached Storage) drive where the filestore folder was relocated. After making the change, SC won't startup.
When using the default service startup of Local System account, SC can startup but complains about not being able to access the filestore:
2020/01/01 13.44.17.528 WARN [DynamicVersionDirectoryWatcher] [WebCacheVersionHandler] Some problem with the path and setting the cache key.
java.nio.file.AccessDeniedException: \\NAS-SERVER1\CAServiceDeskManager\ServiceCatalog\PROD\filestore\custom\explorer\scripts
2020/01/01 13.44.17.528 INFO [localhost-startStop-1] [WPFServlet] Initialized the WPF runtime system successfully.
2020/01/01 13.44.17.544 WARN [localhost-startStop-1] [FolderAsset] Asset folder not found at:\\NAS-SERVER1\CAServiceDeskManager\ServiceCatalog\PROD\filestore\\documents
2020/01/01 13.44.17.560 ERROR [localhost-startStop-1] [FolderAsset] Could not create an asset folder, deleting mismatched folder asset object:assetRoot
2020/01/01 13.44.17.560 ERROR [localhost-startStop-1] [FolderAsset] Can not delete Root FolderAsset.
2020/01/01 13.44.17.560 ERROR [localhost-startStop-1] [FolderAsset] Error occured Asset.getRoot(), query:asset_parent_id = asset_id and (object_type is null or object_type <= 0)
java.lang.Exception: Can not delete Root FolderAsset.
SQL query shows the filestore is configured to the NAS drive:
use mdb;
select * from usm_configuration where name='documentroot'
\-> \\NAS-SERVER1\CAServiceDeskManager\ServiceCatalog\PROD\filestore
A connectivity test from the filestore configuration screen returns error of check your configuration.
Environment
Release : 17.X
Component : CA SERVICE CATALOG
Resolution
Update the SC 17x filestore to point to the NAS drive. Login to the SC 17x server with an account that can access the NAS drive and also has Admin rights over the SC Server, user "NASAdmin". Set the Service Catalog service to run as the "NASAdmin" user, then recycle the Service Catalog service. Test to see if SC works and attachments work (which they should)
Once this is done, you should be able to reboot the SC 17x server, then login to the SC 17x server as any user who has admin rights, besids the designated user who has both SC Server Admin rights and rights to access the NAS Drive, user "NASAdmin". The Service Catalog service should still be running as the "NASAdmin" user.
SC 17x NAS filestore should then be working without issue.
Additional Information
Feedback
