iDC File Manager Knowledge Base

Windows Servers Category

Installation guides for Windows servers (Windows 2003 IIS 6.0,

Windows 2008 IIS 7.0 etc...).

Contents
Windows Servers

Will iDC File Manager run on a Windows Server?

Upload and Download issues with large files (Windows Servers)
The specified CGI application misbehaved by not returning a complete set of HTTP
headers
404 error when uploading on Windows servers.
.WINDOWS Installation guide
iDC File Manager v1.4 to v1.5 - Upgrade Guide
Can't load Configuration file - No such file or directory at C:/Inetpub/wwwroot/cgibin/FileManager/IDC.pm line 89.
Version 1.4 Manual Installation Guide / User Manual

1
1
1
1
2
2
35
37
38

Windows Servers

Installation guides for Windows servers (Windows 2003 IIS 6.0, Windows 2008 IIS
7.0 etc...).

Will iDC File Manager run on a Windows Server?

iDC File Manager is a cross platform system and so will work on Windows Server 2003 IIS 6.0 and
Windows Server 2008 IIS 7.0
However, it is recommend for best results, where possible to install iDC File Manager on a Linux
server.The difference being that the default upload functions Progress bar is not supported on
windows severs, however an upload progress bar is available via the Flash upload function, for
additional information please refer to:
http://www.idotcommunications.co.uk/site.php?page=FeaturesOverview#UploadAndDownload
All other features are supported on both server types.
Copyright i Dot Communications

Upload and Download issues with large files (Windows Servers)

If the server times our before the upload is complete you may get any manner or warnings from a
simple 404 error to the "The specified CGI application misbehaved by not returning a complete set
of HTTP headers" warning.
This is a common issue running all Web based File Manager's (not just iDC File Manager) on
windows servers, as Windows servers with IIS do not by default handle the uploading or
downloading of larger files particularly well.
Below is generic solution to improving the upload and download functions on windows servers:
Open up the file "metabase.xml" with notepad...should be located in C:\windows\sytem32\inetserv.
Find the variable named "AspBufferingLimit" and change it to something greater than what is there.
By default this is set to around 4 megs. By changing this variable you are increasing the max size
of ASP response buffer, thus letting you download files greater than 4 megs. For uploading files
greater than this amount, look for the variable named "AspMaxRequestEntityAllowed" and change it
to the desired size. And there you have it. By increasing the number of these variables, you can
control the size of uploads and downloads (respectively).
Addtionally if you also change the cgi response timeout in IIS / metabase, this will also greatly
improve the upload ability and reduce the potential for server timeouts.
C:\Inetpub\AdminScripts>cscript adsutil.vbs SET W3SVC/CGITimeout xxxx
After setting xxx to a higher value (default 300 sec) you can now download my larger files.
Thanks to Steve and Georg, for the tip on this!
Copyright i Dot Communications

The specified CGI application misbehaved by not returning a complete set

of HTTP headers
If the server times our before the upload is complete you may get any manner or warnings from a
simple 404 error to the "The specified CGI application misbehaved by not returning a complete set
of HTTP headers" warning.

1 of 38

This is a common issue running all Web based File Manager's (not just iDC File Manager) on windows
servers, as Windows servers with IIS do not by default handle the uploading or downloading of larger
files particularly well.
Below is generic solution to improving the upload and download functions on windows servers:
Open up the file "metabase.xml" with notepad...should be located in C:\windows\sytem32\inetserv.
Find the variable named "AspBufferingLimit" and change it to something greater than what is there.
By default this is set to around 4 megs. By changing this variable you are increasing the max size of
ASP response buffer, thus letting you download files greater than 4 megs. For uploading files greater
than this amount, look for the variable named "AspMaxRequestEntityAllowed" and change it to the
desired size. And there you have it. By increasing the number of these variables, you can control the
size of uploads and downloads (respectively).
Addtionally if you also change the cgi response timeout in IIS / metabase, this will also greatly
improve the upload ability and reduce the potential for server timeouts.
Thanks to Steve, for the tip on this!
Copyright i Dot Communications

404 error when uploading on Windows servers.

If the server times our before the upload is complete you may get any manner or warnings from a
simple 404 error to the "The specified CGI application misbehaved by not returning a complete set
of HTTP headers" warning.
This is a common issue running all Web based File Manager's (not just iDC File Manager) on windows
servers, as Windows servers with IIS do not by default handle the uploading or downloading of larger
files particularly well.
Below is generic solution to improving the upload and download functions on windows servers:
Open up the file "metabase.xml" with notepad...should be located in C:\windows\sytem32\inetserv.
Find the variable named "AspBufferingLimit" and change it to something greater than what is there.
By default this is set to around 4 megs. By changing this variable you are increasing the max size of
ASP response buffer, thus letting you download files greater than 4 megs. For uploading files greater
than this amount, look for the variable named "AspMaxRequestEntityAllowed" and change it to the
desired size. And there you have it. By increasing the number of these variables, you can control the
size of uploads and downloads (respectively).
Addtionally if you also change the cgi response timeout in IIS / metabase, this will also greatly
improve the upload ability and reduce the potential for server timeouts.
Thanks to Steve, for the tip on this!
Copyright i Dot Communications

.WINDOWS Installation guide

The following setup instructions are designed to give you a full step by step guide through the
process of configuring and uploading your copy of iDC File Manager.
For more advanced users you can jump to the "Checklist" section of "Prior to starting the
installation".
Prior to starting the installation
Prior to starting the installation you need to be familiar of how your server is setup and configured
and which are the main directory folders.
You need to be aware that although this installation guide is designed for clients installing iDC File

2 of 38

