Ticket #217 (closed task: invalid)

Opened 12 years ago

Last modified 11 years ago

Not able to access a collection

Reported by: glibrarysystem@… Owned by: nobody
Priority: low Milestone:
Component: Sample Collections Severity: blocker
Keywords: Cc:

Description

We have been building collections in Greenstone for a few months now with no hitches but recently one of our employees was trying to add data to a collection and was unable to do so. When they try to open the collection with the client, which is on Windows XP SP2, the collection appears to try to open but then it disappears from the list of collections in the open box. There is an error that appears on the Command Prompt window and that error is as follows:

gliserver args: cmd=download-collection&c=alexande java.io.FileNotFoundException?: C:\Documents and Settings\username\Application Dat a\Greenstone\GLI\collect\alexande\archives\DAlexand\er McBet?\h Store \Ledger p\a ge 10.dir\doc.xml (The system cannot find the path specified)

at java.io.FileOutputStream?.open(Native Method) at java.io.FileOutputStream?.<init>(Unknown Source) at java.io.FileOutputStream?.<init>(Unknown Source) at org.greenstone.gatherer.util.UnzipTools?.unzipFile(UnzipTools?.java:70)

at org.greenstone.gatherer.remote.RemoteGreenstoneServer?$RemoteGreenston?

eServerDownloadCollectionAction.perform(RemoteGreenstoneServer?.java:427)

at org.greenstone.gatherer.remote.RemoteGreenstoneServer?$RemoteGreenston?

eServerActionQueue.run(RemoteGreenstoneServer?.java:229) CollectionManager?.loadCollection: No config file.

I've checked the server that is running Greenstone and the collect.cfg and the build.cfg files seem to be there and match what was there before. Please let me know what I need to do to be able to access and add to this collection again.

Change History

Changed 11 years ago by kjdon

  • status changed from new to closed
  • resolution set to invalid
  • severity set to blocker

This problem was sent to the mailing list also. Hopefully it has been resolved there. Not really a bug for Trac.

Note: See TracTickets for help on using tickets.