Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Content Management (Extended ECM)
CSIDE and OScript
Builder not attaching to Livelink service
Kyle_Baley
The problem's been fixed. Just posting the solution for posterity. Told from the viewpoint of a relative newbie.Short version: If Builder isn't attaching to the Livelink service, check that the NTServiceName entry in opentext.ini (under the [general] section) is accurate.When I launched Builder in our sandbox environment, I wouldn't get the "Do you want to shutdown the service or continue in ReadOnly mode?" message and none of my breakpoints would ever get hit.I checked the shortcut that launched builder and noticed references to two files: webbuilder.lxe and opentext.ini, both of which I was somewhat familiar with. I started with webbuilder.lxe and found near the top the code that asks the question I wanted asked about the service.It was checking to see if serviceName was defined. From there it was clear that I should check the output from the debug window when I opened Builder. That wasn't too helpful because the patches printed too much stuff and the earlier text was getting cleared.No problem, move the patches to a temporary directory and relaunch builder. Now I get: Service Livelink is not running. Bingo. Our service is named LivelinkSandbox, not Livelink.A quick look through earlier code in webbuilder.lxe led me to the NTServiceName entry in opentext.ini. Changed that to LivelinkSandbox and everything is right in our Livelink world sandbox world again.No idea why it thought the service was named Livelink. I uninstalled and reinstalled builder twice and it picked up that Livelink was already installed on the machine. Plus we didn't have the same issue in our dev and test environments which are named similarly.Anyway, I'm sure this would have been obvious to a more experienced Livelinker but there it is. And yes, I remembered to move the patches back.Kyle the Attached
Find more posts tagged with
Comments
John W. Simon, Jr.
thanks for posting your solution.just fyi...you didn't need to remove the patches. you could have turned on logs (debug=2) and checked the log for thread0 in the logs directory...
Kyle_Baley
Sweet. That's good to know. Thanks.