Manager on a Windows server, each server setup is differently and so the folder and directory
names may vary, but the basic principals of the installation will still remain the same.
Connect to your server locally and navigate to the c:\inetpub\ directory.
Alternatively, using an FTP client like CuteFTP: http://www.globalscape.com/products/ftp_clients.aspx
enter your FTP address, FTP Username and FTP password and login into your server.
If you are unsure of your servers FTP login details please contact your host or Network administrator.
Tip: If you use the FTP client option, please be aware that the FTP settings needs to be configured to
allow access to the c:\inetpub\ or c:\inetpub\wwwroot directories and not just the default Anoymous
FTP access which can only be used for basic file transfers.
When you have successfully logged into your server you will be presented with a number of
directories and you will need to locate your servers public root folder.
This directory could be named any of the following:
wwwroot
Again, if you are unsure of this location please contact your host or Network administrator.
Tip: As a test, if you were to upload a file called "example.txt" into the folder you believe to be the
servers root folder, you should then be able to access this file via:
http://www.yoursite.com/example.txt and the file should open correctly. If the server returns a 404
"Not Found" error then this is not the correct location.
After you have located your servers root folder, you then need to locate your servers cgi-bin folder.
This is the directory which your server has designated as the location to allow perl and cgi scripts to
be run from.
On 99.9% of servers this folder is called "cgi-bin" but can sometimes just be called "cgi" or "cgilocal".
This folder will either be located as a subfolder within the servers root folder (a level below the
servers root folder) e.g:
C:\Inetpub\wwwroot\cgi-bin
or at the same level as the servers root folder e.g:
C:\Inetpub\cgi-bin
Tip: If you cannot find your servers cgi-bin directory, this may be an indication that your server does
not have Perl installed and you will therefore need to contact your host or Network administrator to
get Perl setup on your server.
With the servers public root folder and cgi-bin located you now need to ascertain the full server
paths to these two folder locations.
A server path is simply a string of folder locations organized in a hierarchy and used to pinpoint a
particular location within the server.
For example (and again these paths are subjective) if you were to access a Windows 2003 IIS6.0
server via the folders may appear as:
\wwwroot\
and
\wwwroot\cgi-bin
However that is only part of the path, the full path to these locations would be:
C:/Inetpub/wwwroot/cgi-bin
as the folder locations "C:/Inetpub/" are sometimes outside of what you normally see.
To configure iDC File Manager you will need to know the full path to the both the public root and the
cgi-bin folders.

3 of 38

These paths can either be obtained by running one of the common server test scripts or by
contacting your host or referring to their Server F.A.Q / Knowledgebase pages.
Tip: Although your server paths may be displayed as: C:\Inetpub\wwwroot\ and
C:\Inetpub\wwwroot\cgi-bin when you are asked to enter these paths in the script configuration files
these paths need to be entered as: C:/Inetpub/wwwroot/ and C:/Inetpub/wwwroot/cgi-bin i.e the
backwardslash "\" is replaced with a forwardslash "/".
After you have ascertained the paths to both the public root and the cgi-bin folders, your then need
to setup a MySQL database and associated username and password.
If you are unsure of how to setup a MySQL Database please contact your host or Network
administrator.
After you have setup a MySQL database and associated username and password you then to ensure
your server is correctly configured to run perl and cgi scripts (.pl / .cgi) in the first place.
An excellent guide to "Setting up Perl/CGI to work with Windows Server 2003 / 2008" can be found
here:
http://www.visualwin.com/Perl/
Tip: It is advisable to ensure that perl is correctly installed and configured on your server prior to
attempting to install the main File Manager software. You can do this by running one of the common
"Hello World" or perl / cgi server test scripts.
After you have ensured that your server is correctly configured to run perl and cgi scripts, you then
need to locate the servers Path to Perl.
This is the path which is entered on the first line of all perl scripts and points to the location of your
servers installation of perl.
Your host or Network administrator will be able to advise the exact path to perl but it is usually:
#!/c:/perl/bin/perl.exe
However, on 99.9% of Windows servers we have performed installations on, although the true path
to perl was: c:\perl\bin\perl.exe if you change the path from: #!/usr/bin/perl to #!/c:/perl/bin/perl.exe
the script will return an internal server error and so usually the path to perl is left as: #!/usr/bin/perl
and so it is likely that you will not need to configure this path in iDC File Manager.
Pre-installation Checklist:
Prior to moving onto the Step 1, please ensure that you have now:
1) Checked that your FTP details or local server access details are valid and you can correctly login
to your server.
2) Located your servers public root folder and cgi-bin folders.
3) Ascertained the full server paths to the public root folder and cgi-bin folders.
4) Setup a MYSQL Database and associated username and password.
5) Check that Perl is installed on your server and that your server is correctly configured to run perl
and cgi scripts.
6) Ascertained your servers Path to Perl.
7) Please ensure your server meets the requirements here:
http://www.filemanager.net/site.php?page=Requirements
If you have not been able to complete any of the above points please contact your host or Network
administrator for further advice / information.
Step 1
After purchasing your copy of iDC File Manager you will receive a link via email which will enable you
to download the script.
The script will be in a .zip file which will require extracting.
After extraction you will see a single Directory called iDC File Manager.

4 of 38

When you open this directory you will be presented with 2 sub-directories:

Contents of this folder to be uploaded into httpdocs or public_html or wwwroot

Contents to be uploaded into cgi-bin folder

To begin with, upload the folder called "FileManager" contained within the directory named
"Contents of this folder to be uploaded into httpdocs or public_html or wwwroot" into your servers
public root folder.
Please ensure that you do not simply upload the directory "Contents of this folder to be uploaded
into httpdocs or public_html or wwwroot" into the root, just its contents.
When the upload of the folder named "FileManager" and all of its contents has been successfully
uploaded into your servers root folder you can then move on to step 2.
Step 2
Return to the extracted zip file named "iDC File Manager" and open up the folder named "Contents
to be uploaded into cgi-bin folder", before then navigating into the sub folder named "FileManager".
When you have accessed the "FileManager" folder you then need to open the file named
"Configuration.pl" in a perl or text editor.
Please note that although the "Configuration.pl" file caries the extension ".pl" it is not in fact a perl
script but simply a text configuration file, which is used by the iDC File Manager software package to
store all of the configuration settings and is an easy way for you to configure the software without
the issue of script corruption that can sometimes occur when you edit the scripts themselves.
Each configuration setting used in the iDC File Manager software package is broken down into
individual sections and each carries configuration comments.
Depending on the editor you are using, each configuration setting may include the line number. If it
does then you can use the line number to quickly locate the individual configuration settings,
otherwise you will need to perform an Edit -> Find action.
Starting the configuration
Lines 1 - 56 include details of the License agreement you are to abide by when using or installing
iDC File Manager. Although these lines require no direct input, you must read through them fully and
only proceed further if you agree to the terms.
:: Technical Support Links
Lines 58 - 61 include links to the i Dot Communications Technical Support Pages:

58
59
60
61

#############################################################
##################
# For Instructions / Questions / Comments etc... Please visit:
# http://www.filemanager.net/site.php?page=TechnicalSupport
#############################################################
##################

5 of 38

:: File Manager - Version

