AgilePoint Knowledge Base

Why do I get a database permissions error when accessing AgileReports in the Enterprise Manager?

MichaelDa — Fri, 30 Dec 2011 14:19:31 GMT

Summary

When attempting to access AgileReports from Enterprise Manager, the following error occurs: "Sorry, your assigned roles don't have permission to use any of the databases."

Applies To

AgileReports

Details

When attempting to access AgileReports from Enterprise Manager, the following error occurs: "Sorry, your assigned roles don't have permission to use any of the databases."

This error typically occurs because AgilePoint Server was not restarted after the adHocAdmin group was created in Active Directory.

To test whether the adHocAdmin group has been created and AgilePoint Server has been restarted, do the following on the machine where AgileReports is installed:

Add the attached NTLoginTest.aspx page to [AgilePoint installation root]\AgilePoint\AgileReports
Browse to [AgilePoint installation root]\AgilePoint\AgileReports\_Definitions\_Settings.lgx file.
Add LogonFailPage="NTLoginTest.aspx" as below.
Sample “ _Settings.lgx” file:
<Security SecurityEnabled="True" AuthenticationSource="AuthNT" AnonymousUserID="1" LogonFailPage="NTLoginTest.aspx" NTAuthenticationDomain="xxxx" CacheRights="Session" LogonPage="http://localhost:9000/EnterpriseManager/Common/LogonForm.aspx" SchedulerUsername="Admin">
Restart the machine.

Installing AgileReports for Oracle

MichaelDa — Wed, 05 Oct 2011 10:58:58 GMT

Summary

This article provides attached files and instructions for installing AgileReports for Oracle.

Applies To

AgileReports customers using an Oracle database.

Details

To install AgileReports in an Oracle environment:

Download and extract the attached file, AgileReports_Oracle.zip.
Open the file <your path>/AgileReports For Oracle/AgileReportsInstallationInstructionsForOracle.pdf. This document, Installing AgileReports for Oracle, provides instructions for completing the AgileReports installation in an Oracle environment.
Follow the instructions in Installing AgileReports for Oracle to complete the installation. This document explains what to do with the other files in the download package.

AgileConnector sample for Custom Exception Handling

MichaelDa — Wed, 05 Oct 2011 10:58:11 GMT

The information in this article applies to:

AgilePoint Suite v4.0.1 Hotfix 1 or later

TOPIC(S)
	A sample AgileConnector (including source code) for custom exception handling.

SUMMARY
	AgilePoint makes available to customers options for flexibility in exception handling for out-of-the-box, and custom AgileParts by enabling the ability to implement custom logic. This article provides an AgileConnector sample and source code as well as information about how to develop, deploy, and implement an AgileConnector for custom exception handling for AgileParts. Note: Errors in SharePoint and SAP cannot be handled using custom exception handling because these errors tend to be severe with respect to AgilePoint processes. The default behavior for SharePoint and SAP errors is to pause the process and send a notification to the system administrator.

DETAILS
	Please refer to the PDF document contained in the attached ZIP file for additional details.

Last Reviewed:
Keywords:

Set Item Permission Custom AgilePart for SharePoint Integration v2

MichaelDa — Wed, 05 Oct 2011 10:57:05 GMT

Description

Samples and instructions for creating a custom AgilePart that enables you to change the permissions for a list item on the fly in AgilePoint SharePoint Integration v2.

Details

AgilePoint SharePoint Integration v1provided an AgilePart called Item Permission, which enabled permissions to be modified for an item in a SharePoint list on the fly. However, this functionality violates Microsoft Gold Level Certification policy in SharePoint Integration v2. This functionality violates Gold Level policy because it is only available through the Server Object Model and not through web services, which would mean that a custom web service must be placed on the SharePoint server. For these reasons, it was not included in SharePoint Integration v2.

For customers who are willing to place custom web services on SharePoint servers, it possible to use this functionality by creating a custom AgilePart. The attached Zip file provides samples and instructions for creating this custom AgilePart.

(Note that you may see two copies of the Zip file. This is a display error in the KB software. The two copies of the file are the same.)

Keywords

AgilePart, MOSS, SharePoint, v1, v2, compatibility, list item, permission

Exporting Process Models in XPDL

MichaelDa — Wed, 05 Oct 2011 10:56:25 GMT

Summary

This article describes how to export process models from Envision to XPDL 1.0. (This functionality is provided as a customization to the standard product.)

Applies To

AgilePoint Envision users who want to export process models to XPDL.

Details

Setup

To set up the XPDL export functionality:

Download and extract the attached Zip file, CustomXpdlPlugIn.zip.
Copy the file CustomPlugIn.dll to the root folder for your Envision installation.
To add the appropriate registry keys, double-click one of the following files, depending upon your Envision installation type:
- 32-bit - CustomXpdlPlugIn-X32.reg
- 64-bit - CustomXpdlPlugIn-X64.reg

Export

To export your process to XPDL, in Envision, click File > Export & Import > Export Standard XPDL.

Keywords

process, export, xpdl, save as

Use Data Population for the AgilePoint WFComment Control in ASP.NET applications

MichaelDa — Wed, 05 Oct 2011 10:55:00 GMT

Summary

This article provides information on how to use AgilePoint Data Population for the WFComment Control in AgilePoint ASP.NET applications.

The Solution

Use AgilePoint Data Population for the WFComment Control by following these steps:

Create a Table in the database where you want to store the Comments data.

CREATE TABLE [dbo].[Comments](
[CommentBy] [varchar](50) NULL,
[CommentDate] [datetime] NOT NULL,
[CommentText] [varchar](300) NULL,
[RefNo] [varchar](50) NOT NULL,
CONSTRAINT [PK_Comments] PRIMARY KEY CLUSTERED
(
[CommentDate] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]
) ON [PRIMARY]
GO
Map the Parent Table and Child Table (Primary Key and Foreign Key) relationship:
In AgilePoint Envision, add the Schema for the WFComment Control for Data Population.
Schema Mapping for the Data Population:
Drag and drop the WFComment Control on the .aspx page and set the DataBinding property:

<ap:WFComment ID="WFComment1" runat="server" BarColor="SteelBlue"

BarHeight="1px" BindingName="/pd:BudgetRequest/pd:Comments"

CommentBackColor="Orange" CommentCaption="Add Comment" CommentFontSize="Small"

CommentListBackColor="Orange" CommentListCaption="Comment History"

CommentListTitleAlign="Left" CommentTitleAlign="Left" CommentWrap="False"

CustomFormat="{0} by {1}" Height="100px" HistoryCommentBackColor="White"

MappingComment="pd:CommentText" MappingDate="pd:CommentDate"

MappingName="pd:CommentBy"

