Home | Forums | Contact | Search | Syndication  
 
 [login] [create account]   Sunday, May 5, 2024 
 
slxdeveloper.com Community Forums  
   
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
 Administration Forums - Upgrades
Forum to discuss upgrading SalesLogix from version to version. View the code of conduct for posting guidelines.
Forums RSS Feed


 Back to Forum List | Back to Upgrades | New ThreadView:  Search:  
 Author  Thread: Which SP was it?
Phil Parkin
Posts: 819
Top 10 forum poster: 819 posts
 
Which SP was it?Your last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 16 Feb 10 6:04 AM
Does anyone know in which SP the field MODIFIEDDATE on PLUGIN became MODIFYDATE?

I have a partially upgraded db & it's not behaving...

Thanks!
[Reply][Quote]
Steve Robertson
Posts: 146
 
Re: Which SP was it?Your last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 16 Feb 10 6:45 AM
Hi Phil,

I think it was SalesLogix 7.0, it should be in the "SalesLogix v6.2.x to 7.0 Upgrade" bundle.

Cheers,

Steve
[Reply][Quote]
Phil Parkin
Posts: 819
Top 10 forum poster: 819 posts
 
Re: Which SP was it?Your last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 16 Feb 10 6:50 AM
Thanks Steve, but I'm seeing the error in 6.2.6 executables - if I try to open a plugin in Architect, I see an "invalid field 'ModifyDate'" message, so I think it must be a 6.2.x SP ...
[Reply][Quote]
Steve Robertson
Posts: 146
 
Re: Which SP was it?Your last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 16 Feb 10 7:07 AM
I don't see anything in the 6.2 SP 6 documentation referring to the ModifyDate field in the Plugin table.

It is mentioned in the "Upgrading Sage SalesLogix from Version 6.2.x to 7.5.pdf" which says the ModifyDate field in the Plugin table appeared in SalesLogix v7.0.

How far through the upgrade are you?
[Reply][Quote]
Phil Parkin
Posts: 819
Top 10 forum poster: 819 posts
 
Re: Which SP was it?Your last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 16 Feb 10 7:59 AM
Well, if only it were that simple....

I'm doing some work for a new customer on their (apparently) 6.2.6 database. Everything seems to work fine in 6.2.6.1007 on the client and they just want a few changes.

But when I fire up Architect and try to open a plugin, I get the error. Architect 6.2.6.1007 definitely appears to be looking for Plugin.ModifyDate, because if I add it as a new field in SSMS, the error goes away.

I was not involved with this db before and therefore can only guess at its upgrade history by looking at the installed bundles. These are the SLX ones that appear on the 'Bundles' page:


SalesLogix Advanced 6.2.0 21/07/2004 18:14
SalesLogix - Advanced
SalesLogix Web 6.2.0 21/07/2004 13:35
SalesLogix 6.2 Web Bundle
SalesLogix Web Customer Portal 6.2.0 09/11/2004 11:18
SalesLogix 6.2 Web Customer Portal Bundle
SalesLogix v6.2 Service Pack 1 6.2.1 25/02/2005 13:51
SalesLogix Service Pack 1 for 6.2
SalesLogix Web Host v6.2 Service Pack 1 6.2.1 18/01/2005 10:46
SalesLogix Web Host Service Pack 1 for 6.2
SalesLogix 6.2 AIS Adapter Schema Support 1.0.0 22/03/2005 16:21

SalesLogix 6.2 AIS Adapter UI Support 1.0.0 30/03/2005 09:45

SalesLogix 6.2 AIS Integration Log Support 1.0.0 09/03/2005 10:03

InfoPortal 1.0.5 22/03/2005 21:15

SalesLogix v6.2 Service Pack 3 6.2.3 13/10/2005 08:48
SalesLogix Service Pack 3 for 6.2
SalesLogix Advanced v6.2 Service Pack 3 6.2.3 25/08/2005 16:45
SalesLogix - Advanced Service Pack 3 for v6.2
SalesLogix Advanced v6.2 Service Pack 4 6.2.4 20/03/2006 14:29
SalesLogix - Advanced Service Pack 4 for v6.2
SalesLogix WebPhone v6.2 Service Pack 5 6.2.5 17/04/2006 12:41
SalesLogix WebPhone Service Pack 5 for 6.2
SalesLogix Web Customer Portal v6.2 Service Pack 5 6.2.5 17/04/2006 12:41
SalesLogix Web Customer Portal Service Pack 5 for 6.2
SalesLogix v6.2 Service Pack 6 6.2.6 03/01/2007 14:25
SalesLogix Service Pack 6 for 6.2
SalesLogix Web v6.2 Service Pack 6 6.2.6 08/12/2006 02:59
SalesLogix Web Service Pack 6 for 6.2



--Edit The weird part. If I remove Plugin.ModifyDate, I get an error in the Sales client.

I'm just hoping that there's a bundle which fixes the whole mess.
[Reply][Quote]
Lane
Posts: 121
 
