As I expected, this was not an issue with FarCry. I went in to the server and looked at the properties of the Verity Service. Under the 'Logon' tab, I selected the 'Allow service to interact with desktop' and now Verity is working as expected.
Scott -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Stroz Sent: Friday, July 08, 2005 8:10 AM To: FarCry Developers Subject: [farcry-dev] Re: Verity Issue after upgrading to CFMX 7 Geoff, To be honest, after some investigating, I am not convinced this is an issue with FarCry. I have FarCry 2.3.0 runnign on a CFMX 7 box in my dev environment and I don't have any of these issues. Scott -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Geoff Bowers Sent: Thursday, July 07, 2005 10:25 PM To: FarCry Developers Subject: [farcry-dev] Re: Verity Issue after upgrading to CFMX 7 Please raise the issue at http://bugs.farcrycms.org/ -- CF7 compatability is an important aspect of the 2.3 maintenance branch kand obviously any future versions. -- geoff http://www.daemon.com.au/ Scott F. Stroz wrote: > Here is one I can't seem to figure out. > > I have a site in development on a server that was just upgraded to > CFMX 7, running build 230. After the upgrade, I needed to recreate > the Verity Collections. > > I figured the best, and easiest, way was to do it through FarCry Admin > (that's how they were created and indexed initially). When I try to > build/update collections in FarCry I get the following error: > > > > > An error occurred while performing an operation in the Search Engine > library. > > Error opening the category index: > com.verity.organize.WorkSpaceException: Failed to open existing PI > directory [VPIError_FailedToOpenPIDirectory]. (-2519) The error > occurred in > *C:\yadda_yadda_yadda\farcry\farcry_core\packages\farcry\_verity\verityUpdat e.cfm: > line 62* > *Called from* > C:\yadda_yadda_yadda\farcry\farcry_core\packages\farcry\verity.cfc: > line 85 *Called from* > C:\yadda_yadda_yadda\farcry\farcry_core\admin\admin\verityBuild.cfm: > line 97 > > 60 : <!--- update collection ---> > 61 : <cfif q.recordcount> > *62 : <cfindex action="UPDATE" query="q" body="#arrayToList(application.config.verity.contenttype[key].aprops)#" custom1="#key#" key="objectid" title="label" collection="#application.applicationname#_#key#">* > 63 : </cfif> > 64 : > > Now this is weird enough....and it only happens when you try to update > the collection. > > Here is the really odd part, if I manually create the collection > beforehand...I will not get the error, and the collection will update > normally. > > Any one have any ideas? > > Scott Stroz --- You are currently subscribed to farcry-dev as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/ --- You are currently subscribed to farcry-dev as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/ --- You are currently subscribed to farcry-dev as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