Lines 67-69 detail the individual point release of the version of iDC File Manager you are using.
Please note: As this installation guide is for iDC File Manager version 1.5, it is therefore presumed
that the full version including point release would be in this case: V1.5.0
The Last 2-3 letters after the point release reference the individual version e.g. iDC File Manager OEM version
This configuration setting also requires no direct input but is useful to reference when contacting i
Dot Communications technical support.

63
64
65

####File Manager Version:####################################################

Version ".01 OEM"
#############################################################
##################

:: Main File Manager Name

If you hold an OEM or Developer license you can modify the "File Manager Name" to the name you
would like to apply to the File Manager e.g. ABC File Manager.

71
72
73
74
75
76

####Main File Manager

Name#####################################################
FileManagerName "iDC File Manager"
#Do not modify the Main File Manager Name unless you hold an OEM License
#############################################################
##################

:: File Manager - Registered Owner

Change the "File Manager - Registered Owner" to the name of your company or website.
This reference is used in numerous location within iDC File Manager including the about page, email
templates and script headers.

6 of 38

83
84
85
86
87
88
89

####File Manager - Registered

Owner:###########################################
RegisteredOwner "Example Company"
#Change the "File Manager - Registered Owner:" to the name of
#your company or website etc...
#############################################################
##################

:: Main File Manager Title

Change the "Main File Manager Title" to the name of your company or website.
This reference is used in the File Manager page titles.

91
92
93
94
95
96

####Main File Manager

Title####################################################
Filemanagertitle "Example - File Manager"
#Change the "File Manager Title" to the name of your company or website etc...
#############################################################
##################

:: MySQL Database Settings

Change the "MySQL Database Settings" to correspond with the MySQL database you have setup.
Replace "DATABASE-NAME-HERE" with your MySQL Database name.

7 of 38

Replace "HOSTNAME-HERE" with your MySQL Hostname. This is usually "localhost" but often is an IP
or URL etc...
Enter your MySQL Username.
Enter your MySQL Password.

98
99
100
101
102
103
104
105
106

####MySQL Database
Settings####################################################
dns 'DBI:mysql:DATABASE-NAME-HERE:HOSTNAME-HERE'
dbUser 'Your Username'
dbPassword 'Your Password'
#Change the "MySQL Database Settings" to correspond with
#the Mysql database you have setup.
#############################################################
##################

:: Main Clients Directory

Using the server path information you ascertained in the Pre-installation checks, please change the
path to the "Main Clients Directory" to your servers path to the public root directory +
the sub-folder of the File Manager folder which will hold all your Clients folders.
e.g. clientroot "C:/Inetpub/wwwroot/FileManager/Clients"

108
109
110
111
112
113
114
115
116
117

8 of 38

####Main Clients
Directory#####################################################
clientroot "C:/Inetpub/wwwroot/FileManager/Clients"
#Change the path to the "Main Clients Directory" to your servers path to the
#main public root directory + the sub-folder of the File Manager folder which
#will hold all your Clients folders.
#For example:
#e.g.clientroot "C:/Inetpub/wwwroot/FileManager/Clients"
#############################################################
##################

:: Main Shared Clients Directory

Using the server path information you ascertained in the Pre-installation checks, please change the
path to the "Main Shared Clients Directory" to your servers path to the public root directory +
the sub-folder of the File Manager folder which will hold all your Shared folders.
e.g. defaultSharedRoot "C:/Inetpub/wwwroot/FileManager/Shared"

119
120
121
122
123
124
125
126
127
128

####Main Shared Clients

Directory##############################################
defaultSharedRoot "C:/Inetpub/wwwroot/FileManager/Shared"
#Change the path to the "Main Shared Clients Directory" to your servers path
#to the main public root directory + the sub-folder of the File Manager folder
#which will hold all your Shared folders.
#For example:
#e.g. defaultSharedRoot "C:/Inetpub/wwwroot/FileManager/Shared"
#############################################################
##################

:: Main Template Directory

Using the server path information you ascertained in the Pre-installation checks, please change the
path to the "Main Template Directory" to your servers path to the public root directory +
the sub-folder of the File Manager folder which will hold the File Manager template files.

9 of 38

e.g. templateDir "C:/Inetpub/wwwroot/FileManager/Templates"

130
131
132
133
134
135
136
137
138
139

####Main Template
Directory####################################################
templateDir "C:/Inetpub/wwwroot/FileManager/Templates"
#Change the path to the "Main Template Directory" to your servers path to the
#main public root directory + the sub-folder of the File Manager folder which
#will hold all your Template files.
#For example:
#e.g.templateDir "C:/Inetpub/wwwroot/FileManager/Templates"
#############################################################
##################

:: Main Language Messages Directory

Using the server path information you ascertained in the Pre-installation checks, please change the
path to the "Main Language Messages Directory" to your servers path to the public root directory +
the sub-folder of the File Manager folder which will hold the File Manager external language files.
e.g. languageMessagesFolder "C:/Inetpub/wwwroot/FileManager/Languages"

141
142
143
144
145
146
147
148
149
150

####Main Language Messages

Directory###########################################
languageMessagesFolder "C:/Inetpub/wwwroot/FileManager/Languages"

10 of 38

#Change the path to the "Main Language Messages Directory" to your servers
#path to the main public root directory + the sub-folder of the File Manager
#folder which will hold all your Language files.
#For example:
#e.g. languageMessagesFolder "C:/Inetpub/wwwroot/FileManager/Languages"
#############################################################
##################

:: Main Session Directory

Using the server path information you ascertained in the Pre-installation checks, please change the
path to the "Main Session Directory" to your servers path to the cgi-bin directory +
the sub-folder of the File Manager folder which will hold the File Manager sessions directory.
e.g. sessionDir "C:/Inetpub/wwwroot/cgi-bin/FileManager/sessions"

152
153
154
155
156
157
158
159
160

####Main Session
Directory#####################################################
sessionDir "C:/Inetpub/wwwroot/cgi-bin/FileManager/sessions"
#Change the path to the "logActivity " to your servers path to
#the /cgi-bin/FileManager/ folder
#For example:
#e.g. sessionDir "C:/Inetpub/wwwroot/cgi-bin/FileManager/sessions"
#############################################################
##################

:: Skin Theme Config File

Using the server path information you ascertained in the Pre-installation checks, please change the
path to the "Skin Theme Config File" to your servers path to the cgi-bin directory +
the sub-folder of the File Manager folder which will hold the Skins.ini file.
e.g. alternativeConfigurationFile "C:/Inetpub/wwwroot/FileManager/Skins.ini"

