vargam's blog

Appyling 15.1.3.8850 patch generating error

vargam — Sat, 21 May 2011 02:33:53 -0400

Trying to install this patch I am getting the following error:

Truncating iMISTable...
TRUNCATE TABLE IMISTable
Bulk-Loading iMISTable...
SQLState = S1000, NativeError = 0
Error = [Microsoft][ODBC SQL Server Driver]Invalid format file version

Can anyone shed any light?

InvalidCastException: Specified cast is not valid.

vargam — Thu, 14 Apr 2011 01:01:41 -0400

The error extract that is contained below comes from the application event log from the App server. It is registered every time any of the following are attemepted:

Try to create a new object - when selecting the table to include in the Database tab.
Try to add a new field into an existin object
Try to create objected from the user defined tables

In order to try to address I have:

Run a series of functions from the DB Repair utility
Rebuilt the business objects using the DB Upgrader
Run a trace and extracted the SQL, run it, and had no errors returned.

I also had a look through the Community and thought that this link was relevant (but beyond my scope of understanding). http://www.imiscommunity.com/refreshing_view_meta_data_revisited

When I ran the 2nd query in this item I got the following

vGroupInfo The object 'vGroupInfo' does not exist or is invalid for this operation.

This object was the only item not in the list of the first query,

Campaign Management errors

vargam — Thu, 11 Mar 2010 22:40:52 -0500

I am working at a customer, CBM Australia. We are trying to create a campaign structure. When we get to adding source code details, whenever we try to add an Insert or Source List (simple query) to the campaign, we get the following 2 errors:

Error - Value must be unique with a System

Error - The 'Name' property should not be Null

These errors have been occurring intermittently since go live. We logged an SMR but as tech support could not recreate the issue they could not progress it. We have tried to run a trace (output attached) but can't really make any sense of it. We now cannot create any new source codes and cannot generate campaign output. At points in the past, by changing details in the campaign profile we could get the details to save but this no longer works. I am guessing it is related to the PAckage tables but can't get any further than this.

Customer Portfolio screen is not active when IQA returns results

vargam — Tue, 23 Feb 2010 19:27:53 -0500

I have attached a link to a brief video that demonstrates this issue.

Essentially, when using an IQA query that has been set up to return details to the Customer Portfolio, the query runs, the list is generated in an IQA window and a record is selected. When this occurs, the results set is returned to the results pane in the imis customer portfolio, but the cust portfolio is completely inactive. You cannot enter a new record, select a record from the results set, no record is returned to the customer screens, etc.

Patching eSeries to work with new version of Payflow

vargam — Wed, 06 May 2009 12:23:22 -0400

Sorry for the cross post but am hoping to get as much info back on this as possible.

See http://www.imiscommunity.com/patching_eseries_to_work_with_new_version_o...

Implementation of an IQA query framework

vargam — Wed, 18 Mar 2009 18:21:21 -0400

I am trying to find examples of customers where IQA has been used to create some kind of hierarchical framework.

I am looking for examples of a core library of queries and business objects, such as active members, regional breakdown structures, paid through status, specific event attendance, etc, that are then being used to construct second and subsequent level queries, such as active members who attended a specific event by joining 2 or more existing base queries.

Automated Responses in Marketing Suite

vargam — Tue, 26 Aug 2008 23:53:41 -0400

We have been dealing with a number of issues in relation to the auto response allocation process in Marketing Suite. This has ranged from source codes with 10 targets showing 200 responses, to entire campaigns where no response data being recorded. In trying to analyse the issues, a number of things have become apparent:

There does not appear to be any documentation that provides any detail on how the automated response processing is intended to work.