Endpoint Protection Small Business Edition

Every time I login to the endpoint console it goes to load reporting, once so its messed with a lot of script type stuff written in all the areas, then it all goes away and it then loads the login page for the web based reporting in the middle of the console and if i login to that, it pulls up web reporting in the center of the console but still for all the data each section pulls up another thing to login to reporting for a second then it kicks me out of the console completly.

Ive ran some of the diag tools from symantec and tried a couple other things yet nothing seems to help.

 So if I understand you right you are being brought back to the Login screen in SEPM.

Since this thread is posted on SEP 12 forum I assume that the SEPM is ver 12.

In case its SEP 12 try these steps :-

Repair the Symantec Endpoint Protection Manager installation through add/remove programs

If prompted for the Symantec Endpoint Protection Manager.msi file browse to the file inside the SEPM folder in CD1

Complete the repair process

Try to login to the Symantec Endpoint Protection Manager console and the login should be successful.


In case its SEP 11 then follw this link :-


SEPM login revert to login screen

http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008081302490248

follow these documents you need to fix your ODBC ,

Unable to communicate with the reporting component after logging into the Symantec Endpoint Protection Manager

http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008042212582048
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008081312461148
 

Oh, and no its actually SEPM 11

And The steps in ODBC repair didn't seem to help. 

helps paste/attach the scm-server-0.log with is present in Program Files \Symantec\Symantec Endpoint Protection Manager\tomcat\logs 

is the odbc connection successful?
 

yes, the connection was successful.

Try this

Adjust the Symantec Endpoint Protection Manager heap size:
Click Start> Run.
In the Run dialog box, type regedit
Press Enter.
Locate the following registry key:
HKLM\SYSTEM\CurrentControlSet\Services\semsrv\Parameters\

Locate the following keys:
JVM Option Number 0
JVM Option Number 1

Adjust the key values upward, and for optimal performance, match the key values.
  Create a 1 GB static heap, set: "JVM Option Number 0" to "-Xms512m", and set "JVM Option Number 1" to "-Xmx1024m". 
Close Regedit.
Click Start> Settings> Control Panel> Administrative Tools
In the Services dialog box, right-click Symantec Endpoint Protection Manager, and then click Restart.
 

Is your OS 64 bit? I think the issue is with JAVA, you need to download specific to that Bit....
http://java.com/en/download/faq/java_win64bit.xml 

These settings were already set in that matter.

its not java.

If you login locally in SEPM whether it is working properly?
If no
Pls paste/attach the scm-server-0.log with is
present in Program Files \Symantec\Symantec Endpoint Protection
Manager\tomcat\logs
 

is attached.

Remove any proxy if you Re configured in IE.Your log file having following error "Not in GZIP format".This may be because you are selected the no. of revisions to 1. 

if above suggestions not helps try this
Try the steps below..now

1) open your IIS
2) right click symantec web server
3) clcik on properties
4) click on directory security
5) click on autentication and access control
6) check integrated windows authentication.
7) try loggin in now, should work fine

if this does not work,

check your IUSR account, most of the times it will be member of guest account and guest account will be disabled.
IUSR accont should be memeber domain users.

or else create a new account and put in IIS, anonymous access.

Also if,

As we see the Error int he logs provided, we found,

Unexpected server error. ErrorCode: 0x10010000

Follow the KB:

Clients stop communicating with Symantec Endpoint Protection Manager (SEPM) with HTTP 401 error in Sylink log and HTTP 401.1 error in IIS log

http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008032702341648


 

As far as being a guest, that is most likely true but, remember the guest group and the guest user are two different things. the guest account is disabled but the group is not as it isn't even possible to do so.

put a new account in IIS and try ( if you dont have multiple web sites hosted on IIS)  

i have 3 sites on this server including the symantec site.

in the folder program files\symantec\symantec endpoint protection manager\ php.ini

put these lines in ON :

display_errors = Off

display_startup_errors = Off

login in the reporting site by IIS manager and post the error here.(If possible a screen shot)

the problem i've been having is in the sepm console and it kicks me out if i log into reporting which it should go to in the first place. Would you happen to have the url for the reporting site in sepm?

i was able to remember it. I have attached a screenshot.

First restart your SEPM and try.If not helps give full permission for iuser to  \Program Files \Symantec\Symantec Endpoint Protection Manager\Inetpub\ folder and try,if not helps copy the session.php file from a working server to problem matic server ,restart IIS and SEPM services and try. 

So far, Ive looked into everything you have suggested, everything has been in order and all settings correct, yet i still have no access to any form of the reporting. This is the only server with the sepm installed so i have no where to copy the suggested file from and I'm getting a bit tired or this little game.

from what I can see, I will have to completely remove SEPM and re install it and run a bunch or updates and re connect all the clients.

its not able to create a session for sepm
can you increase the heap size and check
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008061813510348 

If Rafeeq's suggestion not helps try by rearing SEPM from add/remove programs..

and also, check the log file under

C:\Program Files\Symantec\Symantec Endpoint Protection Manager\Inetpub\Reporting\Temp
there will be a file called reporting.log
check what it says.