Known Problems — K2 Dashboard


This section includes the following:

Known Problems — K2 Services

 

Known Problems — Indexes

 

Known Problems — K2 Reporting

 

Known Problems — Security

 

Known Problems — Indexing and Viewing

 

Known Problems — Locales and Character Sets

 

Known Problems — General

 


Known Problems — K2 Services

Setting the bind IP for a K2 Spider Service requires a restart of the Administration Server

Before you can bind a K2 Spider Service to a particular IP address, you must stop the K2 Spider Service. After setting up the Bind IP value in the Edit Properties action page, you must restart k2admin manually. This in turn restarts the K2 Spider Service. (100886)

Non-unique port number assignment

A single Verity K2 process must be the sole user of the port number assigned to that process. Care should be taken to ensure that only unused port numbers are assigned to K2 processes. In the event that the same port is assigned to more than one process, a problem will be reported under NT/Windows 2000. (74118)

The K2 Dashboard does not accurately report the state of a Profile Net

If K2 Profiler does not load a Profile Net successfully, the Manage Profile Services and Nets action page in the K2 Dashboard shows the Profile Net state as online when it is actually offline. The K2 Dashboard displays the configured state of the Profile Net, not the actual state. (83629)

K2 Administration as a Windows service cannot connect to a mapped drive or an Exchange server

If K2 Administration is running as a Windows service, there are two ways to specify the property of the service:

Log on with a local system account. In this scenario, you enable the Local System Account radio button in the Logon tab, and select the check box indicating the service can interact with the desktop. (This tab is accessed by right-clicking a service in the Windows Services dialog and choosing Properties.) This is the default.

 

Run the service with a specific user account.

 

If you want to configure an Exchange collection or index a collection on a mapped drive, you must run the service with a specified user account.


Known Problems — Indexes

The K2 Dashboard allows partition merging of online parametric indexes

In the K2 Dashboard, you can create an Update_Parametric_Index user-defined job. The associated dialog box offers you the Merge Partitions check box, even when the parametric index is online. Select this check box only when the parametric index is offline. (101380)

Topic set aliases with symbols require non-default paths

When you add a topic set in the K2 Dashboard and you identify an alias that contains characters other than

alphanumerics

 

the hyphen (-)

 

the underscore (_)

 

you must specify a non-default path. This path must contain only the characters listed above. Otherwise, the K2 Dashboard displays the "Failed to create the index. (-6220)" error message. (100846)

Adding a collection stored outside the default path requires ASCII characters

When you add a collection stored outside the default directory

install_dir\Verity\k2_6\data\colls ,

the path you enter on the Add Index action page must contain only ASCII characters. (90779)

Swapped collection path must include all characters

On UNIX and Windows, when you "swap" collections through a Swap_Collection user-defined job type, you enter a value in the Path of Collection to Swap In field. However, the path you enter must exactly match the path shown on the collection detail page. For example, if the collection detail page path includes a %20 (to designate a blank space), you must enter this in the Collection to Swap In field.

If the collection has not been added or imported using the K2 Dashboard and therein has no detail page information, input the path as it appears on the native operating system. (89502, 89424)

Cannot index collections with long aliases

If you try to create a collection through rcadmin or the K2 Dashboard whose alias is very long, the following error message appears:

“Failed to create the local job INI file. (-6046)”

Non-Latin aliases for indexes stored in the default data directory must not exceed 11 characters in length. (85360) (85288)

The K2 Dashboard cannot add and attach collection map files

You cannot add and attach a collection map file (which links collections together) through the K2 Dashboard. (74372)

Workaround: Use rcadmin with collset and indexattach commands. For more information, see the Verity rcadmin Guide.


Known Problems — K2 Reporting

Documents viewed through parametric index applications are not reported

Documents are not reported in the Top Documents Viewed report when

you view documents through a parametric index application, and

 

you filter the report to include data from these parametric indexes

 

In this case, to view an accurate report, you must filter the report to include data from the collection referenced by the parametric index. (90324)

Limitations summary

Also of note are the following K2 Reporting scenarios, documented in the Verity K2 Dashboard Administrator Guide and the Verity K2 Reporting API Developer Note:

In the Viewing Options tab, if you filter by Service and include a K2 Broker, but also include any K2 Servers/Brokers managed by the included Broker, reports will show multiple query counts for a single user query.

 

If you filter by Index , the data included in reports can depend on whether the original query searched multiple indexes. Queries made against any of the selected indexes, in combination with non-selected indexes, will not be included in the reports.

 

Report data is gathered from query logs through a user-defined job. If the job runs before the most recent query log is saved on disk, the report information will not reflect the most recent log.

 

The number of queries included in the Search Performance Report reflects the number of queries processed by the K2 engine. This may not match the number of queries included in other reports, which reflect user queries only.

 

Viewing PDF files can sometimes cause multiple file view counts to be logged and included in reports.

 

If more than one category tree is available for browsing through a collection, K2 Reporting records multiple hits when one tree is used to refine the search of another.

 