11 of 38

162
163
164
165
166
167
168
169
170
171
172

####Skin Theme Config

File#####################################################
alternativeConfigurationFile
"C:/Inetpub/wwwroot/cgi-bin/FileManager/Skins.ini"
#Change the path to the "Skin Theme" to your servers path to the
#/cgi-bin/FileManager/ folder
#For example:
#e.g. alternativeConfigurationFile
"C:/Inetpub/wwwroot/cgi-bin/FileManager/Skins.ini"
#############################################################
##################

:: Analysis And Log Files - Activity Log

iDC File Manager can be configured to log all user and admin activity as well as any error messages
that may be generated.
To enable the Activity log change logActivityOn "0" to: logActivityOn "1"
To disable the Activity log change logActivityOn "1" to: logActivityOn "0"
If you enable the Activity log you also need to specify the full path to the "logActivity.txt" csv flat file
database.
Using the server path information you ascertained in the Pre-installation checks, please change the
path to the "Log Activity File" to your servers path to the cgi-bin directory +
the sub-folder of the File Manager folder which will hold the logActivity.txt file.
e.g. alternativeConfigurationFile "C:/Inetpub/wwwroot/FileManager/logActivity.txt"

174
175
176
177
178
179
180
181
182
183
184
185

12 of 38

186
187
188

#####Analysis And Log Files - Activity

Log#####################################
logActivityOn "1"
#To enable the Activity log change logActivityOn "0" to: logActivityOn "1"
#To disable the Activity log change logActivityOn "1" to: logActivityOn "0"
logActivity "C:/Inetpub/wwwroot/cgi-bin/FileManager/logActivity.txt"
#Change the path to the "logActivity " to your servers path
#to the /cgi-bin/FileManager/ folder
#For example:
#e.g. logActivity
"C:/Inetpub/wwwroot/cgi-bin/FileManager/logActivity.txt"
#############################################################
##################

:: Main Image Directory

Change the url of the "Main Image Directory" to your servers url to the public root folder
"FileManager" + the File Manager Image Directory called "FileManagerData"
e.g. htmlDataFolder "http://www.yoursite.com/FileManager/FileManagerData"

190
191
192
193
194
195
196
197
198
199

####Main Image
Directory#######################################################
htmlDataFolder "http://www.yoursite.com/FileManager/FileManagerData"
#Change the url of the "Main Image Directory" to your servers url to
#the public root folder "FileManager" + the File Manager Image Directory
#called "FileManagerData"
#For example:
#e.g. htmlDataFolder "http://www.yoursite.com/FileManager/FileManagerData"
#############################################################
##################

13 of 38

:: Main Logo Directory

Change the url of the "Main Logo Directory" to your servers url to the public root folder
"FileManager" + the File Manager Image Directory called "FileManagerData" + "FileManagerLogos"
e.g. htmlLogoFolder "http://www.yoursite.com/FileManager/FileManagerData/FileManagerLogos"

201
202
203
204
205
206
207
208
209
210
211
212

####Main Logo
Directory#######################################################
#
htmlLogoFolder
"http://www.yoursite.com/FileManager/FileManagerData/FileManagerLogos"
#Change the url of the "Main Logo Directory" to your servers url to the
#public root folder "FileManager" + the File Manager Image Directory
#called "FileManagerData" + "FileManagerLogos"
#For example:
#e.g. htmlLogoFolder
"http://www.yoursite.com/FileManager/FileManagerData/FileManagerLogos"
#############################################################
##################

:: Main Clients Directory

Change the url of the "Main Clients Directory" to your servers url to the public root folder
"FileManager" + the Main Clients Directory called "Clients"
e.g. htmlClientsFolder "http://www.yoursite.com/FileManager/Clients"

214

14 of 38

215
216
217
218
219
220
221
222
223

####Main Clients
Directory#####################################################
htmlClientsFolder "http://www.yoursite.com/FileManager/Clients"
#Change the url of the "Main Image Directory" to your servers url to the
#public root folder "FileManager" + the File Manager Main Clients Directory
#called "Clients"
#For example:
#e.g. htmlClientsFolder "http://www.yoursite.com/FileManager/Clients"
#############################################################
##################

:: Main Templates Directory

Change the url of the "Main Templates Directory" to your servers url to the public root folder
"FileManager" + the Main Templates Directory called "Templates"
e.g. htmlTemplateFolder "http://www.yoursite.com/FileManager/Templates"

225
226
227
228
229
230
231
232
233
234

####Main Template
Directory####################################################
htmlTemplateFolder "http://www.yoursite.com/FileManager/Templates"
#Change the url of the "Main Template Directory" to your servers url to the
#public root folder "FileManager" + the File Manager Main Template Directory
#called "Templates"
#For example:
#e.g. htmlTemplateFolder "http://www.yoursite.com/FileManager/Templates"
#############################################################
##################

15 of 38

:: Main Script URL

Change the "Main Script URL" to your servers url to the cgi-bin + the Main File Manager Directory
called "FileManager"
e.g. scriptPath "http://www.yoursite.com/cgi-bin/FileManager"

236
237
238
239
240
241
242
243
244

####Main Script
URL##########################################################
##
scriptPath "http://www.idcfilemanager.com/cgi-bin/FileManager"
#Change the "Main Script URL" to your servers url to the cgi-bin
#+ the Main File Manager Directory called "FileManager"
#For example:
#e.g. scriptPath "http://www.yoursite.com/cgi-bin/FileManager"
#############################################################
##################

:: Upload Settings
Change:
uploadPrBarOn "1" to: uploadPrBarOn "0".
Do not modify the "secretWord" option unless told to do so by iDC Support.

246
247
248
249
250

16 of 38

251
252
253
254
255
256
257
258
259
260
261
262
263
264

####Upload Settings
###########################################################
####HTTP And HTTPS Upload Settings####
#Linux servers only:
uploadPrBarOn "0"
#To enable the Upload Progress bar change:
#uploadPrBarOn "0" to: uploadPrBarOn "1" (Linux servers only)
#To disable the Upload Progress bar change:
#uploadPrBarOn "1" to: uploadPrBarOn "0"
####Flash Upload Settings####
secretWord "fTf4m#G56sGH!"
#Do not modify the "secretWord" unless told to do so by iDC Support.
#############################################################
##################

