win 2003 server and livelink 1

[AndyH1]

I recently upgraded to windows 2003 server (standard) and have managed to get all my sites working locally apart from livelink. After installing as via the book and setting up the site using IIS I get

The page cannot be displayed
The page you are looking for is currently unavailable. The Web site might be experiencing technical difficulties, or you may need to adjust your browser settings.

when I try to go to the admin page.

I had it working on windows 2000 server and wondered if anybody knows of any issues with win 2003 server that neeed additional setting. I found with my other local asp sites I had to tweak around before they ran fine to to extra security issues etc.:-(

 

[AndyH1]

Replying to my own message! Sorted this problem - in 'IIS webs services extensions' the manager has 'All unknown CGI extension's set to 'prohibited' set as default which stops any of the dlls and exes in the OPENTEXT cgi running. You need to either Allow or create a Livelink extension pointing to these.

Once restarted the site then allows you to log into the admin pages, however when trying to upgrade an existing database and modules I now get:

The database upgrade completed with errors
Please review the log below and contact
Open Text Technical support

--------------------------------------------------------------------------------

[06/22/2004 07:11:58 PM] : [06/22/2004 07:11:58 PM] : Database upgrade started
[06/22/2004 07:11:59 PM] : ?
[06/22/2004 07:11:59 PM] : Unable to create program session for system module setup
[06/22/2004 07:11:59 PM] : The Module Upgrade Failed Due To Errors


[06/22/2004 07:35:41 PM] : [06/22/2004 07:35:41 PM] : Database upgrade started
[06/22/2004 07:35:42 PM] : ?
[06/22/2004 07:35:42 PM] : Unable to create program session for system module setup
[06/22/2004 07:35:42 PM] : The Module Upgrade Failed Due To Errors

Any ideas?

Thanks
Andy

 

[appnair]

The errors are probably due because of modules like forms,webforms that needs an alter schema.So basically livelink encountered a chicken and the egg kind of problem.Your existing schema has more entries than the software can upgrade.In these cases I have done these things.

a)I will complete the server upgrade with a new temporary database,just point somehere on your local oracle install and let LL do its merrymaking
b)I will apply the new modules(forms,webforms,xmlWFIC) one at a time.
c)When all is kosher on the new database I point to the old one
There has been instances where I have had to manually delete some rows pertaining to "forms" in the "KINI" table and sometimes take off ceratin sections in the opentext.ini.I am sure it is an interesting experience and no two livelink admin's experiences are ever truly identical.However these are some pointers I have come across.


Freedom is not worth having if it does not include the freedom to make mistakes.
Mahatma Gandhi

appnair

 

[AndyH1]

Thanks appnair

Thanks for your help. Unfortunately one of the major problems we are having is trying to get livelink 9.2 to create a new database, which is why I was trying to use an old version.

You are probably right about the modules - we added some to the old database, so it could well be an issue - thanks for the pointers

 

[appnair]

I recently installed 9.2 on my machine with personal oracle and used the create new database version which also worked
for us.My platform is winxp (IIS5.0) , Oracle 8.1.7 full install,Livelink 9.2.0 SP1.What specific errors are you getting when running the create new db option.

Freedom is not worth having if it does not include the freedom to make mistakes.
Mahatma Gandhi

appnair

 

[AndyH1]

We are using MS SQL Server (sp3a) rather than Oracle. We enter the details ie

ServerName
sa
password
master

giving all the correct details, but when we click we just get:

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.

Seems to have problems connecting to the database (I think). We have the database set for 'use SQL server authentication' with sa and its password.

Thanks
Andy

 

[appnair]

What immediately comes to mind is you need to find whether that the client databse files that livelink uses to connect is the culprit.In oracle it is the NET8 client files which probably can be tested by using SQLplus.I believe it uses the same client files.OT will know for sure the MSSQL or evn tektips has an mssql version even though do they officilaly support win2003.Simple test would be to test creation of any database form the livelink server computer that would rule out the client connectivity.

Freedom is not worth having if it does not include the freedom to make mistakes.
Mahatma Gandhi

appnair

 

[AndyH1]

Appnair,
Finally got it working - like you said a extra module problem - many thanks for all yor help
Andy