OuterXmlTemplate="PHBkOkNvbW1lbnRzIHhtbG5zOnBkPSJodHRwOi8vd3d3LmFzY2VudG4uY29tL3Byb2Nl
c3Nlcy5CdWRnZXRSZXF1ZXN0Ij48cGQ6Q29tbWVudD48cGQ6Q29tbWVudEJ5PlN0cmluZzwvcGQ6Q29tbWVudEJ5
PjxwZDpDb21tZW50RGF0ZT5EYXRlVGltZTwvcGQ6Q29tbWVudERhdGU PHBkOkNvbW1lbnRUZXh0PlN0cmlu
ZzwvcGQ6Q29tbWVudFRleHQ PC9wZDpDb21tZW50PjwvcGQ6Q29tbWVudHM " Width="101%" style="margin-bottom: 10px" />

Keywords

WFComment, Data Population

Show Trial Period Left for Evaluation Keys

MichaelDa — Wed, 05 Oct 2011 10:54:14 GMT

The information in this article applies to:

AgilePoint v4.7 or earlier
AgilePoint Suite Evaluation Package

TOPIC(S)
	This article provides information on using the Show Trial Perod utility to determine the amount of days left before your trial license for AgilePoint expires.

SUMMARY
	See below.

DETAILS
	Download the attached ShowTrialPeriod.zip file and unzip. Copy this program to 'C:\Documents and Settings\All Users\Start Menu\Programs\Startup' Of demo VPC. When logging into Windows, the program will pop-up a message telling you how much time is left before your trial time expires .The window will stay open for five seconds, and close automatically. NOTE: This works only for Evaluatoin License Keys, if you are using a product license key, it would not prompt. NOTE: Another way to find out the trial period is by looking at AgilePoint Server log. The log files are located at below location. You may check the latest log file and it should log ‘You have xxx days to run ‘AgilePoint Server’ before trial time expired’ (see below picture). Local_drive:\AgilePoint\AgilePointServer\log

Last Reviewed:
Keywords:

After upgrading to AgilePoint v4.7, processes are not being initiated.

MichaelDa — Wed, 05 Oct 2011 10:53:25 GMT

Summary

After upgrading to AgilePoint v4.7, processes are not being initiated.

Applies To

Upgrading AgilePoint v4.6 to v4.7.

Symptoms

After upgrading an AgilePoint release from v4.6 to v4.7, processes are not being initiated. The following error message is being shown in the AgilePoint Server Log file:

2009-08-21 17:49:08.519 >>> CShapeSnippet, System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.MissingMethodException: Method not found: 'System.Object Ascentn.Workflow.Base.WFCustomAttributes.Attr(System.String, Ascentn.Workflow.Base.IWFProcessInstance, Ascentn.Workflow.Base.WFAutomaticWorkItem)'.

at CodeSnippet_507020F85C1541849C283EA6D0B22567.Invoke(WFProcessInstance pi, WFAutomaticWorkItem w)

--- End of inner exception stack trace ---

at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)

at System.RuntimeMethodHandle.InvokeMethodFast(Object target, Object[] arguments, Signature sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)

at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)

at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)

at Ascentn.Workflow.Extension.ScriptingAgilePart.CShapeSnippet(WFProcessInstance pi, WFAutomaticWorkItem w, IWFAPI api, NameValue[] parameters)

More Information

This occurs when the Update Custom Attributes shape is being used in a process model and previous process instances have executed. AgilePoint Server first refers to the AgilePoint Server cached assemblies in the C:\AgilePoint\AgilePointServer\cache folder, AgilePoint v4.7 uses a new method that causes a conflict with the cached assemblies.

To resolve the issue,

Stop IIS.
Clear the AgilePointServer\cache folder.
Restart IIS.

Keywords

Update Custom Attributes, Upgrade, Upgrading problem, process initiation problem, AgilePoint Server cache

Add Custom Actions to the AgilePoint Task List and AgilePoint Process Instance List Web Parts

MichaelDa — Wed, 05 Oct 2011 10:52:24 GMT

Summary

Mainly for OEM Partners, this article provides the information for extending the AgilePoint Task List Web Part and AgilePoint Process Instance List Web Part to include Custom Actions. This is supported at the item level as well as at the global level.

Applies To

OEM Partners
Extending the AgilePoint Web Parts
AgilePoint SharePoint Integration

More Information

The document attached provides the information for extending the AgilePoint Task List and AgilePoint Process Instance List Web Part to include Custom Actions.

A sample project for Change Priority in the AgilePoint Task List Web Part is provided.

Keywords

Global actions, web parts, custom actions, change priority

Use AgilePoint's SendMail API to send email notifications

MichaelDa — Wed, 05 Oct 2011 10:48:16 GMT

The information in this article applies to:

AgilePoint Developer

GOAL(S)
	Provides an example of how to use AgilePoint's SendMail API to send email notifications.

SUMMARY
	AgilePoint's SendMail API provides application developers a function to develop custom notification scenarios for applications. For example, it can be used to develop custom email notifications at runtime and/or associate email notifications dynamically to any workflow tasks and/or objects within an application. There are two SendMail() functions under different classes: IWFWorkflowService.SendMail() – This function sends out the email, but does not support attachments. For example, this function is commonly used for an application that is not in-process with AgilePoint Server. IWFAPI.SendMail() – This function supports sending out email with attachments, but is only available in AgilePart/AgileWork/AgileStub components. (See Snippets below). An alternative approach for sending an email with attachments in an AgilePoint Web Application is to use the .NET class, System.Net.Mail.SMTPClient. Please note that for emails that are sent out using System.Net.Mail.SMTPClient, AgilePoint Server has no records of these emails. If in case you run into email issues for this scenario, the troubleshooting effort should be focused on the custom code in your Web application. The SMTP Server address is required when using the System.Net.Mail.SMTPClient. The screen captures below provide a sample for how to obtian the SMTP Server address.
	SMTP and Database is configured via the AgilePoint Server Configuration.