:: Email Settings
iDC File Manager can send automated confirmation emails for when files are uploaded, downloaded
or new accounts are created.
To enable iDC File Manager to send these confirmation emails you need to configure the email
settings.
To / From / Reply To addresses:
Enter Your Email address for the following:
adminMail "[email protected]"
replyMail "[email protected]"
fromAdmin "[email protected]"
toAdmin "[email protected]"
Sendmail Path:

17 of 38

Windows servers do not have Sendmail and so you can leave the Sendmail path blank.
Send as HTML:
To enable HTML emails change sendAsHtml "0" to: sendAsHtml "1"
To disable HTML emails change sendAsHtml "1" to: sendAsHtml "0"
New Account Confirmation:
To enable the option to send the Account details email to new users change sendConfirmAccount "0"
to: sendConfirmAccount "1"
To disable the option to send the Account details email to new users change sendConfirmAccount
"1" to: sendConfirmAccount "0"
Upload Confirmation:
To enable the option to send Upload confirmation emails change sendConfirmUpload "0" to:
sendConfirmUpload "1"
To disable the option to send Upload confirmation emails change sendConfirmUpload "1" to:
sendConfirmUpload "0"
Flash Upload Confirmation:
To enable the option to send Flash Upload confirmation emails change sendConfirmFlashUpload "0"
to: sendConfirmFlashUpload "1"
To disable the option to send Flash Upload confirmation emails change sendConfirmFlashUpload "1"
to: sendConfirmFlashUpload "0"
Group Upload Confirmation:
To enable the option to send Upload confirmation emails to Group users change sendToGroupUser
"0" to: sendToGroupUser "1"
To disable the option to send Upload confirmation emails to Group users change sendToGroupUser
"1" to: sendToGroupUser "0"
Download Confirmation:
To enable the option to send Download confirmation emails change sendConfirmDownload "0" to:
sendConfirmDownload "1"
To disable the option to send Download confirmation emails change sendConfirmDownload "1" to:
sendConfirmDownload "0"

266
267
268
269
270
271
272
273
274
275
276
277
278
279
280

18 of 38

281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318

####Email Configuration
Settings###############################################
#Configure the email settings so that the iDC File Manager can
#send automated confirmation emails.
adminMail "[email protected]"
replyMail "[email protected]"
fromAdmin "[email protected]"
#From Email Address
toAdmin "[email protected]"
#Email Address you want to receive email confirmations
sendMailPath "/usr/sbin/sendmail"
#SendMail Path
sendAsHtml "1"
#To enable HTML emails change sendAsHtml "0" to: sendAsHtml "1"
#To disable HTML emails change sendAsHtml "1" to: sendAsHtml "0"
sendConfirmAccount "1"
#To enable the option to send the Account details email to new
#users change sendConfirmAccount "0" to: sendConfirmAccount "1"
#To disable the option to send the Account details email to new

19 of 38

#users change sendConfirmAccount "1" to: sendConfirmAccount "0"

sendConfirmUpload "1"
#To enable the option to send Upload confirmation emails change
#sendConfirmUpload "0" to: sendConfirmUpload "1"
#To disable the option to send Upload confirmation emails change
#sendConfirmUpload "1" to: sendConfirmUpload "0"
sendConfirmFlashUpload "1"
#To enable the option to send Flash Upload confirmation emails change
#sendConfirmFlashUpload "0" to: sendConfirmFlashUpload "1"
#To disable the option to send Flash Upload confirmation emails change
#sendConfirmFlashUpload "1" to: sendConfirmFlashUpload "0"
sendToGroupUser "1"
#To enable the option to send Upload confirmation emails to
#Group users change sendToGroupUser "0" to: sendToGroupUser "1"
#To disable the option to send Upload confirmation emails to
#Group users change sendToGroupUser "1" to: sendToGroupUser "0"
sendConfirmDownload "1"
#To enable the option to send Download confirmation emails change
#sendConfirmDownload "0" to: sendConfirmDownload "1"
#To disable the option to send Download confirmation emails change
#sendConfirmDownload "1" to: sendConfirmDownload "0"
#############################################################
##################

:: Advanced Email Configuration

As Windows servers don not have SendMail installed, please configure the following option:
To enable sendSMTP change sendSMTP "0" to: sendSMTP "1"
To disable sendSMTP change sendSMTP "1" to: sendSMTP "0"
Enter your servers SMTP server address, e.g. mail.yoursite.com / smtp.yoursite.com / IP Address /
Localhost
e.g: mailHostSMTP "smtp.yoursite.com"
If your server has Email Authentication enabled please change EmailAuthenticationON "0" to:
EmailAuthenticationON "1"
Then enter you username in the AuthenticationUsername "" field and your password in the
AuthenticationPassword "" field.
e.g:
AuthenticationUsername "test"
AuthenticationPassword "pass"

320
321
322
323
324

20 of 38

325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346

####Advanced Email
Configuration###############################################
#If you do not have SendMail installed on your server
#please configure the following option:
sendSMTP "0"
#To enable sendSMTP change sendSMTP "0" to: sendSMTP "1"
#To disable sendSMTP change sendSMTP "1" to: sendSMTP "0"
mailHostSMTP "smtp.yoursite.com"
#Enter your servers SMTP server address,
e.g. mail.yoursite.com / smtp.yoursite.com / IP Address / Localhost
EmailAuthenticationON "0"
#To enable Email Authentication change
#EmailAuthenticationON "0" to: EmailAuthenticationON "1"
#To disable Email Authentication change
#EmailAuthenticationON "1" to: EmailAuthenticationON "0"
AuthenticationUsername ""
#Enter your servers Email Authentication username
AuthenticationPassword ""
#Enter your servers Email Authentication password
#############################################################
##################

:: Client Manager - Control Panel Links Configuration

Configure up to 5 custom links you wish to appear in the iDC Client Manager nav bar.
:: File Manager - Menu Links
Change the Contact Us menu link that appears in the File Manager "Help" menu to your sites own
Contact Page.

21 of 38

358
359
360
361
362
363
364

#####File Manager - Menu

Links#################################################
ContactUsLink "http://www.yoursite.com/ContactUs.html"
#Change the Contact Us menu link that appears in the File Manager
#"Help" menu to your sites own Contact Page
#############################################################
##################

:: Session Timeout
You may configure (if required) the session timeout period.
If no mouse or keyboard activity is detected in the specified time frame the user will be logged out.
The Session Timeout is entered in milliseconds. For example a 30 second session timeout would be
entered as 30000.

366
367
368
369
370
371
372
373
374
375