Known Problems — Security

Managing administration security with multiple K2 Ticket Servers

You can use the Manage Administration Security action to attach or detach a K2 Ticket Server to or from all Administration Servers in your K2 system. However, if you attach or detach more than one K2 Ticket Server, K2 does not authenticate to each Ticket Server in the proper order. Error messages appear, describing an invalid user name and password. (99329, 101422)

Workaround: Sign out of the K2 Dashboard, and then sign in. You may find the K2 Dashboard pages display the old K2 Ticket Server configuration for a short time until a background process is updated.

Managing administration security from the home page results in an error when no K2 Ticket Servers exist

If you click the "Secure all Administration Servers with a K2 Ticket Server" link on the K2 Dashboard home page, but no K2 Ticket Servers exist in your system, a "K2 Dashboard Fatal Error" page appears. (101541)

Workaround:Before managing administration security, create a K2 Ticket Server.

Collections and Profile Nets that share aliases also share assigned security

You can use the Assign Security action in the K2 Dashboard to set up index-level security for collections and Profile Nets. This limits the Verity indexes a user can search by controlling access based on a user’s identity. However, if a collection and Profile Net share the same alias, they also share assigned security groups. (97072)

Assigning security requires a full restart

When you assign security to a collection or Profile Net, you must perform a full restart on the associated K2 Server. The K2 Dashboard does not prompt you for a restart when you use the Assign Security action page. (100998)

Test Credentials is available even when pre-authentication is enabled

When you configure a K2 Ticket Server to use pre-authentication, credentials are trusted and not authenticated by the gateway (the user ID is verified against the user’s group membership). However, the Test Credentials action remains available for that K2 Ticket Server in the K2 Dashboard. When pre-authentication is enabled, K2 only requires a valid user name to access repositories. Therefore, any password you enter on the Test Credentials page will return success. (100620)

All administrators have the same access rights

Although K2 allows multiple administrators to be named, they all have complete and equal administrative access to the K2 system. There is currently no mechanism for dividing tasks or access rights to different administrators and enforcing that through K2.

The K2 Dashboard does not allow you to specify non-starting point secure URLs for an HTTP gateway collection

If an HTTP gateway collection contains secure documents, you can use the K2 Dashboard to specify credentials for the associated URLs, but only if they are indexing starting points. (72559)


Known Problems — Indexing and Viewing

Test Search does not display all results

On the Test Search action page, you can select All as the value in the Maximum Results Returned field so that the K2 Dashboard displays all search results. However, you are only able to view up to page 10, which shows results 91 to 100. If you select other values in the Maximum Results Returned field, such as 200 , 2000 , 5000 , and so on, you are able to view these results. (101490, 101484)

Viewing documents with long VdkVgwKeys requires Field Size adjustment

By default, K2 returns the first 2048 characters from a collection field. This value is too low for documents with long VdkVgwKeys and can prevent viewing. (101458)

Workaround: In the K2 Dashboard, click the Edit Properties action for a particular K2 Server. On the VDK tab, the Field Size text box is null by default. Despite this null value, the default is indeed 2048 bytes. Enter a greater value, click Modify, and perform a full restart on the K2 Server.

UNC provides the most robust selection of network file system content on Windows

When indexing network-mounted drives on Windows platforms, it is recommended you use UNC paths (\\machine\path\ ). This is preferable to mapped drive letters, which are also supported by K2, but which may not map correctly on subsequent restarts when the collection is refreshed or when viewing occurs. (90320)

Errors indexing or viewing UNC paths in Windows

On Windows platforms, you may experience indexing or viewing problems with documents indexed by a UNC path if you fail to set up a user account to run the K2 Administration Server Windows service. This occurs because K2 Administration starts all other K2 processes, which inherit the login (generally needed to access network drives).

The following error message may be found in your K2 Spider, K2 Server, or K2 Index Server logs:

Error E3-0422 (VDK ): Could not find file \\mondo\d\customers\ facts\info.html

The user account can be set up during the initial K2 installation, or set/changed after installation, using the Windows Services setup. To change the user account for a K2 Administration Server:

1. Open the Windows Services window (e.g. on Windows 2000/2003, right-click My Computer and select Manage | Services and Applications | Services).

2. Locate and double-click the Verity K2 6.0 Administration Server service.

3. Click the Log On tab.

4. Enter a user account and password under which K2 processes can run.

 

   
  Note   When you change the password for the account, you must update the password on this tab. The K2 Administration Server only starts (when the machine is restarted) once you update this password.

Depending on domain controller group policy settings, the password for the user account may be reset. As a result, the Verity K2 Administration Server may report logon failures when restarted. To avoid this behavior, contact your Windows Administrator to change group policy settings.
   

 

5. Click OK.

6. Restart the Verity K2 Administration service.

Verity does not support unattended access to UNC paths/network drives that require a separate login. To access these, you must log in and mount the network drive before attempting to have K2 access this content. (90316) (90318)

Indexing tab displays an incorrect default value