EXAMPLE
	Snippet 1: Sample Snippet The following is a C# code snippet of how the SendMail API is called: using System; using System.Collections; using System.Data; using System.Xml; using System.Net; using System.IO; using System.Text; using Ascentn.Workflow.Base; namespace ManagedCode { public class CSharpCodeSnippet { // Invoke method is this class's entry point public void Invoke( WFProcessInstance pi, WFAutomaticWorkItem w, IWFAPI api, NameValue[] parameters) { string emailAddress = WFSystem.SysAdmEMailAddress; string attachment = WFSystem.HomeDirectory + "\\License.en-US.RTF"; IWFActivityInstance ai = api.GetActivityInst(w.ActivityInstID); api.SendMail( pi, ai, emailAddress, null, string.Format("Request for Approval - {0}", pi.ProcInstName), "You are assigned with this task, please review and approve within two days.", attachment); } } } Snippet 2: In AgilePart /// <summary> /// This class is AgilePart runtime class that will be invoked by AgilePoint Server. /// </summary> [AgilePart("Put name here")] public class MyAgilePart : WFAgilePart { [ Description("Put description here"), AgilePartDescriptor(typeof(MyAgilePartDescriptor)) ] public void SendMailByAPI( WFProcessInstance pi, WFAutomaticWorkItem w, IWFAPI api, NameValue[] parameters) { try { string emailAddress = WFSystem.SysAdmEMailAddress; string attachment = WFSystem.HomeDirectory + "\\License.en-US.RTF"; Logger.WriteLine("Send e-mail to '{0}' with attachment '{1}'", emailAddress, attachment); IWFActivityInstance ai = api.GetActivityInst(w.ActivityInstID); api.SendMail( pi, ai, emailAddress, null, string.Format("How To Send E-Mail Using ServerAPI - AgilePart, {0}", pi.ProcInstName), "How To Send E-Mail Using ServerAPI", attachment); if (w.Synchronous) MarkSuccess(api, pi, w, parameters); } catch (Exception ex) { HandleException(api, pi, w, parameters, ex); } } } Snippet 3: In AgileWork /// <summary> /// This class is AgileWork runtime class that will be invoked by AgilePoint Server. /// </summary> [AgileWork("MyAgileWork AgileWork", typeof(MyAgileWorkDescriptor))] public class MyAgileWork : WFAgileWork { #region Constructor public MyAgileWork(WFProcessInstance instance, WFManualActivityInstance activity) : base(instance, activity) { base.AssignWorkItem += new EventHandler(MyAgileWork_AssignWorkItem); } #endregion #region Event Handlers private void MyAgileWork_AssignWorkItem(Object sender, System.EventArgs e) { WFGenerateManualWorkItemEventArgs args = e as WFGenerateManualWorkItemEventArgs; IWFAPI api = args.WFApi; string emailAddress = WFSystem.SysAdmEMailAddress; string attachment = WFSystem.HomeDirectory + "\\License.en-US.RTF"; Logger.WriteLine("Send e-mail to '{0}' with attachment '{1}'", emailAddress, attachment); api.SendMail( this.m_ProcessInstance, this.m_ActivityInstance, emailAddress, null, string.Format("How To Send E-Mail Using ServerAPI - AgileWork, {0}", this.m_ProcessInstance.ProcInstName), "How To Send E-Mail Using ServerAPI", attachment); Logger.WriteLine("MyAgileWork_AssignWorkItem, Activity Instance={0}", base.m_ActivityInstance.DisplayName); } #endregion } Snippet 4: In AgileStub using System; using Ascentn.Workflow.Base; /// <summary> /// Summary description for Class1. /// </summary> public class ProcessDefinition_85B694EF1C014A0FB759FAD859339534 : WFProcessInstance { public ProcessDefinition_85B694EF1C014A0FB759FAD859339534() { } public void SendMailByAPI( WFAutomaticWorkItem w, IWFAPI api) { string emailAddress = WFSystem.SysAdmEMailAddress; string attachment = WFSystem.HomeDirectory + "\\License.en-US.RTF"; Logger.WriteLine("Send e-mail to '{0}' with attachment '{1}'", emailAddress, attachment ); IWFActivityInstance ai = api.GetActivityInst(w.ActivityInstID); api.SendMail( this, ai, emailAddress, null, string.Format("How To Send E-Mail Using ServerAPI, {0}", this.ProcInstName), "How To Send E-Mail Using ServerAPI", attachment); } }

Last Reviewed:
Keywords:

AgilePoint does not support the Custom SharePoint Event Handler - Delete Event

MichaelDa — Wed, 05 Oct 2011 10:47:15 GMT

Summary

AgilePoint does not support the Custom SharePoint Event Handler - Delete Event. At this time it is only supported to initiate a process when a new item is created or when an existing item is changed.

Applies To

AgilePoint SharePoint Integration
Custom SharePoint Event Handler - Delete Event

Symptoms

In a SharePoint Document Library, the user wants to initiate an AgilePoint Process when a document is deleted. When the document is deleted, the process requires approval before the document should be deleted. The implementation is accomplished using a custom SharePoint Event Handler - Delete Event when a document is deleted.

More Information

AgilePoint does not currently support initiating a process based on the Delete Event. The solution would be to disable the delete function in SharePoint (via security) and initiate the process manually where at the last stage, provide the delete function in the AgilePoint Process Model using an AgilePart.

WF knowingly excludes this event from WF because once a document or list item is deleted from the list it does not make sense to kick off a process since the list item won’t be available in case you want to refer to it. Internally AgilePoint does support the deleting event using event handlers to cancel workflows for list items that were deleted.

Keywords

SharePoint Custom Event Handler, Delete Event

How AgilePoint License Usage is Calculated

MichaelDa — Wed, 05 Oct 2011 10:43:35 GMT

Summary

This article provides information about how the AgilePoint licensing percentages are calculated. Based on your AgilePoint license agreement, the following information will help you understand how to retrieve and interpret your Named User License usage and Process Template License usage.

Applies To

Named User License Usage
Process Template License Usage

More Information

AgilePoint Enterprise Manager displays the Process Template License usage and Named Users License usage percentages as shown below.

* Process Template License usage is calculated using the following formula:

For example, if the total number of Child Process templates is 20, the subprocess ratio is 5, the total number of Non-Child Process Templates is 10, the total number of Licensed Process Templates is 20, the average Process Template License usage would be 20/5 + 10 / 20 = .7 or 70%.

* Named User License usage is calculated using the following formula:

For example, if the total number of AgilePoint Registered Users is 35, and the total number of named users in the license agreement is 70, the Average Thread Usage would be 35/70 = .5 or 50%.

Keywords

Average Thread Usage, Process Template License Usage, SubProcess Ratio

In MS Office 2007 Visio, the AgilePoint Envision menu functionality is disabled.

MichaelDa — Wed, 05 Oct 2011 10:42:30 GMT

Applies To

MS Office Visio 2007
AgilePoint Envision

Symptoms

In MS Office Visio 2007, the AgilePoint menu functionality is disabled.

More Information

During the installation of MS Office Visio 2007, the installer is given the option to customize how Visio works. The installer may have selected a setting that disables the AgilePoint menu functionality. In order to correct this issue, via Add/Remove Programs > Microsoft Office Visio 2007 Professional > Change. Set the Microsoft Forms 2.0 .NET Programmability Support to "Run on My Computer".

Keywords

AgilePoint Envision menu disabled
Visio
Microsoft Forms 2.0 .NET Programmability Support

Access Denied, ‘Global’ registry could not be accessed.

MichaelDa — Wed, 05 Oct 2011 10:41:40 GMT

The information in this article applies to:

AgilePoint Suite v4.0.1 Patch 2 or later

ERROR
	The AgilePoint Server Application Pool Identity requires permission for performance counter access, the error message would be: Access Denied, ‘Global’ registry could not be accessed.

STEPS TO REPRODUCE
	NA.

DETAILS
	Add the AgilePoint Application Pool Identity into the ‘Performance Monitor Users’ group.

Last Reviewed:
Keywords:

Access AgilePoint Web Service API from a 3rd party application such as SharePoint or ASP.NET application from a separate machine through Impersonation

