Please note the following System Requirements for installing ARKIIS:
Disk space: 20 MB free disk space
Others: Microsoft Data Access Components (MDAC) v2.1/2.5/2.6/2.8 only.
This message will appear if the server you are trying to connect is not running IIS 4.0 or above. Please refer the question above for more information.
This message will appear, if the server you are trying to connect might have been switched off or it may not be available in the network.
When you try to administer IIS on a computer running Windows 2000 IIS 5.x/ Windows 2003 IIS 6.0 from a computer running Windows NT 4.0 with IIS 4.0 or vice versa, this error message will occur due to the metabase schema difference.
You can connect to the remote IIS Server using the Connect feature in ARKIIS.
ARKIIS connects to the IIS machine using the currently logged on user context. ARKIIS expects the currently logged on user to have administrative privileges in the target IIS Server to connect and generate the reports.
Using ARKIIS Schedule feature, a scheduled task can be created and made to run in a user context which has administrative privileges on the remote machine. You may print/export the output to a CSV/MDB/HTML file.
Yes, you may delete this error log file.
ARKIIS generates an error log file in the application path “C:\Program Files\ARKIIS\Log” The error log file tends to become large in size over a period of time especially if the application meets with frequent error conditions. The application does an “append” to the error log each time it runs. This is required for diagnostic purposes during trouble shooting. You may delete the error log file periodically.
The message will appear when FTP service is not installed/running in the specified IIS server.
The message will appear when you are trying to connect to IIS server whose IIS version is other than 6.0. The selected report is applicable for IIS 6.0 only.
The Log Analysis tool in ARKIIS parses the log files under the specified log file directory of the Web sites and FTP sites. This tool requires log files to be available and logging to be enabled to generate log files. The Enable Logging option and the Log file directory for each Web and FTP site can be modified in property sheet of the Web / FTP site through IIS MMC.
For example, default logfile path is “C:\WINDOWS\system32\Logfiles”
I found Dockit product through SharePoint.com and found it extremely useful. We used Dockit to import hundreds of documents into SPS. Users were in desperate need for them but refused to take the time to upload them. Dockit saved us the upload time, and more importantly, made the information available in a timely fashion. Small issues were worked out quickly by a capable and dedicated customer support staff.
We find that Dockit is an extremely valuable tool for migrating intranet content to SharePoint Portal Server. When you are faced a large number of documents to migrate each of which has to be populated with metadata, Dockit reduces considerably the effort involved in publishing information. Typically it reduces the time a user has to spend per document by 75%, by enabling documents to be published in batch mode rather than real time through the standard SPS interface.
The Dockit application proved extremely useful for importing large numbers of files and folders quickly and easily into SharePoint. Previously, we were having to import files individually, but through using Dockit we were able to deal with huge directories in a fraction of the time that it would have taken. An excellent tool, really glad we found it.
We used Dockit to import over a thousand engineering documents, preserving the folder structure. It was simple to use and saved us a lot of time.