#####Session
Timeout########################################################
###
timeOut "0"
#You may configure (if required) the session timeout period.
#If no mouse or keyboard activity is detected in the specified time frame
#the user will be logged out.
#The Session Timeout is entered in milliseconds. For example a 30 second
#session timeout would be entered as 30000.
#############################################################
##################

22 of 38

:: File Manager Description

To enable File Descriptions change fileDescriptionOn "0" to: fileDescriptionOn "1"
To disable File Descriptions change fileDescriptionOn "1" to: fileDescriptionOn "0"

377
378
379
380
381
382
383
384
385

####File Manager
Description###################################################
fileDescriptionOn "1"
#To enable File Descriptions change
#fileDescriptionOn "0" to: fileDescriptionOn "1"
#To disable File Descriptions change
#fileDescriptionOn "1" to: fileDescriptionOn "0"
#############################################################
##################

:: File Manager Date Stamp

Change the dateFormat to:
dateFormat "US" to date stamp all files using the American Date format (MM-DD-YYYY).
dateFormat "EU" to date stamp all files using the European Date format (DD-MM-YYYY).
dateFormat "" to date stamp all files using the ISO Date format (YYYY-MM-DD).

387
388
389
390
391
392
393

23 of 38

394
395
396
397
398

####File Manager Date

Stamp####################################################
dateFormat "US"
#Change the dateFormat to:
#dateFormat "US"
#to date stamp all files using the American Date format (MM-DD-YYYY).
#dateFormat "EU"
#to date stamp all files using the European Date format (DD-MM-YYYY).
#dateFormat ""
#to date stamp all files using the ISO Date format (YYYY-MM-DD).
#############################################################
##################

:: Auto Transfer Mode

Please enter the file extension you wish to automatically upload in ASCII format.
Those not specified will be uploaded in Binary.

400
401
402
403
404
405
406

#####Auto Transfer
Mode########################################################
autoTxtType "txt, htm, html, cgi, pl, pm"
#Please enter the file extension you wish to be automatically uploaded in
#the ASCII format. Those not specified will be uploaded in Binary.
#############################################################
##################

:: Hidden Files
Specify file extensions you do not want to be shown and they will be automatically hidden from view
when in "User Mode"

24 of 38

408
409
410
411
412
413
414

####Hidden
Files##########################################################
#####
hideFiles "ion,htaccess,gacl"
#Specify file extensions you do not want to be shown and they will be
#automatically hidden from view when in "User Mode".
#############################################################
##################

:: Account Creation Settings

If you hold an OEM of Developer license or have purchased the iDC Account Creation plug-in
separately you need to configure the following iDC Account Creation settings:
Default Account Banned Upload File Formats
Specify the default banned file extensions you would like assigned to each new account.
e.g: defProtection "exe,pl,php,cgi"
Default Account User Rights
Specify the default user rights you would like assigned to each new account.
e.g: defRights "r,u,z,c,v,p,k,t,l,o,a,m,w,n,d"
The Key for the letters assigned to each User right can be seen below:
r = Download
u = Upload
z = Zip
c = CHMOD
v = Preview
p = Pack
k = Unpack
t = Hotlink
l = Notes
o = Copy
a = Rename
m = Move
w = Editor
n = New Folder
d = Delete

25 of 38

New Account Confirmation

To enable the option to send the Account details email to new users change sendNewAccount "0" to:
sendNewAccount "1"
To disable the option to send the Account details email to new users change sendNewAccount "1" to:
sendNewAccount "0"
Automatically Disable New Accounts
To enable the option to automatically disable new accounts pending admin approval change
newAccountDisabled "0" to: newAccountDisabled "1"
To disable the option to automatically disable new accounts pending admin approval change
newAccountDisabled "1" to: newAccountDisabled "0"
Default Disk Quota
Specify the default User account Disk quota in MB.
e.g: defDiskQuota "250"
To specify an Unlimited Disk quota change defDiskQuota "120" to: defDiskQuota ""
Account Notification Subject
Specify the Email subject title for the email that is sent to new users when their account is created.
e.g: AccountNotificationSubject "RE: iDC File Manager Account Created"
Account Notification Subject
Specify the Email subject title for the email that is sent to new users when their account is activated.
e.g: AccountActivatedSubject "RE: iDC File Manager Account Activated"

416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442

26 of 38

443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468

####Default Account Creation

Properties########################################
defProtection "exe,pl,php,cgi"
#Default Account Banned Upload File Formats
defRights "r,u,z,c,v,p,k,t,l,o,a,m,w,n,d"
#Default Account User Rights
#Key:
#r = Download
#u = Upload
#z = Zip
#c = CHMOD
#v = Preview
#p = Pack
#k = Unpack
#t = Hotlink
#l = Notes
#o = Copy
#a = Rename
#m = Move
#w = Editor
#n = New Folder
#d = Delete
sendNewAccount "1"
#To enable the option to send the Account details email to new users change
#sendNewAccount "0" to: sendNewAccount "1"
#To disable the option to send the Account details email to new users change
#sendNewAccount "1" to: sendNewAccount "0"
newAccountDisabled "1"
#To enable the option to automatically disable new accounts pending
#admin approval change newAccountDisabled "0" to: newAccountDisabled "1"
#To disable the option to automatically disable new accounts pending
#admin approval change newAccountDisabled "1" to: newAccountDisabled "0"

27 of 38

defDiskQuota "250"
#Default User account Disk quota in MB.
#To specify an Unlimited Disk quota change defDiskQuota "120"
#to: defDiskQuota ""
AccountNotificationSubject "RE: iDC File Manager Account Created"
#Specify the Email subject title for the email that is sent to
#new users when their account is created.
AccountActivatedSubject "RE: iDC File Manager Account Activated"
#Specify the Email subject title for the email that is sent to
#new users when their account is activated.
#############################################################
##################

:: Login Page - Signup Tab

Enable the iDC Account Creation sign-up tab to appear on the Login Page.
To enable the sign-up tab change ShowSignupOption "hidden" to: ShowSignupOption "visible"
To disable the sign-up tab change ShowSignupOption "visible" to: ShowSignupOption "hidden"

470
471
472
473
474
475
476
477
478
479

####Login Page - Signup

Tab####################################################
ShowSignupOption "visible"
#Enable the iDC Account Creation sign-up tab to appear on the Login Page
#To enable the sign-up tab change
#ShowSignupOption "hidden" to: ShowSignupOption "visible"
#To disable the sign-up tab change
#ShowSignupOption "visible" to: ShowSignupOption "hidden"
#############################################################
##################