MichaelDa — Wed, 05 Oct 2011 10:40:54 GMT

The information in this article applies to:

AgilePoint Developer
Web Service API

GOAL(S)
	Access AgilePoint Web Service API from a 3rd party application such as a SharePoint component or ASP.NET application in a separate machine through Impersonation.

SUMMARY
	Sometimes application developers may need to implement their own custom component to access AgilePoint through Web Service API. These components can be located in a physically separate machine (for example, calling from a SharePoint Web Part) and when accessing the AgilePoint Server through Web Service API, HTTP - 401 authentication error may occur. For the SharePoint component, it runs under the identity that is specified in the SharePoint Application Pool. In some case, the identity could be set using the NetworkService or LocalSystem. These identities will not be able to get authenticated remotely through IIS and therefore returned the HTTP - 401 error. NOTE: This approach is a solution to the well known double hop issue.

SOLUTION
	In a multiple-server envrionment, it is recommend to set up a dedicated user credential that the 3rd party application code can impersonate to get authenticated cross machine in order to access the AgilePoint Web Service. This dedicated user credential is typically stored in the web.config file of the application which can be retrieved before accessing the Web Service. AgilePoint also provides an API called Surrogate() to allow the custom code to set the login user identity after the initial authentication through the impersonation. This will allow the remaining operation with the Web Service to run under the correct login identity. Here are the steps to do surrogating: In your custom coding for surrogating, at api.SetClientAppName("MyApplication"), put in your desired application name (case sensitive). Open the AgilePoint Server Configuration and click the Extension link, then click the Add button. Enter the application name (case sensitive) you used in the custom coding and also the Impersonator name (see picture below). The Impersonator has to be a registered user and preferably an administrator in AgilePoint Server. Here are some code snippets: //Get the credentials using the dedicated user credential retrieved from the web.config System.Net.NetworkCredential credentials = new System.Net.NetworkCredential(ap.m_ImpersonatorName, ap.m_ImpersonatorPassword, ap.m_Domain); //Get the login user info from the HTTP context string context = this.Context.User.Identity.Name; string errmsg; try { // Workflow Web Service api = new WorkflowService(url); //url is the AgilePoint Server Url, should be obtained from the web.config api.CookieContainer = cookieContainer; api.Credentials = credentials; api.SetClientAppName("MyApplication"); //You must also set the Impersonator to this application name using the AgilePoint Server Configuration api.SetClientLocale("en-US"); api.Surrogate(context); string userName = api.CheckAuthenticated();
	... }

Last Reviewed:
Keywords:

Remove all process related data from database

MichaelDa — Wed, 05 Oct 2011 10:38:41 GMT

The information in this article applies to:

AgilePoint Server

SYMPTOMS
	During the QA cycle, there may be pending or completed processes that are created for testing purpose and are no longer needed in the server. It will nice to have sql scripts that can be used to clean up the database to remove unwanted processes.

CAUSE
	QA

RESOLUTION
	To delete all the processes and their related data from the database, please use the following SQL statements: delete WF_EVENTS delete WF_AUTO_WORKITEMS delete WF_MANUAL_WORKITEMS delete WF_ACTIVITY_INSTS delete WF_CUSTOM_ATTRS delete WF_PROC_TRACKINGS delete WF_LARGE_TEXTS where TEXT_ID in ( select PROC_INST_ID from WF_PROC_INSTS ) delete WF_PROC_INSTS delete WF_MAIL_DELIVERABLES .

Last Reviewed:
Keywords:

How do I modify the value of a shared custom process attribute?

MichaelDa — Wed, 05 Oct 2011 10:37:24 GMT

The information in this article applies to:

AgilePoint Envision v4.0 or later

QUESTION(S)
	I have defined a shared custom process attribute called "Something" in Enterprise Manager. I've set the value of the shared custom process attribute in Enterprise Manager. I now want to use a Managed Code C# Snippet to dynamically change the value of the shared custom process attribute "Something". What is the syntax to update the value of the shared custom process attribute "Something"?

SHORT ANSWER
	To dynamically update the shared custom process attribute "Something" at run time, the following syntax can be used within the Managed Code C# Snippet AgilePart.

Last Reviewed:
Keywords:

SharePoint process cannot be initiated

MichaelDa — Wed, 05 Oct 2011 10:36:09 GMT

The information in this article applies to:

AgilePoint SharePoint Integration

SYMPTOMS
	Unable to get a SharePoint process to initiate.

CAUSE
	One area to check is in SharePoint Central Administration, if the General Settings for the Web Application has the "Backward-compatible Event Handlers" turned "Off" the SharePoint integration functionality will not work. You can verify that this is turned off by accessing the SharePoint Library or Lists Advanced Settings, if you do not see the "Backward-Compatible Event Handler" item, it is turned "Off".

RESOLUTION
	In the SharePoint Central Administration the "Backward-Compatible Event Handler" must be turned "On". After switching this to on, re-enable the SharePoint Library or List.

Last Reviewed:
Keywords:

Receive Exception Error in Envision after installing AgilePoint v4.0.1 Patch 2 Hotfix 1

MichaelDa — Wed, 05 Oct 2011 10:35:30 GMT

The information in this article applies to:

AgilePoint Envision v4.0.1 Patch 2 Hotfix 1

ERROR
	Exception has been thrown by the target of an invocation.

STEPS TO REPRODUCE
	This error is thrown after applying AgilePoint v4.0.1 Patch 2 Hotfix 1 and opening a .vsd file in Envison.

DETAILS
	If the Envision machine has a custom plug-in and/or custom process model, Envision will prompt with the above error when opening a .vsd file after apply 4.0.1 Patch 2 and Hotfix 1. This is due to a Visio interoperable assembly version conflict. Most customers should not see this error as it is only prompted in the following special cases: AgilePoint Demo VPC (where a custom plug-in is installed to demo Microsoft Project conversions). In this case, please download the attached assembly to resolve. Place this file at C:\Program Files\Ascentn Corp\AgilePoint Envision. AgileScript (process model), contact us for a solution. OEM customer if using custom process model template, please apply the hot fix, and recompile the process model template module.

Last Reviewed:
Keywords:

PDF Integration AgilePart Requires 3rd Party Aspose License

MichaelDa — Wed, 05 Oct 2011 10:34:25 GMT

The information in this article applies to:

AgilePoint Suite v4.0.1 Patch 2

TOPIC(S)
	PDF Integation AgilePart requires Aspose license.

