The Java Virtual Machine has exited with a code of -1, the service is being stopped.
Updated: 29 May 2010 | 7 comments
This issue has been solved. See solution.
Creating the client install packages never finishes.
Noticed the Symantec Endpoint Protection Manager service was stopped.
Starting the service produces this in the event log:
Event Type: Error
Event Source: semsrv
Event Category: None
Event ID: 4096
Date: 8/20/2008
Time: 11:50:09 AM
User: N/A
Computer: EXCHANGE
Description:
The Java Virtual Machine has exited with a code of -1, the service is being stopped.
Did a custom HTTP site install instead of the default to see if it would act different. No change at all.
Server 2003 R2 64bit Service pack 2
Trail copy of Exchange server 2007 is installed on the same machine and that is why I tried the custom HTTP site
Brian
Discussion Filed Under:
Comments
Same problem after upgrading two SEPM servers to MR2 MP2.
This problem, for me, came from upgrading the server to MR2 MP2. What fixed it was the following that I found in another post:
Make sure that Integrated Windows Authentication is "checked" in the IIS Manager under Direcory Security.
ALso, add the following user accounts with their named permissions as below to the SYMANTEC Folder located at C:\Program Files\
Authenticated USers - FULL CONTROL
IUSR_<Servername> - Read Execute
IWAM_<Servername> - Read Execute
Worked for me on a 2003
Worked for me on a 2003 server with MR4
It works!
I had the same exact problem with v11.0.4202 MR4 MP2, installing SEPM for the first time on a server with SAV 10.1.5.5000 as well as SSC and Central Quarantine already on it.
I applied Rick's fix above and the service is not longer stopping. Except in my case the Symantec folder exists on the E drive, not the C drive.
Thanks!
my case doesn't work with
my case doesn't work with Rick's solution....:(
I thought this may help some one out there
I know it's an old post, but I thought this may help some one so here we go:
I had similar problem. The solution from RickJDS did not work out of the box. I remembered a suggestion from another post and decided to combine them and voila - it worked.
I followed the instructions from RickJDS. In addition to that in IIS / Directory Security I enabled Integrated Windows Authentication.
Hope this helps.
ivm17
Additional help
Contributing to an old topic:
I performed all the above checks and still did not fix the issue.
We made recent application additions to our server; one application installed apache tomcat that was using the same port as SEP manager resulting in a code kick / refusal to start.
Fix:
Shutdown symantec endpoint protection manager using start\run services.msc. Service: Symantec Endpoint Protection Manager
Navigate to: C:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat\conf (or wherever SEP is installed)
Open server.xml with wordpad
Edit this string: <Server debug="0" port="8005" shutdown="
Insert desired port number (I chose to use 8006)
Save and close server.xml
Start SEP Manager.
Should fix problems associated with conflicting port numbers.
-LiNET
Would you like to reply?
Login or Register to post your comment.