Hi Luka/Jamshaid, We have been able to recreate this problem in-house now, the key being to actually attempt to start Virtuoso from the command line prompt, which I presume is what you have been doing as detailed in the VOS windows guide, as opposed actually starting it using the Windows Service control manager or from a machine restart with the windows service set to auto start, which is what I was doing.
This has been reported to development to be fixed as, although not harmful the condition should be handle such that such messages are not displayed, which would be disconcerting for users. I shall let you know when we have a fix ... Best Regards Hugh Williams OpenLink Software Best Regards Hugh Williams Professional Services OpenLink Software Web: http://www.openlinksw.com Support: http://support.openlinksw.com Forums: http://boards.openlinksw.com/support Twitter: http://twitter.com/OpenLink On 7 Nov 2010, at 19:40, Jamshaid Ashraf wrote: > Hi, > > I am sharing because i had very similar expereince. > > I had the same error reported by Luka a month ago and Windows service log > gave the clue that "virtuoso.lck" is giving problem so it renamed it and i > worked fine. I noticed that when window crashes or you try to create service > then this error message come on booting system, of C++ things reported by > Luka. Now i have set the service on manual node and manually start ans stop > when ever i shutdown windows. this is working fine, so far > > I am using Win XP 2002 professional and Vistuoso is 6.1.2 > > Regards > Jamshaid Ashraf > > > > On Sun, Nov 7, 2010 at 7:18 PM, Hugh Williams <hwilli...@openlinksw.com> > wrote: > Hi Luka, > > Strange that this Visual Studio runtime error occurs on server startup when > the lck file is still in place, as I have not seen this error before. Can you > please confirm the Windows XP version and Service Pack level you are using so > we can check this on a similar version in-house ? > > Once you have created the Virtuoso windows service, you can then use the > standard Windows <code>Services</code> Manager to start and stop the > Virtuoso Server, which would be identified in the Server Manager with a name > of <code>OpenLink Virtuoso Server [Instance Name]</code>. The created > Virtuoso service can also be set to auto start using the Windows Services > Manager such that your Virtuoso Server automatically start when the Windows > machine is started. The Windows Services Manager can be accessed from > <code>Control Panel -> Administrative Tools -> Services</code> menu items. > > I have added a note the the online docs to highlight this point for those > unfamiliar with this Service ... > > Best Regards > Hugh Williams > Professional Services > OpenLink Software > Web: http://www.openlinksw.com > Support: http://support.openlinksw.com > Forums: http://boards.openlinksw.com/support > Twitter: http://twitter.com/OpenLink > > On 7 Nov 2010, at 15:41, Luka wrote: > >> Hugh, thank you very much. It's working after deleting virtuoso.lck and >> creating new instance. >> >> Now, please tell me is there quicker way to start the service each time? >> >> Regards, >> Luka >> >> On 7.11.2010 2:13, Hugh Williams wrote: >>> >>> Hi Luka, >>> >>> What files exist in the %VIRTUOSO_HOME%\database folder when you are >>> attempting to start the database, if the file "virtuoso.lck" exists in this >>> location please remove and try again. Please also check the virtuoso.log >>> file in this same directory to see if it reports the reason the database >>> failed to start. If the problem continues then from a command line prompt >>> in the %VIRTUOSO_HOME%\database run the following command to start the >>> Virtuoso server in foreground mode and provide the output produced: >>> >>> ..\bin\virtuoso-t -f >>> >>> Best Regards >>> Hugh Williams >>> Professional Services >>> OpenLink Software >>> Web: http://www.openlinksw.com >>> Support: http://support.openlinksw.com >>> Forums: http://boards.openlinksw.com/support >>> Twitter: http://twitter.com/OpenLink >>> >>> On 7 Nov 2010, at 00:03, Luka wrote: >>> >>>> Hi everyone, >>>> >>>> few days ago I followed the instructions from: >>>> http://virtuoso.openlinksw.com/dataspace/dav/wiki/Main/VOSUsageWindows >>>> and successfully installed Virtuoso on WinXP. I had no problem creating >>>> database and opening conductor at port 8890. >>>> What I'm trying to say is that everything worked as expected. >>>> >>>> Today I wanted to continue my play with Virtuoso but server was down when >>>> I tried opening localhost:8890/conductor >>>> So, in order to start server I typed: virtuoso-t -I "Instance Name" >>>> +service start >>>> error window popped out: >>>> >>>> <debug.jpg> >>>> >>>> If I ignore it I get another window in a minute informing me that >>>> virtuoso-t.exe crashed :( >>>> >>>> Do you know what might be a problem? >>>> >>>> BEst regards, >>>> Luka >>>> ------------------------------------------------------------------------------ >>>> The Next 800 Companies to Lead America's Growth: New Video Whitepaper >>>> David G. Thomson, author of the best-selling book "Blueprint to a >>>> Billion" shares his insights and actions to help propel your >>>> business during the next growth cycle. Listen Now! >>>> http://p.sf.net/sfu/SAP-dev2dev_______________________________________________ >>>> Virtuoso-users mailing list >>>> Virtuoso-users@lists.sourceforge.net >>>> https://lists.sourceforge.net/lists/listinfo/virtuoso-users >>> > > > ------------------------------------------------------------------------------ > The Next 800 Companies to Lead America's Growth: New Video Whitepaper > David G. Thomson, author of the best-selling book "Blueprint to a > Billion" shares his insights and actions to help propel your > business during the next growth cycle. Listen Now! > http://p.sf.net/sfu/SAP-dev2dev > _______________________________________________ > Virtuoso-users mailing list > Virtuoso-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/virtuoso-users > >
