| |
| 1.Q. |
What are the basic requirements to run DocKIT
application? |
| 1.A. |
The following are the basic requirements to run DocKIT application
-
The currently logged on user must belong to the local administrators group.
-
Ensure the following services are running
 |
IIS Admin Service
|
|
World Wide Web Publishing Service
|
At least one site (virtual server) should be in extended state.
The currently logged on user must have access rights in SQL Server.
|
|
Top
|
| 2.Q. |
Why do I get "Login failed for user '<User name>'
"? |
| 2.A. |
This message appears when the currently logged on user does not have 'Grant
Access' in SQL Server Security settings. This possibility may exist if the SQL
Server is shared across other internal applications or for explicit security.
To verify whether the user has 'Grant Access'
permission, follow these steps:
Click Start -> Programs -> Microsoft SQL Server -> Enterprise Manager
In the Enterprise manager
-
Expand Microsoft SQL Servers - > SQL Server Group -> (local) (Windows NT)
-> Security
-
Double click on the Logins icon to show the users in the right pane.
-
Right click on the selected user and click properties.
-
In the General tab, under authentication select the 'Grant access' option.
-
Click the OK button.
|
|
Top
|
| 3.Q. |
Can I connect to a remote SharePoint server through
DocKIT? |
| 3.A. |
No. DocKIT has to be installed on a Windows Server 2003 running SPS
2003 / WSS v2.0. DocKIT can
connect to the Sites, Areas and Libraries in the local SPS server,
Sites & Libraries in WSS.
|
|
Top
|
| 4.Q. |
Can I copy documents directly under an SPS Site/Area or
WSS Site? |
| 4.A. |
No. Documents can be copied to document libraries folder structure only.
|
|
Top
|
|
5.Q.
|
Can I import documents and folders to multiple libraries?
|
| 5.A. |
Yes. DocKIT allows you to import folders/documents to multiple libraries in a
single import session.
|
|
Top
|
|
6.Q.
|
How does DocKIT associate the external metadata to the documents
that are imported?
|
|
6.A.
|
The field names that are specified in the HEADER of the metadata file, if not
present in the target library, will be created automatically by DocKIT and will
be assigned to the respective columns in libraries during migration.
|
|
Top
|
|
7.Q.
|
What types of columns cannot be included in the
metadata?
|
| 7.A. |
DocKIT will not update System defined, Read-only and Computed columns in a
document / picture library. To view the list of system
fields in SharePoint, refer
Field Tables for Default Lists
|
|
Top
|
|
8.Q.
|
What is the required format of data in the CSV (Comma Separated
Value) file in which metadata is to be stored?
|
| 8.A. |
-
The first row of the CSV file should contain the Field Names as headers
separated by comma (,).
-
The first field should be named as Path. Path field should be followed by other
field names separated by comma, in whose names the document properties will be
created in the SPS.
-
The first field named Path is mandatory. This field will not be carried forward
as a metadata into SharePoint Server.
-
The first column of all the rows should contain the path of the file e.g.,
C:\Documentation\Brochures.doc (or) \\FileServer\Documentation\Brochures.doc.
-
Each field should be enclosed within double quotes ("").
-
The Year, Month and Day parts in a date field is required to be within double
quotes and separated by a slash (/) only e.g., "11/23/2000".
-
For local/mapped drives used as source, ensure the 'Path' field has the
corresponding local/mapped drive path (e.g.,
Z:\Projects\Brochures.doc).
-
When network shares are used as source, ensure the 'Path' field has the
corresponding UNC path (e.g.,\\DevServer\Documents\Support.xls).
Sample format of a CSV File:
"Path","Modified Date","Author Name","Post"
Example 1 - "C:\Management\Brochures.doc","11/06/2002","John Doe","CEO"
Example 2 - "C:\Directors\Proposals.xls","16/08/2002","Jane Doe","Director"
Example 3 - "C:\Directors\Demo.ppt","09/09/2002","David","Operations Manager"
|
|
Top
|
|
9.Q.
|
How does DocKIT associate the Date fields of the source documents
that are migrated to SharePoint Portal Server or Windows SharePoint Services?
|
|
9.A.
|
DocKIT assigns the source 'Created Date' and 'Last
Modified Date' fields to 'Created' and 'Modified' system columns respectively.
The currently logged-on-user account will be assigned as the user who created
(Created by) and last modified (Last modified by) the document.
When uploading
documents as a new version, the Created Date field will be the very
first version of the document and last modified date value can be assigned to
the system SharePoint column (Modified).
Please note the following additional information
about assigning date fields:
|
If the 'Created Date' and 'Last Modified Date' fields are unchecked, the values
will be set to the date & time at the time of import.
|
|
While importing 'Last Modified Date' value alone to SharePoint system column,
the date & time at the time of import will be set to 'Created'
column. |
|
|
Top
|
|
10.Q.
|
How does DocKIT associate the current NTFS permissions
in my source folders to SPS / WSS permissions for the Site?
|
|
10.A.
|
DocKIT takes the NTFS security permissions of the folders/files and maps it to a
default set of site groups in the destination site. The user can customize the
NTFS permission to site group mapping, which will be applied to all
users/groups in the list. For each NTFS permissions set for user/group, the
user/group will be added to the appropriate site group. In other words, each
user/group will be added to multiple site groups based on the
NTFS-> Site
Group mapping information.
Alternately, the user running DocKIT can assign the relevant
site groups for each user/group listed in the source folders/files.
|
|
Top
|
|
11.Q.
|
How does DocKIT associate the current NTFS permissions
in my source folders to SPS permissions for the Area?
|
|
11.A.
|
DocKIT takes the NTFS security permissions of the folders/files and maps it to a
default set of ‘rights’ in the destination area. The user can customize the
NTFS permission to Area rights mapping, which will be applied to all
users/groups in the list. For each NTFS permissions set for user/group, the
user/group will be assigned the respective area rights. In other words, each
user/group will be assigned the maximum area/library rights, based on the
NTFS-> Area rights mapping information.
Alternately, the user running DocKIT can assign the relevant
rights for each user/group listed in the source folders/files.
Note: The rights assigned to the user/group will be uniformly applicable
to all destination area/libraries in the current import session.
|
|
Top
|
| 12.Q. |
How does DocKIT associate the current NTFS permissions
in my source folders to SPS / WSS permissions for the Library? |
| 12.A. |
DocKIT takes the NTFS security permissions of the folders/files and maps it to a
default set of ‘rights’ in the destination library. The user can customize the
NTFS permission to Library rights mapping, which will be applied to all
users/groups in the list. For each NTFS permissions set for user/group, the
user/group will be assigned the respective library rights. In other words, each
user/group will be assigned the maximum library rights, based on the
NTFS->
Library rights mapping information.
Alternately, the user running DocKIT can assign the relevant
rights for each user/group listed in the source folders/files.
Note: The rights assigned to the user/group will be uniformly applicable
to all destination area/libraries in the current import session.
|
|
Top
|
| 13.Q. |
How NTFS security mapping is applied if I import
folders/files to multiple libraries? |
| 13.A. |
The NTFS permissions to Library rights mapping will be applied to all libraries
in the current import session. The library rights assigned to the user/group
will be uniformly applicable to all destination libraries in the current
import. If you wish to assign different rights for each destination library,
you have to import folders/file one library at a time.
|
|
Top
|
| 14.Q. |
What roles are set for the ‘Site’ created through
DocKIT? |
| 14.A. |
The currently logged on user during the time of creation of Site will be
assigned to the Administrator site group.
|
|
Top
|
| 15.Q. |
How does DocKIT handle document versions? |
| 15.A. |
DocKIT provides options to handle the condition where a document with the same
name, as the one being imported, already exists in SharePoint. You can
specify whether to overwrite the existing file in
SharePoint, retain existing versions and
update the latest version or to leave the file as-is in SharePoint.
By selecting the 'Overwrite' option, DocKIT deletes the file in SharePoint
(along with its version history) and imports the new file.
By selecting the 'Create New Version' option, DocKIT retains existing
document versions in SharePoint and updates the latest
version only.
|
|
Top
|
| 16.Q. |
What are the precautions to take while migrating
documents to SPS / WSS using DocKIT? |
| 16.A. |
|
Ensure the network traffic is minimal while copying files from remote shares on
the network. |
|
Avoid running any other applications in the background during the migration
process. |
|
Temporarily disable any anti-virus software that may be running during the
migration operation. |
|
We strongly recommend a good hardware configuration. |
|
Run the full import process in DocKIT during off-peak usage of
SPS/WSS (if it's
already in use). |
|
|
Top
|
| 17.Q. |
Additional information in order to troubleshoot the
problem |
| 17.A. |
|
DocKIT version that you are evaluating or you have registered with us. (Version
information could be found in the "About" Screen and in the 'Help'). |
|
Additional services or resource consuming processes/applications (like
anti-virus) running in the background on DocKIT installed machine. |
|
Hardware configuration of DocKIT installed machine. |
|
'Service Pack' version is SharePoint Portal Server / Windows running currently. |
|
Send us, both "DocKIT Activity Log" and "Error Log", available in the
installation path of DocKIT (e.g., C:\Program
Files\DocKIT2003\Log\DocKITErrorLog.txt). |
|
|
Top
|
| 18.Q. |
The application error log file DocKITErrorLog.txt is
gradually increasing in size. Can I delete it? |
| 18.A. |
Yes, you may delete this error log file. DocKIT generates an error log file in
the Log folder in the application path (C:\Program Files\DocKIT2003). The
error log file tends to increase 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.
|
|
Top
|
