SDM error

[Former Member]

Hi All,

I had a sneak preview Java edition installation up and running for the past one week.I was working on the EP of the same creating users ,importing some Business Packages.Suddenly the portal got hanged and I shut down the server went to taskmanager and end the process of jcontrol.exe and rebooted my system.

When I again started the SDM instance all the process except jcontrol.exe is in green meaning was up but jcontrol.exe was showing yellow.

I went to the developer trace of the same and I found from the log the following :-

[Thr 3592] JControlMSReadMessage: NiPeek() returns -5 NIETIMEOUT

I did the starting & stop of SDM 3-4 times and each time it was saying the same error as the above.

Any clues for the same or I have to uninstall and reinstall the entire software again?

Helpful answers will be rewarded.

Regards,

Balaji S

[Former Member]

Rich,

As I said in my previous reply

message server.exe, enserver.exe and igswd.exe is up and running in green color.

only the jcontrol.exe which is under process list tree is in yellow color saying "Some process running" for about 35 mins.Normamly jcontrol.exe will also turns green in less than 10 mins when I start the server.

From the jcontrol.exe developer trace I am seeing this error in the log files for every 5 mins:-

[Thr 3592] Tue Nov 08 12:00:10 2005

[Thr 3592] JControlMSReadMessage: NiPeek() returns -5 NIETIMEOUT

the last time indicated is 12:00 pm CT.

Any clues.

Also Any ideas on EP backups if I wanted to re install the entire server?

Regards,

Balaji S

[Former Member]

Rich,

I stopped the J2EE system and rebooted the machine atleast 3-4 times from morning.

Each time the jcontrol.exe is yellow and shows the timed out error.

Any other clues?Shd I uninstall the entire software and reinstall?

Also any idea how can I have backups of EP works done on the server.If I uninstall I fear I may loose all my EP iviews and pages..

regards,

Balaji S

[RichHeilman]

Uninstalling and reinstalling would probably fix the problem, but you can't be doing that everytime the system acts up. Are you able to access the engine at all? Is there any corresponding service that is not started or has become disabled? Check the services make sure all is running.

Regards,

Rich Heilman

[RichHeilman]

Stop j2ee server, reboot machine, start j2ee server.

Regards,

Rich HEilman