Re: Verity issues with MX 7
just glancing but the first link threw an Access Denied error the second link threw a cf error - Original Message - From: "John Crawford" <[EMAIL PROTECTED]> To: "CF-Talk" Sent: Monday, May 22, 2006 5:30 PM Subject: Verity issues with MX 7 > My company recently upgraded a server from 6.1 to 7.0.1. After doing the upgrade we discovered that our verity functionality has broken. The indexing is taking roughly 50 times longer to complete, and once it does, it does not seem that the collections have been created (the search results return nothing). I know that due to all the new content in verity that the process of indexing takes longer which may be one possible cause. In addition, our system uses multiple collections and that could be another cause. You can see an example of no results here: > http://www.fortworthcpa.org/index.cfm?fuseaction=contentSearch.veritySearch&nodeID=1 > However, we have a client that uses our product on a third-party MX7 server, and they have never experienced this issue. You can seen the correct results here: > http://www.ovariancancer.org/index.cfm?fuseaction=contentSearch.veritySearch&nodeID=1 So, we are not sure how to account for the situation that verity is working with our system in one MX 7 environment but not in another. Any thoughts? Also, as a temporary fix would it be possible to install the verity (version 2.6.1) from 6.1 to work in conjunction with 7.0.1? Thanks in advance, John > > > > > ~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:241421 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
Re: Verity issues with MX 7
The verity core is different in what was shipped in 7 from the version shipped in 6. Verity version in 6.1 was about 4 I tyhink, and in MX7 the verity version is also 7. This means any collections created by your mx6.1 box wont work on 7 and will need to be recreated in the new verity format. Hope that helps. On 5/23/06, John Crawford <[EMAIL PROTECTED]> wrote: > My company recently upgraded a server from 6.1 to 7.0.1. After doing the > upgrade we discovered that our verity functionality has broken. The indexing > is taking roughly 50 times longer to complete, and once it does, it does not > seem that the collections have been created (the search results return > nothing). I know that due to all the new content in verity that the process > of indexing takes longer which may be one possible cause. In addition, our > system uses multiple collections and that could be another cause. You can > see an example of no results here: > > http://www.fortworthcpa.org/index.cfm?fuseaction=contentSearch.veritySearch&nodeID=1 > However, we have a client that uses our product on a third-party MX7 server, > and they have never experienced this issue. You can seen the correct results > here: > http://www.ovariancancer.org/index.cfm?fuseaction=contentSearch.veritySearch&nodeID=1 > So, we are not sure how to account for the situation that verity is > working with our system in one MX 7 environment but not in another. Any > thoughts? Also, as a temporary fix would it be possible to install the > verity (version 2.6.1) from 6.1 to work in conjunction with 7.0.1? > Thanks in advance, John > > > > > ~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:241191 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
