Hi The problem is that you have an old version of the file vdk200.dll in you \system32\ directory
J have one file that run with Search97 V 3.1 PatchLevel=16 dated 06/04/1998 size 1 409 Ko Regards >Hello Sean, > >Monday, December 9, 2002, 9:22:22 PM, you wrote: > >thanks for the tip but... >I think it's more of an install issue or something.. >I'll see how it goes and let ya know. > > >Joachim > > > >SM> I have 0 experience with solaris. But my guess is your collection is >SM> corrupt I would go in stop the k2 service...delete the collection...start >SM> service and recreate collection. Then try spidering it again. > >SM> hope that helps > >SM> sean > >SM> -----Original Message----- >SM> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] >SM> Sent: Monday, December 09, 2002 2:50 PM >SM> To: CF-Talk >SM> Subject: Verity's vspider on Solaris. > > >SM> Hi folks, > >SM> I'm starting to loose my mind on this one so suggestions/clues are more >then >SM> welcome... > >SM> Solaris 2.6 >SM> Coldfusion 5 > >SM> I'm trying to get Verity's vspider up and running but for >SM> some reason it keeps failing. >SM> I've set -loglevel to trace but those logfiles don't >SM> show anything more usefull either (other than the error msgs below). > >SM> Here's the script/result/error: >SM> ---- >/home/scripts >> /opt/coldfusion/verity/_ssol26/bin/vspider -cmdfile >SM> spider_script_en >SM> - Verity, Inc. Version 3.7 (_solaris, Nov 15 1998) >SM> Info 2002/12/09 17:00:51 (ind006000) Message database loaded from >SM> [/opt/coldfusion/verity/_ssol26/bin/ind.msg]. >SM> Info 2002/12/09 17:00:51 (ind012207) Last indexing job was interrupted >SM> 5 time(s). Running in auto-restart mode. >SM> FATAL 2002/12/09 17:00:51 (ind002000) Couldn't create VDK session >[-10]. >SM> IndExcept from /users/qk2v220/BLD11/src/spider/ind/indvdk.cxx:434 >SM> vspider done >SM> ---- > >SM> Looking up the error codes >SM> VdkError_BadArgStruct (-10) Invalid argument structure. >SM> >http://www-2.cv.ihk.dk/cfdocs/Advanced_ColdFusion_Administration/verityutils >SM> 9.html > >SM> But the odd thing is is that if I run the exact same script >SM> on another Solaris machine it works like a charm. > >SM> As far as I can tell it doesn't have anything todo with the script itself, >SM> even with a >SM> basic set of options it keeps failing. I'm starting to think this is >SM> more of a install/config related problem but i'm far from smart enough when >SM> it >SM> comes to Solaris to figure out what could wrong. > > >SM> Any help is appreciated! > >SM> Joachim >SM> http://www.developer.be/ > > >SM> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:235518 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
