Showing results for 
Show  only  | Search instead for 
Did you mean: 

WFMv4.04 error in DataMinorEdit.asp - ODBC error reported on Data Elements

For those of you interested or affected by this:

The 4.04 WFM / AdminStudio 8 patch has introduced the following error when viewing DataElements in the TEMPLATE view of WFM4.
Microsoft OLE DB Provider for ODBC Drivers error '80040e14'
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'Validation'
/Templates/DataMinorEdit.asp, line 761

The reason is the DataMinorEdit.asp file in C:\AdminStudioEnterprise\wwwroot\templates has some errors in line 761 and 766

For those affected, I have fixed the errors and attach a file called "DataMinorEdit.asp.txt".

To apply the fix, please backup your original file "C:\AdminStudioEnterprise\wwwroot\templates\DataMinorEdit.asp" by renaming it to:


You can then copy the attached file to the same location and rename it to remove the ".txt" off the end.

Your Web GUI front end to the SQL database will now display the data correctly and cure the error.


Macrovision support , please advise your techies to fix the 4.04 download - Thanks.
(5) Replies
This is probably not an issue with the 4.04 hotfix.

The instructions accompanying this hotfix require that the database be upgraded. If the database has not been ugraded it will cause this error.

Please refer to the following:

Please be advised that none of the workflow item data validation instructions will work without the schema upgrade.
Thanks for your reply David.

The database schema was upgraded as part of the update.

It may not be the 4.04 patch, but I only got this error after applying the 4.04 patch.
The error message in your post says that the Validation column is missing from the AMS_DataMinorItemTpl table. One of the things that the SQL Script is doing is adding this column. You may want to run the SQL Script again against your database. It will not alter anything if it had been run previously.

Thanks for your reply and apologies for not responding sooner, it's been hectic.

After further investigation we are both correct - kind of ... 🙂

You are correct for people running the "80VP1Upgrade.sql" script against the v8 database on SQL server versions 2005 onwards.

However, we run SQL server 2000 and as such, this script fails to run and fails to create that column.

The reason the "80VP1Upgrade.sql" script fails to run on SQL server 2000 is because :

SQL server 2005 onwards calls the following objects these names :

"sys.objects" and "object_id"


SQL Server 2000 calls those objects :

"sysobjects" and "id"

Hence, the supplied "80VP1Upgrade.sql" script in the WFM 4.04 patch runs fine on SQL server 2005 onwards, but fails on SQL server 2000.

We made changes to the line in the script as follows to get it to run on SQL Server 2000.

Original Line:

IF EXISTS (SELECT * FROM sys.objects WHERE object_id = OBJECT_ID(N'[dbo].[AMS_ValidationExpression]') AND type in (N'U'))

Edited Line:

IF EXISTS (SELECT * FROM sysobjects WHERE id = OBJECT_ID(N'[dbo].[AMS_ValidationExpression]') AND type in (N'U'))

So, anyone running SQL server 2000 who experienced the error as listed in the 1st post should restore their backed up DataMinorEdit.asp and apply the above fix to run the SQL script and update the DB schema accordingly.

Hope this clears up any confusion.

David, could the 4.04patch mention the above - so people not running SQL 2005 Server onwards will be aware of what action to take ?

Hi Atlas,

Sorry for not replying sooner, I was out of the office last week. Thank you for reporting this issue with SQL 2000. We have updated the hotfix download to contain a SQL file that does not exhibit this behavior.
I'm sorry for any inconvenience this has caused and thank you for digging into this issue to discover the cause.

Many Thanks!