Endpoint Protection

 View Only
Back to discussions
Expand all | Collapse all

Unexpected error 0x10010000

Migration User

Migration UserDec 01, 2011 04:11 PM

SQL database external
Migration User

Migration UserDec 01, 2011 05:03 PM

No special character in the User name of SQL
Chetan Savade

Chetan SavadeDec 02, 2011 05:31 AM

Hi, I hope disk space is not causing this issue.
pete

peteDec 02, 2011 05:56 AM

pass on the scm-server-0.log
Migration User

Migration UserDec 02, 2011 11:05 AM

Gets through..
Migration User

Migration UserDec 02, 2011 02:52 PM

but no errors found!
Migration User

Migration UserDec 02, 2011 03:41 PM

check config.log
Migration User

Migration UserDec 09, 2011 08:17 AM

No update?
Migration User

Migration UserDec 21, 2011 10:20 AM

Pete.. any other sugesstions?

  • 1.  Unexpected error 0x10010000

    Posted Dec 01, 2011 03:26 PM

    Unexpected error 0x10010000 Upgraded from 11.0.6 to 12.1 



  • 2.  RE: Unexpected error 0x10010000

    Posted Dec 01, 2011 03:47 PM

    What database are you using? Is the DB external? When does the error pop up?



  • 3.  RE: Unexpected error 0x10010000

    Posted Dec 01, 2011 04:11 PM

    SQL database external



  • 4.  RE: Unexpected error 0x10010000

    Posted Dec 01, 2011 04:20 PM

    Make sure you log into the SEPM using a user account that has full rights to access both the SEPM and the external SQL database.

    http://www.symantec.com/business/support/index?page=content&id=TECH164323



  • 5.  RE: Unexpected error 0x10010000

    Posted Dec 01, 2011 04:30 PM

    The login has all the rights, using Windows authentication.



  • 6.  RE: Unexpected error 0x10010000

    Posted Dec 01, 2011 04:55 PM

    Are there special characters in the name? There was an issue, and the solution was to change to SA authentication from Windows authentication.



  • 7.  RE: Unexpected error 0x10010000

    Posted Dec 01, 2011 05:03 PM

    No special character in the User name of SQL



  • 8.  RE: Unexpected error 0x10010000

    Posted Dec 01, 2011 06:37 PM

    On the Login Screen try to replace the name of server to localhost.



  • 9.  RE: Unexpected error 0x10010000

    Broadcom Employee
    Posted Dec 02, 2011 05:31 AM

    Hi,

    I hope disk space is not causing this issue.



  • 10.  RE: Unexpected error 0x10010000

    Broadcom Employee
    Posted Dec 02, 2011 05:56 AM

    pass on the scm-server-0.log



  • 11.  RE: Unexpected error 0x10010000

    Broadcom Employee
    Posted Dec 02, 2011 06:01 AM

    Log into the SEPM using a user account that has full rights to access both the SEPM and the external SQL database.

    Change the Windows Authentication to SQL authentication using the Management Server Configuration Wizard.

    Cause:The user account being used was not able to authenticate to the external SQL database.

    Try this it might help you.

    In the SEPM configuration to SQL, change to SA authentification from Windows authentication and it solved the issue.

     

    1. In SQL Server Management Studio Object Explorer, right-click the server, and then click Properties.

    2. On the Security page, under Server authentication, select the new server authentication mode, and then click OK.

    3. In the SQL Server Management Studio dialog box, click OK to acknowledge the requirement to restart SQL Server.



  • 12.  RE: Unexpected error 0x10010000

    Posted Dec 02, 2011 09:38 AM

     

    On the Login Screen try to replace the name of server to localhost.: Done That, Didn't help.

    disk space is not causing this issue.

    Already using Windows Authentication.



    • 13.  RE: Unexpected error 0x10010000

      Posted Dec 02, 2011 10:08 AM

       

      11-12-02 09:05:26.999 THREAD 1 SEVERE: ================== Server Environment ===================
      2011-12-02 09:05:26.999 THREAD 1 SEVERE: os.name = Windows 2003
      2011-12-02 09:05:26.999 THREAD 1 SEVERE: os.version = 5.2
      2011-12-02 09:05:26.999 THREAD 1 SEVERE: os.arch = x86
      2011-12-02 09:05:26.999 THREAD 1 SEVERE: java.version = 1.6.0_24
      2011-12-02 09:05:26.999 THREAD 1 SEVERE: java.vendor = Sun Microsystems Inc.
      2011-12-02 09:05:26.999 THREAD 1 SEVERE: java.vm.name = Java HotSpot(TM) Server VM
      2011-12-02 09:05:26.999 THREAD 1 SEVERE: java.vm.version = 19.1-b02
      2011-12-02 09:05:26.999 THREAD 1 SEVERE: java.home = E:\Program Files\Symantec\Symantec Endpoint Protection Manager\jre
      2011-12-02 09:05:26.999 THREAD 1 SEVERE: catalina.home = E:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat
      2011-12-02 09:05:26.999 THREAD 1 SEVERE: java.user = null
      2011-12-02 09:05:26.999 THREAD 1 SEVERE: user.language = en
      2011-12-02 09:05:26.999 THREAD 1 SEVERE: user.country = US
      2011-12-02 09:05:26.999 THREAD 1 SEVERE: scm.server.version = 12.1.671.4971
      2011-12-02 09:05:28.405 THREAD 1 SEVERE: Database Schema Version = 12.1.0.3
      2011-12-02 09:05:29.452 THREAD 1 SEVERE: License state = SEPE_TRIAL
      2011-12-02 09:05:29.452 THREAD 1 SEVERE: License status on SEPM = Good
      2011-12-02 09:05:29.452 THREAD 1 SEVERE: resetAgentOfflineState=true
      2011-12-02 09:05:29.483 THREAD 1 SEVERE: ================== StartClientTransport ===================
      2011-12-02 09:05:29.483 THREAD 1 SEVERE: [1] Initializing Tomcat ClientTransport Key for Secars...
      2011-12-02 09:05:29.499 THREAD 1 SEVERE: startClientTransport>>resetAgentToOfflineState=true
      2011-12-02 09:05:29.499 THREAD 1 SEVERE: startClientTransport>>start set agent offline
      2011-12-02 09:05:29.640 THREAD 1 SEVERE: Schedule is started!
      2011-12-02 09:05:29.671 THREAD 1 SEVERE: SEPM Service started
      2011-12-02 09:05:31.624 THREAD 25 WARNING: No status. Recompile all groups.
      2011-12-02 09:06:01.506 THREAD 39 WARNING: Error during AV record processing: no associated scan start found for scan stop event


    • 14.  RE: Unexpected error 0x10010000

      Posted Dec 02, 2011 10:09 AM

      Even after doing a fresh install, the error remains constant. Would upgrading to 12.1 help?



    • 15.  RE: Unexpected error 0x10010000

      Broadcom Employee
      Posted Dec 02, 2011 10:13 AM

      Hi,

      Please check the ODBC connection if you are able to get through it add the user which pass the ODBC connection to SQL server its the problem with Authentication nothing else.



    • 16.  RE: Unexpected error 0x10010000

      Posted Dec 02, 2011 11:05 AM

      Gets through..



    • 17.  RE: Unexpected error 0x10010000

      Posted Dec 02, 2011 02:03 PM

      This is an issue with Manifest if this machine is server 2008 ...

      http://www.symantec.com/business/support/index?page=content&id=TECH105218



    • 18.  RE: Unexpected error 0x10010000

      Posted Dec 02, 2011 02:05 PM

      This is an issue with IIS which i have experienced though sep upgrade 11.0.6 to 12.1 it still use IIS for service location hence results in this error usually can be found on groups or which crating a group or first 3 tab goes with error 403



    • 19.  RE: Unexpected error 0x10010000

      Posted Dec 02, 2011 02:52 PM

      but no errors found!



    • 20.  RE: Unexpected error 0x10010000

      Posted Dec 02, 2011 03:41 PM

      check config.log



    • 21.  RE: Unexpected error 0x10010000

      Posted Dec 05, 2011 01:08 PM

      I cannot find that file.. Plus i think i found a resolution...

      I'm now getting wireshark logs.



    • 22.  RE: Unexpected error 0x10010000

      Posted Dec 06, 2011 04:29 AM

      ArpitBadwaik

       

      Why would you recommend to change the authetication level? Windows authentication works fine and even allows to login into the SQL server.



    • 23.  RE: Unexpected error 0x10010000

      Posted Dec 09, 2011 08:17 AM

      No update?



    • 24.  RE: Unexpected error 0x10010000

      Posted Dec 09, 2011 03:25 PM

      Could you provide some solid data, like a screen shot?
      Also, search the log files and post an except that contains the error you have mentioned.

      Logs should be located in either %SEPM%\tomcat\logs, %SEPM\apache\logs or %SEPM%\data\inbox\log\exsecars.log



    • 25.  RE: Unexpected error 0x10010000

      Posted Dec 12, 2011 05:15 AM

       When we use Windows Authentication, it does not work and when we use SA authentication, it works just fine and we are able to login in SEPM without any errors... But why??



    • 26.  RE: Unexpected error 0x10010000

      Broadcom Employee
      Posted Dec 12, 2011 05:23 AM

      are these machines in the same domain?



    • 27.  RE: Unexpected error 0x10010000

      Posted Dec 12, 2011 05:34 AM

      Yes Pete, they belong to the same domain... also its a remote SQL on a Windows 2003 machine, but in the same domain.



    • 28.  RE: Unexpected error 0x10010000

      Posted Dec 21, 2011 10:20 AM

      Pete.. any other sugesstions?



    • 29.  RE: Unexpected error 0x10010000

      Posted Dec 21, 2011 01:54 PM

      I'm unclear what you are actually seeing, but if you see this error during the database upgrade wizard, you may want to check (and post) the upgrade.log file. If the is an error from SQL normally there is a line of text in the Upgrade log that says something to the effect of, "The SQL error code is X".



    • 30.  RE: Unexpected error 0x10010000

      Posted Dec 22, 2011 05:03 AM
        |   view attached

      I do not have the upgrade.log file, but do have the SQL logs.

      Attachment(s)

      txt
      SQLServerErrorLog.txt   46 KB 1 version


    • 31.  RE: Unexpected error 0x10010000

      Posted Dec 22, 2011 02:07 PM

      No Upgrade.log? Now I'm really confuse... at what point do you see this error? Would you happen to have a screen shot?

      Is it during the MSI phase, Java Configuration Wizard, Java DB Upgrade, or Console Login phase? A Screen shot should help answer that question.

      Well, I see errors in your SQLServerErrorLog.txt, but of course, I have no idea what the login for your SEP product is, but it if by chance happens to be 'COG-SYMANTEC$', have you checked articles like these ones?
      http://www.eraofdata.com/blog/sql-18456-login-failures/

      State 11 errors seem a little tricky -- but it seems to be a permissions problem with either SQL itself, or between SQL and Active Directory.



    • 32.  RE: Unexpected error 0x10010000

      Posted Dec 23, 2011 05:04 AM

      What kind of screen shot would you want? And when you say permissions what kinda permissions are missing?



    • 33.  RE: Unexpected error 0x10010000
      Best Answer

      Posted Dec 26, 2011 07:33 AM

      Works with SQL authentication, but fails with Windows.. was working fine till version 11.0

      But problems in 12.1 Would be using SQL authentication for now.. :(