We have BaaN IV c4 SP16, OS WinNT, Sql Server 7 setup.
We are facing a problem of connectivity, our clients who try to login get error message
1: rexec failed host 192.1...... username .... command e:\baan/bin...
2: Error" bw failed to connect to 192....!bshell.
(Exact screen attached)

Although, already logged in users are able to work with no problem at all but new logins are not possible.

On server when we check taskbar and usage, sometimes server CPU usage goes upto 100% and most of the usage almost 99% been consumed by rexec.exe.

Please help and suggest what could be the problem. :confused:

thanks
Virender

I would like to add that we we restart the server and it is ok but after some time or a day it reoccurs.

sounds like your logic service is crashing.
You could check the event viewer on the server to see if you can find out why.


On a system as ancient as yours, i dunno, i'd probably just deal with rebooting it every night.

trying to patch to fix it might be disastrous.

Dave

We have BaaN IV c4 SP16, OS WinNT, Sql Server 7 setup.
We are facing a problem of connectivity, our clients who try to login get error message
1: rexec failed host 192.1...... username .... command e:\baan/bin...
2: Error" bw failed to connect to 192....!bshell.
(Exact screen attached)

Although, already logged in users are able to work with no problem at all but new logins are not possible.

On server when we check taskbar and usage, sometimes server CPU usage goes upto 100% and most of the usage almost 99% been consumed by rexec.exe.

Please help and suggest what could be the problem. :confused:

thanks
Virender

Hello,
maybe the number of rexec connections on the server are limited ?
Check if a specific number of connections is used an the next connection is refused.

Regards

Maybe it's wise to upgrade your OS/SQL-server version so you can upgrade your portingset too. It's probably fixed a long time ago.

If it's that essential to your company than, and this is my personal opinion, you should use supported components.

Regards,
Han

Hi,

for more analyze plaese try to send event viewer


Best Rgards

Dave - How can we reinstall logic service to fix it up.

How to check Number of connections allowed?

I am also working on the aspect of upgrading it to higher OS/MSSQL version but that process is a long process and needs a test server to be installed and after sucessful installation of Baan and data transfer, i do the same on live server.

Reinstalling same porting set can resolve it?

Before doing any of these activity i would consider making images of all the partitions for safety on the event of any failure.

Please suggest...

look in the event viewer before you do anything.

I am attaching herewith eventviewer log for your reference.
Please suggest.

Also I am looking forward to shift my OS from WinNT to Linux/Unix platform.
Please suggest what are the possibilities, requirements, risks involved, pros and cons of this.

what are the options available for linux and unix.

what about the database, at present i am using sql server 7.


Regards
Virender

I am attaching herewith eventviewer log for your reference.
Please suggest.

Also I am looking forward to shift my OS from WinNT to Linux/Unix platform.
Please suggest what are the possibilities, requirements, risks involved, pros and cons of this.

what are the options available for linux and unix.

what about the database, at present i am using sql server 7.


Regards
Virender

Also on most of the times on this event CPU usage is 100%, but memory usage is approx 40% and it doesn't go beyond this.

I have 2 GB of RAM on my server, Is there any restriction of RAM usage for baan application, any configuration etc.

ahh, the C00000005 access violation error.

I've see it 100 times and never found out what causes it.

Dave

What is your policy on orphan licenses? Do you clean orphan licenses regularly via a job?
Also, do you let users to leave open connections to baan for a long amount of time? You could avoid that via the session_timeout setting.

a) License daemon can be purged regularly via licmon command or simply restarting the licd service once a week or so.
b) Look at solution 110907 in infor365 for information on how to set up session_timeout. This will kill inactive bshells. If you implement this you might want to consider to set session_timeout=0 for jobs because you might not want them to timeout if they are idle.

Best regards,

Nestor Molina

Reinstallating Logic and license service resolved the problem.

Thanks Gurus.