SEPM: Unexpected server error. Errorcode: 0x10010000

When starting SEPM COnsole you will get the Message „Unexpected  server error. Errorcode: 0x10010000“ but will be sucessfully logged in. You will have black screens at Home, Monitors and Reports.

There my be many reasony for that described at the Symantec Support Page. I have one more:

Look at the …\Symantec Endpoint Protection Manager\apache\logs\error-……..log. In a large Environment you may get this Message :
[Thu Aug 30 08:45:49 2012] [warn] [client x.x.x.x] mod_fcgid: stderr: PHP Warning:  Unknown: POST Content-Length of 8440038 bytes exceeds the limit of 8388608 bytes in Unknown on line 0

Add the following line to  …\Symantec Endpoint Protection Manager\php\php.ini:
post_max_size=xxxM where xxx is the SIze you want it to be, should be more than the POST Content length in the Error Message

Restart „Symantec Endpoint Protection Manager Webserver“ Service

Dispatcher Service does not start after Database move

You have moved the BES Database to another SQL Server and the Dispather Service wont start with some Errors in the Eventlog like: Database error in VerifySchema…..

You forgot one important thing before restoring the bes databases:

copy the „Database“ Directory of your actual Installation ( Version must match ) to the SQL Server and change the BESMgmt.cfg to your environment ( DB_NAME= and Server= ). Then start  „creatdb.exe BESMgmt.cfg“ in the „Database“ directory to create a new BES Database and the needed SQL Server modifications.

Then restore the database.

MAPI call failed. Error ‚The information store could not be opened.‘ after Rebooting the BES

If you get alarms that some users cannot be initialized after rebooting the BES, and see these messages in

Agents logs:

[20400] (05/03 23:49:17.545):{0xF54} {D} MAPIMailbox::MAPIMailbox(2) – OpenMsgStore (0x8004011d) failed, MailboxDN=xxx, ServerDN=xxx/cn=Microsoft Private MDB

[40720] (05/03 23:49:17.545):{0xF54} MAPI call failed. Error ‚The information store could not be opened.‘, LowLevelError 0, Component ‚MAPI 1.0‘, Context 649

This may indicate that the MAPI Profile(s) are corrupted.

Recreate the MAPI Files on a 4.1 Server as follows:

Stop all BB Services.

HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem

Export the Profiles Key and delete it.

Start the BES Configuration and clicke „Edit Mapi Profile“ on the BlackBerry Server tab. Fill in the Servername of the

Exchange holding the BESAdmin Mailbox (BlackBerryServer-Profile).

Start BES Manager and configure the same Servername as above (BlackBerryManager-Profile)

Restart Server.

NTLM Authentication not working. /var/run/samba/winbindd_privileged permission incorrect

You get the following message in your squid’s cache.log:

[2010/03/19 07:04:23, 0] utils/ntlm_auth.c:winbind_pw_check(545)

Login for user [DOMAIN]\[USER]@[COMPUTER] failed due to [winbind client not authorized to use winbindd_pam_auth_crap. Ensure permissions on /var/run/samba/winbindd_privileged are set correctly. ]

Solution: Ensure that the permissions are set to the following:

drwxr-x— root winbindd_priv

You can set them by invoking: chmod 750 /var/run/samba/winbindd_privileged

Check your /etc/group and add the proxy user to the winbindd_priv group.

Changing Ip Address

Changing the main ip address of a tmg can result in many problems, like :
– some Forefront Services take long time to start up
– errors in the forefront console
– no network adapters in the forefront console

Here is how to change the Ip Address successfully:

– Change Ip Address(es) in the Windows System
– Change Ip in TMG Console -> Firewall Policy -> Network Objects -> Computer Sets – Array Servers
– Change Ip’s in SQL Server Configuration manager -> SQL Server Network Configuration -> Protocols for MSFW/ISARS
-> TCP/IP -> IP Addresses ( only if TCP/IP is Enabled )
– Start Administrative Tools -> ADSIEDIT
Connect to:
Connection Point (type):     CN=FPC2
Computer:                         HOSTNAME:2171
Navigate to:   CN=FPC2 -> CN=Array-Root -> CN=Arrays -> CN={UUID} -> CN=Servers -> CN={UUID}
(class: msFPCServer)
Open Properties and change the   msFPCIntraArrayAddress
– wait about 20 Minutes ( replicate adsi edit changes to registry )
– Search the Registry for the old Ip Address and change it
– Reboot

NTLDR is missing (2008)

– Boot into Windows 2008 Server CD/DVD

– Choose Languages

– Choose Repair your Computer (upper left)

– Make sure “System Recovery Options” has found a Operating System

– Choose Command Prompt

– bootsec.exe /FixMbr

– bootsec.exe /FixBoot

– bootsec.exe /RebuildBcd

– Reboot and everything will go fine 🙂