Operating System - OpenVMS
1827384 Members
4032 Online
109963 Solutions
New Discussion

Re: abb-link & decwindows is not running after upgradetion.

 

abb-link & decwindows is not running after upgradetion.

I have alphastation 200 and running openvms 7.1. Now I have done the updradetion of that system and switched over in ds20E server and openvms version is 7.3-1 after completion of upgradetion one application software abb-link is not running. When i want to start that application error messege "illegal image section descriptor" is comming. I have installed encryption software,still the result is same.
after upgradetion another problem is decwindows is not starting during system boot. after booting it is comming into the text mode and i have to start decwindows manually. then GUI is comming.
Please help me out for these two problems asap.

Thanks.

kuntal
3 REPLIES 3
Ian Miller.
Honored Contributor

Re: abb-link & decwindows is not running after upgradetion.

"illegal image section descriptor" suggests an executable image file is corrupt.

Are there any errors messages during the system startup about DECwindows.
____________________
Purely Personal Opinion
Volker Halle
Honored Contributor

Re: abb-link & decwindows is not running after upgradetion.

Kuntal,

this sound suprisingly similar to the problem reported in the following thread:

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1074707

and also in comp.os.vms

http://groups.google.de/group/comp.os.vms/browse_frm/thread/ab0b0f96262e6299/a3da3bc0a4b0e99b?lnk=st&q=image+section&rnum=3&hl=de#a3da3bc0a4b0e99b

Please follow the advice given in those threads and don't cross-post without indication.

Volker.

Volker.
Joseph Huber_1
Honored Contributor

Re: abb-link & decwindows is not running after upgradetion.

To the second problem, DECWindow (server) not starting:
Has the WINDOW_SYSTEM parameter been lost eventually ?
Does "sysman param show window_system" show a 1 ?

If yes, then is there any message at the console (after the Startup process termination) ?

Is a sys$manager:DECW$server*error.log file created (at the failed startup, i.e. a decw$server*error.log;-1 after You did decw$satrtup manually).

Finally there could be a license problem:
usually (?) DECW is licensed within a net-app-sup* license, but eventually it's different in Your case.
Do a "license list/full" and watch for licenses with release and/or termination dates expired.
http://www.mpp.mpg.de/~huber