Created On: 22 October 2012
Problem:
Fileshare is installed as a Windows Service by using the command fsservice -i.
The Fileshare server configuration file, fs.cfg has been copied to the C:\\Windows\\System32 folder so that it will be used during startup.
When the Fileshare service is started it doesn't appear to be finding the fs.cfg file.
Why?
The Fileshare server configuration file, fs.cfg has been copied to the C:\\Windows\\System32 folder so that it will be used during startup.
When the Fileshare service is started it doesn't appear to be finding the fs.cfg file.
Why?
Resolution:
If you are installing the 32-bit version of Fileshare on a Windows 64-bit OS like Windows 7 64-bit then the fs.cfg file must reside in the 32-bit system folder which is C:\\Windows\\SYSWOW64 and not in C:\\Windows\\System32.
So if you are running fsservice -i from within a 32-bit command prompt, fs.cfg goes in C:\\Windows\\SYSWOW64 and if you are running fsservice -i from a 64-bit command prompt then fs.cfg goes in C:\\Windows\\System32.
Fileshare will then start correctly.
So if you are running fsservice -i from within a 32-bit command prompt, fs.cfg goes in C:\\Windows\\SYSWOW64 and if you are running fsservice -i from a 64-bit command prompt then fs.cfg goes in C:\\Windows\\System32.
Fileshare will then start correctly.
Old KB# 36467
#netexpress
#StudioEnterpriseEdition
#VisualCOBOL
#MFDS
#COBOL
#EnterpriseDeveloper
#Enterprise