In the indexing job properties, the Indexing tab displays the Maximum Memory to Allocate field. This field defines the approximate maximum memory used for each indexing thread. VDK ignores the displayed default value of 8192 KB. The minimum value for this field is 32 MB. The maximum is 15/16 of either RAM or the process limit.

 

 
Note   You set the number of indexing threads in the General tab.
 

 

A host cannot run more than 15 indexing jobs at one time

When 15 indexing jobs are running at once on a host, and you try to start a 16th job (either manually through the Start/Stop action, or by scheduling it in the Scheduling tab), the job does not start. The K2 Dashboard prompts you with a warning that indicates there are too many indexers. (82695)

Indexing with certificates and keys

If you need to index with certificate and key files, you need to use the Edit Style Files portion of the StyleSet Editor and import those files into the collection’s style directory. You must name the files certfile.dat and keyfile.dat ahead of time, because you cannot rename files when you import them and the K2 Dashboard indexer looks for those file names explicitly. With those files in the collection’s style directory, your indexing jobs will automatically find them and use them equivalent to the -certfile and -keyfile options for the K2 Spider command-line tool.

Indexing job properties do not show supported MIME types

In the indexing job properties, the Crawling and Indexing tabs show text boxes where you can specify MIME types to include or exclude from the collection. However, the user interface does not prompt you with available MIME types. You must enter the MIME type, rather than selecting it. (73047)

Workaround: Check the style.uni file for supported MIME types.

Multibyte starting points require matching K2 Dashboard and host character sets

If an indexing job specifies a multibyte starting point, the character set of the K2 Dashboard must match the operating system character set of the host on which the collection is indexed.


Known Problems — Locales and Character Sets

The K2 Dashboard does not recognize newly installed locales

On UNIX, if K2 services are started and you install Verity Locales, the K2 Dashboard does not recognize these locales. You cannot add a collection that uses one of the newly installed locales. (90638)

Workaround: Run the command rcadmin -update on the host.

The K2 Dashboard shows uninstalled locales

If you uninstall a Verity locale, it is still available in the Add Index action page when you create a collection in the K2 Dashboard. (73058)

Workaround: Restart k2admin to update the K2 Dashboard with locale changes.


Known Problems — General

When a K2 system spans time zones, editing a scheduled job can require re-clicking the "Schedule this job" check box

When your K2 system is configured as follows, a conflict can exist when you edit a job:

the Master Administration Server exists in one time zone, such as Denver (Mountain Time), and

 

a local Administration Server exists in another time zone, later than that of the master, such as San Francisco (Pacific Time), and

 

an indexing or user-defined job is scheduled to run once on the local machine

 

Editing job properties from the master machine prior to the scheduled start time can affect the job scheduling. For example, consider

it is 10 a.m. in Denver (master machine)

 

it is 9 a.m. in San Francisco (local machine)

 

a job is scheduled to run once at 9:30 a.m. (Pacific Time) today on the local machine in San Francisco

 

If you edit the job properties from the master machine at 9:31 a.m. (Mountain), K2 does not account for the time difference and interprets this time as after the job has run. If you edit properties between 9:31 a.m. (Mountain) and the scheduled run time of 10:30 a.m. (Mountain) /9:30 a.m. (Pacific), you must click the Schedule this job check box before you click Modify. Otherwise, the job reverts to a manual start. (93516)

Error page at K2 Dashboard sign-in

When you sign into the K2 Dashboard, it can display an error page with the following message:

java.lang.NoClassDefFoundError

Workaround: Close your browser and then open a new K2 Dashboard session. (100843)

In Netscape, Modify buttons require two mouse clicks

When you view the K2 Dashboard using Netscape 7.2, some action pages require you to click the Modify button twice: once to set focus on the button, and again to select the button. This is necessary, for example, on the Manage K2 Broker/K2 Server Security action page for a K2 Ticket Server, as well as the Manage Collection Relationships action page for a topic set. (100999)

There is no concurrency control for K2 Dashboard users updating the same K2 component

Although you can identify multiple administrators in the K2 Dashboard, it does not protect against simultaneous updates of the same K2 system components. For example, if multiple administrators work on the same service at the same time and input contradictory information, some changes will be lost.

Workaround: Verity recommends that you define a primary administrator for different K2 components within your system to avoid such simultaneous updates.

With Microsoft Terminal Services, you cannot use the StyleSet Editor for Documentum, Exchange, and Lotus Notes gateways

If you

attempt to launch the StyleSet Editor from the K2 Dashboard to create or modify a style set for the Documentum, Exchange, or Lotus Notes gateways,

 

and you

use Microsoft Terminal Services to access the computer,

 

the actual StyleSet Editor session is launched on the computer’s main console, not the Terminal Services window.

Workaround: Set up direct access to the computer where the StyleSet Editor is installed, or use an alternative remote console application that shows the actual main console.

JavaScript and Java support must be enabled

JavaScript and Java support need to be enabled in both Internet Explorer and Netscape Navigator.