Archive for January 2012

Courion Tip – Restricting the number of systems a user can request

The scenario is this… We have several similar systems (same target type) with different approvers. So, a user could fill out a request for access to system1, system2, and system3. BUT, in 7.80, there is no granularity in the request. If the approver for system3 logs in, and approves the request, then the user by default would be granted access to system1 and system2.

Making a separate workflow for each system involves too much overhead and maintenance.  The best option would be to only allow the user to request one system at a time, and handle figuring out who the approver is as a separate issue. The question is how to restrict the user to a single choice.

The answer is to make a copy of the *.xslt file, and replace “checkbox” with “radio” so that the user is presented with a Radio Button interface. I am using – not the default *.xslt, but instead the BuildIdentityMapCtrl.xslt.

Here are lines 246 thru 250 – yours may differ….

<xsl:template name=”BuildSortTableRows”>
<!– output the addline –>
<xsl:text disable-output-escaping=”yes”>tSORTTABLE_</xsl:text>
<xsl:value-of select=”../../../../name”/>
<xsl:text disable-output-escaping=”yes”>.AddLine(“&lt;center&gt;&lt;INPUT TYPE=‘radio’ NAME='</xsl:text>


Posted January 26, 2012 by mmdmurphy in Courion Tip

Tagged with

Courion Tip – ODBC

The confgiuration managers are 32-bit applications.

The 32-bit ODBC Data Soruce Administrator must be used to configure DSNs for 32-bit applications to use.

To run the 32-bit version of the ODBC Administrator, in the Windows Run dialog box, type: %windir%\syswow64\odbcad32.exe

System data sources created in the 64-bit ODBC administrator are only visible to 64-bit applications. System data sources created in the 32-bit ODBC administrator are only visible to 32-bit applications. 32-bit driver data sources are stored in the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBC.INI (which is only visible to 32-bit applications) rather than the standard location, HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI.

32-bit ODBC drivers are available to 32-bit applications running in the WOW64 layer, but not to 64-bit applications.

On 64-bit Windows platforms, there is both a 32-bit and a 64-bit version of ODBC Administrator. The 64-bit ODBC Administrator is located in the standard location: Administrative tools in Control Panel. The 64-bit version of the ODBC Administrator only lists 64-bit ODBC drivers and data sources.

Make sure you have the 32 bit version of the ODBC driver.

Additionally, if you are using 7.80 or higher, the 64 bit system hosting IIS and the CF (Connector Framework) must be switched into 32 bit compatibility mode along with having the 32 bit version of the .NET framework. (The CF is where the PMM or Connector that needs ODBC is actually being executed.) This same requirement applies to the CFM (Connector Framework Manager) in order to configure the targets in the Connector Configuration Manager.

See KB from Microsoft …


By the way, I switched what I was doing to use the ADO connector instead.

Posted January 25, 2012 by mmdmurphy in Courion Tip

Tagged with

Courion Tip – SQL Server Connector

The documentation on page 297: Configuring_PMMs_Connectors_and_Agents.pdf
AdminUser — The name of the Microsoft SQL Server administrative user that can log on to the SQL server. This user must be a SQL login user, a member of the SQL Server SECURITYADMIN fixed server role, and the DB_ACCESSADMIN database role.

  • I am told it does support named instances.. such as Server\Instance, but since I am not yet able to establish a connection, I cannot verify this.   *When you get the connector to work, it works as show.
  • Basically, your server has to be mixed mode, and the privileged account must be a SQL (not windows, not domain) account
  • There is a configuration parameter that is not mentioned in the documentation…IgnoreAccessGroup. I don’t have a clear understanding of what this is, and I don’t know if it’s ok to leave this unassigned. (*When you get the connector to work, it will tell you valid settings are yes or no)
  • I am using the same configuration information that I used to set up the PMM, which is working, so I know that I have the correct user name and password, BUT I cannot get the AMM to configure correctly. I keep getting an “unable to verify connection”.  *You need the patch below.

The Connector and PMM for Microsoft SQL Server depend upon the SQL-DSO activeX object, which is no longer distributed with the SQL Server client that is packaged with SQL Server 2008 and 2008 R2. To address this missing dependency, download and install Microsoft SQL Server 2005 Backward Compatibility Components on the Courion Server, or on the CF/CFM machine running the Connector/PMM accessing SQL Server 2008. This assumes you have installed the SQL Client Software, as directed in the prerequisites for the Connector/PMM for SQL Server:

The SQL Server client must be installed on each server in which the Connector
Framework or Connector Framework Manager is installed. Note that the SQL
Server Management Studio Express client cannot be used—you must install the
regular SQL Server client.

Microsoft SQL Server 2005 Backward Compatibility Components are packaged with the Microsoft SQL Server 2008 Feature Pack, available at the following Microsoft Downloads location:

Microsoft SQL Server 2008 Feature Pack, August 2008

Posted January 19, 2012 by mmdmurphy in Courion Tip, SQL

Tagged with

SSIS Derived Column forcing data type changes
He’s right. If you open the advanced editor, it’s right there.

Posted January 16, 2012 by mmdmurphy in SQL

Courion Tip – “auxilary” tools

Just a list of tools that are handy to use with Courion….

Posted January 11, 2012 by mmdmurphy in Courion Tip

Tagged with