:: File Manager - Transfer Mode

28 of 38

Show or Hide the Transfer Mode select menu in iDC File Manager.
To show the Transfer Mode select menu change TransferModeDisplay "hidden" to:
TransferModeDisplay "visible"
To hide the Transfer Mode select menu change TransferModeDisplay "visible" to:
TransferModeDisplay "hidden"

481
482
483
484
485
486
487
488
489
490

####File Manager - Transfer

Mode###############################################
TransferModeDisplay "hidden"
#Show or Hide the Transfer Mode select menu in iDC File Manager
#To show the Transfer Mode select menu change
#TransferModeDisplay "hidden" to: TransferModeDisplay "visible"
#To hide the Transfer Mode select menu change
#TransferModeDisplay "visible" to: TransferModeDisplay "hidden"
#############################################################
##################

:: File Manager - Visual Quota Bar

Show or Hide the User Visual Quota Bar in iDC File Manager.
To show the Visual Quota Bar change quoteBarOn "0" to: quoteBarOn "1"
To hide the Visual Quota Bar change quoteBarOn "1" to: quoteBarOn "0"

492
493
494
495
496
497
498
499

29 of 38

####File Manager - Visual Quota

Bar############################################
quoteBarOn "1"
#Show or Hide the User Visual Quota Bar in iDC File Manager
#To show the Visual Quota Bar change quoteBarOn "0" to: quoteBarOn "1"
#To hide the Visual Quota Bar change quoteBarOn "1" to: quoteBarOn "0"
#############################################################
##################

:: File Manager - Account Expiry

Specify the Number of days in which user accounts should expire after creation.
As an example: autoExpireAfter '5' would force a user account to expire after 5 days.
Please note: autoExpireAfter '0' is the default setting which will give
user accounts an unlimited expiry period (i.e. they will not expire).

501
502
503
504
505
506
507
508
509
510
511

####File Manager - Account

Expiry##############################################
autoExpireAfter '0'
#Specify the Number of days in which user accounts should expire after
#creation.
#As an example: autoExpireAfter '5' would force a user account to expire
#after 5 days.
#Please note: autoExpireAfter '0' is the default setting which will give
#user accounts an unlimited expiry period (i.e. they will not expire).
#############################################################
##################

:: Client Manager - Account Listings Per page

Specify the Number of User Account Listings per page in iDC Client Manager, this value is also used
to control then number of listings displayed per page in the Log Viewer.

30 of 38

513
514
515
516
517
518

####Client Manager - Account Listings Per

page#################################
UsersPerPage "20"
#Specify the Number of User Account Listings per page in iDC Client Manager.
#############################################################
##################

:: Master Setting For Banned File Upload Formats

This setting stops the above file formats being uploaded in either admin or user mode and should
not be modified unless told to do so by iDC Support.

520
521
522
523
524
525
526

#####Master Setting For Banned File Upload

Formats#############################
disabledFiles "exe,pl,php,cgi,php5,php4,js,java,dll"
#This setting stops the above file formats being uploaded in either admin
#or user mode and should not be modified unless told to do so by iDC Support.
#############################################################
##################

:: End Of Configuration

31 of 38

You have now concluded the configuration of the External Configuration file.
Do not modify Lines 538 - 625 unless told to do so by iDC Support.
Step 3
After you have completed configuring the External Configuration file you can then return to the
directory called "iDC File Manager" which you earlier extracted from the zip file.
When you open this directory you will be presented with 2 sub-directories:

Contents of this folder to be uploaded into httpdocs or public_html or wwwroot

Contents to be uploaded into cgi-bin folder

Upload the folder called "FileManager" contained within the directory named "Contents to be
uploaded into cgi-bin folder" into your servers cgi-bin folder.
Please ensure that you do not simply upload the directory "Contents to be uploaded into cgi-bin
folder" into the cgi-bin folder, just its contents.
When the upload of the folder named "FileManager" and all of its contents has been successfully
uploaded into your servers cgi-bin folder you can then move on to step 4.
Step 4
So that the File Manager can read / write and execute certain files and folders, you will need to
access the IIS System Manager and set the Internet Guest Account permissions to "Allow" for the
read write and execute permissions for the following (the location of these files may vary, in your
setup so you need to adjust accordingly):
[Directory] /cgi-bin
[Directory] /cgi-bin/FileManager
[Directory] /cgi-bin/FileManager/status
[Directory] /cgi-bin/FileManager/session
[File] /cgi-bin/FileManager/Account.pm
[File] /cgi-bin/FileManager/AccountCreation.pl (Please note this file is only included in the OEM and
Developer versions)
[File] /cgi-bin/FileManager/CleanUp.pl
[File] /cgi-bin/FileManager/ClientManager.pl
[File] /cgi-bin/FileManager/Configuration.pl
[File] /cgi-bin/FileManager/IDC.pm
[File] /cgi-bin/FileManager/Import.pl
[File] /cgi-bin/FileManager/ImportNotes.pl
[File] /cgi-bin/FileManager/logActivity.txt
[File] /cgi-bin/FileManager/Manager.pl
[File] /cgi-bin/FileManager/Manager.pm
[File] /cgi-bin/FileManager/RunOnce.pl

32 of 38

[File] /cgi-bin/FileManager/Session.pm
[File] /cgi-bin/FileManager/Skins.ini
[File] /cgi-bin/FileManager/uploader.pl
[Directory] /FileManager/Languages (including all contents)
[Directory] /FileManager/Shared (including all contents)
[Directory] /FileManager/Templates (including all contents)
[Directory] /FileManager/FileManagerData (including all contents)
[Directory] /FileManager/Clients (including all contents)
So that the File Manager also has permission to delete files and folders you may also need to set the
Internet Guest Account "advanced" permissions to Allow: "Delete Subfolders and Files" and "Delete".
Step 5
The final step is to finalise the configuration by running the "RunOnce.pl" file.
This script is designed to connect to your newly created MySQL database and setup the 7 database
tables used by iDC File Manager to store the user account information and other data.
It also sets up the default Admin Account and Admin Group.
To run the script you need to open up your browser and enter the url to the main File Manager folder
located in your servers cgi-bin + RunOnce.pl
e.g:

http://www.yoursite.com/cgi-bin/FileManager/RunOnce.pl