Re: Which SP was it?Your last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 16 Feb 10 8:42 AM
Did you try,
looking at the dll's for version issues in the provider service and client machine
Or port the system to a clean 626 machine.
[Reply][Quote]
Phil Parkin
Posts: 819
Top 10 forum poster: 819 posts
 
Re: Which SP was it?Your last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 16 Feb 10 9:44 AM
I'm working on a clean VM environment - I restored a backup of their db in it and did a clean 6.2.6 install.

So I still reckon it's an issue with the DB ... somewhere in there.
[Reply][Quote]
Steve Robertson
Posts: 146
 
Re: Which SP was it?Your last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 16 Feb 10 10:29 AM
Just checked in slx_eval 6.2.6 database there is no ModifyDate field in the Plugin table.

What about running slxprofiler and see what is going on?
[Reply][Quote]
Phil Parkin
Posts: 819
Top 10 forum poster: 819 posts
 
Re: Which SP was it?Your last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 16 Feb 10 10:46 AM
I just loaded it - and get the same error in Architect 6.2.6.1009.

Here is the EXECUTED SQL:


SELECT A1.PLUGINID, A1.TYPE, A1.MODIFIEDDATE, A1.READONLY, A1.USERID, A1.DATACODE, A1.RELEASED, A1.DEV, A1.NAME, A1.MODIFYDATE, A1.COMPANY,
A1.COMPANYVERSION, A1.AUTHOR, A1.FAMILY
FROM PLUGIN A1
WHERE ((A1.BASEDON IS NULL OR A1.BASEDON = '') OR
(A1.BASEDON='X')) AND (A1.TYPE IN (28, 3))
ORDER BY A1.NAME ASC, A1.MODIFIEDDATE ASC


So it's looking for both MODIFIEDDATE and MODIFYDATE on PLUGIN - talk about too much of a good thing.
[Reply][Quote]
Steve Robertson
Posts: 146
 
Re: Which SP was it?Your last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 16 Feb 10 11:04 AM
I'm running Architect 6.2.6.1007


SELECT A1.PLUGINID, A1.TYPE, A1.READONLY, A1.USERID, A1.DATACODE, A1.RELEASED, A1.DEV, A1.NAME, A1.MODIFIEDDATE,
A1.COMPANY, A1.COMPANYVERSION, A1.AUTHOR, A1.FAMILY FROM PLUGIN A1
WHERE ((A1.BASEDON IS NULL OR A1.BASEDON = '') OR (A1.BASEDON='X')) AND (A1.TYPE IN (28, 3))
ORDER BY A1.NAME ASC, A1.MODIFIEDDATE ASC


No idea what is up with your database.

[Reply][Quote]
Phil Parkin
Posts: 819
Top 10 forum poster: 819 posts
 
Re: Which SP was it?Your last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 16 Feb 10 11:23 AM
OK, ... I meant 1007.

When I said I loaded 'it', I meant the EVAL database.

So I guess that would suggest that my environment is somehow stuffed up.

If you run the following query


select fieldname, displayname from sectabledefs
where tablename = 'ticket'


do you see ModifyDate or ModifiedDate? I see ModifyDate in both DBs I have here (not that I am sure what the consequences of that are).
[Reply][Quote]
Steve Robertson
Posts: 146
 
Re: Which SP was it?Your last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 16 Feb 10 11:34 AM
I see MODIFYDATE and Modifydate for Ticket.

For Plugin table I see MODIFIEDDATE with no displayname.
[Reply][Quote]
Phil Parkin
Posts: 819
Top 10 forum poster: 819 posts
 
Re: Which SP was it?Your last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 16 Feb 10 12:04 PM
OK, I am losing the plot & maybe should take a break with some beer (interested? )

If I run the previous query for PLUGIN, rather than TICKET, I see ModifiedDate.

So, somehow, I need to work out why Architect is looking for ModifyDate in PLUGIN, even on the EVAL database. I'm pretty much clueless at this point - definitely time for that beer.

Thanks for your help & suggestions Steve.
[Reply][Quote]
Phil Parkin
Posts: 819
Top 10 forum poster: 819 posts
 
Re: Which SP was it?Your last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 17 Feb 10 2:37 AM
A new day and a fresh brain have helped me solve this.

I searched the registry for MODIFYDATE and found it under this key:

HKEY_USERS\S-1-5-21-2428423840-2009784418-1064744888-500\Software\SalesLogix\Architect\ManagePlugins\Columns

Changing column4 from MODIFYDATE to MODIFIEDDATE did the trick.

That key must have been there from a previous (and newer) SLX installation on the VM I am using (which had been deinstalled - though clearly not removing all traces of itself). Thanks again Steve.

Phil
[Reply][Quote]
 Page 1 of 1 
  You can subscribe to receive a daily forum digest in your user profile. View the site code of conduct for posting guidelines.

   Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
 

 
 slxdeveloper.com is brought to you courtesy of Ryan Farley & Customer FX Corporation.
 This site, and all contents herein, are Copyright © 2024 Customer FX Corporation. The information and opinions expressed here are not endorsed by Sage Software.

code of conduct | Subscribe to the slxdeveloper.com Latest Article RSS feed
   
 
page cache (param): 5/5/2024 6:29:06 AM