ospace parse error

hi there,

I have raised a ticket already 4152236 for this issue. I read the issues that are posted here and I am facing issues like database locked and fatal java error when trying to edit the module. As per the SDK offline documentation I tried to import the source oll and I am now getting a new error "Failed to parse ospace <modulename>". Can somebody help how to resolve this.

Also, I was trying to create a new module and I am unable to create request handlers. Please help with this as well.

Regards

Rashmi

Find more posts tagged with

Comments

Nizar Ghazal

If I recall, the actual OSpace you'd be working with and unlocking is a SQLite database, when it says the database is locked, it means the Ospace itself is locked, and not something pertaining to your Oracle/MSSQL/Etc.

Are you automatically building your OSpace, when you import? I get errors about it failing to parse when I try to force build my .os file wherein I have a nasty syntax error that terminates compilation, like having an un-ended function.

To get around your locking issues, locate your ide_startup.lxe, at the root of your OTHOME, find the following lines:

   // Add ospace names in all-caps: toggle their locked status
   //changeStateOspaces += {}

Add in the OSpace you're trying to modify in memory, that previously complained about locks, ex:

   // Add ospace names in all-caps: toggle their locked status
changeStateOspaces += {'YOUROSPACE'}

That should hopefully help you edit it, in the Module Explorer, sans complaints. When performing things like builds, saves, etc, keep an eye on the progress meter on the bottom right of Eclipse. Depending on what state it's in, you may just want to step back and leave it alone, allowing it to fully complete the build.

Some of the veteran OScripters that frequent these parts may have some other ideas for you, too.

Rashmi_S

Quoted Nizar Ghazal on 05/16/2019 12:31 PM:

Some of the veteran OScripters that frequent these parts may have some other ideas for you, too.

hi Nizar,

Thanks for your response.

I get the error even before I build the module. I am still trying to import the module into my oscript explorer so that I can make changes in my request handler. Is it possible for me to create a new module and create new request handlers.

Regards

Rashmi

Dix_Kevin

Just to be clear, I think you need to turn off “Build automatically” before attempting to import the module.

From: eLink Entry: Content Server IDE Development Forum <contentserver-ide@elinkkc.opentext.com>
Sent: Thursday, May 16, 2019 12:37 PM
To: eLink Recipient <devnull@elinkkc.opentext.com>
Subject: ospace parse error

ospace parse error

Posted byrashms@deloitte.com (S, Rashmi) On 05/16/2019 12:31 PM

Quoted Nizar Ghazal on 05/16/2019 12:31 PM:

Some of the veteran OScripters that frequent these parts may have some other ideas for you, too.

hi Nizar,

Thanks for your response.

Regards

Rashmi

[To post a comment, use the normal reply function]
Topic:	ospace parse error
Forum:	Content Server IDE Development Forum
Content Server:	My Support

Dave Carpeneto

Hi Rashmi - After reviewing your ticket with support: it looks like your earlier unlocking / editing of the OSpace in the module explorer (which resulted in the "db is locked" messages) has corrupted your env. This will most likely be causing the "failed to parse" errors you're now seeing.

Before going any further I'd recommend restoring your environment & then follow the "Import your Module" steps provided on the CSIDE quick start guide page ( https://knowledge.opentext.com/knowledge/cs.dll/fetch/-15106263/15106294/15106295/16376487/67794710/67790529/cside/index.html ).

Please let me know if you've any questions on this, or if I've misinterpreted your situation here in any way :-)

Rashmi_S

HI Nizar,

When I changed the ide_startup.lxe as per your suggestion. I restarted the builder then I get this attached error.

Rashmi_S

hi David,

I have installed eclipse and imported CSIDE files as per the link you shared. After fresh configuration of IDE I tried to import the module through oscript explorer that when I end up getting this error.

Regards

Rashmi

Dave Carpeneto

Quoted Rashmi S on 05/21/2019 09:51 AM:

[...] After fresh configuration of IDE [...]

Hi Rashmi - apologies for not being clearer in my last post. When I say "I'd recommend restoring your environment" I mean your Content Server installtion (not the IDE itself, though there's no harm per se in doing that).

The problem is that the bug you hit in our product (where the DB reports as being locked) results in OLL file corruption. As such: this is where the restoration needs to occur. Full back-ups are ideal, however if you have backups of the OLL files that's obviously all that's essential. Note that this specific bug was fixed in newer versions of Content Server (after 16.2.5, which you currently are on).

Nizar Ghazal

Quoted Rashmi S on 05/21/2019 10:33 AM:

HI Nizar,

When I changed the ide_startup.lxe as per your suggestion. I restarted the builder then I get this attached error.

You likely have a typo in your file, as it complains it's not compilable.

Your file should start something like this:

// Called by the IDE to initialize the Content Server server.
//
function Dynamic Startup(
   Boolean       readonly,
   List       changeStateOspaces = {},
   List       additionalIDEOSpaces = {},
   String       webScript = Undefined,            // [ "\opentext\llweb_startup.lxe" ]
   String       configPath = Undefined )       // [ "\opentext\config\opentext.ini" ]

   String       dirPrefix

   Dynamic       retval = Undefined
   Dynamic       serviceName

   // Add ospace names in all-caps: toggle their locked status
   changeStateOspaces = {}

   echo( "***" )
   echo( "Startup parameters ")
   echo( "readonly = " + Str.String( readonly ) )
   echo( "changeStateOspaces = " + Str.String( changeStateOspaces ) )
   echo( "additionalIDEOSpaces = " + Str.String( additionalIDEOSpaces ) )
   echo( "webScript = " + Str.String( webScript ) )
   echo( "configPath = " + Str.String( configPath ) )
   echo( "***" )

...

Add the OSpace you want to start as unlocked, into changeStateOspaces = {}, in the following format:

   changeStateOspaces = {'YOUROSPACE1','YOUROSPACE2','YOUROSPACE3'}

Adding to what Dave mentioned, above, the issue will likely only manifest as a corruption/0-byting of the OLL you were trying to work with. Just copy and paste the original file to restore it.