on 04-18-2008 9:43 AM
Hi Everybody!
We have just upgrade our XID 3.0 system with a SQL Server 2000 DDBB on a Windows Enterprise X64 to a PI 7.0 with SQl Server 2005 and the same S.O.
When we were doing the post-intallations steps for a SLD connection,we need to restart the computer to apply some changes in the instance profile. After we restart the computer, the satck JAVA didn´t work, but ABAP stack runs as well as before. The Sap management Console in Windows shows dispacther: J2ee info unavailable.
The log Files contains something errors about SLD roles, and something about error when try to connect to JAVA message server. You can see them as an attach files in this message.
Please, help me as soon as posible.
Thank you.
Hi Leo
Check whether you have given the right credentials. If you are very sure that you have given right credentials then your problem will be solved by restarting J2EE engine
steps to restart J2EE engine
1) run transaction SMICM
2) then in the tab administration => J2EE instance(local) =>send soft shutdown with restart
by this java engine will restart and will be up in 5-10 minutes and your problem will be solved
If dispatcher error is there then kindly restart your HTTP web dispatcher also
Thanks
sandeep sharma
PS ; if helpful kindly reward points
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you every one of you for your replies.
Finally It was solved with some changes in OS_LIBS directory, we need to put them some *.dll and some J2ee *.exe files that was deleted we didn´t Know when and why...
We could find the error because we took a look for another system with the same Exchange Infrastructure version. Anyway We want to answer here the correction to help somebody with the same error.
Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Leo Moreira,
The directory OS_LIBS contains the executables files. So, it's quite impossible that the system itself deleted them. Proabably someone tried to update the Kernel of this system and forgot to copy all executables to there. There is not a correction in this case. You have only to be sure that all necessary executables are available.
Best regards,
Rafael Toshiaki
PS: Please consider rewarding points for helpful answers on SDN.
Hello Leo Moreira,
Please try to restart again the J2EE Engine using transaction SMICM and then if it still fails, verify if you can see the string "running" in the file dev_dispatcher and dev_server0. If you can't find it in both files, please post the content of them here. If you find an exit code in the dev_server0, please also post the content of std_server0.out trace file.
Best regards,
Rafael Toshiaki
PS: Please consider rewarding points for helpful answers on SDN.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.