Migrating Custom Module from Livelink 9.7.0 to 9.7.1

Good Day - My name is Luke Chalmers and I have been tasked with migrating our existing Livelink system from 9.7.0 to 9.7.1 for our enterprise. While everything has gone relativly smoothly the one issue I have run into is with the one custom module we have which auto-populates PDF forms with data stored in 3 different livelink db tables. Below is a detailed summary:

On each form there exists a “populate” and “Submit” button. After the user enters a an appropriate value they can select populate which then uses that input to get data from the database and populate several fields so that the user does not have to.

In our 9.7.1 environment, after the input value has been entered and the user selects populate an error occurs saying:

"Server did not Respond - The Livelink Server did not respond or sent a document that contained no data. Please try again. If the problem persists, contact your Livelink Administrator."

I have attached a copy of our logs after reproducing this error several times. The most helpful information I have been able to find thus far is an error in one of the thread logs saying "Could not load script". Im not sure if its pertinent but the .ini defines the following:

[dependencies]

requires_1={'kernel',9,5}

requires_2={'aform',9,7}

[description]

moduleName=portforms

Name=Port Forms

Version=2.0 r 2

[install]

Url=func=portforms.configure&module=portforms&nextURL=%1

[OSpaces]

ospace_1=portforms

As I have a limited understanding of ospace code I have not been able to do much in my efforts to find a resolution for this. I am currently going through the livelink_module_development_guide to learn more which is proving helpful but slow. The module was built by Global Services and I have opened a ticket with them but have been waiting for a week and a half with no answer which prompted me to try this conduit.

Attached are the documentation I have for this module, A copy of all module components, and detailed logs created while executing the module.

Any assistance or guidance provided is much appreciated.

Thank you,

Luke Chalmers

portforms_2_0_2.zip

Port of Seattle - Portforms202 Documentation.pdf

Find more posts tagged with

Comments

Jim_Coursey_(inactive)

Did you compare the 9.7.0 Schema and the 9.7.1 Schema match (e.g., table names, field names, field characteristics) for the DB fields you are loading?

From: eLink Entry: Content Server Builder Forum [mailto:componentbuilder@elinkkc.opentext.com]
Sent: Tuesday, March 29, 2011 2:18 PM
To: eLink Recipient
Subject: Migrating Custom Module from Livelink 9.7.0 to 9.7.1

[Attachments exceeded pre-set size limits. Use the links provided to access]

Migrating Custom Module from Livelink 9.7.0 to 9.7.1

Posted by chalmers.l@portseattle.org (Chalmers, Luke) On 2011/03/29 14:12

In our 9.7.1 environment, after the input value has been entered and the user selects populate an error occurs saying:

"Server did not Respond - The Livelink Server did not respond or sent a document that contained no data. Please try again. ! If the problem persists, contact your Livelink Administrator."

[dependencies]

requires_1={'kernel',9,5}

requires_2={'aform',9,7}

[description]

moduleName=portforms

Name=Port Forms

Version=2.0 r 2

[install]

Url=func=portforms.configure&module=portforms&nextURL=%1

[OSpaces]

ospace_1=portforms

As I have a limited understanding of ospace code I have not been able to do much in my efforts to find a resolution for this. I am currently going! through the livelink_module_development_guide to learn more! which is proving helpful but slow. The module was built by Global Services and I have opened a ticket with them but have been waiting for a week and a half with no answer which prompted me to try this conduit.

Attached are the documentation I have for this module, A copy of all module components, and detailed logs created while executing the module.

Any assistance or guidance provided is much appreciated.

Thank you,

Luke Chalmers

Attachment Links:

portforms_2_0_2.zip (21 KB)

PortofSeattle_Logs.zip (4 MB)

Port of Seattle - Portforms202 Documentation.pdf (777 KB)

[To post a comment, use the normal reply function]
Forum:	Content Server Builder Forum
Livelink Server:	knowledge-wlweb01

Appu_Nair

Use this as a basis of what I am saying

https://knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=3498377&objAction=ArticleView

Since you are learning and I do not have aforms module in my builder I could not loos at the code.

Based on this
#600015a6.'Execute'
Go to thread3 log
Match the first 4 number in this case 6000
from your file it is
#OSpace: webaform Root: #60000001 File: C:\OPENTEXT971\module\aform_9_7_1\ospace\webaform. Size: 75008

Looks like aform97.1 has problems understanding the Execute.If you put builder on another server and run it it may break there and show you some info.

BTW don't put a lot of logs in this forum as it contains server info of your env.Perhaps prune the ip addresses etc by running a clean up job.why take risks from a hacker out there.I have always practiced that so became edgy...

If time permits I will try to see what the module does

Appu_Nair

also right where it fails you can see wrote trace3 file a little above that this

LL_FUNC_VALUES = 'A<1,?,''Func''=''formwf.saveformstart'',

''LL_FormID''=''1'',''LL_FormViewID''=572907,''LL_ID''=19532720,''LL_MIC

so does 572907 exist in this livelink?.I am hoping it is something simple like that

Luke_Chalmers

Thank you very much for the reply! Im reviewing your suggestions now which will hopefully lead to some progress.

Thanks!

Appu_Nair

On thinking I belive 'could not load script' usually has happened when there is an error in compilation.I am unsure or I do not rememebr if it is run time error.I would possibly put the 9.7.1 version module and atleast try to compile all oscript modules atleast the new ones which should be easy you might go after the green ones.If one of them does not compile that would give you a better clue as well.For the life of me I have not seen this behaviour unless of course the 9.7 module depended on something that is totally missing from this 9.7.1 install.Run a simple comparison of all modules in 9.7 and compare if they all have a equivalent module as well.