K2.net 2003 support on Vista, Server 2008, Windows 7, Server 2008 R2
Hotfix 10: Memory optimization and management
An Archive Buffer Overflow error occurs when redirecting a Worklist item through K2ROM API
Netstat (Netstat.exe) is a command-line tool that displays TCP/IP protocol statistics and active connections to and from your computer. Netstat also provides an option to display the number of bytes sent and received, as well as network packets dropped (if any). You can use this tool to quickly verify the number of connections opened on a certain port.
This hotfix addresses several issues that may occur when using K2.net 2003 SP4. These include: memory usage, a Remoting object timeout exception, an OpenProcessInstance API call error, a Socket connection TIME_WAIT state, lost Escalations and an Error Repairing problem.
This example will demonstrate how to combine task lists created in Microsoft Office SharePoint Server 2007 (MOSS) with the standard Worklist provided by K2.net. The consolidated view is just for illustration purposes and can easily be customized for new implementations.
The article is a walkthrough of how to setup the various items required to configure InfoPath 2007 client-enabled forms as well as InfoPath Forms Services 2007 web-enabled forms within a K2.net 2003 process.
This article will explore how to call a standard K2.net 2003 Collaboration Tools for Microsoft SharePoint Products & Technologies Workflow process from a custom workflow process, without using Microsoft SharePoint event handling, by means of an Inter Process Call (IPC).
By default, any InfoPath form created from an XSD schema will be considered locked. However, by adding to the XSD any element attribute, InfoPath will allow additional elements to be added to the data structure.
The following steps demonstrate how to install CDO as a component of Outlook using a Windows XP machine.
Collaboration Tools offers additional functionality to users of Windows Sharepoint Services and Sharepoint Portal Server, allowing them to create ad-hoc document centric workflows without any code. This document will show you how to add links to additional non-standard templates, or foreign language templates, that you may have running on your SharePoint installation.
In certain scenarios the location of the SQL database where the K2 and K2Log databases were installed may change, e.g. customers may want to scale their solution. This article will guide the users to components that need to be reconfigured.
In a high security environment, it is not always possible to give the K2.net Server service account local administrator rights. This article details the minimal permissions that the service account requires on the local server.
Improper design practices can limit the success of any solution. As such it is imperative to understand factors that should be factored into any K2.net development project in order to ensure proper system performance and scalability.
In order to avoid getting an error that reads 'The number of installed licenses for K2.net 2003 has been exceeded'; you will need to allow for the limitations of the 10 user development license. K2.net developers can do this by creating mock groups in their development environments that are designed to only ever have 10 test users in them.
This article will help K2.net administrators and developers better understand the conditions affecting their K2.net 2003 Named User License (NUL) systems.
This article provides a detailed explanation of the communication flow and interaction with the components involved in the execution of a K2.net 2003 InfoPath process that integrates with Microsoft SharePoint.
The goal of this article is to highlight the differences between the different K2.net development interfaces and provide some example scenarios of how they can be used.
The purpose of this article is to help diagnose and resolve 401 errors for the K2.net 2003 or blackpearl Workspace when the K2 Workspace components and the K2 Server components are installed on a single server.
The new error logging framework for K2.net 2003 with SP 4 changes the format in which errors are generated by the K2.net 2003 Server. As a result, existing system may be affected when upgrading to the latest service packs from versions prior to K2.net 2003 with SP4.
This KB article details how an object of any type may be stored within an Activity or Process Data Field within a K2.net 2003 Process without having to serialize the object to XML.
In most production environments having user credentials in clear text is considered a security risk. This article will elaborate on how to configure K2.net Workspace web service to use Integrated Security when connecting to the K2 databases to retrieve data for the Workspace reports.
This article details how to rename or copy an existing process or project.
“This form was created with a new version of the form template. InfoPath cannot find the new version. Do you want to open with the older version?”
This document describes how to place the K2Rom.dll in a COM wrapper and then to call the DLL from a COM based application written in VB6.
This article explains how to change from using the SQL user manager (SQLUM) back to using the default Active Directory User Manager (ADUM).
This document describes how to check whether a document in a SharePoint shared document library is checked out before downloading the document.
The error “An error occurred while parsing EntitiyName” will occur during the execution of an InfoPath process when the process name contains the '&' character and the client event is configured to update a SharePoint task list.
After upgrading an existing K2.net 2003 Installation to K2.net 2003 with SP3, some users and / or users in groups may be unable to start or view processes.
This article discusses the expected behavior of .NET 2.0 assemblies referenced in K2.net 2003. This article applies to assemblies referenced from the GAC and the file system.
This article discusses the necessary preparation required before upgrading an existing Microsoft SQL Server 2000 environment to Microsoft SQL Server 2005.
This article discusses the necessary steps required to configure the K2.net environment to run on a specific versions of the Microsoft .NET framework
K2.net 2003 with SP3 introduces an enhancement around Destination Queue user management at runtime. Currently in K2.net we have scenarios where Destination Queues resolve to large number of users creating a huge overhead on K2.net Server having to manage the activity instances representing the worklist items.
This document is intended to give a consolidated list of information contained in various K2.net resources: Online resources (Microsoft sites, K2.net KnowledgeBase, K2.net Forum, FAQs, and other technical discussion groups), trends and experience from K2.net support teams, and scenarios encountered in the field by K2.net training teams and consultants.
When you open the K2.net® 2003 Workspace and you click on “Worklist” you will sometimes see the error “Input string was not in correct format” (Error 1.0) Follow the instructions on how to fix the problem.
This document aims to explain the concept behind Data on Demand, including best practices.
After installation, when trying to browse the K2.net 2003 Workspace a HTTP 404 – File not found error is displayed in the browser.
The article describes how to resolve a network authorization error.
Article describes how to create and deploy a Custom Action for K2.net Collaboration Tools.
Kerberos authentication is a form of Windows Authentication that allows delegation of credentials through multiple application layers and across multiple servers – unlike NTLM, which will pass user credentials through one layer only. Therefore, if you have set up K2.net 2003, IIS and other 3rd party applications on multiple servers and need to pass user credentials throughout, you will have to make sure Kerberos authentication is working.
This article describes the deployment issues with the K2.net InfoPath process settings that are stored in process data fields. It also provides a step-by-step guide to follow when deploying K2.net InfoPath solutions between environments.
This document is intended to provide an overview of what type of clustering K2.net® 2003 supports. At this point in time K2.net® 2003 with Service Pack 2 (SP2) is the latest version and is not cluster aware, it will however; fully support Network Load Balancing (NLB). There are two types of clustering: MSCS (Microsoft Clustering Services) – which K2.net® does NOT support NLB (Network Load Balancing) – which K2.net® does support
This article walks through the process of adding rules to the submission behavior of an InfoPath form so as to allow a form variable determine whether the form gets saved to a SharePoint Form Library or submitted to K2.
Stored User Account Preventing Anonymous Access to IIS Using K2.net 2003 with custom user manager application. HTTP Status 401: Unauthorized error occurs.
This article explains how to enable the trace file for K2 server
This document discusses the methods K2.net customers can use to manage their K2.net server licenses, including obtaining, updating, and troubleshooting issues surrounding K2.net license keys. This document is intended only as a summary of K2.net licensing information described in more details in other documentation and resources.
“A database error occurred” exception/message can be caused by insufficient file system access rights for the user context that the K2.net 2003 Server runs as.
When using a server event with a K2.ExpireActivity('EventName') in code, events following the server event in the same activity are not expired. This document explains how to work around the issue.
This document covers starting a K2.net process from Kofax Ascent 6.1 Release scripts using the K2Rom.dll (placed in a COM wrapper) from the COM dll TextRel.dll found in Kofax. For this article, the TextRell.dll was modified to include a section to start a K2.net 2003 process.
How to monitor file activity with SysInternal's “FileMon” utility. Important Note: This document is only intended to be an overview of how to use the FileMon utility and how it can be used in supporting K2.net systems. Please consult Microsoft documentation for information related to the FileMon utility.
How to monitor Registry activity with SysInternal's “RegMon” utility. Important Note: This document is only intended to be an overview of how to use the RegMon utility and how it can be used in supporting K2.net systems. Please consult Microsoft documentation for information related to the RegMon utility.
This article highlights a known issue when resolving User names from Active Directory if special characters are contained in the username or the user’s group or organizational unit. This issue may be experienced as an “Unknown Error” in K2.net™ 2003 Studio, or an “An Activity with a client event should at least have one destination” error in K2.net™ 2003 Server
The following article explains the use of the XML Field created by the SharePoint Process Wizard.
When the default size of the canvas in K2.net 2003 Studio is enlarged, the whole of a workflow may no longer be visible within the K2.net 2003 Workspace’s View Flow. This article explains how to modify the View Flow in order to set the window the same as the K2.net 2003 Studio canvas area.
What do you do if you need to apply a strong name to an assembly that was provided, already compiled, to you and you don't have the source?
After clicking the link to “View Flow” from the workspace a blank report page is displayed.
This error may occur in K2.net™ 2003 Workspace or when accessing a K2.net™ 2003 Smart form
A specific installation exception (installation error) when trying to move from the components installation screen to the K2.net® database specification screen and the method of working around it.
This document outlines how to set the folio field for an InfoPath 2003 process after you have already run through the InfoPath Process wizard in K2.net Studio.
You may receive a “User cannot be found error” from an InfoPath process that is configured to update a SharePoint task list. To resolve this issue the destination user of the client event must be given explicit permissions to the SharePoint site where the task list is located.
This article explains the steps to take in the event of a “System.NullReferenceException has occurred in K2Studio.exe” error message. This can appear when opening the K2.net 2003 Studio application.
A new feature introduced in Service Pack 2a allows K2 Server to be configured to retry the deleting of temporary files in SPS. The feature was introduced in order to deal with occurences where SharePoint locks documents for a time, even if they are not open.
The information applies to when using the ISO image to upgrade to K2.net 2003 with SP2a is in progress and the installer generates the error “Please insert the disk: 1”.
Article discusses password best practices and how to resolve K2 Portal login issues
With the final release of Windows 2003 Server Service Pack 1, and the high customer uptake rate expected, it is imperative that the expected impact on K2.net 2003 systems be clarified.
System requirements for installing K2.net 2003
When the SharePoint 2003 Document Event Template is used to upload documents to SharePoint and an XML Field is used as the source for document to be uploaded, then characters with an ASCII value above 128 will be replaced by a question mark character [?]. This is because the code generated by the SharePoint 2003 Document Server Event Template uses ASCII encoding.
When browsing to a site hosted in IIS 6.0 you may receive a “Service Unavailable” error. The cause for this issue can be an application pool identity that is not a member of the IIS worker process security group.
A CMS client event submit will cause any workflow that improperly triggers on a CMS submit to launch another process instance.
You may receive a “Page can not be initialized. The worklist item either does not exist or has already been completed” error message when viewing a SmartForm application plan page.
The K2.net Studio and Server BizTalk components require that the Microsoft BizTalk Server 2004 Developer Tools be installed. The “Object not a collection” error will occur if the installation requirements are not satisfied.
There is a known problem with K2 CMS components where a reboot will cause the MSI installer to fire each boot cycle.
The 'Everyone' Active Directory group cannot be used in the K2 service manager to assign process permissions. The 'Domain User' group should be used instead.
You may encounter the error, 'Exception has been thrown by the target of an invocation', during the third step of the K2 .net 2003 Share Point process wizard.
In some cases there may be the requirement to run the InfoPathService web service under a SharePoint site in IIS. This article guides the user to perform the correct steps as well as provides the type of error messages that can be expected if it is not done correctly or not done at all. Helps specifically to resolve the error: The SOAP response indicates that an error occurred on the server: System.Security.SecurityException: Security Error.
The K2.net Workspace reports an error when a user enters the web site.
When an InfoPath document that was used by older versions of K2.net 2003, (prior to SP1a), is refreshed or used again in the newer versions of K2.net 2003, (SP1a and later), an error is displayed when the K2 InfoPath process wizard tries to upgrade the file after the user has made changes to certain sections in the JavaScript for the InfoPath document.
When starting up K2.net 2003 Studio, it crashes after the splash screen with the error: “An exception 'System.Xml.Exception' has occurred in K2Studio.exe”.
An error occurs when browsing your SharePoint portal site's tree view list during the SharePoint process wizard. This error only occurs when SharePoint server is running on a separate server machine to that of K2.net 2003 Server.
This article explains how to add custom error handling in a K2.net 2003 Smartforms project. This can be illustrated by capturing the “All Worklist items have been allocated” exception.
K2.net 2003 Server uses Microsoft SQL Server as its private data store. The data store is made up of 2 physical databases, the transaction runtime database (K2 by default) and the log database (K2Log by default). The following article discusses the security architecture between the various K2.net 2003 components and databases.
When changes are made to the originally submitted data, the process values change to show the new values, and an entry is made in the data audit facility. However, there is no record of what the initial data values were. Read on to find out how to show these initial data values in the audit trail.
This article explains how to enable cross-network communication with Kerberos on a K2.net™ 2003 Server.
This application will allow you to view the event code for a specified client or server event in a running process.
This article explains how to create an activity with a 'placeholder' destination user for scenarios where the destination user for an activity is not known at design-time - or when users need to 'pull' items from a shared Worklist.
This article demonstrates how one can easily create an XSLT definition to display XML data fields in the K2.net 2003 Workspace, by using Microsoft InfoPath.
When you have Windows Sharepoint Services and K2.net™ 2003 Workspace in Internet Information Services (IIS) installed on the same port, you will experience the following error: 'Unverifiable assembly 'K2CSC' failed policy check'
This article explains how to run K2.net™ 2003 Server code in 'Debug' mode using Microsoft® Visual Studio .NET.
This article describes the steps involved for enabling K2.net™ 2003 Studio to use Transaction Processing on a SQL Server database.
This article describes the updating or editing of your K2.net™ 2003 Server License key.
This article explains how to use a custom Microsoft® SharePoint Template to create workspaces in the InfoPath and SharePoint K2.net™ 2003 Studio Templates.
This article explains how to perform debugging of an ASP.NET application that runs in the same site as Microsoft® SharePoint.
This article explains how to configure the K2.net™ 2003 Workspace to run on the same IIS site as Microsoft® SharePoint.
This article explains how to remove K2.net™ 2003 functionality from a Microsoft® InfoPath version 1.0 document
This article explains how to determine which user initiated a SharePoint event.
This article explains how to prevent an activity from completing until all activity slots have been completed.
InfoPath 2003 (with Office 2003 SP1) allows you to use digital signatures on a form template (.xsn) file to help ensure the integrity and authenticity of the form template.
This article explains how to replace the currently installed K2.net™ 2003 databases with clean databases.
When debugging a K2.net™ 2003 database and you need to get it running in another environment, it is necessary to reset the security settings for the K2.net™ 2003 Service Manager, as this contains information about the original network environment.
Creating an empty K2.net™ 2003 Studio Project and having its Solution share the same name.
A user/developer sometimes has to update/add destination rules to a project but may not have access to the Active Directory. It is possible to run the K2.net™ 2003 Studio under another user’s credentials and gain access to the Active Directory via this user’s permissions.
In a development or testing environment, it is sometimes favorable to restore the system to its default installation configuration. By having a backup configuration available, it is simple and easy to revert to a default configuration.
This article suggests ways for troubleshooting e-mail issues experienced on the K2.net™ 2003 Server
This article will illustrate how to change the default logos displayed in the Workspace.
The following article has been replaced by the articles listed below.
This article described the process of customizing the Startup page of your K2.net™ 2003 Studio. In particular, by following the steps described, you will be able to add a link to your K2.net™ 2003 Workspace inside the Start page.
When a user opens a worklist item on his worklist, the item will be, by default, allocated to the user, restricting access to other users attempting to open the same worklist item. The developer can control whether the item should be allocated to the user or not.
Hasty users often click multiple times on a submit button while the page is trying to connect to the K2.net™ 2003 Server to start a process or complete a K2.net™ client event.
This article should repair a SOAP error encountered while viewing Reports in K2.net™ 2003 Workspace.
This article will guide you through the steps required for displaying the K2.net™ 2003 Workspace in Microsoft Outlook.
Typically in cases where developers extend and integrate reports with custom applications they want to also make use of ViewFlow to display a graphical view of the process.
There is no escalation rule that will increase an activity’s (or process's) priority. This is easily achieved by writing an escalation rule that will increase the priority every time it fires.
This article describes how to impersonate users when opening InfoPath forms.
The following sample illustrates the use of the existing workspace service and will allow developers to better understand the way that K2.net™ 2003 Workspace leverages this web service to retrieve process-related reports from the Log data store.
The Viewflow component is not displaying the expected workflow process. Instead a small error picture (red X) in the left corner appears.
What are Destination Queues used for in K2.net™ 2003?
The following section will describe the available license key options for K2.net™ 2003 Server.
This article describes the steps required to configure K2.net 2003 for use over an HTTPS/SSL connection.
Referencing a Web Service in K2.net 2003 Studio to expose the various methods available in the Web Service.
The following example will illustrate the use of sending HTML formatted emails using K2.net™ 2003
Running process instances can be deleted using the K2.net™ 2003 Service Manager, is it possible to do this programmatically?
The “HTTP Error 405 - The HTTP verb used to access this page is not allowed.” typically occurs where ASP.NET is not installed on the IIS Server.
A business process built using K2.net 2003 could quite possibly span over multiple time zones. If this process contains an escalation, it is more than likely that the escalation should only escalate after ‘x’ number of working hours. This article discusses adding dynamic escalations based on time zones.
Sometimes you want to create a Task Item in SharePoint for a Client Event in a process. The functionality of having a Client Event with a matching SharePoint Server Task List Item is currently only available in the InfoPath wizards. This article describes how to combine a Default Client event and a SharePoint 2003 List event.
One of the best practices in any application development is proper client-side validation. Typically a developer using web-based forms for client pages in workflow processes will either use standard ASP.NET web pages or K2.net™ 2003 SmartForms. The following example allows developer to implement client-side validation on both VS.NET web pages and K2.net™ 2003 SmartForms.
The K2.net™ 2003 Studio Task Pane is an HTML container which can contain multiple .html pages to add functionality to the standard K2.net™ Studio interface. This article and supporting files, will guide you through the process of adding a new task pane element which can copy the contained Line Rule from a specific line to another line. It will also show you how to gain access to the K2.net 2003 Studio object model.
K2.net™ 2003 Studio high level objects like Solution, Project and Process names can be easily renamed by pressing F2 on your keyboard.
This article will assist in resolving Access Denied errors upon opening your K2.net™ 2003 Workspace.
How to Import Process and/or Activity Data or XML Fields from another Process in K2.net™ 2003 Studio.
This article will assist in generating a script file which will clear the Recent Solution List on the Start page of K2.net™ 2003 Studio.