SEP Management Console Log on failure / port conflict
Hello,
I have been running SEP 11 on w2k3 2003 R2 SBS for a year and a half. I recall spending a lot of time on the phone with Symantec's support to get it up and running.
Recently I was forced to uninstall SEP and reinstall it. Since the reinstall Ihave not been able to log on to the SEPmanagement console.
I feel like I have read just about every post to try to resolve this on my own but have had no luck.
SEP is installed on my DC. Other applications running on the DC are Back Up Exec and Apache Server. Apache is configured to run on port 80.
During the SEP install I elected to install a custom web site and use the embedded database. After the install I created a new IP address (192.168.100.107) and changed the Symantec Website to use this new IP address in IIS. The default website uses 192.168.100.106, which is the IP address of the DC.
I have tried about every TCP port address I've seen on here (8080, 8083, 8005, 8006,...) and none have worked. Each time I change the potrt address in IIS I also update the conf.properties file to use the new port number and then stop and restart the SEP service. I have also tried all of these port combunations with teh Apache serive stopped, also to no avail.
Nothing ususual (at least to my untrained eye) shows up in the application log.
Here are the results of my most recent netstat -a
TCP dell2600:ftp dell2600.IPIllustration.local:0 LISTENING
TCP dell2600:nameserver dell2600.IPIllustration.local:0 LISTENING
TCP dell2600:http dell2600.IPIllustration.local:0 LISTENING
TCP dell2600:kerberos dell2600.IPIllustration.local:0 LISTENING
TCP dell2600:epmap dell2600.IPIllustration.local:0 LISTENING
TCP dell2600:ldap dell2600.IPIllustration.local:0 LISTENING
TCP dell2600:https dell2600.IPIllustration.local:0 LISTENING
TCP dell2600:microsoft-ds dell2600.IPIllustration.local:0 LISTENING
TCP dell2600:kpasswd dell2600.IPIllustration.local:0 LISTENING
TCP dell2600:http-rpc-epmap dell2600.IPIllustration.local:0 LISTENING
TCP dell2600:ldaps dell2600.IPIllustration.local:0 LISTENING
TCP dell2600:705 dell2600.IPIllustration.local:0 LISTENING
TCP dell2600:1026 dell2600.IPIllustration.local:0 LISTENING
TCP dell2600:1027 dell2600.IPIllustration.local:0 LISTENING
TCP dell2600:1049 dell2600.IPIllustration.local:0 LISTENING
TCP dell2600:1052 dell2600.IPIllustration.local:0 LISTENING
TCP dell2600:1060 dell2600.IPIllustration.local:0 LISTENING
TCP dell2600:1067 dell2600.IPIllustration.local:0 LISTENING
TCP dell2600:1077 dell2600.IPIllustration.local:0 LISTENING
TCP dell2600:1318 dell2600.IPIllustration.local:0 LISTENING
TCP dell2600:1802 dell2600.IPIllustration.local:0 LISTENING
TCP dell2600:2638 dell2600.IPIllustration.local:0 LISTENING
TCP dell2600:msft-gc dell2600.IPIllustration.local:0 LISTENING
TCP dell2600:msft-gc-ssl dell2600.IPIllustration.local:0 LISTENING
TCP dell2600:3306 dell2600.IPIllustration.local:0 LISTENING
TCP dell2600:ms-wbt-server dell2600.IPIllustration.local:0 LISTENING
TCP dell2600:3999 dell2600.IPIllustration.local:0 LISTENING
TCP dell2600:5633 dell2600.IPIllustration.local:0 LISTENING
TCP dell2600:6004 dell2600.IPIllustration.local:0 LISTENING
TCP dell2600:6101 dell2600.IPIllustration.local:0 LISTENING
TCP dell2600:6106 dell2600.IPIllustration.local:0 LISTENING
TCP dell2600:8019 dell2600.IPIllustration.local:0 LISTENING
TCP dell2600:8083 dell2600.IPIllustration.local:0 LISTENING
TCP dell2600:8443 dell2600.IPIllustration.local:0 LISTENING
TCP dell2600:9090 dell2600.IPIllustration.local:0 LISTENING
TCP dell2600:10000 dell2600.IPIllustration.local:0 LISTENING
TCP dell2600:55333 dell2600.IPIllustration.local:0 LISTENING
TCP dell2600:domain dell2600.IPIllustration.local:0 LISTENING
TCP dell2600:ldap dell2600.IPIllustration.local:41745 ESTABLISHED
TCP dell2600:microsoft-ds dell2600.IPIllustration.local:46520 ESTABLISHED
TCP dell2600:1124 dell2600.IPIllustration.local:1125 ESTABLISHED
TCP dell2600:1125 dell2600.IPIllustration.local:1124 ESTABLISHED
TCP dell2600:5152 dell2600.IPIllustration.local:0 LISTENING
TCP dell2600:41745 dell2600.IPIllustration.local:ldap ESTABLISHED
TCP dell2600:46520 dell2600.IPIllustration.local:microsoft-ds ESTABLISHED
TCP dell2600:domain dell2600.IPIllustration.local:0 LISTENING
TCP dell2600:netbios-ssn dell2600.IPIllustration.local:0 LISTENING
TCP dell2600:ldap dell2600.IPIllustration.local:41733 ESTABLISHED
TCP dell2600:ldap dell2600.IPIllustration.local:46421 ESTABLISHED
TCP dell2600:ldap dell2600.IPIllustration.local:46522 TIME_WAIT
TCP dell2600:ldap dell2600.IPIllustration.local:46523 TIME_WAIT
TCP dell2600:1026 dell2600.IPIllustration.local:1056 ESTABLISHED
TCP dell2600:1026 dell2600.IPIllustration.local:1254 ESTABLISHED
TCP dell2600:1026 dell2600.IPIllustration.local:46507 ESTABLISHED
TCP dell2600:1026 dell2600.IPIllustration.local:46518 ESTABLISHED
TCP dell2600:1056 dell2600.IPIllustration.local:1026 ESTABLISHED
TCP dell2600:1063 dell2600.IPIllustration.local:ldap CLOSE_WAIT
TCP dell2600:1083 dell2600.IPIllustration.local:1318 ESTABLISHED
TCP dell2600:1103 dell2600.IPIllustration.local:1318 ESTABLISHED
TCP dell2600:1126 dell2600.IPIllustration.local:1318 ESTABLISHED
TCP dell2600:1127 dell2600.IPIllustration.local:1318 ESTABLISHED
TCP dell2600:1128 dell2600.IPIllustration.local:1318 ESTABLISHED
TCP dell2600:1129 dell2600.IPIllustration.local:1318 ESTABLISHED
TCP dell2600:1148 dell2600.IPIllustration.local:1318 ESTABLISHED
TCP dell2600:1254 dell2600.IPIllustration.local:1026 ESTABLISHED
TCP dell2600:1318 dell2600.IPIllustration.local:1083 ESTABLISHED
TCP dell2600:1318 dell2600.IPIllustration.local:1103 ESTABLISHED
TCP dell2600:1318 dell2600.IPIllustration.local:1126 ESTABLISHED
TCP dell2600:1318 dell2600.IPIllustration.local:1127 ESTABLISHED
TCP dell2600:1318 dell2600.IPIllustration.local:1128 ESTABLISHED
TCP dell2600:1318 dell2600.IPIllustration.local:1129 ESTABLISHED
TCP dell2600:1318 dell2600.IPIllustration.local:1148 ESTABLISHED
TCP dell2600:ms-wbt-server 192.168.1.5:3141 ESTABLISHED
TCP dell2600:41733 dell2600.IPIllustration.local:ldap ESTABLISHED
TCP dell2600:46421 dell2600.IPIllustration.local:ldap ESTABLISHED
TCP dell2600:46497 host24.objectsciences.com:http ESTABLISHED
TCP dell2600:46505 dell2600.IPIllustration.local:1318 TIME_WAIT
TCP dell2600:46506 dell2600.IPIllustration.local:epmap TIME_WAIT
TCP dell2600:46507 dell2600.IPIllustration.local:1026 ESTABLISHED
TCP dell2600:46517 dell2600.IPIllustration.local:epmap TIME_WAIT
TCP dell2600:46518 dell2600.IPIllustration.local:1026 ESTABLISHED
TCP dell2600:46521 dell2600.IPIllustration.local:netbios-ssn TIME_WAIT
TCP dell2600:46525 dell2600.IPIllustration.local:1318 TIME_WAIT
TCP dell2600:46526 dell2600.IPIllustration.local:1318 TIME_WAIT
TCP dell2600:46527 dell2600.IPIllustration.local:1318 TIME_WAIT
TCP dell2600:46528 dell2600.IPIllustration.local:1318 TIME_WAIT
Any help would be appreciated.
Hi
This is the problem I guess !
During the SEP install I elected to install a custom web site and use the embedded database. After the install I created a new IP address (192.168.100.107) and changed the Symantec Website to use this new IP address in IIS. The default website uses 192.168.100.106, which is the IP address of the DC.
This issue can happen if the SEPM web server in IIS is set to bind to a specific IP address instead of (All Unassigned) which is the default.
Here is the document , make it to all unassigned it should work fine.
http://service1.symantec.com/SUPPORT/ent-security.nsf/2326c6a13572aeb788257363002b62aa/86368136366e1ad78025734e004734d9?OpenDocument
If the above does not work, place the scm server log as explanined in this document
Rafeeq
Thanks. I just tried that
Thanks. I just tried that with the same result (failed to log on to server...)
The reason I created the new IP address is that this is one of the steps we performed during the first install when Symantec's tech helped me get SEP up and running.
Hi
Make it to all unassigned, try starting the service, it will faile then post the scm log here... It always should be unassigned.
Rafeeq
2009-11-01 10:09:31.286
2009-11-01 10:09:31.286 SEVERE: ================== Server Environment ===================
2009-11-01 10:09:31.286 SEVERE: os.name = Windows 2003
2009-11-01 10:09:31.286 SEVERE: os.version = 5.2
2009-11-01 10:09:31.286 SEVERE: os.arch = x86
2009-11-01 10:09:31.286 SEVERE: java.version = 1.5.0_12
2009-11-01 10:09:31.286 SEVERE: java.vendor = Sun Microsystems Inc.
2009-11-01 10:09:31.286 SEVERE: java.vm.name = Java HotSpot(TM) Server VM
2009-11-01 10:09:31.301 SEVERE: java.vm.version = 1.5.0_12-b04
2009-11-01 10:09:31.301 SEVERE: java.home = E:\Utilities\Symantec\Symantec Endpoint Protection Manager\jdk\jre
2009-11-01 10:09:31.301 SEVERE: catalina.home = E:\Utilities\Symantec\Symantec Endpoint Protection Manager\tomcat
2009-11-01 10:09:31.301 SEVERE: java.user = null
2009-11-01 10:09:31.301 SEVERE: user.language = en
2009-11-01 10:09:31.301 SEVERE: user.country = US
2009-11-01 10:09:31.301 SEVERE: scm.server.version = 11.0.780.1109
2009-11-01 10:09:35.036 SEVERE: ================== StartClientTransport ===================
2009-11-01 10:09:36.583 SEVERE: Schedule is started!
2009-11-01 10:09:37.599 SEVERE: StateCheckpointTask connect to secars failed: SERVICE NOT AVAILABLE
2009-11-01 10:09:37.677 SEVERE: IISCacheTask connect to secars failed: SERVICE NOT AVAILABLE
HI
Check these discussions...
http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/4bd90f7f0f5b95c18825738c00660e10?OpenDocument
https://www-secure.symantec.com/connect/forums/home-monitors-screen-show-empty-framed-boxes
what was the last thing you canged or installed after which SEPM crashed ?java update ? new softwares?
Rafeeq
Thank you Rafeeq,the first
Thank you Rafeeq,
the first link doesn't seem to apply, as this is the DC. The local admin and the network admin are one in the same for this machine (or so it seems). I did try to log in as local admin and there is only the option to log in to the domain.
The second article seems seems to discuss an issue that is unrelated to mine as they discuss getting blank pages after loggin in.
The reason I uninstalled and reinstalled is that my server had some serious issues, so I had to uninstall and reinstall all the software.
Hi
Hello IPI,
have you assigned different app pool for SEPM website?
can you check if thats stopped ? any DCOM errors in event viewer
Rafeeq
Hello Rafeeq, I have not set
Hello Rafeeq,
I have not set a different app pool for SEPM. I checked the existing app pools and I see:
DefaultAppPool;
ExchangeApplication Pool;
ExchangeMobileBrowseApplicationPool.
Thanks
What else should I try?
What else should I try?
Hi IPI, You mentioned that
Hi IPI,
You mentioned that you can see the 3 app pools in IIS manager. Could you please check if all of them are started as well.
SERVICE NOT AVAILABLE error is returned if the app pool has stopped.
Aniket
I just checked and, yes, they
I just checked and, yes, they are all started.
PLease check the KB:
PLease check the KB: http://service1.symantec.com/support/ent-security....
It has the same error "Service not available" mentioned in the symptoms.
Aniket
Thank you Aniket, I checked
Thank you Aniket,
I checked everything listed in KB artilce 2007122815441848. All the settings were already set as indicated in the article.
the only thing i was unsure of is the user name and password setting in the second step. It's listed here as IUSR_DELL2600 (DELL2600 is the name of the server)
Hi
is this a DC?
Rafeeq
Hi
If its on DC then it should be domain accouts
it should be domain \IUSR do u see that
if not create a new account ,set a pass and put in SEPM website.
MORE on this link
http://www.issociate.de/board/post/228142/Domain-based_IUSR_and_IWAM_accounts.html
Rafeeq
Still a no go
Still a no go
Try by repairing your SEPM
Try by repairing your SEPM installation..
Would you like to reply?
Login or Register to post your comment.