Step 6
After you have successfully run the "RunOnce.pl" file, the File Manager has now been fully setup and
is ready to use.
However to fully conclude the installation, for security reasons you need to remove some of the files
from your server used during the installation process.
Please access your server and access the main "/cgi-bin/FileManager" folder and remove the
following files:
/cgi-bin/FileManager/CleanUp.pl
/cgi-bin/FileManager/Import.pl
/cgi-bin/FileManager/ImportNotes.pl

33 of 38

/cgi-bin/FileManager/RunOnce.pl
Installation Complete
Congratulations, your copy of iDC File Manager, has now been installed!
To access the File Manager you need to open up your browser and enter the url to the main File
Manager folder located in your servers cgi-bin + Manager.pl
e.g:

http://www.yoursite.com/cgi-bin/FileManager/Manager.pl

This is the access url you will need to enter every time you want to access the File Manager.
By default the main Admin Username is:

admin

By default the main Admin Password is:

admin

34 of 38

Tip: For security reasons please change the default username and password as soon as possible!
Common post-installation error messages
If when you attempt to run the script for the first time it returns an error, it is likely to be one of the
following common error messages:
1) Can't locate Archive/Tar.pm in @INC (@INC contains...
2) Can't locate Archive/Zip.pm in @INC (@INC contains...
3) Can't locate Compress/Zlib.pm in @INC (@INC contains...
4) Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
5) Access denied for user: 'YOUR USERNAME HERE' (Using password: YES)
6) Can't load Configuration file - No such file or directory at...
7) Can't locate Account.pm in @INC (@INC contains: C:/Perl/lib...
If you error is not listed here, please visit the: Knowledge Base - Common Error Messages section for
further information.
The Knowledge Base also includes solutions and tips to other commonly asked questions.

Copyright i Dot Communications

iDC File Manager v1.4 to v1.5 - Upgrade Guide

If you are planning to upgrade your copy of iDC File Manager version 1.4 for iDC File Manager
version 1.5 (Lite, Pro, Pro Plus or OEM editions), please follow the following advice.
You can purchase your upgrade version Here.
Prior to purchasing please review the "Which Version?" guide to ensure the edition you choose fits
the requirements of your organization.
After you have successfully purchased your copy of iDC File Manager - Upgrade version 1.5 you will
receive an order confirmation email
detailing your account login details and the download location of the File Manager source code.
Important:
Prior to installing the upgrade you must first take a full backup of your copy of iDC File Manager
version 1.4, this includes:
[Folder] /cgi-bin/FileManager
[Folder] /FileManagerData
[Folder] /Clients
and all of the files and folders contained within these directories. Please note the paths to these
folders may differ to your installation and need to be modified accordingly.
It is then advisable to remove:
[Folder] /cgi-bin/FileManager
[Folder] /FileManagerData

35 of 38

from your server and all supporting files and folders contained within these folder, to avoid confusion
when the new version is installed.
DO NOT REMOVE the Folder: "/Clients" from the server!
Please note the path to the "Clients" folder may differ to your installation and need to be modified
accordingly.
Step1: Starting the Upgrade Installation
To begin the installation of iDC File Manager please refer to the Manual installation guide for your
specific server.
When the installation is complete and you have checked that everything is functioning correctly you
can then move on to Step 2.
Step 2: Importing your existing user data
iDC File Manager version 1.4 used a flat file csv database called "users.txt" (originally located in the
/cgi-bin/FileManager directory) to store the user account details, where as iDC File Manager version
1.5 uses a MySQL database. As a result, you will need to import the data stored in the users.txt file
into the new format.
Please access your backup of iDC File Manager version 1.4. and locate the users.txt file. This file can
then be uploaded into the new installation of iDC File Manager version 1.5 /cgi-bin/FileManager
directory.
When this is complete open up your browser and enter the url to the main File Manager folder
located in your servers cgi-bin + Import.pl
e.g.

http://www.yoursite.com/cgi-bin/FileManager/Import.pl

This script will then read the data stored in the users.txt file, convert it into the new format and then
import it into the MySQL database.
Tip: If the Import.pl file cannot be found in the /cgi-bin/FileManager directory please upload it from
the main Zip file for you copy of iDC File Manager.
When the user data has been successfully imported you can then move on to Step 3.
Step 3: Importing the main "Clients" folder
The final step is to move the main "Clients" folder (used in version 1.4 to store the user account
folders) into the iDC File Manager version 1.5 /FileManager/ directory.
This is the same location you specified in lines 102 - 111 of the Configuration.pl script.
e.g.

102

36 of 38

103
104
105
106
107
108
109
110
111

####Main Clients
Directory#####################################################
clientroot "/home/yoursite/public_html/FileManager/Clients"
#Change the path to the "Main Clients Directory" to your servers path to the
#main public root directory + the sub-folder of the File Manager folder which
#will hold all your Clients folders.
#For example:
#e.g.clientroot "/home/yoursite/public_html/FileManager/Clients"
#############################################################
##################

When the Clients folder has been successfully moved you have then completed your upgrade to iDC
File Manager version 1.5
FREE Upgrade Service
If you are experiencing any problems installing or upgrading your copy of iDC File Manager, why not
request that our expert technicians
remotely access your server to setup and install iDC File Manager on your behalf.
For further infortmation please Click Here.

Copyright i Dot Communications

Can't load Configuration file - No such file or directory at

C:/Inetpub/wwwroot/cgi-bin/FileManager/IDC.pm line 89.
If you are attempting to install iDC File Manager on a Windows server and receive the error message:
Software Error
Can't load Configuration file - No such file or directory at C:/Inetpub/wwwroot/cgibin/FileManager/IDC.pm line 89.
and you have checked that the Configuration.pl file is correctly setup in the /cgi-bin/FileManager
directory and all of the permissions are set to allow, you may need to manually enter the path to the
Configuration.pl file in the following scripts:
RunOnce.pl
Manager.pl
ClientManager.pl
AccountCreation.pl (if included in your copy of iDC File Manager)
Open each of the above scripts in turn in either a perl or text editor and search for the following
string:

37 of 38

config=>'Configuration.pl'

In each of the scripts you then need to enter the full path to the Configuration.pl file e.g:

config=>'C:/Inetpub/wwwroot/cgi-bin/FileManager/Configuration.pl'

Then save and re-upload each file.

This will then allow the server to correctly locate the Configuration.pl script.

Copyright i Dot Communications

Version 1.4 Manual Installation Guide / User Manual

The original manual installation guides for version 1.4 can be downloaded here.
The original user guide for version 1.4 can be downloaded here.
Copyright i Dot Communications

38 of 38