FSVIEW diagnostics

Problem:

This article discusses a useful FSVIEW diagnostic technique when using Enterprise Server fileshare.

Resolution:

Using FSVIEW we can possibly identify which ES process ID have a file locked. This can be useful in determining the root cause for file access issues. To do this we need to set the "Fileshare User" field in the ES region SIT to be the fileshare user id with an extra pound sign. For example, if the ES fileshare user is esadmin, define "esadmin#" in the "Fileshare User" field in region SIT.

The below is an example of FSVIEW output:

C:\\Users\\evank\\Documents>fsview
Fileshare Version 2 Revision 19999  - Administration Utility
 
fsview> admin logon FSVIEW Meryton
fsview> server set fsserv1
fsview> users get
Current Users
uid  user name           No. access   logon time    last access
00001:evank#0000000096   0000000012      09:05:59      16:07:05
                                      on 06/15/17   on 06/15/17
00002:FSVIEW             0000000002      16:09:26      16:10:05
                                      on 06/15/17   on 06/15/17
 
fsview> files get
Open Files
Count / name
     1  C:\\CCISMFS\\DATASETS\\ACCTFIL
 
fsview> file get-users C:\\CCISMFS\\DATASETS\\ACCTFIL
00001  evank#0000000096
 
fsview>

The 0000000096 is the ES process id which has the file locked.

At this time if you try to copy the file you may get error:

"File In Use The action can't be completed because the file is open in Fileshare Server DLL trigger. Close the file and try again."

For detailed FSVIEW Command Line Syntax please check our documentation.