SUMMARY
	The PDF Integration AgilePart included with AgilePoint v4.0.1 P2 provides the function to convert multiple types of file formats to PDF. This AgilePart leverages a 3rd party component from Aspose Corporation (http://www.aspose.com/).

DETAILS
	In order to take advantage of this functionality, a license file for Aspose is required. Drop the Aspose license file to[AgilePoint Server folder]\licenses. The following Aspose licenses are required: Aspose.Pdf.Lic for any supported format: .html; .htm; .rtf; .docx; .doc; .xlsx; .xls; .dib; .tif; .tiff; .emf; .wmf; .jpg; .jpeg; .jfif; .jpe; .gif; .png; .exif; .bmp * Aspose.Words.Lic is required if the file to convert is Microsoft Word * Aspose.Cells.Lic is required if the file to convert is Microsoft Excel NOTE: For demo purposes, a trial version of Aspose is included with the AgilePoint v4.0.1 Patch 2.

Last Reviewed:
Keywords:

Can't find the FinalizeShape option when editing the shape

MichaelDa — Wed, 05 Oct 2011 10:33:32 GMT

The information in this article applies to:

AgilePoint Suite
AgilePoint Enterprise Manager
AgilePoint Envision
AgilePoint Developer
AgilePoint Server

SYMPTOMS
	I am trying to follow the "Edit Visio Stencil Images for AgilePoint Shapes" document to create a customized stencil in a new stencil file. After adding some user-defined cell information, I could not find the Tools>Macros>ThisDocument>FinalizeShape. As a matter of fact, it listed other stencil files currently open in the menu as Tools>Macros>stencil files>ThisDocument>FinalizeShape. Do you know what I have missed?

CAUSE
	The Tools > Macros > ThisDocument > FinalizeShape option is only available if your are editing a shape from an AgilePoint specific stencil.

RESOLUTION
	In order to get the Tools>Macros>ThisDocument>FinalizeShape option, you must be editing a shape in an AgilePoint based Stencil. One suggestion is to copy one of the out-of-the-box Stencils (can be found under [Drive]:\Program Files\Microsoft Office\Visio11\1033\Solutions\Ascentn BPM folder) as your base stencil and rename it to your customized stencil. You can then copy all the customized shapes that you have into this stencil and delete the existing one that you don’t need. After this you can use edit and convert the custom shapes into AgilePoint shape. Here is an example: For example, the following screen shot shows that AP Temp is a new stencil I copied from the Generic.vss file in the above folder. I can then File>Open and select this new vss file to edit. I then copied a shape (Generic object) from the Active Directory Objects stencil into this stencil.
	Now right mouse on the Generic object shape and select Edit Master>Edit Master Shape Now right mouse on the shape image and select Show ShapeSheet. Now you will find the Toos>Macros>ThisDocument>FinalizeShape option available in your menu. Select that option will bring up the following dialog to convert to AgilePoint shape:

Last Reviewed:
Keywords:

Guidelines and best practices for deploying InfoPath 2007 forms

MichaelDa — Wed, 05 Oct 2011 10:32:48 GMT

The information in this article applies to:

AgilePoint Suite v4.0 or later
Microsoft Office InfoPath 2007
Microsoft Office Forms Server 2007
Microsoft Office SharePoint Server 2007

TOPIC(S)

Microsoft Office InfoPath 2007
Microsoft Office InfoPath 2007, which is part of the 2007 Microsoft Office system, allows business to both design and fill out electronic forms. InfoPath is based on Extensible Markup Language (XML).

Microsoft Office InfoPath 2007 is becoming increasingly popular for use with AgilePoint BPMS, because it allows the business analyst and/or IT to develop attractive forms for BPM solutions in a fraction of the time required to create traditional coded forms. Conditional rules and data validation can be added to the forms without writing code.

Standard InfoPath forms are executed on the desktop. As a result, it is recommended that InfoPath be used with AgilePoint BPMS solutions under the following conditions:

InfoPath is licensed and installed on all of the desktops that will participate in the BPM project or need to view the form.
There is sufficient network bandwidth to download the InfoPath form template from the SharePoint document library each time the form is displayed.
The form rules and data validation can be created without writing code.
Secondary data sources are not required. Direct connections to data sources from the InfoPath form on the client desktop add complexity, performance delays and additional security configuration.
The data being collected in the form does not require encryption. Encrypted XML cannot be evaluated in the process instance at runtime.
Active forms in the Microsoft SharePoint 2007 document library can be limited to 2000 items at a time.

Microsoft Office Forms Server 2007

Microsoft Office Forms Server 2007 is a server product built on Microsoft Windows SharePoint Services 3.0 as an ASP.NET Version 2.0 application. It enables users to fill out Microsoft Office InfoPath 2007 forms by using a Web browser instead of, or in addition to, the Office InfoPath 2007 client program. Like standard InfoPath forms, InfoPath forms published to the Microsoft Office Forms Server are based on Extensible Markup Language (XML).

There is a lot of interest in Microsoft Office Forms Server 2007 as a user interface for AgilePoint BPMS because like standard InfoPath forms, it allows the business analyst and/or IT to develop attractive forms for BPM solutions in a fraction of the time required to create traditional coded forms. The primary advantage it offers over the full InfoPath client software is that Microsoft Office Forms Server 2007 renders the form in a browser window and does not require that the Microsoft Office InfoPath 2007 to be installed on the desktop. The second advantage is that it executes the form on the server and downloads a smaller HTML based form similar to an ASP.NET form. As a result of not having the Microsoft Office InfoPath 2007 client, it is recommended that Microsoft Office Forms Server 2007 be used with AgilePoint BPMS solutions under the following conditions:

Microsoft Office Forms Server 2007 licensing has been obtained or budgeted for the Microsoft SharePoint 2007 front end web servers. (It is not included in the Windows SharePoint Services 3.0 install.)
The form design is basic and can be created with a limited set of data controls.
The form does not require Jscript for conditional presentation or data validation.
The development team can support the use of managed code to create and maintain custom form functionality.
JavaScript and cookies can be enabled on the client browser.
Active forms in the Microsoft SharePoint 2007 document library can be limited to 2000 items at a time.

SUMMARY

This article specifically focuses on providing instructions for designing and deploying your InfoPath 2007 forms based on how you would like to display the InfoPath form to your end users.

The following details are some recommendations from Microsoft.

Before you create an InfoPath form template, you need to decide how you want to show the InfoPath form to your end users. You have two options:

Show InfoPath form to user in a Web browser (via Microsoft Office Forms Server 2007); or

Show InfoPath form to user in InfoPath client (via InfoPath client software)

DETAILS

Part A: Showing the InfoPath form in a Web browser

This part provides information about showing the InfoPath form to the user in a Web browser.

IMPORTANT: By default, Forms Server doesn't support InfoPath form templates that include JScript (i.e. Forms that include JScript will not be able to be rendered in a Web browser).

If you plan to show your InfoPath form using Forms Server in a Web browser, you have two options available when developing your InfoPath form:

Clean (No Managed Code and No JScript) using InfoPath Client Software
This option is best if the basic InfoPath form development functionality included within the browser-based InfoPath form can meet your requirements. This is a good approach for fast and easy development and deployment. This approach also maintains the business user friendly InfoPath development and deployment strategy.

If you associate an InfoPath form that does not have a managed code DLL to a process model in AgilePoint Envision, AgilePoint Envision will add JScript to the InfoPath form, making it unable to be rendered in a Web browser. Therefore, it is not supported at this time to publish this type of InfoPath form to SharePoint via AgilePoint Envision. It is necessary to publish the InfoPath form through the InfoPath client and make sure you remove the JScript before publishing. For more information, see Deploying the InfoPath Form to SharePoint section below.
Using Managed Code in the XSN using Microsoft Visual Studio 2005
If you want to incorporate some custom or advanced logic in your InfoPath form, then it is recommended to use the managed code approach to implement your logic. Design your form template in Visual Studio.NET 2005 using Microsoft Visual Studio 2005 Tools for the 2007 Microsoft Office System (VSTO 2005 Second Edition).

It is recommended that you design your form template in Visual Studio.NET 2005 using Microsoft Visual Studio 2005 Tools for the 2007 Microsoft Office System (VSTO 2005 Second Edition), even if you don’t plan to use managed code at the beginning. By default, Forms Server doesn’t support InfoPath form templates with JScript. If you want to incorporate some custom logic in your InfoPath form and you want to show your form in a browser, then it is recommended to use the managed code approach to implement your logic.

Download Microsoft Visual Studio 2005 Tools for the 2007 Microsoft Office System (VSTO 2005 Second Edition) using the link below:

http://www.microsoft.com/downloads/details.aspx?familyid=5e86cab3-6fd6-4955-b979-e1676db6b3cb&displaylang=en

The link below provides a lot of useful information about Microsoft Visual Studio 2005 Tools for the 2007 Microsoft Office System (VSTO 2005 Second Edition)

http://msdn2.microsoft.com/en-us/office/aa905543.aspx

The following screen captures show how to initiate the managed code project in Visual Studio 2005.

After designing and compiling in Visual Studio.NET 2005, you can prepare the XSN file (InfoPath form template that contains your graphical design, the managed code DLL, and other related files) by using the Publish Form Template feature via the “Design Tasks” task pane.

Settings to be done for displaying InfoPath 2007 in a Web Browser

The settings described here apply to both the clean and managed code approaches of InfoPath development and deployment.
NOTE: You can configure the settings described below using either the InfoPath client as described below, or with the Microsoft Visual Studio 2005 Tools for the 2007 Microsoft Office System (VSTO 2005 Second Edition).
Launch the InfoPath form template in design mode and click Tools > Form Options. The Form Options window appears.

In the “Category” field, click Compatibility, and in the “Browser compatibility” field, select the check box for Design a form template that can be opened in a browser or InfoPath.

Click OK.

Use the “Design Checker” option to check if your form is browser compatible. Click Tools > Design Checker. Make sure all InfoPath views are browser compatible.

When publishing the InfoPath form, make sure the check box for Enable this form to be filled out by using a browser is selected.

In SharePoint, to force the InfoPath form to be displayed in Web browser, at the Advanced Settings of your form library, under the “Browser-enabled Documents” section, select Display as a Web page and click OK to save the setting.

Document Name in AgilePoint Task List Web Part
NOTE: The settings described here apply to both the clean and managed code approaches of InfoPath development and deployment.
This part explains how to enable the InfoPath form to be displayed in a browser window when the document name is clicked in the AgilePoint Task List Web Part. The form library is configured to display the InfoPath form as a Web page as shown above. In the form library, when user clicks the New button on the tool bar, the InfoPath form is displayed in browser correctly. The user is able to submit the form and a process is triggered. But when the assigned user goes to the Task List Web Part, and clicks on the document name, the standard SharePoint error page appears.

During the deployment and set up of the AgilePoint SharePoint Integration, add the <assembly> entries in the web.config file under the LAYOUTS folder. This section is included in the Release Notes for AgilePoint version 4.0.
If you want to use the Microsoft Office Forms Server integration for InfoPath forms, there are some manual steps required. In order for the FormServer.aspx.cs file to be compiled at runtime, it needs some extra settings added to the web.config file located within the SharePoint LAYOUT folder. Those settings are not in the web.config by default.
NOTE: It is good practice to make a backup copy of the web.config file before making any changes.
On the machine where SharePoint is installed, modify the web.config file located here:
Local_drive:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\LAYOUTS\web.config
Copy the assemblies section within the compilation tag from the source below:
http://www.ascentn.com/Download/SharePoint_Webconfig.txt
Designing the InfoPath Form
When opening the InfoPath form from the Task List Web Part, the Submit and Close button appears on the top toolbar in a browser window. If the InfoPath form is open within a form library, the Submit and Close button will not appear. We recommend you to use the InfoPath default Submit button for submitting a new form.

The Submit and Close button is built on top of the default InfoPath Submit button. Hence, in your XSN, a Submit Option must be configured and the Submit button must be visible on the InfoPath top toolbar.

For submitting a new form, auto naming support is not provided by AgilePoint, because the auto naming capability provided by InfoPath is rich enough.

How to Configure the Submit Option and Form Auto-Naming

You can configure the auto naming when creating a data connection for a Submit Option. At the same wizard window that asks you for the form library URL, click the fx button beside the “File Name” text box to configure the auto naming.

Launch the InfoPath form template (.xsn) in design mode and click Tools > Submit Options. The Submit Options window appears.

Make sure the check box for Allow users to submit this form is checked.

Select the option button for Send form data to a single destination.

Select SharePoint document library from the drop-down list. Then click Add. The Data Connection Wizard window appears.

In the "Document library" text box, enter the form library URL.

IMPORTANT: You need to provide the form library URL here. If you only provide SharePoint site URL, InfoPath doesn’t know where to submit the form.

Click the fx button. The Insert Formula window appears.

Click the Insert Function button. The Insert Function window appears.

From the “Categories” field, select Date and Time, and from the “Functions” field, select now.

Click OK.

The function now() is inserted in the "Formula" text box. Click OK to save the setting.

In the “Data Connection Wizard” window, click the Next.

Enter a name for this data connection for submit, then click Finish to save the setting.

From the Submit Options window, at the “Choose a data connection for submit” drop-down list, select the data connection that you have just created.

Click OK.

The setting for the Submit Option is complete. In order to show the Submit button when the InfoPath form is displayed in a browser, click Tools > Form Options. In the “Category” field, select Browser and make sure the check box for “Submit” is selected.

NOTE: If you do not see the Browser category, this means your form is not browser compatible. To make it browser compatible, click the Compatibility category and under “Browser compatibility”, select the check box for “Design a form template that can be opened in a browser or InfoPath”.

Click OK to save the setting.

Save the InfoPath form template. Then publish it to the form library in SharePoint. The URL of the form library should be the same URL you entered when configuring the data connection for Submit as above.

The figure below shows the InfoPath form can be submitted successfully if the submit options are configured correctly.

The figure below shows the simple auto-naming has been applied to the form name (xml file name) once the form is submitted.

Deploying the InfoPath Form to SharePoint
The following table provides information about deploying InfoPath forms to be served to the end-user in SharePoint via a Web browser.

InfoPath 2007 Form Template (XSN) Details
Clean (i.e. XSN is designed in the InfoPath client, no managed code DLL in XSN, no Jscript in XSN, and Visual Studio.NET 2005 is not involved)
Can show form in a Web browser.

Deployment of XSN from within Envision to SharePoint is not supported, must use InfoPath client software to publish.

Quick Tip: If you accidentally asociate your XSN to a process template and AgilePoint Envision has added JScript into your XSN, which makes your XSN unable to be rendered in a Web brower, you can use the Remove Code feature in InfoPath client to remove the JScript via (Tools > Form Options > Programming > Programming Lauguage > click the Remove Code button).
JScript in XSN
Microsoft does not support showing the XSN in a Web browser.
Managed code DLL in XSN (i.e. Using Microsoft Visual Studio 2005 Tools for the 2007 Microsoft Office System (VSTO 2005 Second Edition))
Deployment of XSN from within Envision to SharePoint is supported.

The XSN is first added to the SharePoint Central Admin, then it is activated to the SharePoint site as a content type, and finally a form lib is created based on the content type.

Envision will not add JScript to the XSN if the XSN contains a DLL, so that it can be displayed in a Web browser.

Part B: Showing the InfoPath form in the InfoPath client
If you plan to show your InfoPath form using the InfoPath client, you can design your InfoPath form template in the InfoPath client. You can use JScript to implement your logic.

IMPORTANT: When creating a form template using the InfoPath client, make sure you do not check the option “Enable browser-compatible features only” (see screen capture below), if you want to use JScript. If this option is checked, InfoPath forces you to use managed code.

To select Jscript as the code language, go to Tools > Form Options > and select JScript as shown below.

The following screen captures show how to perform the scripting within the InfoPath client.
Designing the InfoPath Form
The Submit and Close button appears on the InfoPath client toolbar. The action behind the button is accomplished by an AgilePoint ActiveX control. AgilePoint JScript functions in the XSN are required to support the ActiveX control.

When associating the XSN to a process template in AgilePoint Envision, AgilePoint Envision adds the AgilePoint JScript functions into the XSN automatically if:

JScript or VBScript is selected for “Form template code language” via (Tools > Form Options > Programming).
No form template code language is selected explicitly. InfoPath will still display “Visual Basic” as the default value even if you never change the value for the drop-down list of “Form template code language”.
No DLL exists in the XSN.
For submitting a new form, auto naming is supported. Two options are available to support auto naming:

Web Service: A sequence number is included in the file name. The file name format can be configured in AgilePoint Envision.
WebDAV: File name format can’t be configured in AgilePoint Envision. Current date and time is provided as the default naming format. You can write JScript to change the naming format.
Deploying the InfoPath Form to SharePoint
The following table provides information about deploying InfoPath forms to be served to the end-user in SharePoint via the InfoPath client software.
InfoPath 2007 Form Template (XSN) Details
Clean (i.e. XSN is designed in the InfoPath client, no managed code DLL in XSN, no Jscript in XSN, and Visual Studio.NET 2005 is not involved)
Deployment of XSN with JScript from within AgilePoint Envision to SharePoint is supported.
If you do not need to implement additional logic using JScript, AgilePoint Envision will still add AgilePoint JScript functions into your XSN for integration purposes.
JScript in XSN
Deployment of XSN with JScript from within AgilePoint Envision to SharePoint is supported.
A copy of the XSN is inserted into the “Forms” folder under the form library as the document template.
Quick Tip: In the InfoPath client, design the form template and write any JScript for the form logic as needed. Then in AgilePoint Envision, associate the XSN when creating an InfoPath form library based process model. Design the process flow. Upload the process model to AgilePoint Server, then publish the InfoPath form template to SharePoint. A form library will be created.
Quick Tip: In the Advanced Settings of the SharePoint form library, select Open in the client application in the “Browser-enabled Documents” field.
Managed code DLL in XSN (i.e. Using Microsoft Visual Studio 2005 Tools for the 2007 Microsoft Office System (VSTO 2005 Second Edition))
Not supported.

Last Reviewed:
Keywords:

Receive exception error while initalizing the AgilePoint Server 4.0.1 64-bit installation

MichaelDa — Wed, 05 Oct 2011 10:32:08 GMT

The information in this article applies to:

AgilePoint Server 4.0.1 64-bit Installation

ERROR
	You may encounter the following error when installing AgilePoint Server 4.0.1 64-bit version. Exception occurred while initalizing the installation: System.BadImageFormatException: Attempted to load a 64-bit assembly on a 32-bit platform. Use ReflectionOnlyLoad() instead if trying to load for reflection purposes.

STEPS TO REPRODUCE
	NA.

DETAILS
	The workaround for this issue can be found at http://blogs.msdn.com/heaths/archive/2005/10/24/windows-installer-on-64-bit-platforms.aspx. Below in an extract from the blog: Windows Installer on 64-bit Platforms Beginning with Windows Installer 2.0 installation developers can write installation packages that target 64-bit platforms. At first only IA64 was supported but support for AMD64 — now collectively referred to along with EM64T as x64 — was added in Windows Installer 3.0. Many questions are asked regarding how to author 64-bit packages and merge modules so I will attempt to enumerate and briefly explain the available resources here. The point of authoring a package differently for 64-bit platforms is to deploy 64-bit binaries and write registry values for 64-bit access correctly. While you can install a 32-bit application on 64-bit Windows, files for 32-bit execution will be redirected to different folders and some registry values for 32-bit access will be redirected to a different parent registry key. Before you can control where files are installed on 64-bit platforms you must author your installer database as a 64-bit installation package. To do this you must set the Template summary property to either Intel64 or x64; Intel, Intel64, and x64 are all mutually exclusive. For these values to be effective the database schema must be set to at least 200. About Windows Installer on 64-bit Operating Systems 64-bit Windows Installer Packages To make sure that the file system and registry aren't redirected when installing 64-bit executables, their support files, and registry values for 64-bit access, components that contain those files and registry values must be marked appropriately with the `msidbComponentAttributes64bit` (256) attribute in the Component table and must target the appropriate 64-bit directories. Components and actions can also be conditioned to install or run only on 64-bit platforms. Using 64-bit Windows Installer Packages System64Folder property ProgramFiles64Folder property CommonFiles64Folder property VersionNT64 property Intel64 property Msix64 property ICE80 If you're authoring a 64-bit package with both 32- and 64-bit binaries, make sure that they resolve to different source and target directories when considering how they lay out on installation media and how files will be extracted during an administrative install otherwise 32- and 64-bit files will overlap each other and cause problems. If a 32-bit component is contained in both a 32-bit installation package and a 64-bit installation package it may have the same component ID but 32- and 64-bit components should have different component IDs, just as 32- and 64-bit products should have different product codes. Product Codes For 64-bit installation packages you'll probably want to run 64-bit custom actions. 64-bit executables will run in either a 32- or 64-bit custom action server correctly but script custom actions must be marked as either running in a 32- or 64-bit script host by being marked appropriately with the `msidbCustomActionType64BitScript` (4096). Custom action scripts are not recommended, however. 64-bit Custom Actions If you want to author merge modules that contain 64-bit binaries and support files and want to merge them into a 64-bit installer package, you'll also need to set the Template summary property to either Intel64 or x64. Only Intel64 merge modules can be merged into Intel64 installer packages, and only x64 merge modules can be merged into x64 installer packages. 32-bit merge modules can be merged into any installer package. Using 64-bit Merge Modules Merge Module Summary Information Stream Reference To help validate that an installation package is authored correctly to install 64-bit binaries and support files and registry values, be sure to run validation — especially ICE80. There are also error codes and Windows Installer error messages you might want to handle that relate to installing 64-bit packages. 1633 — This installation package is not supported on this platform. Contact your application vendor. 2401 — 64-bit registry operation attempted on 32-bit operating system for key [2]. 2943 — This version of Windows does not support deploying 64-bit packages. The script [2] is for a 64-bit package.

Last Reviewed:
Keywords:

Applying SharePoint Service Pack 1 Causes APWS Connection Issue

MichaelDa — Wed, 05 Oct 2011 10:31:13 GMT

The information in this article applies to:

AgilePoint SharePoint Integration
SharePoint Service Pack 1

SYMPTOMS
	After installing SharePoint Service Pack 1, some SharePoint machines are unable to connect to services using APWS (i.e. Unable to browse any of the APWS services on the SharePoint machine). An error message may be similiar to: Unable to connect publishing custom string handler for output caching. IIS Instance Id is '1652300900', Url is 'http://axnysp1/APWS/AgileParts.asmx'.

CAUSE
	On some SharePoint Server machines, applying the SharePoint Service Pack 1 might change the web.config of the SharePoint Virtual Server. Since APWS does not have a web.config file, and uses the web.config of the SharePoint Virtual Server, applying the SharePoint Service Pack 1 may cause connection problems for the AgilePoint SharePoint Integration.

RESOLUTION
	Download the web.config file attached to this article and place it in the root directory of APWS webservice. The path should be something like this: C:\Program Files\Ascentn Corp\SharePoint2007\APWS After this, try to access the APWS from the following URL: http://<sharepoint server address>/APWS/AgileParts.asmx If you get the Web Methods window, then the problem is fixed.

Last Reviewed:
Keywords:

How to setup AgilePoint reporting using SQL Reporting Services and MOSS 2007

MichaelDa — Wed, 05 Oct 2011 10:04:30 GMT

The information in this article applies to:

AgilePoint Suite
AgilePoint MOSS 2007 Integration
SQL Reporting Services

GOAL(S)
	This article provides information for how to setup AgilePoint reporting using SQL Reporting Services and MOSS 2007.

SUMMARY
	NOTE: The information below is basic SharePoint functionality, this article merely addresses the available functionality. Please contact your MOSS Services Company for support questions.

SOLUTION
	Above all, make sure that the SQL Server Report Server has been installed successfully and make sure both “SQL Server (MSSQLSERVER)” and “SQL Server Reporting Services (MSSQLSERVER)” have been started. Open IIS and navigate to Web Sites > Default Web Site. Right-click on Reports and select Browse to view it. Install the SQL Server 2005 (SP2) and the SPS (add-in). After having installed successfully, the following steps should be done. Step 1: Check the file rsreportserver.config Locate the file rsreportserver.config, the default location is “\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\rsreportserver.config”, and find the String “<UrlRoot>http://Hostname/reportserver</UrlRoot>”. NOTE: The Hostname is the Hostname for which Report Server has been installed. NOTE: If the Reports haven’t been installed in the default Port 80, add the Port number as below: “<UrlRoot>http://Hostname:PortNumber/reportserver</UrlRoot>” The PortNumber is the PortNumber of the Web site in which the Reports have been installed. Step 2: Configure SSRS Open SQL Server Reporting Services Configuration and select Database Setup. Click New to create a new SSRS database and check the checkbox Create the report server database in SharePoint Integrated mode. Click OK. SQL Server will execute several processes automatically. Click Apply when it finishes. You will find the color of the SharePoint Integration changes to green and the “Report Manager Virtual Directory” is no longer enabled. Step 3: Configure MOSS First open the SharePoint 3.0 Central Administration, then navigate to the Application Management page, the links for Reporting Services are displayed. Click the Manage integration settings link, and configure the Reporting Services Integration with the Report Server Web Service URL and the Authentication Mode as shown below. Click OK to return to the Application Management page. Click the Grant database access link. Enter the Server Name with the correct Hostname, and select Default instance. Click OK. A credential window is displayed. Before entering the credentials, make sure the SSRS database can be accessed via the Web service and Windows service accounts, otherwise an error message of connecting to Report server failed would appear. It is also recommended to add the Network Service Account to the WSS_WPG group. Restart IIS and return to the Application Management page. The Microsoft SQL Server - MOSS Integration is finished. Step 4: Publish SSRS object in MOSS First login to the SharePoint site and click the Site collection features link under the Site Collection Administration section. Make sure the Report Server Integration Feature is active. Open or create a Document Library to use for the Report Service. Click the Document Library Settings in document library settings, then select Yes to allow management of content types. Add three kinds of content types (Report Data Source, Report Builder Model, Report Builder Report) from the Available Site Content Types to the box below Content types to add. The content types in the Settings page of the document library will be shown. Create a new Report Data Source by clicking the New drop-down list and then Report Data Source. Then enter the correct Connection string (e.g. Data Source=. ; Initial Catalog=AP; Integrated Security=True), then click OK. NOTE: In this case, the AgilePoint database name is AP, please change it in accordance with the name of your AgilePoint database. Upload the AgilePoint Report files that you want to use from the rdl folder in the AgilePoint EnterpriseManager directory by clicking the Browse button. Modify the DataSource of the AgilePoint Report file uploaded by clicking the Manage Data Sources option as shown below. The original state of the file’s Data Source is like the screen shown below, click the Name link to change the Data Source Link to the Report Data Source that you created earlier by clicking the Ellipses button. Click OK. The page will look like the screen below. As implemented here, the report defined by AgilePoint can be used in MOSS 2007. Step 5: Configure the Web.config file Locate the Web.config in the EnterpriseManager installation directory. Modify the node of <appSettings> with something similar to below. Reference: The AgilePoint Server Url, Report Service Url, and Report Server Url can be found by expanding the related Web Site as shown below. The Document Library Url is the Url of the Document Library opened or created above, which include the Reports defined by AgilePoint uploaded. Login to Enterprise Manager and click the Configuration link. The Reports that have been uploaded in the SharePoint document library will be displayed in the Report Browser. Select one of the reports and type a Report name in the Label text box, the selected Report will be added under the Report Management section. When you click the link for the Report name you added, the report will show in the Enterprise Manager. .

Last Reviewed:
Keywords: